From: Alistair John Strachan <alistair@devzero.co.uk>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] abituguru3: Please send .. to the abituguru3 (see
Date: Mon, 20 Oct 2008 16:24:17 +0000 [thread overview]
Message-ID: <200810201724.17975.alistair@devzero.co.uk> (raw)
In-Reply-To: <alpine.DEB.1.10.0810191251550.19058@p34.internal.lan>
Hi Justin,
On Monday 20 October 2008 16:10:51 Justin Piszcz wrote:
[snip]
> Reboot, dmesg:
>
> [ 10.247075] abituguru3: found Abit uGuru3, motherboard ID: 0016
>
> Success.. and the sensors continue to work, btw the colon is off in one of
> the sensors (display artifact), not related to this patch/etc, just FYI:
[snip]
Thanks for testing, and reporting back.
Thanks also for noticing this small cosmetic artifact. When I looked into this
in more detail, I found many similar errors across other supported board
sensors. I've fixed them all up, together with the cosmetic issue in the
original "see MAINTAINERS" message, and I'll send this patch along shortly.
> There should be another fan running as well, will have to check that
> later, but the rest of the sensors look normal.
We had a report just recently of an unreported fan on a different mainboard.
It's entirely possible that the driver erroneously ignores it. When you next
get a chance, please verify that the machine's UGURU BIOS section can see the
fan and read its speed. If it can, we'll get the driver to export this fan.
--
Cheers,
Alistair.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-10-20 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 16:54 [lm-sensors] abituguru3: Please send .. to the abituguru3 (see Justin Piszcz
2008-10-19 19:53 ` Alistair John Strachan
2008-10-20 6:48 ` Jean Delvare
2008-10-20 15:10 ` Justin Piszcz
2008-10-20 16:24 ` Alistair John Strachan [this message]
2008-10-20 18:14 ` Justin Piszcz
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=200810201724.17975.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--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.