From: petit.frederic@free.fr (fred)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] i2cdetect fails on a Asus P5ND2-Sli
Date: Fri, 09 Dec 2005 19:41:12 +0000 [thread overview]
Message-ID: <4399DDD8.2060608@free.fr> (raw)
fred a ?crit :
> Hi,
>
> My kernel is 2.6.14, i2c-nforce2 & it87, which are known to work
> with lm-sensors, are built-in kernel, on a Debian sarge.
>
> it87 works fine (I'll come back later on this, I have a few questions),
> but i2c-nforce2 fails :
> marsu{pts/0}:~/[1]/> 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
> Error: No I2C busses found!
> Be sure you have done 'modprobe i2c-dev'
> and also modprobed your i2c bus drivers
>
> My kernel is set as :
>
> CONFIG_I2C=y
> CONFIG_I2C_CHARDEV=y
> CONFIG_I2C_ALGOBIT=y
> CONFIG_I2C_ISA=y
> CONFIG_I2C_NFORCE2=y
> CONFIG_FB_NVIDIA_I2C=y (for framebuffer, but now, it's not the problem)
>
>
> What's wrong ??
And lspci sounds good :
0000:00:0a.0 ISA bridge: nVidia Corporation: Unknown device 0030 (rev a3)
Subsystem: Asustek Computer, Inc.: Unknown device 818a
Flags: bus master, 66MHz, fast devsel, latency 0
0000:00:0a.1 SMBus: nVidia Corporation: Unknown device 0034 (rev a2)
Subsystem: Asustek Computer, Inc.: Unknown device 818a
Flags: 66MHz, fast devsel, IRQ 3
I/O ports at e400 [size2]
I/O ports at 5000 [sized]
I/O ports at 5100 [sized]
Capabilities: <available only to root>
--
Fred.
reply other threads:[~2005-12-09 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4399DDD8.2060608@free.fr \
--to=petit.frederic@free.fr \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.