All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Abituguru needs force=y
Date: Thu, 11 Oct 2007 08:26:36 +0000	[thread overview]
Message-ID: <470DDE3C.1050209@hhs.nl> (raw)

Graham Murray wrote:
> Hans de Goede <j.w.r.degoede@hhs.nl> writes:
> 
>> Interesting, thanks for the notification. The version in 2.6.23 check
>> a few DMI strings to make sure its running on an Abit motherboard
>> before randomly bit banging some io-ports. So I guess your motherboard
>> has different DMI strings then most, can you please mail me the output
>> of the dmidecode command? Then I'll make sure this gets fixed in
>> 2.6.24.
> 
> I think that the problem is that DMI does not work on my system. At boot
> I get the message "DMI not present or invalid" and running dmidecode
> confirms this. For the i386, there is no user option to disable DMI
> during kernel configuration.
> 
> newton ~ # dmidecode
> # dmidecode 2.9
> # No SMBIOS nor DMI entry point found, sorry.
> 

Hmm,

Have you tried updating your BIOS?

Taking this to the lm-sensors list:

Hi all,

As you can read above the new DMI checks in the abituguru driver are causing 
problems for this user, because he has one of the first abituguru motherboards 
which appearantly  doesn't have dmi. So I guess we should remove the check on 
systems where the BIOS doesn't have DMI? Does anyone have a better idea?

Regards,

Hans


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

             reply	other threads:[~2007-10-11  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  8:26 Hans de Goede [this message]
2007-10-13 12:32 ` [lm-sensors] Abituguru needs force=y Jean Delvare
2007-10-14  7:13 ` Hans de Goede
2007-10-14  7:42 ` Graham Murray
2007-10-14 12:27 ` Hans de Goede

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=470DDE3C.1050209@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.