* How to make a Zaapa LR301AP DVB-T card work
@ 2009-12-19 14:00 Antonio Marcos López Alonso
2009-12-19 19:53 ` hermann pitton
0 siblings, 1 reply; 6+ messages in thread
From: Antonio Marcos López Alonso @ 2009-12-19 14:00 UTC (permalink / raw)
To: linux-media
Hi all,
I borrowed a Zaapa LR301AP DVB-T card from a friend to try to make it work in
Linux, so I kindly request your help. The card features one antenna input, one
IR input (remote and sensor wire being lost) and one AV input. Here follows
the system info:
On-board printed info:
************************
Main chip: Philips SAA 7134 HL
Other chips: TDA 10046A, TDA 8274, MDT 2005ES-G.
lspci -vnn
****************
00:0c.0 Multimedia controller [0480]: Philips Semiconductors SAA7134/SAA7135HL
Video Broadcast Decoder [1131:7134] (rev 01)
Subsystem: Device [4e42:0301]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at dffffc00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Kernel driver in use: saa7134
dmesg | grep saa
*******************
saa7130/34: v4l2 driver version 0.2.15 loaded
[ 8.854415] saa7134 0000:00:0c.0: PCI INT A -> Link[LNKB] -> GSI 11 (level,
low) -> IRQ 11
[ 8.854423] saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 11, latency:
64, mmio: 0xdffffc00
[ 8.854430] saa7134[0]: subsystem: 4e42:0301, board: UNKNOWN/GENERIC
[card=0,autodetected]
[ 8.854453] saa7134[0]: board init: gpio is 10000
[ 8.854458] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 9.004012] saa7134[0]: i2c eeprom 00: 42 4e 01 03 54 20 1c 00 43 43 a9 1c
55 d2 b2 92
[ 9.004022] saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff
ff ff ff ff
[ 9.004030] saa7134[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 e2
ff ff ff ff
[ 9.004038] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004045] saa7134[0]: i2c eeprom 40: ff 1b 00 c0 ff 10 01 00 ff ff ff ff
ff ff ff ff
[ 9.004052] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004059] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004067] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004074] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004081] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004089] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004096] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004103] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004111] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004118] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004125] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 9.004271] saa7134[0]: registered device video0 [v4l2]
[ 9.004299] saa7134[0]: registered device vbi0
[ 9.565411] saa7134 ALSA driver for DMA sound loaded
[ 9.565424] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 9.565451] saa7134[0]/alsa: saa7134[0] at 0xdffffc00 irq 11 registered as
card -1
[ 3368.737762] saa7134[0]/irq[10,4295734480]: r=0x20 s=0x00 PE
[ 3368.737770] saa7134[0]/irq: looping -- clearing PE (parity error!) enable
bit
************************************************************************************
No DVB-T button appears in Kaffeine, so the card is not being detected by the
app.
Thanks for any help
Antonio
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to make a Zaapa LR301AP DVB-T card work
2009-12-19 14:00 How to make a Zaapa LR301AP DVB-T card work Antonio Marcos López Alonso
@ 2009-12-19 19:53 ` hermann pitton
2009-12-20 13:13 ` Antonio Marcos López Alonso
0 siblings, 1 reply; 6+ messages in thread
From: hermann pitton @ 2009-12-19 19:53 UTC (permalink / raw)
To: amlopezalonso; +Cc: linux-media
Hi,
Am Samstag, den 19.12.2009, 14:00 +0000 schrieb Antonio Marcos López
Alonso:
> Hi all,
>
> I borrowed a Zaapa LR301AP DVB-T card from a friend to try to make it work in
> Linux, so I kindly request your help. The card features one antenna input, one
> IR input (remote and sensor wire being lost) and one AV input. Here follows
> the system info:
>
>
> On-board printed info:
> ************************
> Main chip: Philips SAA 7134 HL
> Other chips: TDA 10046A, TDA 8274, MDT 2005ES-G.
>
> lspci -vnn
> ****************
> 00:0c.0 Multimedia controller [0480]: Philips Semiconductors SAA7134/SAA7135HL
> Video Broadcast Decoder [1131:7134] (rev 01)
> Subsystem: Device [4e42:0301]
> Flags: bus master, medium devsel, latency 64, IRQ 11
> Memory at dffffc00 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [40] Power Management version 1
> Kernel driver in use: saa7134
>
> dmesg | grep saa
> *******************
> saa7130/34: v4l2 driver version 0.2.15 loaded
> [ 8.854415] saa7134 0000:00:0c.0: PCI INT A -> Link[LNKB] -> GSI 11 (level,
> low) -> IRQ 11
> [ 8.854423] saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 11, latency:
> 64, mmio: 0xdffffc00
> [ 8.854430] saa7134[0]: subsystem: 4e42:0301, board: UNKNOWN/GENERIC
> [card=0,autodetected]
> [ 8.854453] saa7134[0]: board init: gpio is 10000
> [ 8.854458] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
> IRQs
> [ 9.004012] saa7134[0]: i2c eeprom 00: 42 4e 01 03 54 20 1c 00 43 43 a9 1c
> 55 d2 b2 92
> [ 9.004022] saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004030] saa7134[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 e2
> ff ff ff ff
> [ 9.004038] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004045] saa7134[0]: i2c eeprom 40: ff 1b 00 c0 ff 10 01 00 ff ff ff ff
> ff ff ff ff
> [ 9.004052] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004059] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004067] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004074] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004081] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004089] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004096] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004103] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004111] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004118] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004125] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 9.004271] saa7134[0]: registered device video0 [v4l2]
> [ 9.004299] saa7134[0]: registered device vbi0
> [ 9.565411] saa7134 ALSA driver for DMA sound loaded
> [ 9.565424] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
> IRQs
> [ 9.565451] saa7134[0]/alsa: saa7134[0] at 0xdffffc00 irq 11 registered as
> card -1
> [ 3368.737762] saa7134[0]/irq[10,4295734480]: r=0x20 s=0x00 PE
> [ 3368.737770] saa7134[0]/irq: looping -- clearing PE (parity error!) enable
> bit
> ************************************************************************************
>
> No DVB-T button appears in Kaffeine, so the card is not being detected by the
> app.
>
please try with "card=86".
If everything is fine, we add it to auto detection.
Cheers,
Hermann
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to make a Zaapa LR301AP DVB-T card work
2009-12-19 19:53 ` hermann pitton
@ 2009-12-20 13:13 ` Antonio Marcos López Alonso
2009-12-21 20:51 ` hermann pitton
0 siblings, 1 reply; 6+ messages in thread
From: Antonio Marcos López Alonso @ 2009-12-20 13:13 UTC (permalink / raw)
To: linux-media
>
> please try with "card=86".
>
> If everything is fine, we add it to auto detection.
>
> Cheers,
> Hermann
>
Did it so and the card (TDA10046 chip ) is now detected by MythTV (have to say
previous setup was not detected by Kaffeine because MythTV backend was
running). However scanning process did not find any channel and I'm sure
previous cards have worked doing so.
New "dmesg|grep saa" output:
*********************************
[ 8.840823] saa7130/34: v4l2 driver version 0.2.15 loaded
[ 8.841237] saa7134 0000:00:0c.0: PCI INT A -> Link[LNKB] -> GSI 11 (level,
low) -> IRQ 11
[ 8.841244] saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 11, latency:
64, mmio: 0xdffffc00
[ 8.841251] saa7134[0]: subsystem: 4e42:0301, board: LifeView FlyDVB-T /
Genius VideoWonder DVB-T [card=86,insmod option]
[ 8.841272] saa7134[0]: board init: gpio is 10000
[ 8.841369] input: saa7134 IR (LifeView FlyDVB-T / as
/devices/pci0000:00/0000:00:0c.0/input/input5
[ 8.841411] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 8.992137] saa7134[0]: i2c eeprom 00: 42 4e 01 03 54 20 1c 00 43 43 a9 1c
55 d2 b2 92
[ 8.992147] saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff
ff ff ff ff
[ 8.992155] saa7134[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 e2
ff ff ff ff
[ 8.992163] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992170] saa7134[0]: i2c eeprom 40: ff 1b 00 c0 ff 10 01 00 ff ff ff ff
ff ff ff ff
[ 8.992177] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992185] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992192] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992199] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992207] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992214] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992221] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992229] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992236] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992243] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992250] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
[ 8.992393] saa7134[0]: registered device video0 [v4l2]
[ 8.992418] saa7134[0]: registered device vbi0
[ 9.533985] DVB: registering new adapter (saa7134[0])
[ 10.279639] saa7134 ALSA driver for DMA sound loaded
[ 10.279652] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 10.279679] saa7134[0]/alsa: saa7134[0] at 0xdffffc00 irq 11 registered as
card -1
Cheers
Antonio
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to make a Zaapa LR301AP DVB-T card work
2009-12-20 13:13 ` Antonio Marcos López Alonso
@ 2009-12-21 20:51 ` hermann pitton
2009-12-22 16:41 ` Antonio Marcos López Alonso
0 siblings, 1 reply; 6+ messages in thread
From: hermann pitton @ 2009-12-21 20:51 UTC (permalink / raw)
To: amlopezalonso; +Cc: linux-media
Am Sonntag, den 20.12.2009, 13:13 +0000 schrieb Antonio Marcos López
Alonso:
> >
> > please try with "card=86".
> >
> > If everything is fine, we add it to auto detection.
> >
> > Cheers,
> > Hermann
> >
>
> Did it so and the card (TDA10046 chip ) is now detected by MythTV (have to say
> previous setup was not detected by Kaffeine because MythTV backend was
> running). However scanning process did not find any channel and I'm sure
> previous cards have worked doing so.
>
> New "dmesg|grep saa" output:
> *********************************
> [ 8.840823] saa7130/34: v4l2 driver version 0.2.15 loaded
> [ 8.841237] saa7134 0000:00:0c.0: PCI INT A -> Link[LNKB] -> GSI 11 (level,
> low) -> IRQ 11
> [ 8.841244] saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 11, latency:
> 64, mmio: 0xdffffc00
> [ 8.841251] saa7134[0]: subsystem: 4e42:0301, board: LifeView FlyDVB-T /
> Genius VideoWonder DVB-T [card=86,insmod option]
> [ 8.841272] saa7134[0]: board init: gpio is 10000
> [ 8.841369] input: saa7134 IR (LifeView FlyDVB-T / as
> /devices/pci0000:00/0000:00:0c.0/input/input5
> [ 8.841411] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
> IRQs
> [ 8.992137] saa7134[0]: i2c eeprom 00: 42 4e 01 03 54 20 1c 00 43 43 a9 1c
> 55 d2 b2 92
> [ 8.992147] saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992155] saa7134[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 e2
> ff ff ff ff
> [ 8.992163] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992170] saa7134[0]: i2c eeprom 40: ff 1b 00 c0 ff 10 01 00 ff ff ff ff
> ff ff ff ff
> [ 8.992177] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992185] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992192] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992199] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992207] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992214] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992221] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992229] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992236] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992243] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992250] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff
> [ 8.992393] saa7134[0]: registered device video0 [v4l2]
> [ 8.992418] saa7134[0]: registered device vbi0
> [ 9.533985] DVB: registering new adapter (saa7134[0])
> [ 10.279639] saa7134 ALSA driver for DMA sound loaded
> [ 10.279652] IRQ 11/saa7134[0]: IRQF_DISABLED is not guaranteed on shared
> IRQs
> [ 10.279679] saa7134[0]/alsa: saa7134[0] at 0xdffffc00 irq 11 registered as
> card -1
>
> Cheers
> Antonio
>
Antonio,
the report for tda10046 firmware loading is missing. Was that OK?
LR301 is a LifeView design. It is very common to see multiple other
subvendors for their cards, but they keep the original subdevice ID.
In this case 0x0301. The subvendor 0x4e42 is usually Typhoon/Anubis and
they are distributing clones of almost all LifeView cards.
Gpio init is the same like on the other known LR301 cards and eeprom
differs only for a few bytes, but not for tuner type, tuner and demod
address.
http://ubuntuforums.org/archive/index.php/t-328140.html
Since this design with a saa7134 chip and tda8274 DVB-T only tuner is very old,
I don't expect an additional Low Noise Amplifier on it.
We can't detect such LNAs and on newer cards they can cause problems, if
not configured correctly and might cause "scan" to fail.
If you mean above other card types did previously work for your card,
use them and report.
Sorry, I don't have better ideas for your card so far.
Cheers,
Hermann
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to make a Zaapa LR301AP DVB-T card work
2009-12-21 20:51 ` hermann pitton
@ 2009-12-22 16:41 ` Antonio Marcos López Alonso
2009-12-23 1:50 ` hermann pitton
0 siblings, 1 reply; 6+ messages in thread
From: Antonio Marcos López Alonso @ 2009-12-22 16:41 UTC (permalink / raw)
To: linux-media
>
> Antonio,
>
> the report for tda10046 firmware loading is missing. Was that OK?
Yes:
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
>
> LR301 is a LifeView design. It is very common to see multiple other
> subvendors for their cards, but they keep the original subdevice ID.
> In this case 0x0301. The subvendor 0x4e42 is usually Typhoon/Anubis and
> they are distributing clones of almost all LifeView cards.
>
> Gpio init is the same like on the other known LR301 cards and eeprom
> differs only for a few bytes, but not for tuner type, tuner and demod
> address.
>
> http://ubuntuforums.org/archive/index.php/t-328140.html
>
> Since this design with a saa7134 chip and tda8274 DVB-T only tuner is very
> old, I don't expect an additional Low Noise Amplifier on it.
>
> We can't detect such LNAs and on newer cards they can cause problems, if
> not configured correctly and might cause "scan" to fail.
>
> If you mean above other card types did previously work for your card,
> use them and report.
No, I meant other "physical" cards. Just to ensure it is not likely to be an
aerial problem.
>
> Sorry, I don't have better ideas for your card so far.
I have not included the "tuner" parameter in the "options" line which I think
it could be the problem. Is this parameter mandatory? If so, which is the
proper one?
Cheers,
Antonio
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to make a Zaapa LR301AP DVB-T card work
2009-12-22 16:41 ` Antonio Marcos López Alonso
@ 2009-12-23 1:50 ` hermann pitton
0 siblings, 0 replies; 6+ messages in thread
From: hermann pitton @ 2009-12-23 1:50 UTC (permalink / raw)
To: amlopezalonso; +Cc: linux-media
Am Dienstag, den 22.12.2009, 16:41 +0000 schrieb Antonio Marcos López
Alonso:
> >
> > Antonio,
> >
> > the report for tda10046 firmware loading is missing. Was that OK?
>
> Yes:
>
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
>
> >
> > LR301 is a LifeView design. It is very common to see multiple other
> > subvendors for their cards, but they keep the original subdevice ID.
> > In this case 0x0301. The subvendor 0x4e42 is usually Typhoon/Anubis and
> > they are distributing clones of almost all LifeView cards.
> >
> > Gpio init is the same like on the other known LR301 cards and eeprom
> > differs only for a few bytes, but not for tuner type, tuner and demod
> > address.
> >
> > http://ubuntuforums.org/archive/index.php/t-328140.html
> >
> > Since this design with a saa7134 chip and tda8274 DVB-T only tuner is very
> > old, I don't expect an additional Low Noise Amplifier on it.
> >
> > We can't detect such LNAs and on newer cards they can cause problems, if
> > not configured correctly and might cause "scan" to fail.
> >
> > If you mean above other card types did previously work for your card,
> > use them and report.
>
> No, I meant other "physical" cards. Just to ensure it is not likely to be an
> aerial problem.
Good to know. However, the first revisions of silicon tuners like the
tda8274 can't compete with can tuners. Only the tda8275a hybrid can come
_close_ to a good can tuner like the FMD1216ME/I H-3 (MK3) on a well
designed PCB. Signal quality might be still not sufficient for your
card.
You also had parity errors on your first report, which likely indicate
problems on your mobo at least with this PCI slot and/or sharing
interrupts with other devices there.
> > Sorry, I don't have better ideas for your card so far.
>
> I have not included the "tuner" parameter in the "options" line which I think
> it could be the problem. Is this parameter mandatory? If so, which is the
> proper one?
>
No. You can force tuner types only for analog TV. The tda8274 is not a
hybrid tuner, it is only used for DVB-T. An early tda8275 hybrid with a
saa7134 chip would have a separate tda8290 chip for analog IF
demodulation. Without that no analog TV and no tuner type to set.
For DVB-T the tda8274 is treated like a tda8275.
Cheers,
Hermann
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-12-23 1:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-19 14:00 How to make a Zaapa LR301AP DVB-T card work Antonio Marcos López Alonso
2009-12-19 19:53 ` hermann pitton
2009-12-20 13:13 ` Antonio Marcos López Alonso
2009-12-21 20:51 ` hermann pitton
2009-12-22 16:41 ` Antonio Marcos López Alonso
2009-12-23 1:50 ` hermann pitton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox