Okay, so I've seen postings all over the internet about the infamous
Quote:
|
ivtv0: unable to open firmware v4l-cx2341x-enc.fw
|
error messages that seem to keep popping up in IVTV installations, and over the past month I've followed each and every one of these and come up with nothing. Here's my data
kernel version: 2.6.17.6
ivtv version : 0.7
dmesg | grep ivtv :
Quote:
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.7.0 (tagged release) loading
ivtv: Linux version: 2.6.17.6 mod_unload K7 gcc-4.0
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
cx25840 4-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #0)
tuner 4-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 4-0043: chip found @ 0x86 (ivtv i2c driver #0)
ivtv0: This is the first unit of a PVR500
ivtv0: unable to open firmware v4l-cx2341x-enc.fw
ivtv0: did you put the firmware in the hotplug firmware directory?
ivtv0 warning: failed loading encoder firmware
ivtv0 warning: Error loading firmware -3!
ivtv0: Error -3 initializing firmware.
ivtv0: Error -12 on initialization
ivtv: probe of 0000:02:08.0 failed with error -12
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
cx25840 4-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #0)
tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 4-0043: chip found @ 0x86 (ivtv i2c driver #0)
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
ivtv0: unable to open firmware v4l-cx2341x-enc.fw
ivtv0: did you put the firmware in the hotplug firmware directory?
ivtv0 warning: failed loading encoder firmware
ivtv0 warning: Error loading firmware -3!
ivtv0: Error -3 initializing firmware.
ivtv0: Error -12 on initialization
ivtv: probe of 0000:02:09.0 failed with error -12
ivtv: ==================== END INIT IVTV ====================
|
/lib/udev/hotplug.functions contains the following line:
FIRMWARE_DIRS='/lib/firmware /usr/local/lib/firmware /usr/lib/hotplug/firmware'
/lib/udev/firmware.agent loads
/lib/udev/hotplug.functions
When udev's logging is set to "debug", running `modprobe ivtv` dumps the following data into /var/log/syslog (the output is actually about 230 lines, but I've shorted it quite a bit):
Code:
Aug 21 23:12:44 localhost udevd[31121]: udev_event_run: seq 1638 forked, pid [884], 'add' 'module', 0 seconds old
Aug 21 23:12:44 localhost udevd[31121]: udev_event_run: seq 1639 forked, pid [885], 'add' 'drivers', 0 seconds old
Aug 21 23:12:44 localhost udevd[31121]: udev_event_run: seq 1640 forked, pid [886], 'add' 'i2c-adapter', 0 seconds old
Aug 21 23:12:44 localhost udevd[31121]: udev_event_run: seq 1641 forked, pid [887], 'add' 'firmware', 0 seconds old
Aug 21 23:12:44 localhost udevd-event[884]: pass_env_to_socket: passed 103 bytes to socket '/org/freedesktop/hal/udev_event',
Aug 21 23:12:44 localhost udevd-event[884]: run_program: '/lib/udev/udev_run_hotplugd'
Aug 21 23:12:44 localhost udevd-event[884]: run_program: '/lib/udev/udev_run_hotplugd' returned with status 0
Aug 21 23:12:44 localhost udevd-event[884]: udev_event_run: seq 1638 finished
Aug 21 23:12:44 localhost udevd[31121]: udev_done: seq 1638, pid [884] exit with 0, 0 seconds old
Aug 21 23:12:44 localhost udevd-event[885]: pass_env_to_socket: passed 122 bytes to socket '/org/freedesktop/hal/udev_event',
Aug 21 23:12:44 localhost udevd-event[885]: run_program: '/lib/udev/udev_run_hotplugd'
Aug 21 23:12:44 localhost udevd-event[885]: run_program: '/lib/udev/udev_run_hotplugd' returned with status 0
Aug 21 23:12:44 localhost udevd-event[885]: udev_event_run: seq 1639 finished
Aug 21 23:12:44 localhost udevd[31121]: udev_done: seq 1639, pid [885] exit with 0, 0 seconds old
Aug 21 23:12:44 localhost udevd-event[886]: pass_env_to_socket: passed 194 bytes to socket '/org/freedesktop/hal/udev_event',
Aug 21 23:12:44 localhost udevd-event[886]: run_program: '/lib/udev/udev_run_hotplugd'
Aug 21 23:12:44 localhost udevd-event[886]: run_program: '/lib/udev/udev_run_hotplugd' returned with status 0
Aug 21 23:12:44 localhost udevd-event[886]: udev_event_run: seq 1640 finished
Aug 21 23:12:44 localhost udevd[31121]: udev_done: seq 1640, pid [886] exit with 0, 0 seconds old
Aug 21 23:12:44 localhost udevd-event[887]: pass_env_to_socket: passed 220 bytes to socket '/org/freedesktop/hal/udev_event',
Aug 21 23:12:44 localhost udevd-event[887]: run_program: '/lib/udev/udev_run_hotplugd'
Aug 21 23:12:44 localhost udevd-event[887]: run_program: '/lib/udev/udev_run_hotplugd' returned with status 0
Aug 21 23:12:44 localhost udevd-event[887]: udev_event_run: seq 1641 finished
Aug 21 23:12:44 localhost udevd[31121]: udev_done: seq 1641, pid [887] exit with 0, 0 seconds old
Aug 21 23:12:54 localhost udevd[31121]: udev_event_run: seq 1642 forked, pid [894], 'remove' 'firmware', 0 seconds old
Aug 21 23:12:54 localhost udevd[31121]: udev_event_run: seq 1643 forked, pid [895], 'add' 'i2c', 0 seconds old
Aug 21 23:12:54 localhost udevd[31121]: udev_event_run: seq 1644 forked, pid [896], 'add' 'i2c', 0 seconds old
Aug 21 23:12:54 localhost udevd[31121]: udev_event_run: seq 1645 forked, pid [897], 'add' 'i2c', 0 seconds old
Aug 21 23:12:54 localhost udevd[31121]: udev_event_run: seq 1646 forked, pid [898], 'add' 'i2c', 0 seconds old
The file
/proc/sys/kernel/hotplug is empty and any attempts to put anything in there lead to permission denied errors (even as root)
I have copied the firmware files into /lib/firmware, /usr/local/lib/firmware, and /usr/lib/hotplug/firmware and given them all 777 permissions (more out of frustration than actually thinking it would help).
As best as I can tell, /lib/udev/firmware.agent is never getting read by anything and I can't figure out why. I tried to give as much information as the LQ forum would allow, but I'm sure I left out 2 or 3 pieces of key information. I've been struggling with this on and off for over a month now and have made no progress, so I'm really at my wits end right now. After living with MythTV for the past 3 years or so, not having it is like torture!
Any suggestions/ideas/tips would be GREATLY appreciated!!
