Es schrieb Matthew Tidy: > > hermann pitton wrote: > > > Es schrieb suriya mohan: > > > > > >> Hi, > >> Check whether some other process uses /dev/video0 by using > >> the > >> following command in the shell prompt. > >> > >> fuser /dev/video0. > >> > >> Kill that process. Then verify from "dmesg" command whether u > >> have > >> loaded the upgraded driver. Default loading using modprobe or > >> insmod > >> will load only the old driver module. Rename the old driver module > >> and > >> use depmod to load new driver module. > >> > > > > Gerds advise to use at least 2.4.22 to follow the changes was > > serious! > > Thanks for your responses Hermann Pitton and suriya mohan > > Below is the output i get from dmesg(only for the card). It seems to > find the card. But are you saying that i should be using a more > advanced kernel like 2.5.x or 2.6.x to get the card working? > No, but ... (2.5 is dead) > i2c-core.o: i2c core module > Linux video capture interface: v1.00 > i2c-core.o: driver i2c TV tuner driver registered. > i2c-core.o: driver i2c tda9887 driver registered. > saa7130/34: v4l2 driver version 0.2.4 loaded > PCI: Found IRQ 12 for device 00:11.0 > PCI: Sharing IRQ 12 with 00:0b.0 > saa7134[0]: found at 00:11.0, rev: 1, irq: 12, latency: 64, mmio: > 0xcfffd800 > saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000 > [card=2,insmod option] > tuner: probing saa7134[0] i2c adapter [id=0x90000] > tuner: chip found @ 0xc2 > i2c-core.o: client [(tuner unset)] registered to adapter > [saa7134[0]](pos. 0). > tda9887: probing saa7134[0] i2c adapter [id=0x90000] > i2c-core.o: adapter saa7134[0] registered as adapter 0. > saa7134[0]: Huh, no eeprom present (err=-5)? > saa7134[0]: registered device video31 [v4l2] > saa7134[0]: registered device vbi31 > saa7134[0]: registered device radio31 > saa7134[0]/audio: oops: audio carrier scan failed > > I still cannot get the card working. The fuser command return nothing > even when i am running a root user. I have also downloaded the > earlier versions of the saa7134 device driver (0.2.4) and tried them, > after trying the 0.2.8 and 0.2.7 drivers. It does not seem to make > any difference. Does anybody know what the problem with my setup is? Main problem are your device nodes. That is why you get the xawtv error. Afaik, newest versions of the driver support up to 18 devices, older nine, but none 32 yet. Fuser returns nothing, because maybe there is nothing? On RH all is installed with the dev.rpm and must allways be there. Make sure you have at least /dev/video0 vbi0 radio0 and also /dev/dsp0. The old style /dev/video /dev/dsp and so on should be symbolic links to the new style 'numbered devices', means video0, dsp0 ... Not to have it that way causes trouble with some apps seen on RH. Also there are drivers creating their own directory named video in /dev and that can cause trouble too. Use saa7134-0.2.8 here! New snapshots of the driver do not work with that "old" kernel. 2.4.22x is suggested to follow the devel, or better 2.6.0-latest. The driver usually should not load the tda9887 with card=2 (loads tuner=5, PHILIPS_PAL_BG, FI1216 and compatibles), but it shouldn't do any harm and might be historic on 0.2.4. If you have the standard FV3K Ok. Otherwise look at saa7134-cards.c and add-new-cards.txt ... but there is autodetection in progress, if a eeprom is found and the tuner identified. Greetings Hermann --
