Sander Sweers wrote: > Julian Edwards wrote: > >> Hi folks >> >> I use ATrpms for my ivtv binaries for my PVR250. I just upgraded my FC5 >> box from 2.6.17 and ivtv 0.7.1 to 2.6.18-1.2257.fc5 with >> ivtv-kmdl-2.6.18-1.2257.fc5-0.8.2-123.fc5.at. >> >> On boot, ivtv bails out with these errors: >> Feb 9 16:59:56 mythbox kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware >> (262144 bytes) >> [snip.....] >> Feb 9 16:59:56 mythbox kernel: ivtv0 warning: 1000 ms time out waiting >> for firmware >> Feb 9 16:59:56 mythbox kernel: ivtv0 warning: Failed api call 0x00000080 >> with result 0xfffffff0 >> Feb 9 16:59:56 mythbox kernel: ivtv0 warning: Encoder firmware dead! >> Feb 9 16:59:56 mythbox kernel: ivtv0: Error initializing firmware >> Feb 9 16:59:56 mythbox kernel: ivtv0: Error -19 on initialization >> >> If I modprobe -r ivtv then modprobe ivtv again it has a different error: >> Feb 9 17:02:18 mythbox kernel: firmware_loading_store: unexpected value (0) >> Feb 9 17:02:18 mythbox kernel: ivtv0: unable to open firmware >> v4l-cx2341x-enc.fw (must be 262144 bytes) >> Feb 9 17:02:18 mythbox kernel: ivtv0: did you put the firmware in the >> hotplug firmware directory? >> Feb 9 17:02:18 mythbox kernel: ivtv0 warning: failed loading encoder >> firmware >> Feb 9 17:02:18 mythbox kernel: ivtv0 warning: Error loading firmware -3! >> Feb 9 17:02:18 mythbox kernel: ivtv0: Error -3 initializing firmware. >> >> If I remove it and modprobe again, it works! This sequence is 100% >> repeatable. >> (full message output shown below) >> > > Can you try and remove the old firmware and download the "recommended" > firmware from [1]? If that does not work it looks similar to the problem > people had with udev. See [2] for the 2 udev hang fixes. > > Greets > Sander > > [1]http://dl.ivtvdriver.org/ivtv/firmware/firmware.tar.gz > [2] > http://ivtvdriver.org/index.php/Troubleshooting#Lock_up_when_loading_ivtv_module_.28udev_related.29 >
Hi Sander Unfortunately this has reared its ugly head again, using the "new" firmware. I say "new" because I think the firmware that was being used beforehand was the same as the firmware at [1] except it had the padding at the end. Diffing the first 262144 bytes was certainly the same. I also don't think its [2] because I don't have the hotplug agent. The firmware *is* loaded on the initial attempt at boot, it's just that it seems to time out on an API call. I don't think it's faulty hardware either. As I said, 0.7.1 worked perfectly. Is there anything else I can do to debug or track down this problem? Cheers Julian _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
