From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] mcp61 sensors support
Date: Tue, 20 Feb 2007 08:02:53 +0000 [thread overview]
Message-ID: <20070220090253.215d8fea.khali@linux-fr.org> (raw)
In-Reply-To: <9ef864c50702182307q4364770cj53c6dbab30fcd887@mail.gmail.com>
Hi Thomas,
On Mon, 19 Feb 2007 16:36:25 -0500, Thomas Garner wrote:
> [root at ns ~]# lspci -v -s 00:01.1
> 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
> Subsystem: Elitegroup Computer Systems Unknown device 2602
> Flags: 66MHz, fast devsel, IRQ 11
> I/O ports at fc00 [sized]
> I/O ports at 1c00 [sized]
> I/O ports at f400 [sized]
> Capabilities: [44] Power Management version 2
Hmmm, OK. If the MCP61 is similar to the previous models, the two SMBus
controllers correspond to the 2nd and 3rd I/O port ranges. However I am
surprised because these used to always live back-to-back. In your case
the two addresses are completely different, which makes me suspect that
something is different.
Either way, if you want to try, we can instruct the i2c-nforce2 driver
to handle your chip as a supported one and see what happens. Here's the
procedure (as root):
modprobe i2c-nforce2
modprobe i2c-dev
echo "10DE 03EB" /sys/bus/pci/drivers/nForce2_smbus/new_id
(check the logs)
i2cdetect -l
(you should see the two nVidia SMBus listed)
i2cdetect 0
i2cdetect 1
(assuming the nVidia SMBus are bus numbers 0 and 1)
Please report your results. Beware that bad things might happen if it
happens that the MCP61 is not actually compatible with the older chips.
Hopefully nothing a reboot won't fix, though.
--
Jean Delvare
next prev parent reply other threads:[~2007-02-20 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 7:07 [lm-sensors] mcp61 sensors support Thomas Garner
2007-02-19 18:48 ` Jean Delvare
2007-02-19 19:39 ` Thomas Garner
2007-02-19 21:21 ` Jean Delvare
2007-02-19 21:36 ` Thomas Garner
2007-02-20 8:02 ` Jean Delvare [this message]
2007-02-21 2:55 ` Thomas Garner
2007-02-21 17:39 ` Jean Delvare
2007-02-22 3:02 ` Thomas Garner
2007-02-22 16:41 ` Jean Delvare
2007-02-22 17:43 ` Thomas Garner
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=20070220090253.215d8fea.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.