Do you use any options to any of the modules in modprobe.conf? You
shouldn't need to. Make absolutely sure you're not getting any
modules from
the kernel. Weird problems are often caused by that.
dragonfly ~ # cat /etc/modules.autoload.d/kernel-2.6
# /etc/modules.autoload.d/kernel-2.6: kernel modules to load when
system boots.
<SNIP>
sbp2
intel_agp
agpgart
drm
i915
ivtv
I meant checking each module from the ivtv driver set with : /sbin/
modinfo and verifying that it comes back with the ivtv version
instead of the kernel version. For example :
[EMAIL PROTECTED] ivtv]# /sbin/modinfo msp3400
filename: /lib/modules/2.6.12-1.1447_FC4/ivtv/msp3400.ko
Is using the ivtv version of msp3400. While :
[EMAIL PROTECTED] ivtv]# /sbin/modinfo tveeprom
filename: /lib/modules/2.6.12-1.1447_FC4/kernel/drivers/media/
video/tveeprom.ko
Is using the tveeprom module from the kernel (I don't recommend this
- I only have it to make my HD-3000 happy). You should check every
module compiled by ivtv (don't run modinfo from inside a directory
that contains the modules, or it will give you the info on those
instead of what is loaded).
I'm using both a 150 and a 250. Is your setup similar?
Not anymore. My 250 overheated and now I just have a PVR500 and
HD-3000.
Keith C
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
