[mythtv-users] Video distortion/fracturing at top quarter
marius at schrecker.org
Fri Dec 16 16:03:14 EST 2005
> Can someone confirm the firmware rev compatible with the 0.4.1 driver
> I also have a PVR-150 and the distortion on the top of the screen, and
> issue where sound fails requiring a reboot/power cycle to restore sound.
> I pulled the v0.4.1 ivtv driver from the ivtvdriver.org download section
> installed the latest firmware.
> md5sum /lib/modules/ivtv-fw-enc.bin /lib/modules/HcwMakoA.ROM
> 5f5fa240ada73c3565f5f7de4c7b5138 /lib/modules/ivtv-fw-enc.bin
> 3a4803384f749d644ee1f1ca9dcb12fa /lib/modules/HcwMakoA.ROM
> I also moved a copy of the firmware into /lib/firmware and also renamed
> as the 0.5.0 driver would expect.
> To make sure the old drivers were gone I did the following:
> mv /lib/modules/2.6.13-1.1532_FC4/ivtv /root/ivtv-atrpms
> mkdir /lib/modules/2.6.13-1.1532_FC4/ivtv
> make install
> depmod -ae
> roboot/power cycle
> On a reboot mplayer /dev/video0 works great
> Start mythbackend and mythfrontend Try to watch livetv and I get a
> 2005-12-15 08:54:21.241 Changing from None to WatchingPreRecorded
> 2005-12-15 08:54:21.619 Video timing method: SGI OpenGL
> 2005-12-15 08:54:23.401 Changing from WatchingPreRecorded to None
> 2005-12-15 08:54:23.492 Changing from None to None
> 2005-12-15 08:54:25.776 Using protocol version 15
> 2005-12-15 08:54:31.020 taking too long to be allowed to read..
> 2005-12-15 08:54:36.023 taking too long to be allowed to read..
> 2005-12-15 08:54:45.026 Waited 4 seconds for data to become available,
> 2005-12-15 08:54:49.030 Waited 4 seconds for data to become available,
> 2005-12-15 08:54:53.033 Waited 4 seconds for data to become available,
> 2005-12-15 08:54:57.037 Waited 4 seconds for data to become available,
> 2005-12-15 08:55:01.040 Waited 4 seconds for data to become available,
> 2005-12-15 08:55:05.044 Waited 4 seconds for data to become available,
> 2005-12-15 08:55:09.047 Waited 4 seconds for data to become available,
> 2005-12-15 08:55:13.051 Waited 4 seconds for data to become available,
> 2005-12-15 08:55:13.051 Waited 14 seconds for data to become available,
> Couldn't read file: rbuf://192.168.123.1:6543/video/buffers/ringbuf3.nuv
> 2005-12-15 08:55:13.103 Changing from None to WatchingLiveTV
> 2005-12-15 08:55:13.103 Decoder not alive, and trying to play..
> 2005-12-15 08:55:33.117 ReadStringList timeout (quick).
> Remote encoder not responding.
> 2005-12-15 08:55:33.137 Changing from None to None
> 2005-12-15 08:55:43.276 ReadStringList timeout (quick).
> 2005-12-15 08:55:43.276 RemoteFile::Read(): No response from control
> 2005-12-15 08:55:43.276 RemoteFile::Read() failed in
> 2005-12-15 08:55:43.284 WriteStringList: Bad socket
> 2005-12-15 08:55:43.284 ReadStringList: Bad socket
> 2005-12-15 08:55:43.284 Remote file timeout.
> At this point mplayer /dev/video0 hangs no output If I cat
>> test.mpg is a zero length file. Looks like mythfrontend locks up the
> pvr-150. It takes a power cycle to get mplayer to work with /dev/video0
> If I revert the firmware back to the older version mythfrontend no longer
> hangs but sound is garbled occasionally and it looks like livetv skips
> frames. (the video jumps). And the distortion returns on the top of the
> screen. No errors in mythfronnd or mythbackend.
> So with the 0.4.1 driver what version of firmware are you loading? Can
> provide the md5sum?
> Also according to the dmesg output 0.4.1 still pulls the firmware
> from /lib/modules not from the /lib/firmware directory as I thought it
> ivtv: ==================== START INIT IVTV ===================ivtv:
> version 0.4.0 (tagged release) loading
> ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM 4KSTACKS gcc-4.0
> ivtv: In case of problems please include the debug info
> ivtv: between the START INIT IVTV and END INIT IVTV lines when
> ivtv: mailing the ivtv-devel mailinglist.
> ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based)
> ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNK3] -> GSI 10 (level, low)
> IRQ 10
> i2c-algo-bit.o: (0) scl=1, sda=1
> i2c-algo-bit.o: (1) scl=1, sda=0
> i2c-algo-bit.o: (2) scl=1, sda=1
> i2c-algo-bit.o: (3) scl=0, sda=1
> i2c-algo-bit.o: (4) scl=1, sda=1
> i2c-algo-bit.o: ivtv i2c driver #0 passed test.
> tveeprom: ivtv version
> tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8136354
> tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> tveeprom: audio processor = CX25841 (type = 23)
> tveeprom: decoder processor = CX25841 (type = 1c)
> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
> tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 2-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes)
> ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
> wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
> ivtv0: loading /lib/modules/ivtv-fw-enc.bin
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
> tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
> ivtv0: Initialized WinTV PVR 150, card #0
> ivtv: ==================== END INIT IVTV ==================On Wednesday
> 14 December 2005 19:30, mythtv-users-request at mythtv.org wrote:
>> > Does it show when you do mplayer /dev/video0 ?
>> > I had the problem with my pvr-150mce untill I
>> > put in ivtv 0.4.1 and made double sure I got rid
>> > of all the old .ko files and ran depmod -ae so
>> > that only the newest drivers were found.
>> > Then I upgraded to the firmware recommend
>> > on the ivtvdriver.org site and the 150 is perfect now.
>> > Note there is a change in firmware nameing and
>> > location when you go to 0.4.1, but that puts you
>> > into good position for 0.5 when it becomes stable.
been following this thread and it looks like I'm having some related
issues (currently trying ivtv 0.5.1 with the recommended firmware for the
150/500 from the ivtv site). Reception is noticeably worse than in the
late 0.3x days with the firmware from the cd, and I get intermittent
flickering along the top part of the picture after some channel changes
(completely random which channels are affected). Switching between the
500's tuners usually clears this up so it's clearly a firmware/ivtv
problem. What's the recommended current recipe for ivtv and firmware on
More information about the mythtv-users