[mythtv-users] Yum upgrade to 2.6.15-1.1831_FC4 broken bttv

[kanetse@gmail.com]

On 2/15/06, kanetse at gmail.com <kane.tse at gmail.com> wrote:
> I recently upgraded to kernel 2.6.15-1.1831_FC4 using smart, thanks to
> Axel's advice.  However, after rebooting my machine into the new
> kernel, my (bt8x8) tuners are no longer working.
>
> # dmesg
> bttv: Unknown symbol i2c_bit_add_bus
> bttv: Unknown symbol i2c_master_recv
> bttv: Unknown symbol i2c_del_adapter
> bttv: Unknown symbol tveeprom_read
> bttv: Unknown symbol i2c_bit_del_bus
> bttv: Unknown symbol i2c_clients_command
> bttv: Unknown symbol i2c_add_adapter
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol i2c_master_send
>
> # modprobe bttv
> WARNING: Error inserting i2c_core
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/i2c/i2c-core.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting tveeprom
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/media/video/tveeprom.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting i2c_algo_bit
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/i2c/algos/i2c-algo-bit.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting i2c_core
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/i2c/i2c-core.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting tveeprom
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/media/video/tveeprom.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting i2c_algo_bit
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/i2c/algos/i2c-algo-bit.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting bttv
> (/lib/modules/2.6.15-1.1831_FC4/kernel/drivers/media/video/bttv.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error running install command for bttv
>
> I was previously running kernel 2.6.11-1.1369_FC4.. and everything worked fine.
>

Turns out the error was that the i2c_core module was not loading
because I was specifying the i2c_debug=1 flag in my /etc/modprobe.conf
file.  This flag is now obsolete.

Hope that helps anyone searching throgh the list.