Seeking help for a 713x based card

Seeking help for a 713x based card

[Per Baekgaard]

I have a card of unknown (to me) brand that identifies itself as a 
1131:7133 (chipset) with 1a7f:2004 rev d1 as the subsystem ID/revision.

The card is unfortunately glued (!) inside a LCD enclosure, and I am not 
able to see any further identifications on it.

Google'ing the SVID/SSID hints that it could be a PAL derivative of an 
Encore ENLTV-FM card. When asked, Encore basically just said that the 
closest match would appear to be ENLTV-FM and that there is no support 
for linux and asked me to look at sourceforge.net ;-)

I am able to get it partially running by using "options saa7134 card=107 
tuner=54" (or card 3), but it appears that changing channel via tvtime 
or myth  fails roughly half the time and simply causes it to return an 
invalid (or empty) video stream. Indeed, in myth, it sometimes crashes 
the application.

I am also not able to capture any sound from the card, although 
saa7134_alsa gets loaded as expected.


How do I debug this, and get the driver to recognise the card properly?

Or any good hints at what the card may be? Would the i2c reveal any 
further hints?


Thanks in advance,


-- Per.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Seeking help for a 713x based card

[hermann pitton]

Hi Per,

Am Donnerstag, den 17.07.2008, 00:12 +0200 schrieb Per Baekgaard:
> I have a card of unknown (to me) brand that identifies itself as a 
> 1131:7133 (chipset) with 1a7f:2004 rev d1 as the subsystem ID/revision.

1131:7133 in .dk means a saa7135 or more likely a recent saa7131e.
The subvendor 1a7f seems to be seen the first time here, subdevice 2004
is only known on some Philips reference designs.

> The card is unfortunately glued (!) inside a LCD enclosure, and I am not 
> able to see any further identifications on it.

;) what to say.

> Google'ing the SVID/SSID hints that it could be a PAL derivative of an 
> Encore ENLTV-FM card. When asked, Encore basically just said that the 
> closest match would appear to be ENLTV-FM and that there is no support 
> for linux and asked me to look at sourceforge.net ;-)

They are likely right to send you out into the deserts.

> I am able to get it partially running by using "options saa7134 card=107 
> tuner=54" (or card 3), but it appears that changing channel via tvtime 
> or myth  fails roughly half the time and simply causes it to return an 
> invalid (or empty) video stream. Indeed, in myth, it sometimes crashes 
> the application.

If channel change sometimes works it is some tuner=54, but might need
some card specific calibration or your signal is weak.

Is DVB-T or DVB-S announced too or only analog TV?

> I am also not able to capture any sound from the card, although 
> saa7134_alsa gets loaded as expected.

Most of the recent cards don't have analog sound output to the sound
card anymore. The chips do provide it, but manufacturers decide against
to provide the connector.

The saa7134-alsa must be properly used and does not work automagically,
also if a gpio switched sound mux chip is on the card, it needs to be
configured correctly for sound switching. This is not visible in the
logs.

> How do I debug this, and get the driver to recognise the card properly?
> 
> Or any good hints at what the card may be? Would the i2c reveal any 
> further hints?

To set up an invisible device is a bit odd,
but copy and paste "dmesg" output after loading the driver with
i2c_scan=1 enabled ("modinfo saa7134") might help on some further
guessing.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Seeking help for a 713x based card

[Per Baekgaard]

Hi Hermann,

Thanks for the quick reply.

You wrote:
> Hi Per,
>
> Am Donnerstag, den 17.07.2008, 00:12 +0200 schrieb Per Baekgaard:
>   
>> I have a card of unknown (to me) brand that identifies itself as a 
>> 1131:7133 (chipset) with 1a7f:2004 rev d1 as the subsystem ID/revision.
>>     
>
> 1131:7133 in .dk means a saa7135 or more likely a recent saa7131e.
> The subvendor 1a7f seems to be seen the first time here, subdevice 2004
> is only known on some Philips reference designs.
>   
There is a windows driver that comes with the system. Inspecting the 
3xhybrid.inf file reveals only tiny bits more information to me. Appears 
copyrighted by Philips Semi and is labelled "SAA713x Based - BDA TV 
Capture Driver" with a random provider name "Active Development Co., Ltd.".

Cards in the series are apparently called "Mercur, Tiger", "Proteus", 
"Europa (1-3), Snake, Tough, Smart, Clever" and "Europe (4.x)"

Some parts here:

;******** Proteus ***
;%PHILIPS_30.DeviceDesc% = 
PHILIPS_PROTEUS.NTx86,PCI\VEN_1131&DEV_7130&SUBSYS_20011A7F
;%PHILIPS_33.DeviceDesc% = 
PHILIPS_PROTEUS.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_20011A7F
;%PHILIPS_34.DeviceDesc% = 
PHILIPS_PROTEUS.NTx86,PCI\VEN_1131&DEV_7134&SUBSYS_20011A7F

;******** PHILIPS PROTEUS x32 ***
[PHILIPS_PROTEUS.NTx86.CoInstallers]
CopyFiles     = SectionX32.CopyDll.NTx86
AddReg        = SectionX32.DllAddReg.NTx86
 
[PHILIPS_PROTEUS.NTx86]
Include       = ks.inf, wdmaudio.inf, kscaptur.inf, bda.inf
Needs         = KS.Registration.NT, WDMAUDIO.Registration.NT, 
KSCAPTUR.Registration.NT, BDA.Installation.NT
CopyFiles     = SectionX32.CopyDriver.NTx86, SectionX32.CopyDll.NTx86
AddReg        = SectionX32.AddReg.NTx86, PHILIPS_PROTEUS.AddReg
 
[PHILIPS_PROTEUS.NTx86.Services]
AddService    = %SERVICE_NAME_X32%, 0x00000002, 
SectionX32.ServiceInstall.NTx86

;---- Proteus ----
[PHILIPS_PROTEUS.AddReg]
; Prefix will be displayed in front of the device name on every filter
HKR, "Parameters","Prefix",,%PHILIPS_CUSTOM_TUNERNAME%
 
; SmallXBar=0: XBar inputs => Tuner, Composite1, S-Video1, Composite2, 
S-Video2
; SmallXBar=1: XBar inputs => Tuner, Composite1, S-Video1
HKR, "Parameters", "SmallXBar",0x00010001,1
 
HKR, "I2C Devices", "Force Registry Settings",0x00010001,0x01
HKR, "VideoDecoder", "Tuner Channel",0x00010001,0x01
HKR, "VideoDecoder", "CVBS Channel",0x00010001,0x00
HKR, "VideoDecoder", "SVHS Channel",0x00010001,0x06
;HKR, "VideoDecoder", "FM Radio Channel",0x00010001,0x00
 
HKR, "AudioDecoder", "Tuner Channel",0x00010001,0x01
HKR, "AudioDecoder", "CVBS Channel",0x00010001,0x02
HKR, "AudioDecoder", "SVHS Channel",0x00010001,0x02
;HKR, "AudioDecoder", "FM Radio Channel",0x00010001,0x02
;HKR, "AudioDecoder", "XTAL",0x00010001,0x0                ;Default = 32MHz
 
HKR, "I2C Devices", "Number of I2C Devices",0x00010001,0x01
HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x03  ; Tuner ID
HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC0  ; Tuner slave addr.
HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86  ; Tuner IF PLL 
slave addr.
;HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x0   ; Demod slave addr.
;HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x0   ; Size of add. data
;HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x0   ; Add. data #1
;HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x0   ; Add. data #2
;HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x0   ; Add. data #3



PHILIPS_33.DeviceDesc         = "PCI DTV Card"


... but not sure how helpful this is at all?

>> The card is unfortunately glued (!) inside a LCD enclosure, and I am not 
>> able to see any further identifications on it.
>>     
>
> ;) what to say.
>   
... know it sounds strange (and indeed it is). It is inside an otherwise 
well-equipped enclosure of .cn origin that basically embeds a low-noise 
PC (GA-MA78M-S2H MB w/AMD X2 5400 CPU) inside what looks like a normal 
LCD based TV.
>> I am able to get it partially running by using "options saa7134 card=107 
>> tuner=54" (or card 3), but it appears that changing channel via tvtime 
>> or myth  fails roughly half the time and simply causes it to return an 
>> invalid (or empty) video stream. Indeed, in myth, it sometimes crashes 
>> the application.
>>     
>
> If channel change sometimes works it is some tuner=54, but might need
> some card specific calibration or your signal is weak.
>   
I don't think the signal is weak as such here, and it is also pretty 
random what channels fail. In tvtime, I can sometimes just roll through 
the inputs (tuner, composite, ...) and then the signal is there when the 
tuner is re-selected. More likely some card specifics that needs to be 
added, me thinks.
> Is DVB-T or DVB-S announced too or only analog TV?
>   
This is not evident. The specs on the device leads me to think that 
there is at least DVB-T support, but I'm not sure.
>> I am also not able to capture any sound from the card, although 
>> saa7134_alsa gets loaded as expected.
>>     
>
> Most of the recent cards don't have analog sound output to the sound
> card anymore. The chips do provide it, but manufacturers decide against
> to provide the connector.
>
> The saa7134-alsa must be properly used and does not work automagically,
> also if a gpio switched sound mux chip is on the card, it needs to be
> configured correctly for sound switching. This is not visible in the
> logs.
>   
OK -- so likely some setup missing too.
>   
>> How do I debug this, and get the driver to recognise the card properly?
>>
>> Or any good hints at what the card may be? Would the i2c reveal any 
>> further hints?
>>     
>
> To set up an invisible device is a bit odd,
> but copy and paste "dmesg" output after loading the driver with
> i2c_scan=1 enabled ("modinfo saa7134") might help on some further
> guessing.
>   
Here's the relevant clip:


[   46.297474] saa7130/34: v4l2 driver version 0.2.14 loaded
[   46.297544] ACPI: PCI Interrupt 0000:03:07.0[A] -> GSI 21 (level, 
low) -> IRQ 21
[   46.297552] saa7133[0]: found at 0000:03:07.0, rev: 209, irq: 21, 
latency: 32, mmio: 0xfdcff000
[   46.297558] saa7133[0]: subsystem: 1a7f:2004, board: UNKNOWN/GENERIC 
[card=0,autodetected]
[   46.297566] saa7133[0]: board init: gpio is ac6ee00
[   46.311610] usbcore: registered new interface driver libusual
[   46.423269] Initializing USB Mass Storage driver...
[   46.426251] scsi6 : SCSI emulation for USB Mass Storage devices
[   46.427460] usbcore: registered new interface driver usb-storage
[   46.427465] USB Mass Storage support registered.
[   46.427469] usb-storage: device found at 4
[   46.427470] usb-storage: waiting for device to settle before scanning
[   46.430243] saa7133[0]: i2c eeprom 00: 7f 1a 04 20 54 20 1c 00 43 43 
a9 1c 55 d2 b2 92
[   46.430250] saa7133[0]: i2c eeprom 10: 00 df 86 0f ff 20 ff ff ff ff 
ff ff ff ff ff ff
[   46.430255] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 ff 01 03 08 ff 
00 8f ff ff ff ff
[   46.430260] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff ff ff
[   46.430264] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15 08 
ff ff ff ff ff ff
[   46.430269] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff 5f 84 ff 
31 30 4d 4f 4f 4e
[   46.430273] saa7133[0]: i2c eeprom 60: 53 50 44 41 31 30 30 ff 50 ff 
ff ff ff ff ff ff
[   46.430278] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff ff ff
[   46.446649] saa7133[0]: i2c scan: found device @ 0x10  [???]
[   46.462198] saa7133[0]: i2c scan: found device @ 0x96  [???]
[   46.473848] saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
[   46.496852] saa7133[0]: registered device video0 [v4l2]
[   46.498102] saa7133[0]: registered device vbi0
[   46.504905] lirc_dev: IR Remote Control driver registered, at major 61
[   46.520467] ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, 
low) -> IRQ 18
[   46.535450]
[   46.535452] lirc_mceusb2: Philips eHome USB IR Transciever and 
Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $
[   46.535455] lirc_mceusb2: Daniel Melander <lirc@rajidae.se>, Martin 
Blatter <martin_a_blatter@yahoo.com>
[   46.547154] saa7134 ALSA driver for DMA sound loaded
[   46.547182] saa7133[0]/alsa: saa7133[0] at 0xfdcff000 irq 21 
registered as card -2
[   46.556138] hda_codec: Unknown model for ALC882, trying auto-probe 
from BIOS...
[   46.594717] ACPI: PCI Interrupt 0000:01:05.1[B] -> GSI 19 (level, 
low) -> IRQ 20
[   46.594747] PCI: Setting latency timer of device 0000:01:05.1 to 64
[   46.736190] usb 3-2: reset full speed USB device using ohci_hcd and 
address 4
[   46.947578] lirc_dev: lirc_register_plugin: sample_rate: 0
[   46.951560] lirc_mceusb2[4]: Topseed eHome Infrared Transceiver on usb3:4
[   46.951584] usbcore: registered new interface driver lirc_mceusb2
[   46.951689] usbcore: registered new interface driver hiddev

Full log is temporarily here:

   http://www.b4net.dk/dmesg.log2

There is also a http://www.b4net.dk/dmesg.log when run with my "normal" 
parameters for getting the card somehow working. Sometimes, randomly (as 
in the log above) there is a also a whole slew of dsp errors, which 
again points in the direction of some setup failing.


Thanks for any advice you can give!


-- Per.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Seeking help for a 713x based card

[hermann pitton]

Hi!

Am Donnerstag, den 17.07.2008, 09:31 +0200 schrieb Per Baekgaard:
> Hi Hermann,
> 
> Thanks for the quick reply.
> 
> You wrote: 
> > Hi Per,
> > 
> > Am Donnerstag, den 17.07.2008, 00:12 +0200 schrieb Per Baekgaard:
> >   
> > > I have a card of unknown (to me) brand that identifies itself as a 
> > > 1131:7133 (chipset) with 1a7f:2004 rev d1 as the subsystem ID/revision.
> > >     
> > 
> > 1131:7133 in .dk means a saa7135 or more likely a recent saa7131e.
> > The subvendor 1a7f seems to be seen the first time here, subdevice 2004
> > is only known on some Philips reference designs.

Correction for the record, link to another 1a7f:2004, but with saa7130
chip, Tena TNF5835-MFF, tuner=69, Encore ENLTV-FM (TV tuner Pro).

http://lists-archives.org/video4linux/21631-encore-enltv-fm-tv-tuner-pro.html

(If I understand also the following right, we should provide an entry
for that one too, using card=3 as example, also for gpio, but for mute
amux = LINE1 or some different gpio needs to be found. Not sure if radio
works and if it has a remote.)
 
> There is a windows driver that comes with the system. Inspecting the
> 3xhybrid.inf file reveals only tiny bits more information to me.
> Appears copyrighted by Philips Semi and is labelled "SAA713x Based -
> BDA TV Capture Driver" with a random provider name "Active Development
> Co., Ltd.".
> 
> Cards in the series are apparently called "Mercur, Tiger", "Proteus",
> "Europa (1-3), Snake, Tough, Smart, Clever" and "Europe (4.x)"
> 
> Some parts here:
> 
> ;******** Proteus *** 
> ;%PHILIPS_30.DeviceDesc% = PHILIPS_PROTEUS.NTx86,PCI
> \VEN_1131&DEV_7130&SUBSYS_20011A7F 
> ;%PHILIPS_33.DeviceDesc% = PHILIPS_PROTEUS.NTx86,PCI
> \VEN_1131&DEV_7133&SUBSYS_20011A7F 
> ;%PHILIPS_34.DeviceDesc% = PHILIPS_PROTEUS.NTx86,PCI
> \VEN_1131&DEV_7134&SUBSYS_20011A7F

Hmm, subsystem 20041A7F not listed.
>From the eeprom the card looks like Philips TIGER hybrid.
Some 3xHybrid.sys should be around then.

> ;******** PHILIPS PROTEUS x32 *** 
> [PHILIPS_PROTEUS.NTx86.CoInstallers] 
> CopyFiles     = SectionX32.CopyDll.NTx86 
> AddReg        = SectionX32.DllAddReg.NTx86 
>  
> [PHILIPS_PROTEUS.NTx86] 
> Include       = ks.inf, wdmaudio.inf, kscaptur.inf, bda.inf 
> Needs         = KS.Registration.NT, WDMAUDIO.Registration.NT,
> KSCAPTUR.Registration.NT, BDA.Installation.NT 
> CopyFiles     = SectionX32.CopyDriver.NTx86, SectionX32.CopyDll.NTx86 
> AddReg        = SectionX32.AddReg.NTx86, PHILIPS_PROTEUS.AddReg 
>  
> [PHILIPS_PROTEUS.NTx86.Services] 
> AddService    = %SERVICE_NAME_X32%, 0x00000002,
> SectionX32.ServiceInstall.NTx86
> 
> ;---- Proteus ---- 
> [PHILIPS_PROTEUS.AddReg] 
> ; Prefix will be displayed in front of the device name on every
> filter 
> HKR, "Parameters","Prefix",,%PHILIPS_CUSTOM_TUNERNAME% 
>  
> ; SmallXBar=0: XBar inputs => Tuner, Composite1, S-Video1, Composite2,
> S-Video2 
> ; SmallXBar=1: XBar inputs => Tuner, Composite1, S-Video1 
> HKR, "Parameters", "SmallXBar",0x00010001,1 
>  
> HKR, "I2C Devices", "Force Registry Settings",0x00010001,0x01 
> HKR, "VideoDecoder", "Tuner Channel",0x00010001,0x01 
> HKR, "VideoDecoder", "CVBS Channel",0x00010001,0x00 
> HKR, "VideoDecoder", "SVHS Channel",0x00010001,0x06 
> ;HKR, "VideoDecoder", "FM Radio Channel",0x00010001,0x00 
>  
> HKR, "AudioDecoder", "Tuner Channel",0x00010001,0x01 
> HKR, "AudioDecoder", "CVBS Channel",0x00010001,0x02 
> HKR, "AudioDecoder", "SVHS Channel",0x00010001,0x02 
> ;HKR, "AudioDecoder", "FM Radio Channel",0x00010001,0x02 
> ;HKR, "AudioDecoder", "XTAL",0x00010001,0x0                ;Default =
> 32MHz 

That would for example match with card=117 or 96, Philips Tiger based.

> HKR, "I2C Devices", "Number of I2C Devices",0x00010001,0x01 
> HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x03  ; Tuner ID 
> HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC0  ; Tuner slave
> addr.

Also tuner address 0xc0/0x60.

> HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86  ; Tuner IF PLL
> slave addr. 
> ;HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x0   ; Demod slave
> addr.

That doesn't say much here, a tda10046 DVB-T demod is likely on 0x10.

> ;HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x0   ; Size of add.
> data 
> ;HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x0   ; Add. data
> #1 
> ;HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x0   ; Add. data
> #2 
> ;HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x0   ; Add. data
> #3 
> 
> 
> 
> PHILIPS_33.DeviceDesc         = "PCI DTV Card"

DTV sounds like digital TV support too.

> 
> ... but not sure how helpful this is at all?
> 
> > > The card is unfortunately glued (!) inside a LCD enclosure, and I am not 
> > > able to see any further identifications on it.
> > >     
> > 
> > ;) what to say.
> >   
> ... know it sounds strange (and indeed it is). It is inside an
> otherwise well-equipped enclosure of .cn origin that basically embeds
> a low-noise PC (GA-MA78M-S2H MB w/AMD X2 5400 CPU) inside what looks
> like a normal LCD based TV.

Is support for wireless network announced too?

It has some sequences identical to the Asus WIFI card,
but this one comes only together with Asus motherboards and here is a
Gigabyte one. The WIFI card has undiscovered issues with DVB-T.
IIRC, it also comes with an USB remote, but I'm not sure.

> > > I am able to get it partially running by using "options saa7134 card=107 
> > > tuner=54" (or card 3), but it appears that changing channel via tvtime 
> > > or myth  fails roughly half the time and simply causes it to return an 
> > > invalid (or empty) video stream. Indeed, in myth, it sometimes crashes 
> > > the application.

The ENCORE_ENLTV_FM card=107 might not be sufficient to initialize it
correctly to analog mode. It also has TV amux=3. That might explain the
missing sound. Stay away from it.

If you have saa7134-alsa loaded and you have a sound card/chip on the
MB, something like sox can be used for testing.
"sox -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp"
    
> > 
> > If channel change sometimes works it is some tuner=54, but might need
> > some card specific calibration or your signal is weak.
> >   
> I don't think the signal is weak as such here, and it is also pretty
> random what channels fail. In tvtime, I can sometimes just roll
> through the inputs (tuner, composite, ...) and then the signal is
> there when the tuner is re-selected. More likely some card specifics
> that needs to be added, me thinks.

You might try with card=117 or card=96.

> > Is DVB-T or DVB-S announced too or only analog TV?
> >   
> This is not evident. The specs on the device leads me to think that
> there is at least DVB-T support, but I'm not sure.

It looks like DVB-T is supported.

Do you have two antenna input connectors or only one?

If two, both female or one male like for radio?
There might be some antenna input switching, can't say.

> > > I am also not able to capture any sound from the card, although 
> > > saa7134_alsa gets loaded as expected.
> > >     
> > 
> > Most of the recent cards don't have analog sound output to the sound
> > card anymore. The chips do provide it, but manufacturers decide against
> > to provide the connector.
> > 
> > The saa7134-alsa must be properly used and does not work automagically,
> > also if a gpio switched sound mux chip is on the card, it needs to be
> > configured correctly for sound switching. This is not visible in the
> > logs.
> >   
> OK -- so likely some setup missing too.
> > > How do I debug this, and get the driver to recognise the card properly?
> > > 
> > > Or any good hints at what the card may be? Would the i2c reveal any 
> > > further hints?
> > >     
> > 
> > To set up an invisible device is a bit odd,
> > but copy and paste "dmesg" output after loading the driver with
> > i2c_scan=1 enabled ("modinfo saa7134") might help on some further
> > guessing.
> >   
> Here's the relevant clip:

We need also the output from loading and detecting the tuner.
Most important tuner i2c address.

My card guessing is likely wrong based on your above provided driver
information. The eeprom says tuner is at 0xc2/0x61 !

For DVB-T we need the correct tuner address, for analog it is
autodetected.

Card=81 Philips Tiger would be better then.

If two female antenna connectors, maybe card=78 Asus P7131 Dual.
On that design radio and DVB-T are on the second and upper from the slot
connector.

> [   46.297474] saa7130/34: v4l2 driver version 0.2.14 loaded
> [   46.297544] ACPI: PCI Interrupt 0000:03:07.0[A] -> GSI 21 (level,
> low) -> IRQ 21
> [   46.297552] saa7133[0]: found at 0000:03:07.0, rev: 209, irq: 21,
> latency: 32, mmio: 0xfdcff000
> [   46.297558] saa7133[0]: subsystem: 1a7f:2004, board:
> UNKNOWN/GENERIC [card=0,autodetected]
> [   46.297566] saa7133[0]: board init: gpio is ac6ee00
-------------------------------------------------^^^^^^^
The first 8 gpio pins are 0. This might indicate DVB-T.
The gpio21 is 0 too. Can be used for analog/radio/digital AGC switching
and can also trigger antenna input switching.

> [   46.311610] usbcore: registered new interface driver libusual
> [   46.423269] Initializing USB Mass Storage driver...
> [   46.426251] scsi6 : SCSI emulation for USB Mass Storage devices
> [   46.427460] usbcore: registered new interface driver usb-storage
> [   46.427465] USB Mass Storage support registered.
> [   46.427469] usb-storage: device found at 4
> [   46.427470] usb-storage: waiting for device to settle before
> scanning
> [   46.430243] saa7133[0]: i2c eeprom 00: 7f 1a 04 20 54 20 1c 00 43
> 43 a9 1c 55 d2 b2 92
> [   46.430250] saa7133[0]: i2c eeprom 10: 00 df 86 0f ff 20 ff ff ff
> ff ff ff ff ff ff ff
> [   46.430255] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 ff 01 03 08
> ff 00 8f ff ff ff ff
> [   46.430260] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [   46.430264] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15
> 08 ff ff ff ff ff ff
> [   46.430269] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff 5f 84
> ff 31 30 4d 4f 4f 4e
> [   46.430273] saa7133[0]: i2c eeprom 60: 53 50 44 41 31 30 30 ff 50
> ff ff ff ff ff ff ff
> [   46.430278] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [   46.446649] saa7133[0]: i2c scan: found device @ 0x10  [???]

That would be the tda10046 DVB-T demod.

> [   46.462198] saa7133[0]: i2c scan: found device @ 0x96  [???]

Tuner=54 analog demod.

> [   46.473848] saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
> [   46.496852] saa7133[0]: registered device video0 [v4l2]
> [   46.498102] saa7133[0]: registered device vbi0
> [   46.504905] lirc_dev: IR Remote Control driver registered, at major
> 61 
> [   46.520467] ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level,
> low) -> IRQ 18
> [   46.535450] 
> [   46.535452] lirc_mceusb2: Philips eHome USB IR Transciever and
> Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $
> [   46.535455] lirc_mceusb2: Daniel Melander <lirc@rajidae.se>, Martin
> Blatter <martin_a_blatter@yahoo.com>
> [   46.547154] saa7134 ALSA driver for DMA sound loaded
> [   46.547182] saa7133[0]/alsa: saa7133[0] at 0xfdcff000 irq 21
> registered as card -2
> [   46.556138] hda_codec: Unknown model for ALC882, trying auto-probe
> from BIOS...
> [   46.594717] ACPI: PCI Interrupt 0000:01:05.1[B] -> GSI 19 (level,
> low) -> IRQ 20
> [   46.594747] PCI: Setting latency timer of device 0000:01:05.1 to 64
> [   46.736190] usb 3-2: reset full speed USB device using ohci_hcd and
> address 4
> [   46.947578] lirc_dev: lirc_register_plugin: sample_rate: 0
> [   46.951560] lirc_mceusb2[4]: Topseed eHome Infrared Transceiver on
> usb3:4
> [   46.951584] usbcore: registered new interface driver lirc_mceusb2
> [   46.951689] usbcore: registered new interface driver hiddev
> 
> Full log is temporarily here:
> 
>    http://www.b4net.dk/dmesg.log2
> 
> There is also a http://www.b4net.dk/dmesg.log when run with my
> "normal" parameters for getting the card somehow working. Sometimes,
> randomly (as in the log above) there is a also a whole slew of dsp
> errors, which again points in the direction of some setup failing.

Ah good, here we can see tuner address is 0x61.
TV amux is for sure wrong on card=107.

If you have sometimes a flashing picture with card=81 or 78 on analog
TV, or in case you get audio working and hear humming sound or you get
DVB-T working, but unstable lock, such could indicate that it has a
LowNoiseAmplifier that needs to be correctly configured, that is another
story.

Good luck on the invisible unknown card.

Cheers,
Hermann



--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Seeking help for a 713x based card

[Per Baekgaard]

Thanks again -- quite a lot to digest.

I was working late yesterday, so unfortunately I was copying some 
incorrect lines from the 3xhybrid.inf file ;-(

The correct lines would be these ones, I think:

;******** Mercur, Tiger,... ***
;%PHILIPS_30.DeviceDesc% = 
PHILIPS_30.NTx86,PCI\VEN_1131&DEV_7130&SUBSYS_20181A7F
;%PHILIPS_33.DeviceDesc% = 
PHILIPS_33.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_20181A7F
;%PHILIPS_34.DeviceDesc% = 
PHILIPS_34.NTx86,PCI\VEN_1131&DEV_7134&SUBSYS_20181A7F
 
;******** Europa (1-3), Snake, Tough, Smart, Clever ***
%PHILIPS_30.DeviceDesc% = 
PHILIPS_30.NTx86,PCI\VEN_1131&DEV_7130&SUBSYS_20041A7F
%PHILIPS_33.DeviceDesc% = 
PHILIPS_33.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_20041A7F
%PHILIPS_34.DeviceDesc% = 
PHILIPS_34.NTx86,PCI\VEN_1131&DEV_7134&SUBSYS_20041A7F

;******** SAA7133 x32 ***
[PHILIPS_33.NTx86.CoInstallers]
CopyFiles     = SectionX32.CopyDll.NTx86
AddReg        = SectionX32.DllAddReg.NTx86
 
[PHILIPS_33.NTx86]
Include       = ks.inf, wdmaudio.inf, kscaptur.inf, bda.inf
Needs         = KS.Registration.NT, WDMAUDIO.Registration.NT, 
KSCAPTUR.Registration.NT, BDA.Installation.NT
CopyFiles     = SectionX32.CopyDriver.NTx86, SectionX32.CopyDll.NTx86
AddReg        = SectionX32.AddReg.NTx86, PHILIPS_33.AddReg
 
[PHILIPS_33.NTx86.Services]
AddService    = %SERVICE_NAME_X32%, 0x00000002, 
SectionX32.ServiceInstall.NTx86

;******** General DLL Registry Entries ***
;
 
[SectionX32.DllAddReg.NTx86]
HKR,,CoInstallers32,0x00010000,"34CoInstaller.dll, CoInstallerEntry"
 
 
;
;******** General Driver Registry Entries ***
;
 
[SectionX32.AddReg.NTx86]
 
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,3xHybrid.sys
 
; --- Registry Entries For Audio Capture ---
 
HKR,,Driver,,3xHybrid.sys
HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook"
 
HKR,Drivers,SubClasses,,"wave,mixer"
HKR,Drivers\wave\wdmaud.drv,Driver,,wdmaud.drv
HKR,Drivers\mixer\wdmaud.drv,Driver,,wdmaud.drv
HKR,Drivers\wave\wdmaud.drv,Description,,%PHILIPS.AudioDeviceDesc%
HKR,Drivers\mixer\wdmaud.drv,Description,,%PHILIPS.AudioDeviceDesc%
 
; add audio input and output pinnames
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_IN_PIN%,"Name",,"Analog 
Audioinput"
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_OUT_PIN%,"Name",,"Audio" 

HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_VIDEO_ITU_PIN%,"Name",,"Analog 
ITU Video"
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_I2S_PIN%,"Name",,"I2S 
Audio"
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_AES_PIN%,"Name",,"MPEG 
Audio ES"
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_VES_PIN%,"Name",,"MPEG 
Video ES"
HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_PS_PIN%,"Name",, 
"MPEG2 Program"

;---- SAA7133 ----
[PHILIPS_33.AddReg]
 
; Prefix will be displayed in front of the device name on every filter
HKR, "Parameters","Prefix",,%PHILIPS_CUSTOM_TUNERNAME%
 
; Reduces second pair of video/audio inputs
HKR, "Parameters","SmallXBar",0x00010001,0x01



... so much for trying to reduce the amount of data. Apologies.

The entire file is here:

   http://www.b4net.dk/3xhybrid.inf

hermann pitton wrote:
> Hmm, subsystem 20041A7F not listed.
> From the eeprom the card looks like Philips TIGER hybrid.
> Some 3xHybrid.sys should be around then.
>   
Mea culpa. It is not a Proteus system but as you point out maybe a Tiger 
derivative of some sort "Snake, Tough, Smart, Clever" -- whatever that is!

> Is support for wireless network announced too?
>   
On the motherboard, yes, but not on the tuner as far as I can see.
> IIRC, it also comes with an USB remote, but I'm not sure.
>   
Yes, there is a remote, but not USB based, as far as I can tell.
> If you have saa7134-alsa loaded and you have a sound card/chip on the
> MB, something like sox can be used for testing.
> "sox -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp"
>   
I've tried something similar (arecord|aplay) but it doens't seem to 
capture any sound at all.
>   
> You might try with card=117 or card=96.
>   
Will do -- makes sense even if not a Proteus card (as I apparently 
copied some incorrect lines above)?
> Do you have two antenna input connectors or only one?
>   
One for this tuner only. There is a normal RCA video connector, a 
S-video of some sort and a mini-jack for sound input, I believe.
> Card=81 Philips Tiger would be better then.
>   
I'll try that too.
> That would be the tda10046 DVB-T demod.
>
>   
> Tuner=54 analog demod.
>   
So card 81 and tuner 54 would be a good quess then?
> Ah good, here we can see tuner address is 0x61.
> TV amux is for sure wrong on card=107.
>   
Yep... looks like it is ;-)
> If you have sometimes a flashing picture with card=81 or 78 on analog
> TV, or in case you get audio working and hear humming sound or you get
> DVB-T working, but unstable lock, such could indicate that it has a
> LowNoiseAmplifier that needs to be correctly configured, that is another
> story.
>   
I'll try and report back on my findings -- mainly card 81, 117 or 96 
then? Or are there other tiger based ones I should try?


-- Per.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Pinnacle PCTV Remote

[John Ortega]

Hello,

Does anyone have the remote working for the Pinnacle PCTV usb device. I've
got the TV working. But, the remote doesn't work at all.

Thanks,
John

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV Remote

[Devin Heitmueller]

On Fri, Jul 18, 2008 at 1:17 AM, John Ortega
<jortega@listpropertiesnow.com> wrote:
> Hello,
>
> Does anyone have the remote working for the Pinnacle PCTV usb device. I've
> got the TV working. But, the remote doesn't work at all.
>
> Thanks,
> John

If you're talking about the Pinnacle PCTV HD Pro Stick (800e), then I
can tell you outright that the remote control support is not
implemented.

I have wrote some code for it but never got around to getting it fully
debugged or checking it in.

I'm pretty sure Markus's em28xx driver does support it though
(mcentral.de), although I've never tried it myself.

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Seeking help for a 713x based card

[hermann pitton]

Hi,

Am Freitag, den 18.07.2008, 00:09 +0200 schrieb Per Baekgaard:
> Thanks again -- quite a lot to digest.
> 
> I was working late yesterday, so unfortunately I was copying some 
> incorrect lines from the 3xhybrid.inf file ;-(
> 
> The correct lines would be these ones, I think:
> 
> ;******** Mercur, Tiger,... ***
> ;%PHILIPS_30.DeviceDesc% = 
> PHILIPS_30.NTx86,PCI\VEN_1131&DEV_7130&SUBSYS_20181A7F
> ;%PHILIPS_33.DeviceDesc% = 
> PHILIPS_33.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_20181A7F
> ;%PHILIPS_34.DeviceDesc% = 
> PHILIPS_34.NTx86,PCI\VEN_1131&DEV_7134&SUBSYS_20181A7F
>  
> ;******** Europa (1-3), Snake, Tough, Smart, Clever ***
> %PHILIPS_30.DeviceDesc% = 
> PHILIPS_30.NTx86,PCI\VEN_1131&DEV_7130&SUBSYS_20041A7F
> %PHILIPS_33.DeviceDesc% = 
> PHILIPS_33.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_20041A7F
> %PHILIPS_34.DeviceDesc% = 
> PHILIPS_34.NTx86,PCI\VEN_1131&DEV_7134&SUBSYS_20041A7F

not sure in any way, could be some Mini PCI stuff.

> ;******** SAA7133 x32 ***
> [PHILIPS_33.NTx86.CoInstallers]
> CopyFiles     = SectionX32.CopyDll.NTx86
> AddReg        = SectionX32.DllAddReg.NTx86
>  
> [PHILIPS_33.NTx86]
> Include       = ks.inf, wdmaudio.inf, kscaptur.inf, bda.inf
> Needs         = KS.Registration.NT, WDMAUDIO.Registration.NT, 
> KSCAPTUR.Registration.NT, BDA.Installation.NT
> CopyFiles     = SectionX32.CopyDriver.NTx86, SectionX32.CopyDll.NTx86
> AddReg        = SectionX32.AddReg.NTx86, PHILIPS_33.AddReg
>  
> [PHILIPS_33.NTx86.Services]
> AddService    = %SERVICE_NAME_X32%, 0x00000002, 
> SectionX32.ServiceInstall.NTx86
> 
> ;******** General DLL Registry Entries ***
> ;
>  
> [SectionX32.DllAddReg.NTx86]
> HKR,,CoInstallers32,0x00010000,"34CoInstaller.dll, CoInstallerEntry"
>  
> 
> ;
> ;******** General Driver Registry Entries ***
> ;
>  
> [SectionX32.AddReg.NTx86]
>  
> HKR,,DevLoader,,*NTKERN
> HKR,,NTMPDriver,,3xHybrid.sys
>  
> ; --- Registry Entries For Audio Capture ---
>  
> HKR,,Driver,,3xHybrid.sys
> HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook"
>  
> HKR,Drivers,SubClasses,,"wave,mixer"
> HKR,Drivers\wave\wdmaud.drv,Driver,,wdmaud.drv
> HKR,Drivers\mixer\wdmaud.drv,Driver,,wdmaud.drv
> HKR,Drivers\wave\wdmaud.drv,Description,,%PHILIPS.AudioDeviceDesc%
> HKR,Drivers\mixer\wdmaud.drv,Description,,%PHILIPS.AudioDeviceDesc%
>  
> ; add audio input and output pinnames
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_IN_PIN%,"Name",,"Analog 
> Audioinput"
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_OUT_PIN%,"Name",,"Audio" 
> 
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_VIDEO_ITU_PIN%,"Name",,"Analog 
> ITU Video"
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_ANLG_AUDIO_I2S_PIN%,"Name",,"I2S 
> Audio"
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_AES_PIN%,"Name",,"MPEG 
> Audio ES"
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_VES_PIN%,"Name",,"MPEG 
> Video ES"
> HKLM,SYSTEM\CurrentControlSet\Control\MediaCategories\%AVSTREAM_MPEG_PS_PIN%,"Name",, 
> "MPEG2 Program"
> 
> ;---- SAA7133 ----
> [PHILIPS_33.AddReg]
>  
> ; Prefix will be displayed in front of the device name on every filter
> HKR, "Parameters","Prefix",,%PHILIPS_CUSTOM_TUNERNAME%
>  
> ; Reduces second pair of video/audio inputs
> HKR, "Parameters","SmallXBar",0x00010001,0x01
> 
> 
> 
> ... so much for trying to reduce the amount of data. Apologies.
> 
> The entire file is here:
> 
>    http://www.b4net.dk/3xhybrid.inf
> 
> hermann pitton wrote:
> > Hmm, subsystem 20041A7F not listed.
> > From the eeprom the card looks like Philips TIGER hybrid.
> > Some 3xHybrid.sys should be around then.
> >   
> Mea culpa. It is not a Proteus system but as you point out maybe a Tiger 
> derivative of some sort "Snake, Tough, Smart, Clever" -- whatever that is!
> 
> > Is support for wireless network announced too?
> >   
> On the motherboard, yes, but not on the tuner as far as I can see.
> > IIRC, it also comes with an USB remote, but I'm not sure.
> >   
> Yes, there is a remote, but not USB based, as far as I can tell.
> > If you have saa7134-alsa loaded and you have a sound card/chip on the
> > MB, something like sox can be used for testing.
> > "sox -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp"
> >   
> I've tried something similar (arecord|aplay) but it doens't seem to 
> capture any sound at all.
> >   
> > You might try with card=117 or card=96.
> >   
> Will do -- makes sense even if not a Proteus card (as I apparently 
> copied some incorrect lines above)?
> > Do you have two antenna input connectors or only one?
> >   
> One for this tuner only. There is a normal RCA video connector, a 
> S-video of some sort and a mini-jack for sound input, I believe.
> > Card=81 Philips Tiger would be better then.
> >   
> I'll try that too.
> > That would be the tda10046 DVB-T demod.
> >
> >   
> > Tuner=54 analog demod.
> >   
> So card 81 and tuner 54 would be a good quess then?
> > Ah good, here we can see tuner address is 0x61.
> > TV amux is for sure wrong on card=107.
> >   
> Yep... looks like it is ;-)
> > If you have sometimes a flashing picture with card=81 or 78 on analog
> > TV, or in case you get audio working and hear humming sound or you get
> > DVB-T working, but unstable lock, such could indicate that it has a
> > LowNoiseAmplifier that needs to be correctly configured, that is another
> > story.
> >   
> I'll try and report back on my findings -- mainly card 81, 117 or 96 
> then? Or are there other tiger based ones I should try?
> 
> 
> -- Per.
> 

Most interesting should be next what you get on trying on DVB-T.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list