Hi Folks.
        I *had* a working system when I was running 2.6.17-1.2157_FC5 kernel
and the then current versions from ATRPMs.  MythTV was running great.
        *THEN* I had some disk problems, and by the time I recovered, yum had
updated me to kernel 2.6.17-1.2187_FC5.  So I disabled the loading of
ivtv on bootup (it wasn't loading right).
        Last night, yum updated ivtv to 0.7.1, and mythtv as well, so I tried
again, and I've copied the /var/log/messages text below.  The system
hung, hard, when I tried the modprobe.  After recovering by hitting the
reset button, here's what I found in the logs:

# modprobe ivtv

> Sep 28 00:36:15 kjc386 yum: Updated: ivtv.i386 1:0.7.1-118.fc5.at
> Sep 28 00:36:18 kjc386 yum: Updated: ivtv-kmdl-2.6.17-1.2187_FC5.i686 
> 1:0.7.1-118.fc5.at
> Sep 28 00:37:02 kjc386 ntpd[2320]: synchronized to 146.115.9.13, stratum 3
> Sep 28 00:37:05 kjc386 kernel: v4l2_common: no version for "struct_module" 
> found: kernel tainted.
> Sep 28 00:37:05 kjc386 kernel: Linux video capture interface: v2.00
> Sep 28 00:37:05 kjc386 kernel: ivtv:  ==================== START INIT IVTV 
> ====================
> Sep 28 00:37:05 kjc386 kernel: ivtv:  version 0.7.1 (tagged release) loading
> Sep 28 00:37:05 kjc386 kernel: ivtv:  Linux version: 2.6.17-1.2187_FC5 
> mod_unload 686 REGPARM 4KSTACKS gcc-4.1
> Sep 28 00:37:05 kjc386 kernel: ivtv:  In case of problems please include the 
> debug info between
> Sep 28 00:37:05 kjc386 kernel: ivtv:  the START INIT IVTV and END INIT IVTV 
> lines, along with
> Sep 28 00:37:05 kjc386 kernel: ivtv:  any module options, when mailing the 
> ivtv-users mailinglist.
> Sep 28 00:37:05 kjc386 kernel: ivtv0: Autodetected Hauppauge WinTV PVR-350 
> card (cx23415 based)
> Sep 28 00:37:05 kjc386 kernel: ivtv0: Unreasonably low latency timer, setting 
> to 64 (was 32)
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: Hauppauge model 48132, rev 
> K268, serial# 7875777
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: tuner model is LG TAPE H001F 
> MK3 (idx 68, type 47)
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: TV standards NTSC(M) (eeprom 
> 0x08)
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: audio processor is MSP4448 
> (idx 27)
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: decoder processor is SAA7115 
> (idx 19)
> Sep 28 00:37:05 kjc386 kernel: tveeprom 5-0050: has radio, has IR remote
> Sep 28 00:37:05 kjc386 kernel: tuner 5-0043: chip found @ 0x86 (ivtv i2c 
> driver #0)
> Sep 28 00:37:05 kjc386 kernel: tda9887 5-0043: tda988[5/6/7] found @ 0x43 
> (tuner)
> Sep 28 00:37:05 kjc386 kernel: tuner 5-0061: chip found @ 0xc2 (ivtv i2c 
> driver #0)
> Sep 28 00:37:05 kjc386 kernel: saa7115 5-0021: saa7115 found @ 0x42 (ivtv i2c 
> driver #0)
> Sep 28 00:37:05 kjc386 kernel: saa7127 5-0044: saa7129 found @ 0x88 (ivtv i2c 
> driver #0)
> Sep 28 00:37:05 kjc386 kernel: msp3400 5-0040: MSP4448G-A2 found @ 0x80 (ivtv 
> i2c driver #0)
> Sep 28 00:37:05 kjc386 kernel: msp3400 5-0040: MSP4448G-A2 supports radio, 
> mode is autodetect and autoselect
> Sep 28 00:37:06 kjc386 kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware 
> (262144 bytes)
> Sep 28 00:37:06 kjc386 kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware 
> (262144 bytes)
> Sep 28 00:37:06 kjc386 firmware_helper[27467]: Loading of 
> /lib/firmware/v4l-cx2341x-dec.fw for ivtv driver failed: No such file or 
> directory

The next thing in my logs is the syslog restart from the reboot (which
only worked because ivtv is blacklisted).

Any idea whats going on?

Oh yeah:

> # ls -l /lib/firmware
> total 668
> -rw-r--r-- 1 root root 262144 May 29 16:31 v4l-cx2341x-dec.fw
> -rw-r--r-- 1 root root 376836 Jan 17  2005 v4l-cx2341x-enc.fw
> lrwxrwxrwx 1 root root     33 Sep 28 00:36 v4l-cx2341x-init.mpg -> 
> /lib/modules/v4l-cx2341x-init.mpg
> -rw-r--r-- 1 root root  16382 Feb  9  2006 v4l-cx25840.fw

-- 
Kevin J. Cummings
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Registered Linux User #1232 (http://counter.li.org)

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to