[mythtv-users] Loading device at boot time

[Michael T. Dean]

On 03/03/2006 07:33 PM, Kevin Kuphal wrote:
> Michael T. Dean wrote:
>> Post again if you're using 2.6.10 or higher... :)
> I'm using 2.6.15

Heh.  It looks like that should work.  Gerd Knorr put some serious 
research into how to ensure the saa7134 will load saa7134-dvb when 
required (and only when required) back at the end of 2004.  However, I 
didn't see /anything/ at all that confirmed it actually worked once he 
wrote it...  You could probably make him very happy if you figure out 
why it's failing and fix it for him.  ;)

Anyway, since it doesn't seem to work, you have a couple of options:

    a) Do what you said you didn't want to do to work around the broken 
module:  modify your modprobe.conf to load saa7134-dvb after saa7134 
with something like
install saa7134 /sbin/modprobe --ignore-install saa7134; \
                /sbin/modprobe saa7134-dvb

    b) Install the CVS version of v4l-dvb ( http://linuxtv.org/cvs.php 
and http://linuxtv.org/v4lwiki/index.php/How_to_build_from_CVS ) and 
hope it works.  Since the V4L CVS is often more reliable than the kernel 
source's V4L code, this may work.  However, not having used the card, I 
can't say whether it's worth the effort (but I can say that the saa7134 
CVS doesn't appear to be much different from that in 2.6.15).

So, unfortunately, it seems that the "proper" way to fix it that you 
were seeking isn't an option (the proper way is for the saa7134 module 
to load it for you).  As far as "fixing" udev/hotplug to load it 
automatically, we have a bit of a problem in that the PCI ID is already 
correctly mapped to the saa7134 driver.  If you tried changing the 
mapping to load the saa7134-dvb module (which is more trouble than it's 
worth), instead of saa7134, it may cause both to load, but it's actually 
less "proper" than the modprobe.conf line above (which was designed to 
be changed by the end user--as opposed to the mappings, which should be 
the same on every system, everywhere).

Oh, BTW, you mentioned modifying your modprobe.conf earlier in the 
thread (I looked it--and your "AverTVHD A180 Success" post--up to find 
your card type--and noticed you had already specified your kernel 
version, too :-[ ).  It should specify:

alias char-major-81 videodev
alias char-major-81-0 saa7134

(or whatever the appropriate minor device number is for that card) as 
that's the driver for your card, but saa7134 uses the saa7134-dvb module 
to modify how the saa7134 module works.  It would probably work OK even 
if you put "saa7134-dvb" in there (and the modprobe.conf install line 
above), but it looks like you're going for a correct setup (instead of 
taking the short cuts I hate to see people taking :).

HTH.

Mike