From: "Andrew S. Johnson" <andy@asjohnson.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.53] So sloowwwww......
Date: Thu, 02 Jan 2003 01:26:40 -0600 [thread overview]
Message-ID: <3E13E9B0.8050504@asjohnson.com> (raw)
In-Reply-To: <fa.f29f77v.on2i97@ifi.uio.no>
Paul Rolland wrote:
> Well, I did made another kernel without ACPI and with APM,
> and it is working fine.
Did you try using acpi=no-idle in your kernel append line (if using
lilo) and see what difference that makes? It works in 2.4.
Andy Johnson
>
> To summarize :
> - ACPI Enumeration only is fine
> - More functionnalities from ACPI is bad.
>
> If someone has an idea and wants me to make tests, please contact
> me...
>
> Regards,
> Paul
next parent reply other threads:[~2003-01-02 7:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.el8u04v.1jks783@ifi.uio.no>
[not found] ` <fa.f29f77v.on2i97@ifi.uio.no>
2003-01-02 7:26 ` Andrew S. Johnson [this message]
2003-01-05 14:19 ` [2.5.54 + ACPI] Slow [Was: Re: [2.5.53] So sloowwwww......] Paul Rolland
2003-01-05 19:11 ` Randy.Dunlap
2003-01-05 19:34 ` Randy.Dunlap
2003-01-05 19:40 ` Paul Rolland
2003-01-05 19:46 ` Randy.Dunlap
2003-01-06 0:59 ` Martin J. Bligh
2003-01-06 7:24 ` Paul Rolland
2003-01-06 3:08 ` Bill Davidsen
2002-12-29 18:22 [2.5.53] So sloowwwww Hell.Surfers
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 17:47 Manfred Spraul
2002-12-29 17:54 ` John Bradford
2002-12-29 18:18 ` Paul Rolland
2002-12-29 17:12 rwhron
2002-12-29 17:13 ` Paul Rolland
2002-12-29 15:29 Paul Rolland
2002-12-29 16:56 ` Andrew Walrond
2002-12-29 17:12 ` Paul Rolland
2002-12-29 21:07 ` Andrew Walrond
2002-12-29 22:06 ` Paul Rolland
2002-12-29 17:30 ` John Stoffel
2002-12-29 17:36 ` Paul Rolland
2002-12-30 13:16 ` venom
2002-12-29 18:55 ` Alvaro Lopes
2002-12-29 19:16 ` Paul Rolland
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=3E13E9B0.8050504@asjohnson.com \
--to=andy@asjohnson.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox