[ATrpms-users] 1656 Kernel and ivtv problem
mrhinkle+atrpms at redvino.com
Sat Jan 21 22:40:53 CET 2006
Axel Thimm wrote:
> On Sat, Jan 21, 2006 at 10:51:47AM -0500, Mark Hinkle wrote:
>> I also had problems with the 1656 kernel and the ivtv rpms. My system was
>> running fine (a PVR 350 card with ivtv 0.4.0) until I "upgraded" to 0.4.1.
>> I spent a few nights trying various suggestions from this and the ivtv
>> lists. The best I could get with ivtv 0.4.1 and the supporting firmware
>> rpms was video on one channel with no audio. I could play previous
>> recordings and audio came through just fine.. just nothing coming in from
>> the cable. Changing channels got nothing but static.
>> Eventually I gave up on the RPMS and tried compiling 0.4.2 and installing
>> the firmware files by hand. That worked on the first try.
>> If you find yourself having similar problems you may want to try jumping
>> ship from the rpms for this release until new rpms are available.
> In fact 0.4.2 rpms are available. Could you try them?
Ok.. I tried the 0.4.2 rpms and they seem to be an improvement over the
0.4.1 rpms, at least for my system (FC4 with PVR 350). Audio works this
time and changing channels doesn't give static. A big thumbs-up there.
There are still warnings in my dmesg, though. Depending on whether I
have the *-ivtv modules aliased or not I get different warnings. I
either get the couple dozen "ivtv0 warning: i2c client addr: 0x40 not
found for command ..." warnings or the couple dozen "cx8800: Unknown
symbol ..." warnings. I didn't keep playing until I found the
combination that yielded no warnings.
I also noticed that the ivtv-firmware-enc-2.04.024-8.at rpm contains the
buggy encoder firmware. I tried overwriting the file with revision
0x02050032 but noticed no difference except the lack of the dmesg warning.
More information about the atrpms-users