-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just compiled 2.4.20 + the 2002112 patch for 2.4.20rc3 + the cpufreq for rc3 on my Dell Inspiron 2650 (Mobile P4 1.9GHz. A few weeks work and a few things don't :) * I can successfully sleep and wakeup from S1, even while in X, which is wonderful. (great to see it working, thanks to everybody who's contributed!). However, the screen does not seem to be turned off, only much darker -- I can still see the screen albeit darkly when the system is supposedly asleep. Also, entering S1 means that the system clock seems to stop. For example, if I watch the clock on KDE's Kicker, and enter S1, then the system will show the same time when it wakes up as when it entered sleep. Also, the processor fan continues to run even when in S1. The fan stops while in standby mode in XP, IIRC, which is what I expect -- the processor is halted (I think) so it should cool down, so there's no need t * dmesg reveals a few errors, whether the are important or not I do not know: Journalled Block Device driver loaded ACPI-1103: *** Error: Method execution failed, AE_AML_REGION_LIMIT And after having cat'ed a few things in /proc/acpi, the following appears at the end of the dmesg: ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT ACPI-1103: *** Error: Method execution failed, AE_BAD_HEX_CONSTANT I'm current using NVidia's propreitary kernel modules, I'd be happy to re-test with this module not loaded if that is likely to make any difference. * Reading battery information partially works: chris@gandalf:/proc/acpi/battery/BAT1$ cat * alarm: unsupported present: yes ERROR: Unable to read battery information present: yes capacity state: ok charging state: unknown present rate: 0 mA remaining capacity: 3676 mAh present voltage: 16700 mV However, the battery is not recognised after removing and reinserting it. chris@gandalf:/proc/acpi/battery/BAT1$ cat * present: no present: no present: no * The /proc/acpi/ac_adapter and fan (and possibly other) directories are empty. * Slightly OT for here, but controlling the processor speed using cpufreq and /proc/cpufreq seems to work perfectly, with /proc/cpuinfo reporting that the speed varies between 1.2 and 1.9, depending whether I ask for performance or max battery. Whether it actually will increase battery life needs more investigation :) I remember there being a acpi->cpufreq patch -- has that been accepted into the main acpi patch yet? Does the patch only switch between the maximum and minimum speeds, or other speeds in between, as the SpeeedStep driver for XP does? A full dmesg is attached. - -- Chris Howells -- chris-NvB7AskkBIqIudiWw5vspbVCufUGDwFn@public.gmane.org, pp0u20d9@liv.ac.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE96VWwF8Iu1zN5WiwRAjdNAJ9v1vNEF3AzVVDVhwYBWSLAx9hT0gCcDdHk hZloPvz+jCS4z9qJbRN883w= =rppD -----END PGP SIGNATURE-----