[mythtv-users] Newbie Question about getting a Winfast 2000XP Expert working with MythTV

[Chris Keegan]

It kindof works for TVtime, by which I mean I get one channel of
analog tv. I haven't tried xdtv.

I believe the card is a dvb-t tuner, but I'm not even certain of that anymore.

Chris...

On 20/01/2008, jongi <jongitech at gmail.com> wrote:
>
>  Chris Keegan wrote:
>
> Hi All,
>
> This is all pretty new to me and despite having been going at this for
> a couple of weeks, I don't seem to be able to make any progress so any
> insights would be much appreciated.
>
> Here's the results (tail /var/logs/messages) of doing (rmmod cx8800,
> rmmod cx88xx, modprobe i2c_scan=1 card=5 tuner=63,
>  modprobe cx8800):
>
> kernel: [180077.710839] cx2388x v4l2 driver version 0.0.6 loaded
> kernel: [180077.711670] ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 21
> (level, low) -> IRQ 22
> kernel: [180077.711726] CORE cx88[0]: subsystem: 107d:6611, board:
> Leadtek Winfast 2000XP Expert [card=5,insmod option]
> kernel: [180077.711729] TV tuner 63 at 0x1fe, Radio tuner -1 at 0x1fe
> kernel: [180077.834190] tuner 0-0043: chip found @ 0x86 (cx88[0])
> kernel: [180077.834306] tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
> kernel: [180077.837642] tuner 0-0060: All bytes are equal. It is not a
> TEA5767
> kernel: [180077.837646] tuner 0-0060: chip found @ 0xc0 (cx88[0])
> kernel: [180077.840427] tuner 0-0060: type set to 63 (Philips
> FMD1216ME MK3 Hybrid Tuner)
> kernel: [180077.843097] tuner 0-0060: type set to 63 (Philips
> FMD1216ME MK3 Hybrid Tuner)
> kernel: [180077.937726] cx88[0]: i2c scan: found device @ 0x86
> [tda9887/cx22702]
> kernel: [180077.947619] cx88[0]: i2c scan: found device @ 0xa0 [eeprom]
> kernel: [180077.962047] cx88[0]: i2c scan: found device @ 0xc0 [tuner
> (analog)]
> kernel: [180078.026649] cx88[0]: Leadtek Winfast 2000XP Expert config:
> tuner=38, eeprom[0]=0x01
> kernel: [180078.033239] input: cx88 IR (Leadtek Winfast 2000XP as
> /class/input/input8
> kernel: [180078.033556] cx88[0]/0: found at 0000:02:05.0, rev: 5, irq:
> 22, latency: 32, mmio: 0xe2000000
> kernel: [180078.080894] cx88[0]/0: registered device video0 [v4l2]
> kernel: [180078.081381] cx88[0]/0: registered device vbi0
> kernel: [180078.081842] cx88[0]/0: registered device radio0
>
> and here's the result of dmesg | grep cx2388:
>
> [180077.710839] cx2388x v4l2 driver version 0.0.6 loaded
>
> and dmesg | grep cx8800:
>
> [ 38.458611] CORE cx88[0]: subsystem: 107d:6611, board: Leadtek
> Winfast 2000XP Expert [card=5,autodetected]
> [ 38.614539] cx88[0]: Leadtek Winfast 2000XP Expert config:
> tuner=38, eeprom[0]=0x01
> [ 38.614660] input: cx88 IR (Leadtek Winfast 2000XP as /class/input/input4
> [ 38.614706] cx88[0]/0: found at 0000:02:05.0, rev: 5, irq: 22,
> latency: 32, mmio: 0xe2000000
> [ 38.734957] tuner 0-0043: chip found @ 0x86 (cx88[0])
> [ 38.751554] tuner 0-0060: chip found @ 0xc0 (cx88[0])
> [ 38.767240] cx88[0]/0: registered device video0 [v4l2]
> [ 38.767273] cx88[0]/0: registered device vbi0
> [ 38.767306] cx88[0]/0: registered device radio0
> [180077.711726] CORE cx88[0]: subsystem: 107d:6611, board: Leadtek
> Winfast 2000XP Expert [card=5,insmod option]
> [180077.834190] tuner 0-0043: chip found @ 0x86 (cx88[0])
> [180077.837646] tuner 0-0060: chip found @ 0xc0 (cx88[0])
> [180077.937726] cx88[0]: i2c scan: found device @ 0x86 [tda9887/cx22702]
> [180077.947619] cx88[0]: i2c scan: found device @ 0xa0 [eeprom]
> [180077.962047] cx88[0]: i2c scan: found device @ 0xc0 [tuner (analog)]
> [180078.026649] cx88[0]: Leadtek Winfast 2000XP Expert config:
> tuner=38, eeprom[0]=0x01
> [180078.033239] input: cx88 IR (Leadtek Winfast 2000XP as
> /class/input/input8
> [180078.033556] cx88[0]/0: found at 0000:02:05.0, rev: 5, irq: 22,
> latency: 32, mmio: 0xe2000000
> [180078.080894] cx88[0]/0: registered device video0 [v4l2]
> [180078.081381] cx88[0]/0: registered device vbi0
> [180078.081842] cx88[0]/0: registered device radio0
>
> >From all of which I think I can surmise that the driver is loading and
> detecting the card correctly (but I have really no idea, it just looks
> plausible).
>
> But when I load MythTV nothing that I do when adding a capture capture
> card yields any results and there are no errors in the mythtv back end
> logs.
>
> I don't think I've seen any recent posts anywhere where someone has
> successfully got this card to work with MythTV so any response or help
> would be great. I know I should probably give up and buy an easier
> card to work with but there's a principal at stake!
>
> Thanks again all and apologies in advance for my ignorance!
>
> Chris...
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>  Does your card work with other TV apps such as xdtv?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>