By Date: <-- -->
By Thread: <-- -->

pinnacle 310i Problems maybe i2c



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, and thanks.

After each reboot i have when i type lsmod :
Module Size Used by
nvidiafb 47260 0
i2c_algo_bit 7816 1 nvidiafb
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
i2c_nforce2 5376 0
i2c_core 18000 5 nvidiafb,i2c_algo_bit,saa7134,ir_kbd_i2c,i2c_nforce2


there is already this module loaded. I don't know why they loads automatically.
So if i do : dmesg | grep eeprom i got this :
saa7133[0]: i2c eeprom read error (err=-5)


so if i remove the module with
rmmod saa7134  and latera load it with  modprovbe saa7134 card=77 alsa=1
the error remains!!!

if dvb-t is not supported i want at least use this card with analog and not buy another one :(

thanks so much

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