From: mike corn <mikecorn@arcor.de>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Intel D975XBX2 motherboard "no sensors found"
Date: Sun, 22 Jul 2007 08:10:22 +0000 [thread overview]
Message-ID: <46A310EE.4080206@arcor.de> (raw)
Motherboard: Intel D975XBX2
CPU: Core 2 Quad 6600
Linux: Ubuntu 7.04
lm-sensors: 2.10.1
Your online docs are in shambles, so perhaps I did not understand them.
Here is exactly what I did:
1. sensors-detect: found i2c-i801 and eeprom
(I answered YES to all queries, including the auto add to /etc/modules)
2. modprobe i2c-i801 and eeprom
3. sensors --> "no sensors found"
Relevant outputs are pasted below.
Note "unknown adaptor NVIDIA i2c".
regards,
Mike
===================
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `NVIDIA i2c adapter 0 at 2:00.0'
Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55
0x56 0x57)
Chip `EDID EEPROM' (confidence: 8)
* Bus `SMBus I801 adapter at 4000'
Busdriver `i2c-i801', I2C address 0x50
Chip `eeprom' (confidence: 6)
* Bus `SMBus I801 adapter at 4000'
Busdriver `i2c-i801', I2C address 0x52
Chip `eeprom' (confidence: 6)
====================
To make the sensors modules behave correctly, add these lines to
/etc/modules:
#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter 0 at 2:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 2:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 2:00.0
i2c-i801
# Chip drivers
eeprom
#----cut here----
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2007-07-22 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 8:10 mike corn [this message]
2007-07-22 14:17 ` [lm-sensors] Intel D975XBX2 motherboard "no sensors found" Hans de Goede
2007-07-22 14:31 ` George Joseph (dev)
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=46A310EE.4080206@arcor.de \
--to=mikecorn@arcor.de \
--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.