Problems with Pinnacle 310i (saa7134) and recent kernels

Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hello,
I have a problem with my Pinnacle PCTV Hybrid Pro PCI using recent kernels. With
 2.6.29 both dvbscan and MPlayer stopped to work giving:

dvbscan:
Unable to query frontend status

mplayer:
MPlayer SVN-r29351-4.2.4 (C) 2000-2009 MPlayer Team

Not able to lock to the signal on the given frequency, timeout: 30
dvb_tune, TUNING FAILED

Now with 2.6.30.1 Kaffeine sometimes works and sometimes not, going in timeout.
This is the hardware:

01:02.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Vi
deo Broadcast Decoder (rev d1)
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR- INTx-
        Latency: 32 (63750ns min, 63750ns max)
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at cfddf800 (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=3 PME-
        Kernel driver in use: saa7134
        Kernel modules: saa7134

dmesg output:

saa7130/34: v4l2 driver version 0.2.15 loaded
saa7134 0000:01:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 0xcfddf
800
saa7133[0]: subsystem: ffff:ffff, board: Pinnacle PCTV 310i [card=101,insmod opt
ion]
saa7133[0]: board init: gpio is 600c000
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom read error (err=-5)
tuner 1-004b: chip found @ 0x96 (saa7133[0])
tda829x 1-004b: setting tuner address to 61
tda829x 1-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[0])
DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
saa7134 ALSA driver for DMA sound loaded
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]/alsa: saa7133[0] at 0xcfddf800 irq 22 registered as card -1
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok

Can anyone help me getting my tyner working again?
Thanks, avljawrowski

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

[-- Attachment #1: Type: text/plain, Size: 4279 bytes --]

Hi,

Am Samstag, den 18.07.2009, 14:05 +0000 schrieb Avl Jawrowski:
> Hello,
> I have a problem with my Pinnacle PCTV Hybrid Pro PCI using recent kernels. With
>  2.6.29 both dvbscan and MPlayer stopped to work giving:
> 
> dvbscan:
> Unable to query frontend status
> 
> mplayer:
> MPlayer SVN-r29351-4.2.4 (C) 2000-2009 MPlayer Team
> 
> Not able to lock to the signal on the given frequency, timeout: 30
> dvb_tune, TUNING FAILED
> 
> Now with 2.6.30.1 Kaffeine sometimes works and sometimes not, going in timeout.
> This is the hardware:
> 
> 01:02.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Vi
> deo Broadcast Decoder (rev d1)
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
> ping- SERR- FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
> - <MAbort- >SERR- <PERR- INTx-
>         Latency: 32 (63750ns min, 63750ns max)
>         Interrupt: pin A routed to IRQ 22
>         Region 0: Memory at cfddf800 (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=3 PME-
>         Kernel driver in use: saa7134
>         Kernel modules: saa7134
> 
> dmesg output:
> 
> saa7130/34: v4l2 driver version 0.2.15 loaded
> saa7134 0000:01:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 0xcfddf
> 800
> saa7133[0]: subsystem: ffff:ffff, board: Pinnacle PCTV 310i [card=101,insmod opt
> ion]

i2c fails to read the subsystem from the eeprom.

> saa7133[0]: board init: gpio is 600c000
> IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]: i2c eeprom read error (err=-5)

Confirmed here again for the complete eeprom content.

> tuner 1-004b: chip found @ 0x96 (saa7133[0])
> tda829x 1-004b: setting tuner address to 61
> tda829x 1-004b: type set to tda8290+75a

Nothing about the IR, but at least all tuner modules seem to be
correctly loaded.

> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[0])
> DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
> saa7134 ALSA driver for DMA sound loaded
> IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]/alsa: saa7133[0] at 0xcfddf800 irq 22 registered as card -1
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
> 
> Can anyone help me getting my tyner working again?
> Thanks, avljawrowski
> 

What was your last good working kernel and was your eeprom already
failing there too, or is that new?

Usually such is caused by bad contacts of the PCI slot or by a bad PSU,
but we have reports from a Pinnacle 50i with the same i2c remote.

It has i2c troubles (ARB_LOST) and then also problems on loading the
tuner modules correctly. With disable_ir=1 for saa7134 it became at
least somewhat usable again.

But for the 310i is another problem reported starting with kernel
2.6.26.

The 310i and the HVR1110 are the only cards with LowNoiseAmplifier
config = 1. Before 2.6.26 two buffers were sent to the tuner at 0x61,
doing some undocumented LNA configuration, since 2.6.26 they go to the
analog IF demodulator tda8290 at 0x4b.

This was bisected here on the list and is wrong for the 300i.
Thread is "2.6.26 regression ..."

The HVR1110 using the same new configuration seems to come in variants
with and without LNA and nobody knows, how to make a difference for
those cards. At least still no reports about troubles with the new LNA
configuration there.

The attached patch against recent mercurial master v4l-dvb at
linuxtv.org tries to restore the pre 2.6.26 behaviour for DVB-T on the
300i.

It changes also the i2c remote address of the Upmost Purple TV from 0x7a
to 0x3d, since recent i2c on >= 2.6.30 complains about it as invalid
7-bit address, just in case.

Good luck,

Hermann








[-- Attachment #2: Type: text/x-patch, Size: 1925 bytes --]

diff -r d277b05c41fe linux/drivers/media/video/ir-kbd-i2c.c
--- a/linux/drivers/media/video/ir-kbd-i2c.c	Sun Jul 12 11:04:15 2009 -0300
+++ b/linux/drivers/media/video/ir-kbd-i2c.c	Sun Jul 19 19:44:30 2009 +0200
@@ -601,7 +601,7 @@
 	*/
 
 	static const int probe_bttv[] = { 0x1a, 0x18, 0x4b, 0x64, 0x30, -1};
-	static const int probe_saa7134[] = { 0x7a, 0x47, 0x71, 0x2d, -1 };
+	static const int probe_saa7134[] = { 0x3d, 0x47, 0x71, 0x2d, -1 };
 	static const int probe_em28XX[] = { 0x30, 0x47, -1 };
 	static const int probe_cx88[] = { 0x18, 0x6b, 0x71, -1 };
 	static const int probe_cx23885[] = { 0x6b, -1 };
diff -r d277b05c41fe linux/drivers/media/video/saa7134/saa7134-dvb.c
--- a/linux/drivers/media/video/saa7134/saa7134-dvb.c	Sun Jul 12 11:04:15 2009 -0300
+++ b/linux/drivers/media/video/saa7134/saa7134-dvb.c	Sun Jul 19 19:44:30 2009 +0200
@@ -580,6 +580,13 @@
 	.switch_addr = 0x4b
 };
 
+static struct tda827x_config tda827x_cfg_1_310i = {
+	.init = philips_tda827x_tuner_init,
+	.sleep = philips_tda827x_tuner_sleep,
+	.config = 1,
+	.switch_addr = 0x61
+};
+
 static struct tda827x_config tda827x_cfg_2 = {
 	.init = philips_tda827x_tuner_init,
 	.sleep = philips_tda827x_tuner_sleep,
@@ -1139,7 +1146,7 @@
 		break;
 	case SAA7134_BOARD_PINNACLE_PCTV_310i:
 		if (configure_tda827x_fe(dev, &pinnacle_pctv_310i_config,
-					 &tda827x_cfg_1) < 0)
+					 &tda827x_cfg_1_310i) < 0)
 			goto dettach_frontend;
 		break;
 	case SAA7134_BOARD_HAUPPAUGE_HVR1110:
diff -r d277b05c41fe linux/drivers/media/video/saa7134/saa7134-input.c
--- a/linux/drivers/media/video/saa7134/saa7134-input.c	Sun Jul 12 11:04:15 2009 -0300
+++ b/linux/drivers/media/video/saa7134/saa7134-input.c	Sun Jul 19 19:44:30 2009 +0200
@@ -737,7 +737,7 @@
 	struct i2c_board_info info;
 	struct IR_i2c_init_data init_data;
 	const unsigned short addr_list[] = {
-		0x7a, 0x47, 0x71, 0x2d,
+		0x3d, 0x47, 0x71, 0x2d,
 		I2C_CLIENT_END
 	};
 

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi, thank you!

hermann pitton <hermann-pitton <at> arcor.de> writes:

> > tuner 1-004b: chip found @ 0x96 (saa7133[0])
> > tda829x 1-004b: setting tuner address to 61
> > tda829x 1-004b: type set to tda8290+75a
> 
> Nothing about the IR, but at least all tuner modules seem to be
> correctly loaded.

Im not using the IR because for now I dont need it, but I will try it.
 
> What was your last good working kernel and was your eeprom already
> failing there too, or is that new?

I don't remember the last working kernel.
I tried to recompile 2.6.25 but I obtain this error:

DVB: Unable to find symbol tda10046_attach()
saa7133[0]/dvb: frontend initialization failed

The eeprom was working a few months ago giving this messages:

saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 19, latency: 64, mmio: 0xcfddf
800
saa7133[0]: subsystem: ffff:ffff, board: UNKNOWN/GENERIC [card=0,autodetected]
saa7133[0]: board init: gpio is 600e000
saa7133[0]: i2c eeprom 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0

Even then the card was not recognised.

> Usually such is caused by bad contacts of the PCI slot or by a bad PSU,
> but we have reports from a Pinnacle 50i with the same i2c remote.
> 
> It has i2c troubles (ARB_LOST) and then also problems on loading the
> tuner modules correctly. With disable_ir=1 for saa7134 it became at
> least somewhat usable again.
>
> But for the 310i is another problem reported starting with kernel
> 2.6.26.
> 
> The 310i and the HVR1110 are the only cards with LowNoiseAmplifier
> config = 1. Before 2.6.26 two buffers were sent to the tuner at 0x61,
> doing some undocumented LNA configuration, since 2.6.26 they go to the
> analog IF demodulator tda8290 at 0x4b.
> 
> This was bisected here on the list and is wrong for the 300i.
> Thread is "2.6.26 regression ..."
> 
> The HVR1110 using the same new configuration seems to come in variants
> with and without LNA and nobody knows, how to make a difference for
> those cards. At least still no reports about troubles with the new LNA
> configuration there.
> 
> The attached patch against recent mercurial master v4l-dvb at
> linuxtv.org tries to restore the pre 2.6.26 behaviour for DVB-T on the
> 300i.
> 
> It changes also the i2c remote address of the Upmost Purple TV from 0x7a
> to 0x3d, since recent i2c on >= 2.6.30 complains about it as invalid
> 7-bit address, just in case.
> 
> Good luck,
> 
> Hermann
> 
> 
> Attachment (saa7134-try_to_improve_the_310i.patch): text/x-patch, 1925 bytes

I tried the patch with 2.6.30.2 on v4l-dvb-1cb6f19d2c9d, but I get only some
errors (I have rebooted):

videodev: exports duplicate symbol video_unregister_device (owned by kernel)
v4l2_common: exports duplicate symbol v4l2_chip_ident_i2c_client (owned by kerne
l)
saa7134: Unknown symbol v4l_bound_align_image

I get these errors even not applying the patch.

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Montag, den 20.07.2009, 23:30 +0000 schrieb Avl Jawrowski:
> Hi, thank you!
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > > tuner 1-004b: chip found @ 0x96 (saa7133[0])
> > > tda829x 1-004b: setting tuner address to 61
> > > tda829x 1-004b: type set to tda8290+75a
> > 
> > Nothing about the IR, but at least all tuner modules seem to be
> > correctly loaded.
> 
> Im not using the IR because for now I dont need it, but I will try it.
>  
> > What was your last good working kernel and was your eeprom already
> > failing there too, or is that new?
> 
> I don't remember the last working kernel.
> I tried to recompile 2.6.25 but I obtain this error:
> 
> DVB: Unable to find symbol tda10046_attach()
> saa7133[0]/dvb: frontend initialization failed
> 
> The eeprom was working a few months ago giving this messages:
> 
> saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 19, latency: 64, mmio: 0xcfddf
> 800
> saa7133[0]: subsystem: ffff:ffff, board: UNKNOWN/GENERIC [card=0,autodetected]
> saa7133[0]: board init: gpio is 600e000
> saa7133[0]: i2c eeprom 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> 
> Even then the card was not recognised.
> 
> > Usually such is caused by bad contacts of the PCI slot or by a bad PSU,
> > but we have reports from a Pinnacle 50i with the same i2c remote.
> > 
> > It has i2c troubles (ARB_LOST) and then also problems on loading the
> > tuner modules correctly. With disable_ir=1 for saa7134 it became at
> > least somewhat usable again.
> >
> > But for the 310i is another problem reported starting with kernel
> > 2.6.26.
> > 
> > The 310i and the HVR1110 are the only cards with LowNoiseAmplifier
> > config = 1. Before 2.6.26 two buffers were sent to the tuner at 0x61,
> > doing some undocumented LNA configuration, since 2.6.26 they go to the
> > analog IF demodulator tda8290 at 0x4b.
> > 
> > This was bisected here on the list and is wrong for the 300i.
> > Thread is "2.6.26 regression ..."
> > 
> > The HVR1110 using the same new configuration seems to come in variants
> > with and without LNA and nobody knows, how to make a difference for
> > those cards. At least still no reports about troubles with the new LNA
> > configuration there.
> > 
> > The attached patch against recent mercurial master v4l-dvb at
> > linuxtv.org tries to restore the pre 2.6.26 behaviour for DVB-T on the
> > 300i.
> > 
> > It changes also the i2c remote address of the Upmost Purple TV from 0x7a
> > to 0x3d, since recent i2c on >= 2.6.30 complains about it as invalid
> > 7-bit address, just in case.
> > 
> > Good luck,
> > 
> > Hermann
> > 
> > 
> > Attachment (saa7134-try_to_improve_the_310i.patch): text/x-patch, 1925 bytes
> 
> I tried the patch with 2.6.30.2 on v4l-dvb-1cb6f19d2c9d, but I get only some
> errors (I have rebooted):
> 
> videodev: exports duplicate symbol video_unregister_device (owned by kernel)
> v4l2_common: exports duplicate symbol v4l2_chip_ident_i2c_client (owned by kerne
> l)
> saa7134: Unknown symbol v4l_bound_align_image
> 
> I get these errors even not applying the patch.
> 

there is no excuse for getting errors on linux ;)

Where you got this card from and did it ever work on the same machine
with m$ stuff?

Clean up your module mess, read again, and if the eeprom has still
nothing to tell than 1 for all, get rid of it.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi,

hermann pitton <hermann-pitton <at> arcor.de> writes:

> there is no excuse for getting errors on linux ;)
> 
> Where you got this card from and did it ever work on the same machine
> with m$ stuff?

I don't have m$ stuff.

> Clean up your module mess, read again, and if the eeprom has still
> nothing to tell than 1 for all, get rid of it.

The errors were caused by a statically compiled v4l module.
However the patch seems makes no difference. Maybe it make working
the EPG but I haven't test it enough because the card works occasionally.

Is the eeprom so important? With a certain kernel configuration (all modules
compiled) gives no errors but only "f"s:

Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.15 loaded
saa7134 0000:01:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
saa7133[0]: found at 0000:01:01.0, rev: 209, irq: 21, latency: 32, mmio:
0xcfddf800
saa7133[0]: subsystem: ffff:ffff, board: Pinnacle PCTV 310i [card=101,insmod
option]
saa7133[0]: board init: gpio is 600e000
IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner 1-004b: chip found @ 0x96 (saa7133[0])
tda829x 1-004b: setting tuner address to 61
tda829x 1-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[0])
DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
saa7134 ALSA driver for DMA sound loaded
IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]/alsa: saa7133[0] at 0xcfddf800 irq 21 registered as card -1

But now the card don't works not even with Kaffeine:

/dev/dvb/adapter0/frontend0 : opened ( Philips TDA10046H DVB-T ) (0ms)
0 EPG plugins loaded for device 0:0.
Loaded epg data : 0 events (0 msecs)
DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such file or directory
Using DVB device 0:0 "Philips TDA10046H DVB-T"
Not able to lock to the signal on the given frequency
Frontend closed
Tuning delay: 1701 ms

I think the occasional nonfunctional are caused by this error:

IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs

Is it possible?

The option disable_ir=1 has no effect. Changing PCI slot makes no difference.
Anyway with w_scan and Kaffeine in normal conditions the tuner works almost
always.

> Cheers,
> Hermann

Thank you!

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Mittwoch, den 22.07.2009, 12:41 +0000 schrieb Avl Jawrowski:
> Hi,
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > there is no excuse for getting errors on linux ;)
> > 
> > Where you got this card from and did it ever work on the same machine
> > with m$ stuff?
> 
> I don't have m$ stuff.

also fine. We can exclude the eeprom was messed up by windows toys.

> > Clean up your module mess, read again, and if the eeprom has still
> > nothing to tell than 1 for all, get rid of it.
> 
> The errors were caused by a statically compiled v4l module.
> However the patch seems makes no difference. Maybe it make working
> the EPG but I haven't test it enough because the card works occasionally.

As said, 2.6.25 is reported working fine without LNA or other issues.
If that doesn't work, there are issues with your card itself or other
hardware environment involved.

> Is the eeprom so important? With a certain kernel configuration (all modules
> compiled) gives no errors but only "f"s:

The eeprom content is not important on that card at all, except for auto
detection, but flaky eeprom read outs likely indicate more and other
hardware trouble.

If it seems to deliver stable results now, you can even try to re-flash
it with rewrite_eeprom.pl in v4l2-apps/util. Read the instructions on
top of it. 

> Linux video capture interface: v2.00
> saa7130/34: v4l2 driver version 0.2.15 loaded
> saa7134 0000:01:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
> saa7133[0]: found at 0000:01:01.0, rev: 209, irq: 21, latency: 32, mmio:
> 0xcfddf800
> saa7133[0]: subsystem: ffff:ffff, board: Pinnacle PCTV 310i [card=101,insmod
> option]
> saa7133[0]: board init: gpio is 600e000
> IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]: i2c eeprom 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> tuner 1-004b: chip found @ 0x96 (saa7133[0])
> tda829x 1-004b: setting tuner address to 61
> tda829x 1-004b: type set to tda8290+75a
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[0])
> DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
> saa7134 ALSA driver for DMA sound loaded
> IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]/alsa: saa7133[0] at 0xcfddf800 irq 21 registered as card -1
> 
> But now the card don't works not even with Kaffeine:

Hm, with the patch on current v4l-dvb and 2.6.30 something? On 2.6.25
current v4l-dvb won't compile anymore and you should try that kernel
without any changes.

> /dev/dvb/adapter0/frontend0 : opened ( Philips TDA10046H DVB-T ) (0ms)
> 0 EPG plugins loaded for device 0:0.
> Loaded epg data : 0 events (0 msecs)
> DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such file or directory
> Using DVB device 0:0 "Philips TDA10046H DVB-T"
> Not able to lock to the signal on the given frequency
> Frontend closed
> Tuning delay: 1701 ms

Also increase tuning delay to 5000 ms and check for different signal and
SNR values. In that mentioned "2.6.26 regression ..." thread analog TV
functionality was fully restored by a similar hack, but also lots of
changes to the drivers since 2.6.25.  

> I think the occasional nonfunctional are caused by this error:
> 
> IRQ 21/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> 
> Is it possible?

We see that hint on almost all drivers since 2.6.29 and not using that
IRQ flag anymore did not make any difference so far, for what I can
tell.

> The option disable_ir=1 has no effect. Changing PCI slot makes no difference.
> Anyway with w_scan and Kaffeine in normal conditions the tuner works almost
> always.

Thanks for your reports and sorry for not having a final conclusion yet.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

hermann pitton <hermann-pitton <at> arcor.de> writes:

> If it seems to deliver stable results now, you can even try to re-flash
> it with rewrite_eeprom.pl in v4l2-apps/util. Read the instructions on
> top of it. 

With 2.6.30 it's stable. I've reflashed the eeprom and now the card is
autodetected:

saa7130/34: v4l2 driver version 0.2.15 loaded
saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 
0xcfddf800
saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i 
[card=101,autodetected]
saa7133[0]: board init: gpio is 600e000
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2e 15 13 ff ff
saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2
saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 03 c5 e8 9d
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
i2c-adapter i2c-0: Invalid 7-bit address 0x7a
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tda829x 0-004b: setting tuner address to 61
tda829x 0-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[0])
DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok

However it works still only with Kaffeine and w_scan.
dvbscan (last mercurial) give:

Unable to query frontend status

And with 2.6.31 (same configuration) appears this new error:

i2c-adapter i2c-0: Invalid 7-bit address 0x7a

It can be a problem?

> Cheers,
> Hermann

Thank you!

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi Avl,

Am Donnerstag, den 10.09.2009, 21:51 +0000 schrieb Avl Jawrowski:
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > If it seems to deliver stable results now, you can even try to re-flash
> > it with rewrite_eeprom.pl in v4l2-apps/util. Read the instructions on
> > top of it. 
> 
> With 2.6.30 it's stable. I've reflashed the eeprom and now the card is
> autodetected:

because of other obligations I do only follow loosely what happens on
the list. Don't expect me at latest.

> saa7130/34: v4l2 driver version 0.2.15 loaded
> saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 
> 0xcfddf800
> saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i 
> [card=101,autodetected]
> saa7133[0]: board init: gpio is 600e000
> IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2e 15 13 ff ff
> saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2
> saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 03 c5 e8 9d
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> i2c-adapter i2c-0: Invalid 7-bit address 0x7a
> tuner 0-004b: chip found @ 0x96 (saa7133[0])
> tda829x 0-004b: setting tuner address to 61
> tda829x 0-004b: type set to tda8290+75a
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[0])
> DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok

It is important to reflash it with your _original_ eeprom stuff on the
long run, for now it does not matter.

I see at least three different eeprom contents for now, might make a
difference for LNA activation or for external voltage to an active
antenna, also seven different remotes are listed, one marked as
dysfunctional currently on the m$ driver ...


> However it works still only with Kaffeine and w_scan.
> dvbscan (last mercurial) give:

Off hand I can't tell, but try with "scan".
I did not use "dvbscan" since years and can't tell the status.

> Unable to query frontend status
> 
> And with 2.6.31 (same configuration) appears this new error:
> 
> i2c-adapter i2c-0: Invalid 7-bit address 0x7a
> 
> It can be a problem?

No, it is only related to the first i2c remote on the Upmost Purple TV.
It is unlikely that anybody is on the list with such a card currently.

Likely it means we should shift it >> 1.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

hermann pitton <hermann-pitton <at> arcor.de> writes:

> > However it works still only with Kaffeine and w_scan.
> > dvbscan (last mercurial) give:
> 
> Off hand I can't tell, but try with "scan".
> I did not use "dvbscan" since years and can't tell the status.

Even scan works perfectly (I didn't know it).
I think it's an mplayer problem, I'll write about it in the mplayer mailing list.

> Cheers,
> Hermann

You've been very helpful!
Thank you very much,
Avl

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Samstag, den 12.09.2009, 21:39 +0000 schrieb Avl Jawrowski:
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > > However it works still only with Kaffeine and w_scan.
> > > dvbscan (last mercurial) give:
> > 
> > Off hand I can't tell, but try with "scan".
> > I did not use "dvbscan" since years and can't tell the status.
> 
> Even scan works perfectly (I didn't know it).
> I think it's an mplayer problem, I'll write about it in the mplayer mailing list.
> 
> > Cheers,
> > Hermann
> 
> You've been very helpful!
> Thank you very much,
> Avl
> 

I'm sorry that we have some mess on some of such devices, but currently
really nobody can help much further.

Mike and Hauppauge don't have any schematics for LNA and external
antenna voltage switching for now, he assured it to me personally and we
must live with the back hacks for now and try to further work through
it.

However, mplayer should work as well, but my last checkout is a little
out dated.

It will go to Nico anyway, he is usually at the list here.

If you can tell me on what you are, I might be able to confirm or not.

The only other issue I'm aware of is that radio is broken since guessed
8 weeks on my tuners, only realized when testing on enabling external
active antenna voltage for DVB-T on a/some 310i.

Might be anything, hm, hopefully I should not have caused it ;)

Cheers,
Hermann
        

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi,

hermann pitton <hermann-pitton <at> arcor.de> writes:

> 
> I'm sorry that we have some mess on some of such devices, but currently
> really nobody can help much further.
> 
> Mike and Hauppauge don't have any schematics for LNA and external
> antenna voltage switching for now, he assured it to me personally and we
> must live with the back hacks for now and try to further work through
> it.
> 
> However, mplayer should work as well, but my last checkout is a little
> out dated.
> 
> It will go to Nico anyway, he is usually at the list here.
> 
> If you can tell me on what you are, I might be able to confirm or not.

Do you mean the exact card I have? I can do some photos if they can help.
Unfortunately I don't have the original eeprom content.

In the matter of the IR, the modules seems to be loaded:

tda1004x               13048  1
saa7134_dvb            20772  0
videobuf_dvb            5644  1 saa7134_dvb
ir_kbd_i2c              5500  0
tda827x                 8880  2
tuner                  16960  1
saa7134               138436  1 saa7134_dvb
ir_common              41828  2 ir_kbd_i2c,saa7134
videobuf_dma_sg         9876  2 saa7134_dvb,saa7134
videobuf_core          13596  3 videobuf_dvb,saa7134,videobuf_dma_sg
tveeprom               10488  1 saa7134

But I can't find anything in /proc/bus/input/devices.

> The only other issue I'm aware of is that radio is broken since guessed
> 8 weeks on my tuners, only realized when testing on enabling external
> active antenna voltage for DVB-T on a/some 310i.
> 
> Might be anything, hm, hopefully I should not have caused it ;)

The radio works for me, even if there's much noise (I don't usually use it).
I'm using the internal audio cable.

> Cheers,
> Hermann

Thank you!

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Sonntag, den 13.09.2009, 12:02 +0000 schrieb Avl Jawrowski:
> Hi,
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > 
> > I'm sorry that we have some mess on some of such devices, but currently
> > really nobody can help much further.
> > 
> > Mike and Hauppauge don't have any schematics for LNA and external
> > antenna voltage switching for now, he assured it to me personally and we
> > must live with the back hacks for now and try to further work through
> > it.
> > 
> > However, mplayer should work as well, but my last checkout is a little
> > out dated.
> > 
> > It will go to Nico anyway, he is usually at the list here.
> > 
> > If you can tell me on what you are, I might be able to confirm or not.
> 
> Do you mean the exact card I have? I can do some photos if they can help.
> Unfortunately I don't have the original eeprom content.

no, in this case I meant mplayer should work for you too.
You need to have DVB support enabled and a channels.conf file in
~/.mplayer.

We might collect pictures of the cards and remotes as well.
To identify those card with an additional LNA circuitry is likely not
easy hardware wise, since the tuner shielding is soldered with 16 pins,
many close to lines. Maybe we can identify those boards by the card
revision printed on them. Don't know how to auto detect them.

> In the matter of the IR, the modules seems to be loaded:
> 
> tda1004x               13048  1
> saa7134_dvb            20772  0
> videobuf_dvb            5644  1 saa7134_dvb
> ir_kbd_i2c              5500  0
> tda827x                 8880  2
> tuner                  16960  1
> saa7134               138436  1 saa7134_dvb
> ir_common              41828  2 ir_kbd_i2c,saa7134
> videobuf_dma_sg         9876  2 saa7134_dvb,saa7134
> videobuf_core          13596  3 videobuf_dvb,saa7134,videobuf_dma_sg
> tveeprom               10488  1 saa7134
> 
> But I can't find anything in /proc/bus/input/devices.

We might have more than the two supported remotes on such cards.
After all that would not make me wonder anymore and the windows driver
presents some more. Do you have that silver remote with colored buttons.
There must be a device at 0x47 detected to support it.

You might have to load ir-kbd-i2c at first or reload saa7134-alsa and
saa7134-dvb, which includes saa7134.

If OK, looks like this here.

saa7133[2]: setting pci latency timer to 64
saa7133[2]: found at 0000:04:03.0, rev: 208, irq: 21, latency: 64, mmio: 0xfebfe800
saa7133[2]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i [card=101,insmod option]
saa7133[2]: board init: gpio is 600c000
saa7133[2]: gpio: mode=0x0000000 in=0x600c000 out=0x0000000 [pre-init]
IRQ 21/saa7133[2]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[2]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[2]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2c b0 22 ff ff
saa7133[2]: i2c eeprom 20: 01 2c 01 02 02 01 04 30 98 ff 00 a5 ff 21 00 c2
saa7133[2]: i2c eeprom 30: 96 10 03 32 15 20 ff ff 0c 22 17 88 03 44 31 f9
saa7133[2]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
input: i2c IR (Pinnacle PCTV) as /class/input/input7
ir-kbd-i2c: i2c IR (Pinnacle PCTV) detected at i2c-3/3-0047/ir0 [saa7133[2]]
tuner 3-004b: chip found @ 0x96 (saa7133[2])
tda829x 3-004b: setting tuner address to 61
tda829x 3-004b: type set to tda8290+75a
saa7133[2]: gpio: mode=0x0200000 in=0x600e000 out=0x0000000 [Television]
saa7133[2]: gpio: mode=0x0200000 in=0x600e000 out=0x0000000 [Television]
saa7133[2]: gpio: mode=0x0200000 in=0x600c000 out=0x0000000 [Television]
saa7133[2]: registered device video2 [v4l2]
saa7133[2]: registered device vbi2
saa7133[2]: registered device radio0
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[0])
DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
saa7133[0]/dvb: setting GPIO21 to 1 (Radio antenna?)
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[1])
DVB: registering adapter 1 frontend 0 (Philips TDA10086 DVB-S)...
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[2])
DVB: registering adapter 2 frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok

> > The only other issue I'm aware of is that radio is broken since guessed
> > 8 weeks on my tuners, only realized when testing on enabling external
> > active antenna voltage for DVB-T on a/some 310i.
> > 
> > Might be anything, hm, hopefully I should not have caused it ;)
> 
> The radio works for me, even if there's much noise (I don't usually use it).
> I'm using the internal audio cable.

The radio is broken for all tuners, you must be on older stuff.

I finally found the time to do the mercurial bisect today.

It is broken since Hans' changeset 12429 on seventh August.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Hans Verkuil]

On Monday 14 September 2009 00:42:16 hermann pitton wrote:
> Hi,
> 
> Am Sonntag, den 13.09.2009, 12:02 +0000 schrieb Avl Jawrowski:
> > Hi,
> > 
> > hermann pitton <hermann-pitton <at> arcor.de> writes:
> > 
> > > 
> > > I'm sorry that we have some mess on some of such devices, but currently
> > > really nobody can help much further.
> > > 
> > > Mike and Hauppauge don't have any schematics for LNA and external
> > > antenna voltage switching for now, he assured it to me personally and we
> > > must live with the back hacks for now and try to further work through
> > > it.
> > > 
> > > However, mplayer should work as well, but my last checkout is a little
> > > out dated.
> > > 
> > > It will go to Nico anyway, he is usually at the list here.
> > > 
> > > If you can tell me on what you are, I might be able to confirm or not.
> > 
> > Do you mean the exact card I have? I can do some photos if they can help.
> > Unfortunately I don't have the original eeprom content.
> 
> no, in this case I meant mplayer should work for you too.
> You need to have DVB support enabled and a channels.conf file in
> ~/.mplayer.
> 
> We might collect pictures of the cards and remotes as well.
> To identify those card with an additional LNA circuitry is likely not
> easy hardware wise, since the tuner shielding is soldered with 16 pins,
> many close to lines. Maybe we can identify those boards by the card
> revision printed on them. Don't know how to auto detect them.
> 
> > In the matter of the IR, the modules seems to be loaded:
> > 
> > tda1004x               13048  1
> > saa7134_dvb            20772  0
> > videobuf_dvb            5644  1 saa7134_dvb
> > ir_kbd_i2c              5500  0
> > tda827x                 8880  2
> > tuner                  16960  1
> > saa7134               138436  1 saa7134_dvb
> > ir_common              41828  2 ir_kbd_i2c,saa7134
> > videobuf_dma_sg         9876  2 saa7134_dvb,saa7134
> > videobuf_core          13596  3 videobuf_dvb,saa7134,videobuf_dma_sg
> > tveeprom               10488  1 saa7134
> > 
> > But I can't find anything in /proc/bus/input/devices.
> 
> We might have more than the two supported remotes on such cards.
> After all that would not make me wonder anymore and the windows driver
> presents some more. Do you have that silver remote with colored buttons.
> There must be a device at 0x47 detected to support it.
> 
> You might have to load ir-kbd-i2c at first or reload saa7134-alsa and
> saa7134-dvb, which includes saa7134.
> 
> If OK, looks like this here.
> 
> saa7133[2]: setting pci latency timer to 64
> saa7133[2]: found at 0000:04:03.0, rev: 208, irq: 21, latency: 64, mmio: 0xfebfe800
> saa7133[2]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i [card=101,insmod option]
> saa7133[2]: board init: gpio is 600c000
> saa7133[2]: gpio: mode=0x0000000 in=0x600c000 out=0x0000000 [pre-init]
> IRQ 21/saa7133[2]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[2]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> saa7133[2]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2c b0 22 ff ff
> saa7133[2]: i2c eeprom 20: 01 2c 01 02 02 01 04 30 98 ff 00 a5 ff 21 00 c2
> saa7133[2]: i2c eeprom 30: 96 10 03 32 15 20 ff ff 0c 22 17 88 03 44 31 f9
> saa7133[2]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[2]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> input: i2c IR (Pinnacle PCTV) as /class/input/input7
> ir-kbd-i2c: i2c IR (Pinnacle PCTV) detected at i2c-3/3-0047/ir0 [saa7133[2]]
> tuner 3-004b: chip found @ 0x96 (saa7133[2])
> tda829x 3-004b: setting tuner address to 61
> tda829x 3-004b: type set to tda8290+75a
> saa7133[2]: gpio: mode=0x0200000 in=0x600e000 out=0x0000000 [Television]
> saa7133[2]: gpio: mode=0x0200000 in=0x600e000 out=0x0000000 [Television]
> saa7133[2]: gpio: mode=0x0200000 in=0x600c000 out=0x0000000 [Television]
> saa7133[2]: registered device video2 [v4l2]
> saa7133[2]: registered device vbi2
> saa7133[2]: registered device radio0
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[0])
> DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
> saa7133[0]/dvb: setting GPIO21 to 1 (Radio antenna?)
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[1])
> DVB: registering adapter 1 frontend 0 (Philips TDA10086 DVB-S)...
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[2])
> DVB: registering adapter 2 frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> tda1004x: found firmware revision 29 -- ok
> 
> > > The only other issue I'm aware of is that radio is broken since guessed
> > > 8 weeks on my tuners, only realized when testing on enabling external
> > > active antenna voltage for DVB-T on a/some 310i.
> > > 
> > > Might be anything, hm, hopefully I should not have caused it ;)
> > 
> > The radio works for me, even if there's much noise (I don't usually use it).
> > I'm using the internal audio cable.
> 
> The radio is broken for all tuners, you must be on older stuff.
> 
> I finally found the time to do the mercurial bisect today.
> 
> It is broken since Hans' changeset 12429 on seventh August.

What are the symptoms? What application do you use to test the radio?
I don't immediately see why that changeset would break radio support as
it only affects VIDIOC_G_STD and VIDIOC_G_PARM.

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

saa7134 - radio broken for v4l1 apps - was - Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Montag, den 14.09.2009, 08:24 +0200 schrieb Hans Verkuil:
> On Monday 14 September 2009 00:42:16 hermann pitton wrote:
> > Hi,
> > 
> > Am Sonntag, den 13.09.2009, 12:02 +0000 schrieb Avl Jawrowski:
> > > Hi,
> > > 
> > > hermann pitton <hermann-pitton <at> arcor.de> writes:
> > > 
[snip]
> > 
> > > > The only other issue I'm aware of is that radio is broken since guessed
> > > > 8 weeks on my tuners, only realized when testing on enabling external
> > > > active antenna voltage for DVB-T on a/some 310i.
> > > > 
> > > > Might be anything, hm, hopefully I should not have caused it ;)
> > > 
> > > The radio works for me, even if there's much noise (I don't usually use it).
> > > I'm using the internal audio cable.
> > 
> > The radio is broken for all tuners, you must be on older stuff.
> > 
> > I finally found the time to do the mercurial bisect today.
> > 
> > It is broken since Hans' changeset 12429 on seventh August.
> 
> What are the symptoms? What application do you use to test the radio?
> I don't immediately see why that changeset would break radio support as
> it only affects VIDIOC_G_STD and VIDIOC_G_PARM.
> 
> Regards,
> 
> 	Hans

Hans, it are indeed only the v4l1 apps like radio, qtradio, gnomeradio
and fm from fmtools. Avl is right, mplayer does still work and also
kradio.

So the trouble happens in the v4l1 compat layer.

Symptoms are, that you just have loud static noise and tuning has not
any effect. Also no signal and/or stereo detection.

"fm" gives now "ioctl VIDIOCGTUNER: Invalid argument".

qtradio
Using v4l
Video4Linux detected
87 - 108
SIGNAL = 0
SIGNAL = 0
VIDIOCGAUDIO: Ungültiger Dateideskriptor
VIDIOCSAUDIO: Ungültiger Dateideskriptor
VIDIOCGAUDIO: Ungültiger Dateideskriptor
VIDIOCSAUDIO: Ungültiger Dateideskriptor

Tested on old style simple tuners, some tda9887 stuff and
tda8275a/tda8290/saa7131e, on both x86 and x86_64, with some 2.6.29 and
some 2.6.30.

Cheers,
Hermann

Re: saa7134 - radio broken for v4l1 apps - was - Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Hans Verkuil]

On Tuesday 15 September 2009 01:50:32 hermann pitton wrote:
> Hi,
> 
> Am Montag, den 14.09.2009, 08:24 +0200 schrieb Hans Verkuil:
> > On Monday 14 September 2009 00:42:16 hermann pitton wrote:
> > > Hi,
> > > 
> > > Am Sonntag, den 13.09.2009, 12:02 +0000 schrieb Avl Jawrowski:
> > > > Hi,
> > > > 
> > > > hermann pitton <hermann-pitton <at> arcor.de> writes:
> > > > 
> [snip]
> > > 
> > > > > The only other issue I'm aware of is that radio is broken since guessed
> > > > > 8 weeks on my tuners, only realized when testing on enabling external
> > > > > active antenna voltage for DVB-T on a/some 310i.
> > > > > 
> > > > > Might be anything, hm, hopefully I should not have caused it ;)
> > > > 
> > > > The radio works for me, even if there's much noise (I don't usually use it).
> > > > I'm using the internal audio cable.
> > > 
> > > The radio is broken for all tuners, you must be on older stuff.
> > > 
> > > I finally found the time to do the mercurial bisect today.
> > > 
> > > It is broken since Hans' changeset 12429 on seventh August.
> > 
> > What are the symptoms? What application do you use to test the radio?
> > I don't immediately see why that changeset would break radio support as
> > it only affects VIDIOC_G_STD and VIDIOC_G_PARM.
> > 
> > Regards,
> > 
> > 	Hans
> 
> Hans, it are indeed only the v4l1 apps like radio, qtradio, gnomeradio
> and fm from fmtools. Avl is right, mplayer does still work and also
> kradio.
> 
> So the trouble happens in the v4l1 compat layer.
> 
> Symptoms are, that you just have loud static noise and tuning has not
> any effect. Also no signal and/or stereo detection.
> 
> "fm" gives now "ioctl VIDIOCGTUNER: Invalid argument".

Hermann, I've fixed this in v4l1-compat.c. Can you try this tree:

http://www.linuxtv.org/hg/~hverkuil/v4l-dvb

If this works (and I expect it will), then I'll post a pull request for this.

Regards,

	Hans

> 
> qtradio
> Using v4l
> Video4Linux detected
> 87 - 108
> SIGNAL = 0
> SIGNAL = 0
> VIDIOCGAUDIO: Ungültiger Dateideskriptor
> VIDIOCSAUDIO: Ungültiger Dateideskriptor
> VIDIOCGAUDIO: Ungültiger Dateideskriptor
> VIDIOCSAUDIO: Ungültiger Dateideskriptor
> 
> Tested on old style simple tuners, some tda9887 stuff and
> tda8275a/tda8290/saa7131e, on both x86 and x86_64, with some 2.6.29 and
> some 2.6.30.
> 
> Cheers,
> Hermann
> 
> 
> 



-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

Re: saa7134 - radio broken for v4l1 apps - was - Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Am Dienstag, den 15.09.2009, 18:39 +0200 schrieb Hans Verkuil:
> On Tuesday 15 September 2009 01:50:32 hermann pitton wrote:
> > Hi,
> > 
> > Am Montag, den 14.09.2009, 08:24 +0200 schrieb Hans Verkuil:
> > > On Monday 14 September 2009 00:42:16 hermann pitton wrote:
> > > > Hi,
> > > > 
> > > > Am Sonntag, den 13.09.2009, 12:02 +0000 schrieb Avl Jawrowski:
> > > > > Hi,
> > > > > 
> > > > > hermann pitton <hermann-pitton <at> arcor.de> writes:
> > > > > 
> > [snip]
> > > > 
> > > > > > The only other issue I'm aware of is that radio is broken since guessed
> > > > > > 8 weeks on my tuners, only realized when testing on enabling external
> > > > > > active antenna voltage for DVB-T on a/some 310i.
> > > > > > 
> > > > > > Might be anything, hm, hopefully I should not have caused it ;)
> > > > > 
> > > > > The radio works for me, even if there's much noise (I don't usually use it).
> > > > > I'm using the internal audio cable.
> > > > 
> > > > The radio is broken for all tuners, you must be on older stuff.
> > > > 
> > > > I finally found the time to do the mercurial bisect today.
> > > > 
> > > > It is broken since Hans' changeset 12429 on seventh August.
> > > 
> > > What are the symptoms? What application do you use to test the radio?
> > > I don't immediately see why that changeset would break radio support as
> > > it only affects VIDIOC_G_STD and VIDIOC_G_PARM.
> > > 
> > > Regards,
> > > 
> > > 	Hans
> > 
> > Hans, it are indeed only the v4l1 apps like radio, qtradio, gnomeradio
> > and fm from fmtools. Avl is right, mplayer does still work and also
> > kradio.
> > 
> > So the trouble happens in the v4l1 compat layer.
> > 
> > Symptoms are, that you just have loud static noise and tuning has not
> > any effect. Also no signal and/or stereo detection.
> > 
> > "fm" gives now "ioctl VIDIOCGTUNER: Invalid argument".
> 
> Hermann, I've fixed this in v4l1-compat.c. Can you try this tree:
> 
> http://www.linuxtv.org/hg/~hverkuil/v4l-dvb
> 
> If this works (and I expect it will), then I'll post a pull request for this.
> 
> Regards,
> 
> 	Hans

Hans, it works and restores previous behavior.

Tested-by: hermann pitton <hermann-pitton@arcor.de>

Thanks for the quick fix.

Cheers,
Hermann

> > 
> > qtradio
> > Using v4l
> > Video4Linux detected
> > 87 - 108
> > SIGNAL = 0
> > SIGNAL = 0
> > VIDIOCGAUDIO: Ungültiger Dateideskriptor
> > VIDIOCSAUDIO: Ungültiger Dateideskriptor
> > VIDIOCGAUDIO: Ungültiger Dateideskriptor
> > VIDIOCSAUDIO: Ungültiger Dateideskriptor
> > 
> > Tested on old style simple tuners, some tda9887 stuff and
> > tda8275a/tda8290/saa7131e, on both x86 and x86_64, with some 2.6.29 and
> > some 2.6.30.
> > 
> > Cheers,
> > Hermann
> > 
> > 

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi,

hermann pitton <hermann-pitton <at> arcor.de> writes:

> no, in this case I meant mplayer should work for you too.
> You need to have DVB support enabled and a channels.conf file in
> ~/.mplayer.

It's compiled with --enable-dvbhead, and the channels.conf is made by w_scan,
but I tried even with a made by scan one.

> We might collect pictures of the cards and remotes as well.
> To identify those card with an additional LNA circuitry is likely not
> easy hardware wise, since the tuner shielding is soldered with 16 pins,
> many close to lines. Maybe we can identify those boards by the card
> revision printed on them. Don't know how to auto detect them.

I will post some photos.

> > In the matter of the IR, the modules seems to be loaded:
> > 
> > tda1004x               13048  1
> > saa7134_dvb            20772  0
> > videobuf_dvb            5644  1 saa7134_dvb
> > ir_kbd_i2c              5500  0
> > tda827x                 8880  2
> > tuner                  16960  1
> > saa7134               138436  1 saa7134_dvb
> > ir_common              41828  2 ir_kbd_i2c,saa7134
> > videobuf_dma_sg         9876  2 saa7134_dvb,saa7134
> > videobuf_core          13596  3 videobuf_dvb,saa7134,videobuf_dma_sg
> > tveeprom               10488  1 saa7134
> > 
> > But I can't find anything in /proc/bus/input/devices.
> 
> We might have more than the two supported remotes on such cards.
> After all that would not make me wonder anymore and the windows driver
> presents some more. Do you have that silver remote with colored buttons.
> There must be a device at 0x47 detected to support it.

Yes that is: http://www.hwp.ru/Tvtuners/Pinnaclehybridpro.pci
/Pinnaclepctvhybridpropci-1sm.jpg

> You might have to load ir-kbd-i2c at first or reload saa7134-alsa and
> saa7134-dvb, which includes saa7134.

I've unloaded all modules, then loaded first ir-kbd-i2c and next saa7134-dvb,
but I can't see any difference.
Loading saa7134 with ir_debug=1 and i2c_debug=1 I can see some of these errors:

saa7133[0]: i2c xfer: < 8e ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < e2 ERROR: NO_DEVICE
saa7133[0]: i2c xfer: < 5a ERROR: NO_DEVICE

> > > The only other issue I'm aware of is that radio is broken since guessed
> > > 8 weeks on my tuners, only realized when testing on enabling external
> > > active antenna voltage for DVB-T on a/some 310i.
> > > 
> > > Might be anything, hm, hopefully I should not have caused it ;)
> > 
> > The radio works for me, even if there's much noise (I don't usually use it).
> > I'm using the internal audio cable.
> 
> The radio is broken for all tuners, you must be on older stuff.

Using 2.6.31 and mplayer it really works for me.

> I finally found the time to do the mercurial bisect today.
> 
> It is broken since Hans' changeset 12429 on seventh August.
> 
> Cheers,
> Hermann

Thank you!

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Montag, den 14.09.2009, 13:32 +0000 schrieb Avl Jawrowski:
> Hi,
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > no, in this case I meant mplayer should work for you too.
> > You need to have DVB support enabled and a channels.conf file in
> > ~/.mplayer.
> 
> It's compiled with --enable-dvbhead, and the channels.conf is made by w_scan,
> but I tried even with a made by scan one.

mplayer works on all my cards including the 310i for DVB-T and DVB-S
since years. Guess you miss something or have a broken checkout.

> > We might collect pictures of the cards and remotes as well.
> > To identify those card with an additional LNA circuitry is likely not
> > easy hardware wise, since the tuner shielding is soldered with 16 pins,
> > many close to lines. Maybe we can identify those boards by the card
> > revision printed on them. Don't know how to auto detect them.
> 
> I will post some photos.

Best is to add them to the wiki, else upload somewhere else or post off
list.

> > > In the matter of the IR, the modules seems to be loaded:
> > > 
> > > tda1004x               13048  1
> > > saa7134_dvb            20772  0
> > > videobuf_dvb            5644  1 saa7134_dvb
> > > ir_kbd_i2c              5500  0
> > > tda827x                 8880  2
> > > tuner                  16960  1
> > > saa7134               138436  1 saa7134_dvb
> > > ir_common              41828  2 ir_kbd_i2c,saa7134
> > > videobuf_dma_sg         9876  2 saa7134_dvb,saa7134
> > > videobuf_core          13596  3 videobuf_dvb,saa7134,videobuf_dma_sg
> > > tveeprom               10488  1 saa7134
> > > 
> > > But I can't find anything in /proc/bus/input/devices.
> > 
> > We might have more than the two supported remotes on such cards.
> > After all that would not make me wonder anymore and the windows driver
> > presents some more. Do you have that silver remote with colored buttons.
> > There must be a device at 0x47 detected to support it.
> 
> Yes that is: http://www.hwp.ru/Tvtuners/Pinnaclehybridpro.pci
> /Pinnaclepctvhybridpropci-1sm.jpg

Remote and IR sensor look the same like mine on the 310i, but they still
might have changed something and you are by far not the first reporting
the remote not working on newer devices. BTW, mine seems not to work on
vista with the Pinnacle media software.

> > You might have to load ir-kbd-i2c at first or reload saa7134-alsa and
> > saa7134-dvb, which includes saa7134.
> 
> I've unloaded all modules, then loaded first ir-kbd-i2c and next saa7134-dvb,
> but I can't see any difference.
> Loading saa7134 with ir_debug=1 and i2c_debug=1 I can see some of these errors:
> 
> saa7133[0]: i2c xfer: < 8e ERROR: NO_DEVICE

Here is the problem. The supported cards do have the i2c chip at 0x47 or
0x8e in 8bit notation. Needs closer investigation.

> saa7133[0]: i2c xfer: < e2 ERROR: NO_DEVICE
> saa7133[0]: i2c xfer: < 5a ERROR: NO_DEVICE
> 
> > > > The only other issue I'm aware of is that radio is broken since guessed
> > > > 8 weeks on my tuners, only realized when testing on enabling external
> > > > active antenna voltage for DVB-T on a/some 310i.
> > > > 
> > > > Might be anything, hm, hopefully I should not have caused it ;)
> > > 
> > > The radio works for me, even if there's much noise (I don't usually use it).
> > > I'm using the internal audio cable.
> > 
> > The radio is broken for all tuners, you must be on older stuff.
> 
> Using 2.6.31 and mplayer it really works for me.

Ah, thanks. Should have thought about it. Most radio apps are still
v4l1. Mplayer indeed works, tested with saa7134-alsa, as does "kradio",
just installed it again, both are v4l2. 

> > I finally found the time to do the mercurial bisect today.
> > 
> > It is broken since Hans' changeset 12429 on seventh August.

So only all the v4l1 apps are broken.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi,

hermann pitton <hermann-pitton <at> arcor.de> writes:

> mplayer works on all my cards including the 310i for DVB-T and DVB-S
> since years. Guess you miss something or have a broken checkout.

I've just compiled another checkout, but it's the same.
With some channels I can see even something like this:

TS file format detected.
dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 816 bytes
dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1736 bytes
dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1148 bytes

or like this:

dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 2048 bytes
dvb_streaming_read, return 0 bytes

But I can't see any video.
With Kaffeine I can see the same channels as well.

> Best is to add them to the wiki, else upload somewhere else or post off
> list.

Then I'm going to sign me up to the wiki.
Do you think it's better to create a "Pinnacle PCTV Hybrid Pro PCI" page or to
add the photos to the 310i page?

> > saa7133[0]: i2c xfer: < 8e ERROR: NO_DEVICE
> 
> Here is the problem. The supported cards do have the i2c chip at 0x47 or
> 0x8e in 8bit notation. Needs closer investigation.

If can be useful, I can attach the entire log.

> Cheers,
> Hermann

Thank you!

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi,

Am Dienstag, den 15.09.2009, 20:27 +0000 schrieb Avl Jawrowski:
> Hi,
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > mplayer works on all my cards including the 310i for DVB-T and DVB-S
> > since years. Guess you miss something or have a broken checkout.
> 
> I've just compiled another checkout, but it's the same.
> With some channels I can see even something like this:
> 
> TS file format detected.
> dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 816 bytes
> dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1736 bytes
> dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1148 bytes
> 
> or like this:
> 
> dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, return 0 bytes

yes, that you do usually see on critical frequencies.

dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 1088 bytes
dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1068 bytes
dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1236 bytes
dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 484 bytes
dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 108 bytes
dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 108 bytes
TRIED UP TO POSITION 0, FOUND 47, packet_size= 188, SEEMS A TS? 1
GOOD CC: 5, BAD CC: 20

Mplayer decides, the relation from good to bad packets is too worse to
try on it in that case.

> But I can't see any video.
> With Kaffeine I can see the same channels as well.

My guess is, kaffeine has a bit more trust in error correction,
but you over all reception quality seems to be on a critical limit.

> > Best is to add them to the wiki, else upload somewhere else or post off
> > list.
> 
> Then I'm going to sign me up to the wiki.
> Do you think it's better to create a "Pinnacle PCTV Hybrid Pro PCI" page or to
> add the photos to the 310i page?

Good question, but since yours still has the same PCI subsystem and your
eeprom is not original anymore, we can only try identification by
different chips, layout or board revisions.

So it is still some sort of 310i, but you should mention the new name
and that the remote chip on 0x47/0x8e is not detected.

> > > saa7133[0]: i2c xfer: < 8e ERROR: NO_DEVICE
> > 
> > Here is the problem. The supported cards do have the i2c chip at 0x47 or
> > 0x8e in 8bit notation. Needs closer investigation.
> 
> If can be useful, I can attach the entire log.

You might try with i2c_scan=1, if another and new address is reported
instead. Guess no.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi, sorry for the late.

hermann pitton <hermann-pitton <at> arcor.de> writes:

> > But I can't see any video.
> > With Kaffeine I can see the same channels as well.
> 
> My guess is, kaffeine has a bit more trust in error correction,
> but you over all reception quality seems to be on a critical limit.

In Kaffeine I see signal at 72% and SNR at 100% for that channel, so I don't
think it's so bad.

> So it is still some sort of 310i, but you should mention the new name
> and that the remote chip on 0x47/0x8e is not detected.

I add a note and some photos:

http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_(310i)

Can I add any other useful information, log or photo?

> Cheers,
> Hermann

Thank you again,

Avl

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi Avl,

Am Samstag, den 20.02.2010, 11:49 +0000 schrieb Avl Jawrowski:
> Hi, sorry for the late.
> 
> hermann pitton <hermann-pitton <at> arcor.de> writes:
> 
> > > But I can't see any video.
> > > With Kaffeine I can see the same channels as well.
> > 
> > My guess is, kaffeine has a bit more trust in error correction,
> > but you over all reception quality seems to be on a critical limit.
> 
> In Kaffeine I see signal at 72% and SNR at 100% for that channel, so I don't
> think it's so bad.

yes, should be good enough.

> > So it is still some sort of 310i, but you should mention the new name
> > and that the remote chip on 0x47/0x8e is not detected.
> 
> I add a note and some photos:
> 
> http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_(310i)
> 
> Can I add any other useful information, log or photo?

We most likely need the former Pinnacle devs here, if not already fired.
Maybe Mike and Devin can agree these days on it and it seems some
work-flow does recover.

You can have from me all details for the early device I do have now,
after later ones caused more confusion, and of course can use all that
on the wiki.

Let me know, I'll sent photos off list then.

After latest on wiki stuff, I'm for sure not interested to have an
account and was always in doubt, how to separate developer announces and
user reports there.

I did vote for user reports, if in doubt, since you can't match all
conditions, at least for such cards I was involved, and did stay away,
even on worst wrong stuff you sometimes can read there.

Either that wiki idea works or not. In longer terms it should,
but can also become pretty crufty soon.

Cheers,
Hermann
 

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Hi,
there are some news with 2.6.34 (or previous).
The IR is detected and the device seems to be created, but it doesn't work.

saa7130/34: v4l2 driver version 0.2.15 loaded
saa7134 0000:01:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 
xcfddf800
saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i
[card=101,autodetected]
saa7133[0]: board init: gpio is 600c000
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2e 15 13 ff ff
saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2
saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 03 c5 e8 9d
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
input: i2c IR (Pinnacle PCTV) as /class/input/input5
Creating IR device irrcv0
ir-kbd-i2c: i2c IR (Pinnacle PCTV) detected at i2c-0/0-0047/ir0 [saa7133[0]]
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tda829x 0-004b: setting tuner address to 61
tda829x 0-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
dvb_init() allocating 1 frontend
DVB: registering new adapter (saa7133[0])
DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...

And loading it with i2c_debug=1 ir_debug=1 I get a lot of these:

[ 3757.243258] input: i2c IR (Pinnacle PCTV) as /class/input/input6
[ 3757.243314] Creating IR device irrcv0
[ 3757.243318] ir-kbd-i2c: i2c IR (Pinnacle PCTV)
detected at i2c-0/0-0047/ir0 [saa7133[0]]
[ 3757.243330] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3757.243470] i2c IR (Pinnacle PCTV)/ir: read error
[ 3757.243512] saa7133[0]: i2c xfer: < 10 3c 33 60 >
[ 3757.251420] saa7133[0]: i2c xfer: < 84 ERROR: NO_DEVICE
[ 3757.251599] saa7133[0]: i2c xfer: < 86 ERROR: NO_DEVICE
[ 3757.251777] saa7133[0]: i2c xfer: < 94 ERROR: NO_DEVICE
[ 3757.251955] saa7133[0]: i2c xfer: < 96 >
[ 3757.256422] saa7133[0]: i2c xfer: < 96 00 >
[ 3757.262970] saa7133[0]: i2c xfer: < 97 =01 =01 =00 =11 =01 =04 =01 =85 >
[ 3757.269646] saa7133[0]: i2c xfer: < 96 1f >
[ 3757.276302] saa7133[0]: i2c xfer: < 97 =89 >
[ 3757.283045] tuner 0-004b: chip found @ 0x96 (saa7133[0])
[ 3757.283135] saa7133[0]: i2c xfer: < 96 1f >
[ 3757.289700] saa7133[0]: i2c xfer: < 97 =89 >
[ 3757.296308] saa7133[0]: i2c xfer: < 96 2f >
[ 3757.302981] saa7133[0]: i2c xfer: < 97 =00 >
[ 3757.309643] saa7133[0]: i2c xfer: < 96 21 c0 >
[ 3757.339639] saa7133[0]: i2c xfer: < c1 ERROR: NO_DEVICE
[ 3757.339818] saa7133[0]: i2c xfer: < c3 =0a >
[ 3757.346302] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3793.576474] i2c IR (Pinnacle PCTV)/ir: read error
[ 3793.678145] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3793.678290] i2c IR (Pinnacle PCTV)/ir: read error
[ 3793.776341] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3793.776481] i2c IR (Pinnacle PCTV)/ir: read error
[ 3793.876338] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3793.876480] i2c IR (Pinnacle PCTV)/ir: read error
[ 3793.976343] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3793.976484] i2c IR (Pinnacle PCTV)/ir: read error
[ 3794.076337] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 3794.076478] i2c IR (Pinnacle PCTV)/ir: read error

It is an improvement or not?
Thanks,
Avl

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[hermann pitton]

Hi Avl,

Am Samstag, den 26.06.2010, 12:08 +0000 schrieb Avl Jawrowski:
> Hi,
> there are some news with 2.6.34 (or previous).
> The IR is detected and the device seems to be created, but it doesn't work.
> 
> saa7130/34: v4l2 driver version 0.2.15 loaded
> saa7134 0000:01:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: 
> xcfddf800
> saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i
> [card=101,autodetected]
> saa7133[0]: board init: gpio is 600c000
> IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2e 15 13 ff ff
> saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2
> saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 03 c5 e8 9d
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> input: i2c IR (Pinnacle PCTV) as /class/input/input5
> Creating IR device irrcv0
> ir-kbd-i2c: i2c IR (Pinnacle PCTV) detected at i2c-0/0-0047/ir0 [saa7133[0]]
> tuner 0-004b: chip found @ 0x96 (saa7133[0])
> tda829x 0-004b: setting tuner address to 61
> tda829x 0-004b: type set to tda8290+75a
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> dvb_init() allocating 1 frontend
> DVB: registering new adapter (saa7133[0])
> DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
> 
> And loading it with i2c_debug=1 ir_debug=1 I get a lot of these:
> 
> [ 3757.243258] input: i2c IR (Pinnacle PCTV) as /class/input/input6
> [ 3757.243314] Creating IR device irrcv0
> [ 3757.243318] ir-kbd-i2c: i2c IR (Pinnacle PCTV)
> detected at i2c-0/0-0047/ir0 [saa7133[0]]
> [ 3757.243330] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3757.243470] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3757.243512] saa7133[0]: i2c xfer: < 10 3c 33 60 >
> [ 3757.251420] saa7133[0]: i2c xfer: < 84 ERROR: NO_DEVICE
> [ 3757.251599] saa7133[0]: i2c xfer: < 86 ERROR: NO_DEVICE
> [ 3757.251777] saa7133[0]: i2c xfer: < 94 ERROR: NO_DEVICE
> [ 3757.251955] saa7133[0]: i2c xfer: < 96 >
> [ 3757.256422] saa7133[0]: i2c xfer: < 96 00 >
> [ 3757.262970] saa7133[0]: i2c xfer: < 97 =01 =01 =00 =11 =01 =04 =01 =85 >
> [ 3757.269646] saa7133[0]: i2c xfer: < 96 1f >
> [ 3757.276302] saa7133[0]: i2c xfer: < 97 =89 >
> [ 3757.283045] tuner 0-004b: chip found @ 0x96 (saa7133[0])
> [ 3757.283135] saa7133[0]: i2c xfer: < 96 1f >
> [ 3757.289700] saa7133[0]: i2c xfer: < 97 =89 >
> [ 3757.296308] saa7133[0]: i2c xfer: < 96 2f >
> [ 3757.302981] saa7133[0]: i2c xfer: < 97 =00 >
> [ 3757.309643] saa7133[0]: i2c xfer: < 96 21 c0 >
> [ 3757.339639] saa7133[0]: i2c xfer: < c1 ERROR: NO_DEVICE
> [ 3757.339818] saa7133[0]: i2c xfer: < c3 =0a >
> [ 3757.346302] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3793.576474] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3793.678145] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3793.678290] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3793.776341] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3793.776481] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3793.876338] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3793.876480] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3793.976343] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3793.976484] i2c IR (Pinnacle PCTV)/ir: read error
> [ 3794.076337] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 3794.076478] i2c IR (Pinnacle PCTV)/ir: read error
> 
> It is an improvement or not?
> Thanks,
> Avl
> 

unfortunately no improvement for you.

Jean Delvare just changed i2c to use reads at 0x8f for probing the
device instead of writes at 0x8e previously.

The result for you is the same.

Also no news about how to make any difference between the 310i variants.

Those later ones with some first sort of LNA should still be broken.

All I can say is, some people reported, proved by bisecting, that they
need the old LNA config = 1, Mike Krufky also assured to me, that he
can't say, which of the HVR 1110 needs the new LNA config = 1, but can't
exclude it is needed on some card.

You, obviously with some latest variant of the 310i, seem to have not
the best performance, even Signal and SNR do look good.

My old variant of the 310i, not the best in sensitivity compared to
others, does not show any change on any LNA config, but works as usual
including the remote.

Philips RF solutions/NXP is sold to Trident in Taiwan. Some of Hartmut's
latest RF work was calibration of the new saa7231 in Hamburg. He is now
working in another field for Philips there.

We exchanged some mails in private recently, caused by the saa7231, Manu
is working on a driver, but I forgot to ask him, who gave him the input
to change the LNA config = 1 in his latest patch and if maybe anything
is known about a new remote configuration.

That is all i have.

Cheers,
Hermann

Re: Problems with Pinnacle 310i (saa7134) and recent kernels

[Avl Jawrowski]

Well, thank you very much Hermann!
You're very helpul. The sure thing is that when I'll buy a new card I'll ask you 
for a hint.
Thank you again,
Avl