Re: Continuing Saga for FlyVideo 2000

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



>  I noticed that the saa7134 module pretty much detects the card on its own,
>  there's no insmod option to specify the card type unlike for bttv.

I hope I don't need a card= insmod option.  It is the purpose of the PCI
Subsystem IDs to allow autodetection.  Unless some TV card vendor f*cks
it up by using some ID which isn't unique it should work just fine
without a card= insmod option.

>  However, the TV input (tuner input 1) still does not have any video or
>  audio signal, although I can see some static on the xawtv screen and hear
>  the background static noise via the speakers.

Some static is good, so picking the tuner as input source works.  Now
it should be just a matter of the right tuner type to get some video
signal.  Once video is there audio hopefully works too.  But video is
the first step, audio handling depends on the TV norm detected, so audio
wouldn't work without a video signal anyway ...

>  I can try to hack the drivers but I'd need some pointers as to what to
>  look out for, and where to find the IC specs. Right now, I'm still rather
>  confused as to the relationship between saa7134, tuner, tvaudio, and some
>  of the other modules.

saa7134 + tuner should be all you need.  

>  Also, how does video inputs correlate to audio
>  inputs?

see video_mux() in saa7134-video.c.

>  As for the hard-lock I experienced previously, most instances didn't have
>  any usable oops messages. There's one I enclosed below, but I think it
>  could've been caused by almost anything at all (even a buggy kernel
>  2.4.17-0.12custom from RH Rawhide).....
>  
>  ----------------------------- from /var/log/messages -------------------------
>  Feb  8 10:41:09 tca kernel: Unable to handle kernel paging request at virtual address 5f5e1051
>  Feb  8 10:41:09 tca kernel:  printing eip:
>  Feb  8 10:41:09 tca kernel: c016cbfc
>  Feb  8 10:41:09 tca kernel: *pde = 00000000
>  Feb  8 10:41:09 tca kernel: Oops: 0002

Hmm, bad.  Its truncated.  A serial console probably is the only way to
get the complete Oops message.

  Gerd

-- 
#define	ENOCLUE 125 /* userland programmer induced race condition */





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux