Need driver for ATV-TUNER-F
- From: hermann pitton <hermann-pitton (at) arcor.de>
- Date: Tue, 16 May 2006 03:47:37 +0200
Am Montag, den 15.05.2006, 06:56 -0300 schrieb chalito:
>
> hermann pitton wrote:
> > Am Freitag, den 12.05.2006, 16:12 -0300 schrieb chalito:
> >> Hi ppl.
> >>
> >> I subscribed to the list because I saw a message that was never
> >> answered, and I thought I might have some info on it.
> >>
> >> I recently purchased an Advantek ATV-TUNER-F card (in Argentina)
> >> mistakenly believing it was supported... it's not :(
> >>
> >> Anyway, someone posted something about this card, and was asked for
> >> details. Here is what I could manage:
> >>
> >> $ lspci -v
> >>
> >> <snip>
> >> 05:0d.0 Multimedia video controller: Brooktree Corporation Bt878 Video
> >> Capture (rev 11)
> >> Flags: bus master, medium devsel, latency 66, IRQ 16
> >> Memory at fc500000 (32-bit, prefetchable) [size=4K]
> >> Capabilities: [44] Vital Product Data
> >> Capabilities: [4c] Power Management version 2
> >>
> >> 05:0d.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
> >> (rev 11)
> >> Flags: bus master, medium devsel, latency 66, IRQ 16
> >> Memory at fc501000 (32-bit, prefetchable) [size=4K]
> >> Capabilities: [44] Vital Product Data
> >> Capabilities: [4c] Power Management version 2
> >>
> >>
> >> $ lspci -vn
> >>
> >> <snip>
> >> 05:0d.0 0400: 109e:036e (rev 11)
> >> Flags: bus master, medium devsel, latency 66, IRQ 16
> >> Memory at fc500000 (32-bit, prefetchable) [size=4K]
> >> Capabilities: [44] Vital Product Data
> >> Capabilities: [4c] Power Management version 2
> >>
> >> 05:0d.1 0480: 109e:0878 (rev 11)
> >> Flags: bus master, medium devsel, latency 66, IRQ 16
> >> Memory at fc501000 (32-bit, prefetchable) [size=4K]
> >> Capabilities: [44] Vital Product Data
> >> Capabilities: [4c] Power Management version 2
> >>
> >>
> >>
> >> I don't have pics right now, but I'll try to post them later. However,
> >> looking at the card, I noticed that the label sticked on the metal
> >> casing (which said : NTSC/FM, as it is an FM capable model) there was
> >> another label, so I tried to take the first label off and here's what I
> >> found underneath it:
> >>
> >> MFNM05-4
> >> TCL0506159 3
> >> (I'm not completely sure about the last one, the label didn't come out
> >> cleanly).
> >>
> >> So here's 2 things I can tell about the card so far:
> >> 1) It uses a bt878 chip
> >> 2) It has a Philips NTSC MK3 (FM1236MK3, type 43) tuner.
> >>
> >> I tried various values for the card parameter in bttv.ko, and for some
> >> of them I had a signal, but very distorted and ugly. It looks as if the
> >> norm wasn't correct.
> >>
> >> Theoreticaly here in Argentina we use PAL-N, but if I set the norm to
> >> pal-n or pal-nc in tvtime I don't get signal on any channels. Only ntsc
> >> works (barely).
> >> The weird part is that booting into windows, and using the bundled soft,
> >> I configure the tv player with pal-nc and it works perfectly.
> >>
> >> anyone has any Ideas?
> >> I *definetly* need it working before the world cup begins :)
> >>
> >> thanks!
> >>
> >> Chalito
> >>
> >
> > Hi Chalito,
> >
> > is the tda9887 module loaded?
> >
> > If you experience hissing noise on audio try port2=0 for it.
> >
> > Cheers,
> > Hermann
> >
> >
> >
>
> Yes, it is loaded. I also tried adding the port2=0 option in
> /etc/modprobe.conf but It didn't change much.
>
> Here's the output output from dmesg
>
> Linux video capture interface: v1.00
> bttv: driver version 0.9.16 loaded
> bttv: using 4 buffers with 2080k (520 pages) each for capture
> bttv: Bt8xx card found (0).
> ACPI: PCI Interrupt 0000:05:0d.0[A] -> GSI 18 (level, low) -> IRQ 16
> bttv0: Bt878 (rev 17) at 0000:05:0d.0, irq: 16, latency: 66, mmio:
> 0xfc500000
> bttv0: using: 3Dfx VoodooTV FM (Euro), VoodooTV 200 (USA)
> [card=68,insmod option]
> bttv0: gpio: en=00000000, out=00000000 in=00f9807f [init]
> bttv0: Hauppauge/Voodoo msp34xx: reset line init [20]
> bttv0: using tuner=43
> bttv0: i2c: checking for MSP34xx (at) 0x80... not found
> bttv0: i2c: checking for TDA9875 (at) 0xb0... not found
> bttv0: i2c: checking for TDA7432 (at) 0x8a... not found
> bttv0: i2c: checking for TDA9887 (at) 0x86... found
> tda9887 0-0043: chip found (at) 0x86 (bt878 #0 [sw])
> tuner 0-0060: All bytes are equal. It is not a TEA5767
> tuner 0-0060: chip found (at) 0xc0 (bt878 #0 [sw])
> tuner 0-0060: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: registered device radio0
> bttv0: PLL: 28636363 => 35468950 .. ok
> bt878: AUDIO driver version 0.0.0 loaded
> bt878: Bt878 AUDIO function found (0).
> ACPI: PCI Interrupt 0000:05:0d.1[A] -> GSI 18 (level, low) -> IRQ 16
> bt878_probe: card id=[0x0],[ <NULL> ] has DVB functions.
> bt878(0): Bt878 (rev 17) at 05:0d.1, irq: 16, latency: 66, memory:
> 0xfc501000
>
> and a screenshot
>
Seems there is some bug, but I'm very limited in testing on this, even
my out of usual PCI norms tda9887 card works again on some nforce3
stuff. (PSU or onboard voltage problems on the prior KT133a maybe ... )
The reports we have for MK3 like tuners using PAL-Nc are zero I think
and even if I fake tuner=43 the current deemphasis settings seem not to
come through, something is off, maybe related to the dynamic configuring
of NTSC/PAL IF calculations.
Best start might be with some current mercurial to enable debug and see
if we can catch something obvious, like "modprobe tuner debug=1 pal=Nc"
and debug=2 for tda9887 and what you can enable for video and audio on
the bttv driver.
If somebody has a MK3 working successfully on PAL-Nc, also on other
drivers, please report. Gerd's xawtv/v4lctl setnorm PAL-Nc might be
useful too for testing.
Cheers,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list