[mythtvnz] kernel/ivtv upgrade problems

Wed, 17 Jan 2007 18:56:25 +1300

Mike

mmm yes tearing it was something that almost made me ditch MythTV, finally got 
it sorted though.

Have never tried "mplayer /dev/video0" would be interesting to see if there's 
any difference.

Tim

On Wednesday 17 January 2007 18:18, Mike Dilger wrote:
> Ok I'm further.  I got video.  I just reselected and rebuilt the
> kernel/modules.  Dunno why that worked.
> "mplayer /dev/video0" looks great, and my channel changer script
> (modified to use v4l2-ctl instead of ivtvctl, and using MHz freqs
> instead of 16*MHz) works fine again.
>
> But once I start mythtv, the video changes.  It doesn't sync, and there
> is substantial video tearing.
>
> If I shut mythtv down and go back to "mplayer /dev/video0", the
> framesync video-tearing problem persists, so I'm pretty sure mythbackend
> is setting an ivtv module setting that it shouldn't be setting.
>
> Ideas?
>
> Mike
>
> Mike Dilger wrote:
> > I've just upgraded from kernel gentoo-sources 2.6.16-r4 to
> > gentoo-sources 2.6.19-r4
> > This required an upgrade from ivtv-0.6.4 to ivtv-0.9.1
> > I also brought mythtv up to the latest patchlevel release 0.20_p12376
> > (from 12325).
> >
> > After rebuilding modules and generally getting everything else to
> > work, I'm stuck on ivtv.
> >
> > "mplayer /dev/video0" hangs.  When I break out, it says it was
> > interrupted in module demux_open.
> > I have ensured that mythbackend is NOT starting, so there shouldn't be
> > any contention for the device.
> > Also I know that the permissions on the device allow me to open/read
> > it.  Plus, it used to work just fine.
> > I have cold-booted, and I get the same result.
> >
> > Some things to notice in dmesg:
> >
> > 1) ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > I think this is harmless.
> >
> > 2) i2c_adapter i2c-2: Client creation failed at 0x44 (-1)
> > This is concerning...
> >
> > 3) tveeprom 2-0050: The eeprom says no radio is present, but the tuner
> > type
> >    tveeprom 2-0050: indicates otherwise. I will assume that radio is
> > present.
> > I definately have no radio.  But this doesn't concern me.
> >
> > Any ideas?
> >
> > Mike
> >
> >
> > ivtv:  ==================== START INIT IVTV ====================
> > ivtv:  version 0.9.1 (tagged release) loading
> > ivtv:  Linux version: 2.6.19-gentoo-r4cinema-splash preempt mod_unload K8
> > 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 card (cx23416 based)
> > ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
> > PCI: setting IRQ 11 as level-triggered
> > ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNK3] -> GSI 11 (level,
> > low) -> IRQ
> > 11
> > ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > nvidia: module license 'NVIDIA' taints kernel.
> > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> > i2c_adapter i2c-2: Client creation failed at 0x44 (-1)
> > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
> > tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > cx25840 2-0044: cx25842-23 found @ 0x88 (ivtv i2c driver #0)
> > cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> > tveeprom 2-0050: The eeprom says no radio is present, but the tuner type
> > tveeprom 2-0050: indicates otherwise. I will assume that radio is
> > present.
> > tveeprom 2-0050: Hauppauge model 26139, rev G1A5, serial# 9533933
> > tveeprom 2-0050: tuner model is TCL MPE05-2 (idx 105, type 38)
> > tveeprom 2-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
> > (eeprom 0x
> > 74)
> > tveeprom 2-0050: audio processor is CX25842 (idx 36)
> > tveeprom 2-0050: decoder processor is CX25842 (idx 29)
> > tveeprom 2-0050: has radio, has IR remote
> > ivtv0: Autodetected Hauppauge WinTV PVR-150
> > ivtv0: reopen i2c bus for IR-blaster support
> > i2c_adapter i2c-2: Client creation failed at 0x44 (-1)
> > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
> > tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > cx25840 2-0044: cx25842-23 found @ 0x88 (ivtv i2c driver #0)
> > cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> > ivtv0: Encoder revision: 0x02050032
> > ivtv0: Registered device video0 for encoder MPEG
> > ivtv0: Registered device video32 for encoder YUV
> > ivtv0: Registered device vbi0 for encoder VBI
> > ivtv0: Registered device video24 for encoder PCM audio
> > ivtv0: Registered device radio0 for encoder radio
> > tuner 2-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
> > ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> > ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 3
> > ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNK1] -> GSI 3 (level,
> > low) -> IRQ
> > 3
> > NVRM: loading NVIDIA UNIX x86 Kernel Module  1.0-9746  Fri Dec 15
> > 09:54:45 PST 2
> > 006
> > ivtv:  ====================  END INIT IVTV  ====================
> >
> >
> > _______________________________________________
> > mythtvnz mailing list
> > mythtvnz@lists.linuxnut.co.nz
> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.linuxnut.co.nz
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

-- 
Regards
Tim, Donna & Erin Gibson
ICQ - 2207616