hermann pitton wrote: Thanks for the ideas, Hermann. The following is with the 2.6.17-1.2174 FC5 kernel and modules installed from the ATrpms website in video4linux-kmdl-2.6.17-1.2174_FC5-20060723-76.fc5.at.i686.rpm. I'll check to see if the latest mercurial release is the same later this evening. > # modprobe -v saa7134 I get the same as you, and no errors. I'm not passing any flags to the saa7134 module atm though, as it appears to autodetect as card=71. > # modprobe -v saa7134-alsa index=1,2,3 Same again, and here's my dmesg output: saa7130/34: v4l2 driver version 0.2.14 loaded ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 185 saa7130[0]: found at 0000:00:13.0, rev: 1, irq: 185, latency: 32, mmio: 0xf0800000 saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected] saa7130[0]: board init: gpio is 843f00 input: saa7134 IR (Compro Videomate DV as /class/input/input5 saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 40: ff d0 00 c2 86 10 ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7130[0]: i2c eeprom 60: 30 26 ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: registered device video0 [v4l2] saa7130[0]: registered device vbi0 saa7134 ALSA driver for DMA sound loaded saa7130[0]/alsa: saa7130[0] at 0xf0800000 irq 185 registered as card 1 > # modprobe -v saa7134-dvb Here things are a little different: insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/dvb/frontends/tda1004x.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/dvb/frontends/nxt200x.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/dvb/dvb-core/dvb-core.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/video/video-buf-dvb.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/dvb/frontends/mt352.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/dvb/frontends/dvb-pll.ko insmod /lib/modules/2.6.17-1.2174_FC5/updates/drivers/media/video/saa7134/saa7134-dvb.ko I'm also getting the nxt200x and mt352 modules. dmesg gives: DVB: registering new adapter (saa7130[0]). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... > and after starting an dvb app like tzap -r, xine > > tda1004x: setting up plls for 48MHz sampling clock > tda1004x: found firmware revision 26 -- ok tda1004x: setting up plls for 53MHz sampling clock tda1004x: found firmware revision 26 -- ok > Check "dmesg" and it should be without errors up to this point. It certainly looks that way. > You could now test composite and svideo with say tvtime for picture and > external sound input. I'll do that shortly. scan returns 31 channels currently. This morning it was 56, last night it was 48, so it does look like there's an issue with weak signals for me. > Don't know if Axel has it in the atrpms already, but with the > get_dvb_firmware script from the mercurial master repo you can get > revision 29 from LifeView. > "yum install mercurial" > "hg clone http://linuxtv.org/hg/v4l-dvb"; > "./get_dvb_firmware tda10046lifeview" and put it in /lib/firmware. I've done this, but it just doesn't appear to be getting installed. > FC5 has all related device nodes like video0 0660, means only root > has access. The same goes for the dvb stuff, which is script generated > in /etc/udev/rules.d/50-udev.rules. One can change it there. > > # DVB > KERNEL=="dvb", MODE="0660" > SUBSYSTEM=="dvb", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter%%i/%%s $${K%%%%.*} $${K#*.}'", \ > NAME="%c", MODE="0660" That looks like what I have. So, everything looks good to me so far. The only outstanding problem appears to be getting the firmware loaded. Looking through the latest mercurial code, it appears that it's the saa7134-dvb module that's supposed to start the firmware loading off, so I guess I need to get the mercurial code built and see what happens. Thanks for your help so far, James _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
