James Fidell wrote: > Unfortunately running "modprobe saa7134-dvb" appears to achieve > absolutely nothing at all. The module loads, but gives no dmesg output > and no /dev/dvb devices are created. Any ideas? This would usually happen if the driver doesnt think your card has DVB functionality, although that sounds unlikely in your case. Maybe you'd have better results with the sources in linuxtv.org mercurial, unless Hartmut has any better idea... BTW, linuxtv.org's mercurial drivers will NOT build correctly against the FC5 kernel, due to the fact that FC5 is currently using a 2.6.18 kernel which identifies itself as 2.6.17. OTOH, if you're using the atrpms package repository, you can upgrade your v4l-dvb modules by doing: yum install video4linux-kmdl-`uname -r` > I'm running FC5 fully patched with kernel 2.6.17.11, if that matters. Yup. > (The same thing happens when I load cx88-dvb for my other two cards. Or > doesn't, rather. And if I use MAKEDEV to create the /dev/dvb structure > manually, then running "scan" reports "no such device". It's like the > low-level drivers can see the hardware, but somewhere something is > failing to tie everything together inside the kernel.) umm... what makes you think the drivers can see the hardware? You are using cx88-blackbird devices -- these do not have DVB functionality. You should see cx88-dvb announce the fact that it has loaded itself, but it will not do anything with those cards. > > James -- Michael Krufky _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
