From: Craig Ringer <craig-izDLMxIPhbnw5XnJhPqE1ikBLnlaf3ui@public.gmane.org>
To: ACPI Devel list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: acpi and presario 700
Date: Fri, 18 Oct 2002 15:04:58 +0800 [thread overview]
Message-ID: <3DAFB29A.3060501@postnewspapers.com.au> (raw)
In-Reply-To: 3D929B6A000178E7@ims4c.cp.tin.it
>>i'm a newbie (acpi is in my kernel but how to apply?)
In case you missed it from the last post, you'll quite possibly need to
patch your kernel for ACPI support since the ACPI code shipped in the
kernel is very outdated. I don't use Red Hat, so its possible that their
kernel includes an up-to-date ACPI - but I wouldn't bet on it.
If you have any problems, download a vanilla 2.4 kernel from your local
kernel.org mirror and the latest ACPI patches from
sourceforge.net/projects/acpi, apply the ACPI patches, build and install
the kernel, then give it another try.
> Note: if you want S3 you must use 2.5 kernels
... however, you can get away with swsusp ( virtual S4 ) on a 2.4
kernel. I'm using it on my laptop, a Toshiba Satellite Pro 4600, and it
works a treat. Really nice in combination with win2k's hibernate feature
if you have to use win2k too (eg to make the crapmodem in your laptop work).
--
Craig Ringer
GPG Key Fingerprint: AF1C ABFE 7E64 E9C8 FC27 C16E D3CE CDC0 0E93 380D
-- if it ain't broke, add features 'till it is. (or:)
while (! broken) { features ++ ; broken = isBroken(features) }
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-18 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 6:27 Re:acpi and presario 700 salva_ste-nc/lrvXPQ4s
2002-10-18 7:04 ` Craig Ringer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 20:11 acpi " ruud
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=3DAFB29A.3060501@postnewspapers.com.au \
--to=craig-izdlmxiphbnw5xnjhpqe1ikblnlaf3ui@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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