[linux-dvb] My Pinnacle 300i again....

[Michael Schröder]

It seems I got the same problem.
The driver just keeps on saying saa7134[0]: mt352_pinnacle_init called 
and the tuner is heating up.
So I gave back the card and got a different one. It would be nice 
though, if this worked.

Michael

tim0m1a wrote:

> Hi,
>
> I have some trouble with my Pinnacle 300i again.
> After I have updated my kernel from 2.6.12 to 2.6.14 I can not tune 
> any  channel anymore.
>
> I installed the latest CVS v4l-dvb drivers into my kernel.
>
> After I've executeted "modprobe saa7134-dvb" I can find the following  
> output in my /var/log/messages:
>
> Dec 15 21:46:46  Linux video capture interface: v1.00
> Dec 15 21:46:46  saa7130/34: v4l2 driver version 0.2.14 loaded
> Dec 15 21:46:46  ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 
> (level,  low) -> IRQ 17
> Dec 15 21:46:46  saa7134[0]: found at 0000:00:0a.0, rev: 1, irq: 17,  
> latency: 32, mmio: 0xcfffcc00
> Dec 15 21:46:46  saa7134[0]: subsystem: 11bd:002d, board: Pinnacle 
> PCTV  300i DVB-T + PAL [card=50,autodetected]
> Dec 15 21:46:46  saa7134[0]: board init: gpio is 8806000
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 00: bd 11 2d 00 f8 f8 1c 00 43 
> 43  a9 1c 55 d2 b2 92
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 10: 00 f0 04 04 ff 20 ff ff ff 
> ff  ff ff ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 20: 01 40 01 02 03 ff 03 01 08 
> ff  00 25 ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff 
> ff  ff ff ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 40: ff 16 00 c0 86 3c 01 01 ff 
> ff  ff ff ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff 
> ff  ff ff ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 60: 0c 22 17 44 02 9f 6a 13 ff 
> ff  ff ff ff ff ff ff
> Dec 15 21:46:46  saa7134[0]: i2c eeprom 70: 00 30 8d 15 b4 f4 ff ff 74 
> 9c  ff ff ff ff ff ff
> Dec 15 21:46:46  tda9887 0-0043: chip found @ 0x86 (saa7134[0])
> Dec 15 21:46:46  saa7134[0]: registered device video0 [v4l2]
> Dec 15 21:46:46  saa7134[0]: registered device vbi0
> Dec 15 21:46:47  saa7134[0]: pinnacle 300i dvb setup
> Dec 15 21:46:47  DVB: registering new adapter (saa7134[0]).
> Dec 15 21:46:47  DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
>
> So, it looks again like no errors are reported and the card as well as 
> the  frontend can be detected by the driver.
>
> But if i try to tune a channel via tzap I only get the following 
> message  in my /var/log/messages:
>
> Dec 15 21:51:04  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:04  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:05  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:06  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:07  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:08  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:09  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:10  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:11  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:12  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:13  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:14  saa7134[0]: mt352_pinnacle_init called
> Dec 15 21:51:16  saa7134[0]: mt352_pinnacle_init called
>
> And as tzap shows no channel could be locked:
>
> status 00 | signal 1ebf | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 1fbf | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 1f3f | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 1f5f | snr 0000 | ber 00000000 | unc 00000000 |
> status 04 | signal 1edf | snr 0000 | ber 00000000 | unc 00000000 |
> status 04 | signal 1e1f | snr 0000 | ber 00000000 | unc 00000000 |
>
> Can someone help me?
>
> Tim
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>