5.4-REL && noteboock F/S AMILO-D && S4

[guru at Sisis.de]

Hello,

Maybe I'm asking something completely stupid, but after a lot
of re-boots and fsck's and Googles, I see no other way :-(

My notebook (Fujitsu Siemens AMILO D) claims to have
ACPI support as:

$ sysctl hw.acpi
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.reset_video: 1

and when I do (following the FreeBSD handbook) a

# acpiconf -s S4OS

it gets turned off (and hopefully suspended CPU and RAM to disk, I don't
know); the only real result is in /var/log/messages as

$ fgrep suspend /var/log/messages
Oct 23 11:02:11 rebelion acpi: suspend at 20051023 11:02:11
Oct 23 11:23:43 rebelion acpi: suspend at 20051023 11:23:43
Oct 23 11:52:35 rebelion acpi: suspend at 20051023 11:52:35
Oct 23 14:57:12 rebelion acpi: suspend at 20051023 14:57:12
$

The problem is, I don't know *how* to awake it again. The only
button which is working is the power-on of the mobile and this
does a normal boot-up (resulting in fsck's because the disks
not have been properly dismounted, of course not);

Is there some magic flag in re-boot to let it use the saved
BIOS? If so it would be nice to add a note of how to resume and
not only how to suspend the beast to the FreeBSD handbook :-)

Thx

	Matthias

-- 
Matthias Apitz / Sisis Informationssysteme GmbH
Gruenwalder Weg 28g / D-82041 Oberhaching
Fon: ++49 89 / 61308-351, Fax: -399, Mobile ++49 170 4527211
http://www.sisis.de/