Hi all,

In an effort to squash the last remaining "Wife Glee Hinderance" issues (truncated recordings, occasional unwanted pauses when watching TV or recordings), I decided last night to upgrade ivtv from 0.4.0 to 0.4.1 just in case improvements were made.

Things have not gone well, and my system cannot seem to find the firmware files in the hotplug folders - here is a snippet of my syslog:

Jan 12 06:54:38 mythtv kernel: ivtv0: unable to open firmware v4l-cx2341x-enc.fw
Jan 12 06:54:38 mythtv kernel: ivtv0: did you put the firmware in the hotplug firmware directory?
Jan 12 06:54:38 mythtv kernel: ivtv0 warning: failed loading encoder firmware
Jan 12 06:54:38 mythtv kernel: ivtv0 warning: Error loading firmware -3!
Jan 12 06:54:38 mythtv kernel: ivtv0: Error -3 initializing firmware.
Jan 12 06:54:38 mythtv kernel: ivtv0: Error -12 on initialization
Jan 12 06:54:38 mythtv kernel: ivtv: probe of 0000:02:0b.0 failed with error -12


I've verified spelling after a kind soul on the ivtv list caught my typo (v41 instead of v4l), but still no dice. The firmware files live in /lib/firmware, which is the first 'FIRMWARE_DIR' listed in /etc/hotplug/firmware.agent.

Has anyone here encountered such a snafu with upgrading ivtv? I don't know enough about the rest of Knoppmyth to know if there's anything else I need to do regarding hotplug files or whatnot, so I am widening the cast of my net, so to speak. My system is down for the time being, and Battlestar is on tomorrow night.

I tried rolling back to 0.4.0 last night, and that's proving to be its own special train wreck. My next option if I can't get this fixed is to reinstall or install R5A30 which in and of itself isn't a bad idea, but I wanted to wait until the box and I had more "alone time" to do that.

Many thanks for any insight offered,
Steve

_________________
-Steve

The firmware should go in /usr/lib/hotplug/firmware

Check this site out for more detail
http://ivtvdriver.org/index.php/Firmware

I tried that folder as well, to no avail. Finally resolved the problem, it turns out that I had corrupted one or more of the firmware files by downloading them from my PC onto a samba shared folder.

Grabbing them from an ssh session using wget gave me firmware files that were loadable, and the machine is back in business.

Thanks,
Steve