From: Eric Valette <eric.valette@free.fr>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: akpm@osdl.org, andrew.grover@intel.com, sziwan@hell.org.pl,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list
Date: Mon, 21 Jul 2003 10:07:19 +0200 [thread overview]
Message-ID: <3F1B9F37.509@free.fr> (raw)
In-Reply-To: <200307210114.h6L1El7M018996@harpo.it.uu.se>
Mikael Pettersson wrote:
> While I don't dispute your machine has some problem, please
> do the following first before we completely blacklist it:
> - ensure you have the latest BIOS (ftp.asuscom.de has the ones for
> their desktop mainboards, presumably the laptop BIOSen are also there)
Have the latest BIOS from 3 June...
> - in what way is ACPI mandatory? does it fail to boot, or does it
> just lose some specific feature? If you just want suspend support,
> try APM if the machine has it
Many ACPI managed buttons, Fans, ...
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next prev parent reply other threads:[~2003-07-21 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 1:14 [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list Mikael Pettersson
2003-07-21 8:07 ` Eric Valette [this message]
2003-07-21 15:59 ` [ACPI] " Eric Valette
2003-07-21 16:18 ` Karol Kozimor
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 20:52 Grover, Andrew
2003-07-14 18:56 Linux 2.6-pre1 Does not boot on ASUS L3800C: lock up in acpi while "Executing all Devices _STA and_INIT methods" Grover, Andrew
2003-07-20 13:18 ` Eric Valette
2003-07-20 19:48 ` [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list Eric Valette
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=3F1B9F37.509@free.fr \
--to=eric.valette@free.fr \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=sziwan@hell.org.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).