On Sunday 11 September 2005 04:46 pm, Hans Verkuil wrote: > > Please provide the output of the following: run i2cdetect (hopefully > installed on your system). You should see a list of installed i2c busses. > Now run i2cdetect -a <busnr> where busnr is the number of the ivtv i2c bus > (pick one). Say 'Y' to the 'Continue' question and mail the output. > > I get the feeling that the cx25840 chip might be using a different I2C > address then 0x44. This should verify that. > > Hans
For future reference w/ other Gentoo users who may have the same problem it
turns out that i2cdetect is part of the lm_sensors package. I just installed
that.
Anyways I ran it and it complained about not having i2c_dev installed so I
modprobed that and ran it again. There are two i2c busses and here is the
output for each of them:
gratz1 ~ # i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
i2cdetect -l
i2cdetect -V
I2CBUS is an integer
With -a, probe all addresses (NOT RECOMMENDED)
With -q, uses only quick write commands for probing (NOT RECOMMENDED)
With -r, uses only read byte commands for probing (NOT RECOMMENDED)
If provided, FIRST and LAST limit the probing range.
With -l, lists installed busses only
Installed I2C busses:
i2c-1 unknown ivtv i2c driver #1
Algorithm unavailable
i2c-0 unknown ivtv i2c driver #0
Algorithm unavailable
gratz1 ~ # i2cdetect -a 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0.
I will probe address range 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX UU XX XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: UU UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
gratz1 ~ # i2cdetect -a 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/1.
I will probe address range 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX UU XX XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
I'm not sure I totally understand this output but if I'm guessing correctly it
looks like on bus 0 we have addresses 0x1b,0x43,0x50,0x60 and 0x61. On bus1
we have 0x1b,0x43,0x50, and 0x61. Does look right?
Thanks!
Paul
pgpyrzvp7okah.pgp
Description: PGP signature
