* MCE TV Philips 7135 Cardbus don't work
@ 2008-04-29 18:07 Emilio Lazo Zaia
2008-04-29 23:20 ` Marc Randolph
0 siblings, 1 reply; 9+ messages in thread
From: Emilio Lazo Zaia @ 2008-04-29 18:07 UTC (permalink / raw)
To: video4linux-list
Hello,
I have purchased a "MCE TV Philips 7135 Cardbus" and I'm to set it up.
When I plug it, the module saa7134 is being loaded and dmesg says:
pccard: CardBus card inserted into slot 0
Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.14 loaded
PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 17 (level, low) -> IRQ 17
saa7133[0]: found at 0000:06:00.0, rev: 209, irq: 17, latency: 0, mmio:
0x54000000
PCI: Setting latency timer of device 0000:06:00.0 to 64
saa7133[0]: subsystem: 1131:0000, board: UNKNOWN/GENERIC
[card=0,autodetected]
saa7133[0]: board init: gpio is e2c0c0
saa7133[0]: Huh, no eeprom present (err=-5)?
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
Since card is not detected, I've typed some little bash script to unload
(rmmod) and load again saa7134 module with modprobe adding "card=n"
parameter with n from 1 to 117 and execute tvtime each time module is
being loaded with different card number (The tuner module I've not
reloaded with different values). Note that a message of no EEPROM
present is issued by saa7134 module! This is related specifically to
the tuner?
None of these 117 cards works in tv mode, some of these have not
"Television" input facility, others have "Composite1", "Composite2",
"S-Video" and some others have "TV (mono)" but in "Television" mode,
almost in all cases a blue screen is showed.
Here, the television norm is NTSC; I'm using Debian lenny with
2.6.24-amd64 kernel. Cardbus controller according to lspci is:
05:09.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus
Controller
and the output of "lspci -vv" regarding this TV card is:
06:00.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135
Video Broadcast Decoder (rev d1)
Subsystem: Philips Semiconductors Unknown device 0000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (3750ns min, 9500ns max)
Interrupt: pin A routed to IRQ 17
Region 0: Memory at 54000000 (32-bit, non-prefetchable)
[size=2K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Anyone has this card working or has some idea about the correct
combination of card and tuner number?
TIA
Regards.
--
Emilio Lazo Zaia <emiliolazozaia@gmail.com>
Facultad de Ciencias, UCV
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: MCE TV Philips 7135 Cardbus don't work
2008-04-29 18:07 MCE TV Philips 7135 Cardbus don't work Emilio Lazo Zaia
@ 2008-04-29 23:20 ` Marc Randolph
2008-04-29 23:47 ` Andy Walls
0 siblings, 1 reply; 9+ messages in thread
From: Marc Randolph @ 2008-04-29 23:20 UTC (permalink / raw)
To: Emilio Lazo Zaia, video4linux-list
--- Emilio Lazo Zaia <emiliolazozaia@gmail.com> wrote:
> Hello,
>
> I have purchased a "MCE TV Philips 7135 Cardbus" and I'm to set it up.
> When I plug it, the module saa7134 is being loaded and dmesg says:
>
> pccard: CardBus card inserted into slot 0
> Linux video capture interface: v2.00
> saa7130/34: v4l2 driver version 0.2.14 loaded
> PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> saa7133[0]: found at 0000:06:00.0, rev: 209, irq: 17, latency: 0, mmio:
> 0x54000000
> PCI: Setting latency timer of device 0000:06:00.0 to 64
> saa7133[0]: subsystem: 1131:0000, board: UNKNOWN/GENERIC
> [card=0,autodetected]
> saa7133[0]: board init: gpio is e2c0c0
> saa7133[0]: Huh, no eeprom present (err=-5)?
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
Howdy Emilio,
Google gives a ton of hits on that very unique error message. I assume you
already did this:
"try to pass newi2c=1 or newi2c=0 to the ivtv module. Add it to
/etc/modprobe.conf (or /etc/modules.d/ivtv if you are an gentoo user).
options ivtv newi2c=1
If setting this works please report it to the ivtv-devel mailing list."
Copied from
http://ivtvdriver.org/index.php/Troubleshooting#Error:_Huh.2C_no_eeprom_present_.28err.3D-121.29.3F
Good luck,
Marc
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-04-29 23:20 ` Marc Randolph
@ 2008-04-29 23:47 ` Andy Walls
2008-05-04 1:15 ` Emilio Lazo Zaia
0 siblings, 1 reply; 9+ messages in thread
From: Andy Walls @ 2008-04-29 23:47 UTC (permalink / raw)
To: Marc Randolph; +Cc: video4linux-list
On Tue, 2008-04-29 at 16:20 -0700, Marc Randolph wrote:
> --- Emilio Lazo Zaia <emiliolazozaia@gmail.com> wrote:
>
> > Hello,
> >
> > I have purchased a "MCE TV Philips 7135 Cardbus" and I'm to set it up.
> > When I plug it, the module saa7134 is being loaded and dmesg says:
> >
> > pccard: CardBus card inserted into slot 0
> > Linux video capture interface: v2.00
> > saa7130/34: v4l2 driver version 0.2.14 loaded
> > PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
> > ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> > saa7133[0]: found at 0000:06:00.0, rev: 209, irq: 17, latency: 0, mmio:
> > 0x54000000
> > PCI: Setting latency timer of device 0000:06:00.0 to 64
> > saa7133[0]: subsystem: 1131:0000, board: UNKNOWN/GENERIC
> > [card=0,autodetected]
> > saa7133[0]: board init: gpio is e2c0c0
> > saa7133[0]: Huh, no eeprom present (err=-5)?
> > saa7133[0]: registered device video0 [v4l2]
> > saa7133[0]: registered device vbi0
>
> Howdy Emilio,
>
> Google gives a ton of hits on that very unique error message. I assume you
> already did this:
>
> "try to pass newi2c=1 or newi2c=0 to the ivtv module. Add it to
> /etc/modprobe.conf (or /etc/modules.d/ivtv if you are an gentoo user).
>
> options ivtv newi2c=1
>
> If setting this works please report it to the ivtv-devel mailing list."
>
> Copied from
> http://ivtvdriver.org/index.php/Troubleshooting#Error:_Huh.2C_no_eeprom_present_.28err.3D-121.29.3F
>
Marc,
Good reasoning, but as it happens, this error message is not quite
unique. The ivtv/tveeprom modules will additionally gripe about "not a
Hauppauge EEPROM". The ivtv/tveeprom modules will usually return -121
corresponding to -EREMOTEIO.
Emilio,
This card is handled by the saa7134, module, not the ivtv module, so
newi2c doesn't apply.
"Huh, no eeprom present" in this case is being emitted by the saa7134
module itself and not the tveeprom module that ivtv uses.
"err=-5" is -EIO, referring to an I2C bus error with the i2c bus of the
saa7133.
With the saa7134 module "/sbin/modinfo" has two interesting options:
i2c_scan and i2c_debug which you may wish to try.
Regards,
Andy
> Good luck,
>
> Marc
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-04-29 23:47 ` Andy Walls
@ 2008-05-04 1:15 ` Emilio Lazo Zaia
2008-05-04 20:21 ` Hartmut Hackmann
0 siblings, 1 reply; 9+ messages in thread
From: Emilio Lazo Zaia @ 2008-05-04 1:15 UTC (permalink / raw)
To: Andy Walls; +Cc: video4linux-list
Hi Andy, Marc and all list members! Thanks for your answers!
El mar, 29-04-2008 a las 19:47 -0400, Andy Walls escribió:
> Emilio,
>
> This card is handled by the saa7134, module, not the ivtv module, so
> newi2c doesn't apply.
Yes Andy, I know! I'm trying with saa7134 and have tested all cards
listed in kernel source's CARDLIST.saa7134 and all these reported "Huh,
no eeprom present". After that I've tested with all tuners listed in
CARDLIST.tuner with the same card=56 parameter and the results were
similar: the same "no eeprom" message and a blue screen in TV input
mode.
> "err=-5" is -EIO, referring to an I2C bus error with the i2c bus of the
> saa7133.
> With the saa7134 module "/sbin/modinfo" has two interesting options:
> i2c_scan and i2c_debug which you may wish to try.
With this two options, I have these interesting messages in kernel log:
> Apr 29 22:47:20 uqbar kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: found at 0000:06:00.0, rev: 209, irq: 17, latency: 64, mmio: 0x54000000
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: subsystem: 1131:0000, board: Avermedia AVerTV 307 [card=56,insmod option]
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: board init: gpio is e2c0c4
> Apr 29 22:47:20 uqbar kernel: input: saa7134 IR (Avermedia AVerTV 30 as /class/input/input14
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < f5 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < e3 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < a0 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: Huh, no eeprom present (err=-5)?
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 01 ERROR: NO_DEVICE
> .
> .
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 95 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c scan: found device @ 0x96 [???]
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 99 ERROR: NO_DEVICE
> .
> .
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 86 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 94 ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 01 02 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 00 00 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 07 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 =00 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 01 04 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 00 00 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 07 >
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 =7b >
> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: chip found @ 0x96 (saa7133[0])
> Apr 29 22:47:20 uqbar kernel: tuner i2c attach [addr=0x4b,client=(tuner unset)]
> Apr 29 22:47:20 uqbar kernel: tuner-simple 0-004b: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: type set to Philips NTSC (FI123
> Apr 29 22:47:20 uqbar kernel: tuner-simple 0-004b: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: type set to Philips NTSC (FI123
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < c0 ERROR: NO_DEVICE
> .
> .
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < de ERROR: NO_DEVICE
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: registered device video0 [v4l2]
> Apr 29 22:47:20 uqbar kernel: saa7133[0]: registered device vbi0
> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b 6f 8e 90 >
> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b 6f 8e 90 >
> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b dc 8e 90 >
> Apr 29 22:47:21 uqbar last message repeated 2 times
> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 8e a0 07 b0 >
>
Card is found at 0x96, but what tuner and card number combination may
work for this card? What other debugging information can I supply to add
this card to the list of supported cards in saa7134 module?
Thanks! Regards.
--
Emilio Lazo Zaia <emiliolazozaia@gmail.com>
Escuela de Física
Universidad Central de Venezuela
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-05-04 1:15 ` Emilio Lazo Zaia
@ 2008-05-04 20:21 ` Hartmut Hackmann
2008-05-06 3:38 ` Emilio Lazo Zaia
0 siblings, 1 reply; 9+ messages in thread
From: Hartmut Hackmann @ 2008-05-04 20:21 UTC (permalink / raw)
To: Emilio Lazo Zaia; +Cc: video4linux-list
Hi, Emilio
Emilio Lazo Zaia schrieb:
> Hi Andy, Marc and all list members! Thanks for your answers!
>
> El mar, 29-04-2008 a las 19:47 -0400, Andy Walls escribió:
>> Emilio,
>>
>> This card is handled by the saa7134, module, not the ivtv module, so
>> newi2c doesn't apply.
>
> Yes Andy, I know! I'm trying with saa7134 and have tested all cards
> listed in kernel source's CARDLIST.saa7134 and all these reported "Huh,
> no eeprom present". After that I've tested with all tuners listed in
> CARDLIST.tuner with the same card=56 parameter and the results were
> similar: the same "no eeprom" message and a blue screen in TV input
> mode.
>
>> "err=-5" is -EIO, referring to an I2C bus error with the i2c bus of the
>> saa7133.
>> With the saa7134 module "/sbin/modinfo" has two interesting options:
>> i2c_scan and i2c_debug which you may wish to try.
>
> With this two options, I have these interesting messages in kernel log:
>
>> Apr 29 22:47:20 uqbar kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: found at 0000:06:00.0, rev: 209, irq: 17, latency: 64, mmio: 0x54000000
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: subsystem: 1131:0000, board: Avermedia AVerTV 307 [card=56,insmod option]
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: board init: gpio is e2c0c4
>> Apr 29 22:47:20 uqbar kernel: input: saa7134 IR (Avermedia AVerTV 30 as /class/input/input14
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < f5 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < e3 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < a0 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: Huh, no eeprom present (err=-5)?
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 01 ERROR: NO_DEVICE
>> .
>> .
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 95 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c scan: found device @ 0x96 [???]
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 99 ERROR: NO_DEVICE
>> .
>> .
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 86 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 94 ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 01 02 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 00 00 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 07 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 =00 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 01 04 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 00 00 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 96 07 >
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < 97 =7b >
>> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: chip found @ 0x96 (saa7133[0])
>> Apr 29 22:47:20 uqbar kernel: tuner i2c attach [addr=0x4b,client=(tuner unset)]
>> Apr 29 22:47:20 uqbar kernel: tuner-simple 0-004b: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
>> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: type set to Philips NTSC (FI123
>> Apr 29 22:47:20 uqbar kernel: tuner-simple 0-004b: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
>> Apr 29 22:47:20 uqbar kernel: tuner 0-004b: type set to Philips NTSC (FI123
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < c0 ERROR: NO_DEVICE
>> .
>> .
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: i2c xfer: < de ERROR: NO_DEVICE
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: registered device video0 [v4l2]
>> Apr 29 22:47:20 uqbar kernel: saa7133[0]: registered device vbi0
>> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b 6f 8e 90 >
>> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b 6f 8e 90 >
>> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 1b dc 8e 90 >
>> Apr 29 22:47:21 uqbar last message repeated 2 times
>> Apr 29 22:47:21 uqbar kernel: saa7133[0]: i2c xfer: < 96 8e a0 07 b0 >
>>
>
> Card is found at 0x96, but what tuner and card number combination may
> work for this card? What other debugging information can I supply to add
> this card to the list of supported cards in saa7134 module?
>
> Thanks! Regards.
>
There are many saa713x based cards without eeprom. It stores the vendor ID and
- in many cases - the board configuration. For you this means
- you need to find out the configuration the hard way
* identify the chips on the card
* find the input configuration by try and error
- You will always need to force the card type with a card=xxx option, there is
no way to automatically identify the card.
So please have a close look at the card and write down all chip types. Is there
a metal box with the antenna connector on the card? What is its type?
Hartmut
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-05-04 20:21 ` Hartmut Hackmann
@ 2008-05-06 3:38 ` Emilio Lazo Zaia
2008-05-06 20:20 ` Hartmut Hackmann
0 siblings, 1 reply; 9+ messages in thread
From: Emilio Lazo Zaia @ 2008-05-06 3:38 UTC (permalink / raw)
To: Hartmut Hackmann; +Cc: video4linux-list
Hi Hartmut!
This is a Cardbus adapter, so maybe I need to break in to have a
look :-)
If this is possible without a possible physical damage, I can try!
What you say is that "no eeprom present" is not an error and can be
ignored if the correct configuration is found the hard way?
In the case of a PCI adapter, what can be deduced about the presence of
these metal box? I saw some board with and without it.
Thanks,
Regards!
El dom, 04-05-2008 a las 22:21 +0200, Hartmut Hackmann escribió:
> There are many saa713x based cards without eeprom. It stores the vendor ID and
> - in many cases - the board configuration. For you this means
> - you need to find out the configuration the hard way
> * identify the chips on the card
> * find the input configuration by try and error
> - You will always need to force the card type with a card=xxx option, there is
> no way to automatically identify the card.
>
> So please have a close look at the card and write down all chip types. Is there
> a metal box with the antenna connector on the card? What is its type?
>
> Hartmut
--
Emilio Lazo Zaia <emiliolazozaia@gmail.com>
Escuela de Física
Universidad Central de Venezuela
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-05-06 3:38 ` Emilio Lazo Zaia
@ 2008-05-06 20:20 ` Hartmut Hackmann
2008-05-23 7:04 ` Emilio Lazo Zaia
2008-06-30 20:50 ` Emilio Lazo Zaia
0 siblings, 2 replies; 9+ messages in thread
From: Hartmut Hackmann @ 2008-05-06 20:20 UTC (permalink / raw)
To: Emilio Lazo Zaia; +Cc: video4linux-list
Emilio Lazo Zaia schrieb:
> Hi Hartmut!
>
> This is a Cardbus adapter, so maybe I need to break in to have a
> look :-)
> If this is possible without a possible physical damage, I can try!
>
You need to be careful but you can bend most modules open with a
not too sharp knife. You need to start this from the far side of the
cardbus connector.
I did this several times.
> What you say is that "no eeprom present" is not an error and can be
> ignored if the correct configuration is found the hard way?
>
yes.
> In the case of a PCI adapter, what can be deduced about the presence of
> these metal box? I saw some board with and without it.
>
This box is the so-called tuner. It is important to know its type.
But before you open the module, you might try a "modprobe saa7134 card=55"
and watch the kernel log. If the driver tells you it found a tda8175(a),
we already learned a lot.
> Thanks,
> Regards!
>
> El dom, 04-05-2008 a las 22:21 +0200, Hartmut Hackmann escribió:
>
>> There are many saa713x based cards without eeprom. It stores the vendor ID and
>> - in many cases - the board configuration. For you this means
>> - you need to find out the configuration the hard way
>> * identify the chips on the card
>> * find the input configuration by try and error
>> - You will always need to force the card type with a card=xxx option, there is
>> no way to automatically identify the card.
>>
>> So please have a close look at the card and write down all chip types. Is there
>> a metal box with the antenna connector on the card? What is its type?
>>
>> Hartmut
Good luck
Hartmut
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-05-06 20:20 ` Hartmut Hackmann
@ 2008-05-23 7:04 ` Emilio Lazo Zaia
2008-06-30 20:50 ` Emilio Lazo Zaia
1 sibling, 0 replies; 9+ messages in thread
From: Emilio Lazo Zaia @ 2008-05-23 7:04 UTC (permalink / raw)
To: Hartmut Hackmann, video4linux-list
Hi!
El mar, 06-05-2008 a las 22:20 +0200, Hartmut Hackmann escribió:
> But before you open the module, you might try a "modprobe saa7134 card=55"
> and watch the kernel log. If the driver tells you it found a tda8175(a),
> we already learned a lot.
With card=53 (ASUS TV-FM 7135) and tuner=54 (tda8290+75) radio works!
but seems to be swapped Television and Composite modes; I can watch RCA
input using _Television_ mode and switching to Composite mode shows
typical TV noise. Obviously the channel can't be changed in Composite
but there is a way to correct this input mode confusion?
There is a lag when radio station is changed, maybe because of a
card/tuner misconfiguration but works and ALSA audio capture function
also works!
--
Emilio Lazo Zaia <emiliolazozaia@gmail.com>
Facultad de Ciencias, UCV
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: MCE TV Philips 7135 Cardbus don't work
2008-05-06 20:20 ` Hartmut Hackmann
2008-05-23 7:04 ` Emilio Lazo Zaia
@ 2008-06-30 20:50 ` Emilio Lazo Zaia
1 sibling, 0 replies; 9+ messages in thread
From: Emilio Lazo Zaia @ 2008-06-30 20:50 UTC (permalink / raw)
To: Hartmut Hackmann, video4linux-list
Inside the adapter I see these four major chips:
SAA7135HL/203
CH7329 10
TS607372
TDA8290
SC8386
.1 01
ZPG06221
74HC4052D
AC234 08
Un60540D
8275AC1
CH8688
04
TPG07371
Clearly first three chips are Philips.
This cardbus module can't be autodetected, has no eeprom and still not
working to watch tv input, only radio works and seems to be swapped
Television and Composite modes because composite input can be seen in
Television mode and when Composite input is selected, TV noise is being
watched.
El mar, 06-05-2008 a las 22:20 +0200, Hartmut Hackmann escribió:
> You need to be careful but you can bend most modules open with a
> not too sharp knife. You need to start this from the far side of the
> cardbus connector.
> I did this several times.
--
Emilio Lazo Zaia <emiliolazozaia@gmail.com>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-06-30 20:51 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-29 18:07 MCE TV Philips 7135 Cardbus don't work Emilio Lazo Zaia
2008-04-29 23:20 ` Marc Randolph
2008-04-29 23:47 ` Andy Walls
2008-05-04 1:15 ` Emilio Lazo Zaia
2008-05-04 20:21 ` Hartmut Hackmann
2008-05-06 3:38 ` Emilio Lazo Zaia
2008-05-06 20:20 ` Hartmut Hackmann
2008-05-23 7:04 ` Emilio Lazo Zaia
2008-06-30 20:50 ` Emilio Lazo Zaia
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox