pinnacle 310i Problems maybe i2c
- From: hermann pitton <hermann.pitton (at) onlinehome.de>
- Date: Fri, 10 Feb 2006 17:26:30 +0100
Am Freitag, den 10.02.2006, 12:28 +0100 schrieb KevinLuX:
> hermann pitton wrote:
>
> >Am Donnerstag, den 09.02.2006, 23:27 +0100 schrieb KevinLuX:
> >
> >
> >>Hi all, I have read many times thread about pinnacle 310i, but at moment
> >>not success for me with this card.
> >>with kdetv i can't find channel also with tvtime. I'm from milan and i
> >>have a good coverage of dvb signal
> >>with windows i can take all channel with a very good quality. But my Os
> >>is linux and i have read that
> >>in analog mode this card works but for me no :'(
> >>Here my steps :
> >>configuring the kernel 2.6.14r2 on an gentoo machine :
> >>RTC enable (for tv time) (static) | only V4L device enable in the
> >>section of v4l. (module) | Only I2C_CONFIG enable. (module)
> >>In the IRDA section all disable.
> >>
> >>After this i have compile the source extratted from mercurial cvs:
> >>make
> >>make install
> >>
> >>after booting machine :
> >>kevinlux (at) eva ~ $ lsmod
> >>Module Size Used by
> >>rivafb 48592 0
> >>vgastate 7616 1 rivafb
> >>saa7134 96032 0
> >>video_buf 15364 1 saa7134
> >>compat_ioctl32 896 1 saa7134
> >>v4l2_common 6208 1 saa7134
> >>v4l1_compat 11908 1 saa7134
> >>ir_kbd_i2c 5712 1 saa7134
> >>ir_common 23044 2 saa7134,ir_kbd_i2c
> >>videodev 6848 1 saa7134
> >>
> >>dmesg say ::
> >>saa7133[0]: board init: gpio is 600c000
> >>
> >>
> >
> >the same card sometimes has also 600e000, bit 13 high.
> >
> >
> >
> >>saa7133[0]: i2c eeprom read error (err=-5)
> >>saa7133[0]: registered device video0 [v4l2]
> >>saa7133[0]: registered device vbi0
> >>
> >>How is possible that module loads automatically?' no signal in kde tv
> >>for channels.
> >>
> >>
> >
> >With eeprom read error I guess only as unknown/generic without tuner.
> >
> >
> >
> >>soi try :
> >>rmmod saa7134
> >>modprobe saa7134 card=81
> >>modprobe saa7134_dvb
> >>with this result
> >>
> >>saa7133[0]: registered device video0 [v4l2]
> >>saa7133[0]: registered device vbi0
> >>saa7133[0]: registered device radio0
> >>DVB: registering new adapter (saa7133[0])
> >>DVB: registering frontend 0 (Philips TDA10046H DVB-T)
> >>
> >>after : tvtime-scanner always nosignal..
> >>
> >>i think that's the error is in i2c ... some helps?'
> >>
> >>thanks in advance.
> >>
> >>
> >
> >
> >Hi,
> >
> >they used card=77 for analog tv, it has a different vmux connection than
> >card=81. You don't even get a analog TV picture with card=81.
> >
> >According to Hartmut the 310i doesn't follow the Philips reference
> >design and this makes it complicated to support it for DVB-T currently.
> >
> >If you power cycle/cold reboot the machine, goes the eeprom read error
> >away using only card=77 for now?
> >
> >Cheers,
> >Hermann
> >
>
> Hi Hermann
> In this thread
> http://marc.theaimsgroup.com/?l=linux-video&m=113863402907172&w=2
> i have found the solution for now :
> <<saa7133[0]: i2c eeprom read error (err=-5) is solved loading first
> tda9887 with port2=1and lager saa7134.>>
> So i have unload saa7134 and load first tda9887 and later saa7134. The
> error from i2c disappear and dmesg :
>
> saa7133[0]: found at 0000:01:09.0, rev: 208, irq: 5, latency: 64, mmio: 0xd8100000
> saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 110i (saa7133) [card=77,insmod option]
> saa7133[0]: board init: gpio is 600e000
> input: Pinnacle PCTV as /class/input/input5
> ir-kbd-i2c: Pinnacle PCTV detected at i2c-2/2-0047/ir0 [saa7133[0]]
> tda9887 2-004b: chip found (at) 0x96 (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 2c f5 37 ff ff
> saa7133[0]: i2c eeprom 20: 01 2c 01 02 02 01 04 30 98 ff 00 a5 ff 21 00 c2
> saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff ff 0c 22 17 88 03 48 ca 0c
> 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
> saa7133[0]: registered device radio0
>
> but with tvtime-scanner -n PAL and KDETV no signal :(
> so i unload saa7134 ad try to load saa7134 card=81 and later saa7134_dvb....dmesg say :
>
>
> saa7133[0]: found at 0000:01:09.0, rev: 208, irq: 5, latency: 64, mmio: 0xd8100000
> saa7133[0]: subsystem: 11bd:002f, board: Philips Tiger reference design [card=81,insmod option]
> saa7133[0]: board init: gpio is 600c000
> tda9887 2-004b: chip found (at) 0x96 (saa7133[0])
> 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 2c f5 37 ff ff
> saa7133[0]: i2c eeprom 20: 01 2c 01 02 02 01 04 30 98 ff 00 a5 ff 21 00 c2
> saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff ff 0c 22 17 88 03 48 ca 0c
> 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
> Fsaa7133[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
> saa7133[0]: registered device radio0
> DVB: registering new adapter (saa7133[0]).
> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
>
>
> i think that's all is correct...but no signal everywhere tvtime-scanner and kdetv...
>
> where's my error?? pleaase help me ;
> thanks in advance
Kevin, unfortunately not all is correct ...
The problems on the 300i should not be related to those on 310i,
because it is totally different hardware.
You don't have a tda9887 at all, but it wrongly now sits on the tda8290
address, which is the IF part of the 8275a silicon tuner on your board
integrated in the saa7131e chip. No tuning this way.
The current code is even assumed to be able to detect the difference
between a tda9887 and tda8290, also between the older 8275 and the
hybrid 8275a silicon tuner, which should result in a tuner line in
"dmesg" with tda8290/75a registered. No chance without it!
I don't know what causes your eeprom read errors, but you should stop to
load saa7134-dvb in favor to get analog tv with card=77 first.
Attempts of digital tuning might cause i2c breakdown on the card, also
using the old code of the 8275 not _8275a_ silicon tuner. That's why I
asked for a _cold_ reboot and then try with card=77 and mercurial.
After modprobe -r the related modules first do "modprobe tuner debug=1".
Then you can try "modprobe -v saa7134 card=77 i2c_debug=1" to see if
hidden options slipped into your modprobe and where the i2c
communication fails. DVB-T doesn't work yet on the card and also tvtime
doesn't support it.
Cheers,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list