New suspend/resume problem - need expert advice

[kgha]

Yes, it does.

I ran it from a terminal too, and there were no messages of any kind.

[flux]

Ok, then I will change the script to the short one for eeePCs 900 ...

Thank you for your investigation!

flux.

[kgha]

Thank you for your investigation!

flux.

I'm glad if I can contribute a tiny bit 

[kgha]

continued...

I've been doing some experimenting and found that it is unproblematic to keep also the sync, systohc, and chvt commands in the suspend file. Suspend/resume is a bit slower (but maybe less risk for corrupting anything?)

Here's my etc/acpi/suspend file at the moment:

Code:

#!/bin/bash

# switch to virtual terminal 1 to avoid graphics
# corruption in X
chvt 1

# set hardware clock
/sbin/hwclock --systohc

# write all unwritten data (just in case)
sync

# suspend
echo -n mem > /sys/power/state

# resume
/sbin/hwclock --hctosys

chvt 2

[flux]

You are right, the problems are resulting out of the lines concerning /proc/eee/fsb, because the script tries to clock down the CPU of the 900. I think this is not correct because the 900 is running per default with a higher FSB!?!?

flux.

[kgha]

Yes, with fluxflux-sl I have noticed that the freqency is constant 900 MHz both on AC and battery.. With xandros it automatically clocked down to 630 on battery.. But I think this can differ depending on the BIOS (my version is 0804). If I remember correctly some older versions were underclocked (630) by default.