From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] abituguru3: no Abit uGuru3 found
Date: Thu, 08 Jan 2009 19:21:35 +0000 [thread overview]
Message-ID: <4966523F.60809@hhs.nl> (raw)
In-Reply-To: <49657F3B.3060607@NickAndBarb.net>
Alistair John Strachan wrote:
> On Thursday 08 January 2009 17:09:43 Jean Delvare wrote:
>> On Thu, 08 Jan 2009 13:02:38 +0100, Hans de Goede wrote:
>>> Nick Pasich wrote:
>>>> No BIOS update....
>>>>
>>>> Here's the output from "dmidecode" Attached...
>>> Hmm, nasty. We've got "IP35 Pro(Intel P35-ICH9R)" as identifaction string
>>> in the driver, and your DMI table has: "IP35 PRO(P35+ICH9R)"
>>>
>>> You should be able to work around your problem (for now) by doing this
>>> (as root):
>>>
>>> modprobe abituguru3 force=1
>>>
>>> After that, please do "dmesg" and copy paste the relevant (abituguru
>>> related) lines in your mail, that will help us diagnose this.
>> Might be worth reading this discussion thread again:
>> http://lists.lm-sensors.org/pipermail/lm-sensors/2008-October/024522.html
>>
>> We gave up on fixing it back then, but apparently there really is a
>> need. Alistair, do you have a patch?
>
> I think the consensus we came to at the time was to switch to strncmp'ing a
> subset of the DMI string, but in this case we'll need strncasecmp. This isn't
> too terrible as false positives are pretty unlikely (we already check the
> board manufacturer too, which does seem to be unchanging). Hans?
>
That was my idea too, just make the dmi string stored in the driver: "IP35 Pro"
and do a strncasecmp for the length of the string in the driver, with the one
from the BIOS, if it is a match assume we have found an abituguru3 equipped
motherboard.
> Of course, if Abit start putting arbitrary spaces and hyphens into the names
> too, all bets are off. But I read that their motherboard division was ceasing
> operation soon so (alas) this shouldn't be a problem. :-)
>
I didn't know that.
> Find attached a patch that should fix it (Nick, please test this if you can).
>
Yes that is exactly what I had in mind, +1 :
Reviewed-By: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-01-08 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 4:21 [lm-sensors] abituguru3: no Abit uGuru3 found Nick Pasich
2009-01-08 7:49 ` Hans de Goede
2009-01-08 11:25 ` Nick Pasich
2009-01-08 12:02 ` Hans de Goede
2009-01-08 17:09 ` Jean Delvare
2009-01-08 18:09 ` Alistair John Strachan
2009-01-08 18:53 ` Nick Pasich
2009-01-08 19:21 ` Hans de Goede [this message]
2009-01-08 19:45 ` Jean Delvare
2009-01-08 19:53 ` Alistair John Strachan
2009-01-08 19:58 ` Alistair John Strachan
2009-01-08 22:22 ` Hans de Goede
2009-01-09 13:08 ` Hans de Goede
2009-01-12 9:06 ` 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=4966523F.60809@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.