From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Supermicro X6DH8-G2+ / sensors not working
Date: Mon, 09 Oct 2006 20:03:39 +0000 [thread overview]
Message-ID: <20061009220339.b467d1e9.khali@linux-fr.org> (raw)
In-Reply-To: <451FF905.60001@hal.saar.de>
> Hi Jean,
>
> Jean Delvare wrote:
> > Well hopefully this new version of the driver will just work. However,
> > be aware that, contrary to the previous version, I couldn't give a try
> > to this one, so you're the first tester. This means there could be a
> > couple sharp edges left, please let me know if you notice anything
> > wrong.
> >
> > The changes are essentially in the way the driver is registered, so
> > basically, if you are able to load, unload and reload the driver, and
> > everything still works, it's a good sign that the conversion is a
> > success. You should also see the reserved I/O region in /proc/ioports
> > as "pc87427 FMC".
> >
> > Please give it a try and report!
> >
>
> I tried it - i.e. I replaced pc87427.c in a copy of the directory
> containing the old pc87427.c
> But I regret to report a failure. I try to document the relevant things...
Is the attached version any better? I had forgotten to create the
"name" attribute file, and libsensors needs it. This is fixed now,
hopefully this is all that was missing.
> By the way, I found that sensors-detect now detects a PC87360:
> Found `Nat. Semi. PC87360 Super IO Fan Sensors'
> (but not activated)
> If I try a 'modprobe pc87360' I get
> FATAL: Error inserting pc87360
> (/lib/modules/2.6.16-xen/kernel/drivers/hwmon/pc87360.ko): No such device
> pc87360: Device 0x09 not activated
> pc87360: No active logical device, module not inserted.
>
> I don't know if it's somehow related. I think, it finds it at least
> since the snapshot you published recently. It definitely didn't
> recognize before.
I have seen the same of the test system I had access to. I know for
sure that there is no such chip on the board, this is a misdetection.
Just ignore it. I can't tell why you didn't see it before.
--
Jean Delvare
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pc87427.c
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20061009/46037df5/attachment-0001.c
next prev parent reply other threads:[~2006-10-09 20:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 17:21 [lm-sensors] Supermicro X6DH8-G2+ / sensors not working Michael Kress
2006-10-04 13:15 ` Jean Delvare
2006-10-04 23:14 ` Michael Kress
2006-10-06 11:09 ` Jean Delvare
2006-10-07 7:35 ` Jean Delvare
2006-10-08 9:14 ` Michael Kress
2006-10-08 9:17 ` Jean Delvare
2006-10-08 10:25 ` Michael Kress
2006-10-08 10:59 ` Michael Kress
2006-10-08 12:21 ` Jean Delvare
2006-10-08 13:07 ` Michael Kress
2006-10-08 13:46 ` Jean Delvare
2006-10-08 14:42 ` Michael Kress
2006-10-08 17:03 ` Jean Delvare
2006-10-08 17:20 ` Michael Kress
2006-10-09 9:23 ` Jean Delvare
2006-10-09 18:03 ` Michael Kress
2006-10-09 20:03 ` Jean Delvare [this message]
2006-10-09 20:25 ` Michael Kress
2006-10-10 10:21 ` Jean Delvare
2006-10-14 11:43 ` Michael Kress
2006-10-14 16:49 ` Michael Kress
2006-10-15 9:03 ` Michael Kress
2006-10-15 12:03 ` Jean Delvare
2006-10-15 20:56 ` Michael Kress
2006-10-16 6:27 ` Jean Delvare
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=20061009220339.b467d1e9.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.