Re: Kernel 2.5 configuration, was: compaq evo 800v dsdt

On Fri, Feb 14, 2003 at 10:36:02AM +0000, Faye Pearson wrote:

Hi,

Ducrot Bruno [ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org] wrote:

quoted

The P4-M is supported by the speedstep "legacy" driver in cpufreq.

I think this is a big problem at the moment in the kernel 2.5 power
management configuration.

In 2.5, power state of the CPU (aka SpeedStep, Longhaul, ARM, etc)
is done via cpufreq which present a more general interface than
ACPI power state management of CPUs.
Speedstep 'legacy' support is also here as a cpu driver
as well, usefull when ACPI do not provide support for it (as
my toshiba).

There are too many ways of doing the same
thing, and things which look as though they are new in 2.5 (cpufreq) say
that they are 2.4 and 'legacy'.  And SWSUSP, should it be on or off if you
want to try S3/4 BIOS?

Same.  Swsusp is 'generic'.  It is expected that it will work
with other archs as well (that is why I don't see any perticular
reason to trigger swsusp via /proc/acpi/sleep).

What are the options which should be turned on to have the best
supported configuration for all ACPI features including S3/S4 sleep.

All acpi but not toshiba (unless you dont have a real toshiba) and HT only.
You have also to get at least PM and SWSUSP (PM for devices suspensions,
and swsusp for a kind of S4 and a really really basic checkpoint of
processes).

Which kernel and patches should I apply to have the best starting point
for helping debug?

I will be happy to get one myself :))

I've compiled up a 2.5.60 kernel but I'm not sure I have the correct set
of options enabled.
Also, the kernel PCMCIA (yenta) drivers don't work for me on a Sony Vaio
GRX516MD.  I've been using pcmcia-cs drivers under 2.4 but I believe I
have to use the kernel drivers for 2.5 and they fail to allocate an IRQ
because of lack of resources for my wireless card when it is plugged.

How can I tell whether the failure to allocate an IRQ is a PCMCIA issue
or an ACPI issue?  Under 2.4 everything seems to want to use IRQ 9 but

I don't know (sorry).

it only seems to be a problem for USB which complains that it's seeing
IRQs for non USB events and doesn't actually function properly.

I've put as much information as I can think of on my home page at
http://dude.noc.clara.net/~faye/ if any other information is necessary,
I'll happily provide it.

I'll take a look, but alas I will be off-line for one week at monday..

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en