All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Berger <oberger@ouvaton.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Incorrect ACPI blacklisting of ASUS P4B266 ?
Date: Thu, 30 Apr 2009 06:22:23 +0200	[thread overview]
Message-ID: <87preupy80.fsf@olivierberger.com> (raw)
In-Reply-To: <200904281956.50640.trenn@suse.de> (Thomas Renninger's message of "Tue\, 28 Apr 2009 19\:56\:49 +0200")

Thomas Renninger <trenn@suse.de> writes:

> On Tuesday 28 April 2009 19:15:47 Olivier Berger wrote:
>> Thomas Renninger <trenn@suse.de> writes:
>
>
>> I'm thinking about some kind of warning message that might be provided
>> by the kernel.
>> 
>> Currently, the blacklisting issues something like : 
>>  xxx detected : force use of acpi=ht 
>> 
>> Maybe in some greylisted cases (like such ASUS P4B266), an additional
>> message may be issued, something like :
>>  xxx detected : may work with acpi=force (test at own risk)
>> or something like that ?
> Sounds like a good idea.
> Something like that (not tested at all).
> I could imagine Len adds this one if you give it a try and see
> the message popping up in dmesg.

I can confirm this works.

Here's the dmesg :
Apr 29 23:17:42 asustour kernel: [    0.000000] ASUS P4B266 detected: force use of acpi=ht
Apr 29 23:17:42 asustour kernel: [    0.000000] Latest BIOSes might work better with acpi=force

Hope this is would be at least better than previous state.

Thanks for your help.

Best regards,
-- 
Olivier BERGER 
(OpenPGP: 1024D/B4C5F37F)
http://www.olivierberger.com/weblog/

  reply	other threads:[~2009-04-30  4:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 15:32 Incorrect ACPI blacklisting of ASUS P4B266 ? Olivier Berger
     [not found] ` <200904021502.31021.trenn@suse.de>
2009-04-25 19:35   ` Olivier Berger
2009-04-27 10:18     ` Thomas Renninger
2009-04-28  6:09       ` Olivier Berger
2009-04-28 11:39         ` Thomas Renninger
2009-04-28 17:15           ` Olivier Berger
2009-04-28 17:56             ` Thomas Renninger
2009-04-30  4:22               ` Olivier Berger [this message]
2009-05-06  6:11                 ` Olivier Berger
2009-05-14 17:14               ` Len Brown
2009-05-17  7:38                 ` Olivier Berger
2009-05-22  5:52                   ` Olivier Berger
2009-05-14 17:18     ` Len Brown

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=87preupy80.fsf@olivierberger.com \
    --to=oberger@ouvaton.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=trenn@suse.de \
    /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.