[mythtv-users] Ivtv 0.4.2 and bttv conflict on FC3

[Joseph A. Caputo]

On Tuesday 31 January 2006 19:25, Brian Fischer wrote:
> I just tried your modprobe and still the same results.  If I rmmod
> both tuners and try to insert the bttv module first I get:
>
> [root at mythtv mythtv]# /sbin/modprobe bttv
> FATAL: Error inserting bttv
> (/lib/modules/2.6.12-1.1381_FC3/updates/drivers/media/video/bttv.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> [root at mythtv mythtv]# dmesg | grep bttv
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bt878: Unknown symbol bttv_read_gpio
> bt878: Unknown symbol bttv_write_gpio
> bt878: Unknown symbol bttv_gpio_enable
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
>
> I think that this is probably causing some confusion with the ivtv
> driver. Any other hints?

What does "rpm -q bttv-kmdl-2.6.12-1.1381_FC3" tell you?

Also, have you tried cold booting?  I don't know what you're updating 
from, but it's sometimes necessary with an ivtv upgrade to power off 
for a few minutes to let the registers on the card clear.  Though, I 
wouldn't think that would be the cause of the bttv conflicts.

-JAC