From owner-freebsd-mobile@FreeBSD.ORG Sun Oct 23 13:14:01 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 822C816A41F for ; Sun, 23 Oct 2005 13:14:01 +0000 (GMT) (envelope-from guru@Sisis.de) Received: from hunter.Sisis.de (hunter.sisis.de [193.31.11.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6BA643D46 for ; Sun, 23 Oct 2005 13:14:00 +0000 (GMT) (envelope-from guru@Sisis.de) Received: (from mail@localhost) by hunter.Sisis.de (8.8.8/8.8.8) id PAA00570 for ; Sun, 23 Oct 2005 15:12:38 +0200 (CEST) (envelope-from guru@Sisis.de) From: guru@Sisis.de Received: from hermes.sisis.de(193.31.10.38) by hunter.Sisis.de via smap (V2.1) id xma000566; Sun, 23 Oct 05 15:12:34 +0200 Received: from rebelion.Sisis.de (torwart.Sisis.de [193.31.10.94]) by hermes.sisis.de (8.8.8/8.8.8) with ESMTP id PAA10772 for ; Sun, 23 Oct 2005 15:13:56 +0200 (CEST) (envelope-from guru@Sisis.de) Received: (from guru@localhost) by rebelion.Sisis.de (8.13.3/8.13.3/Submit) id j9NDDru4001113 for freebsd-mobile@freebsd.org; Sun, 23 Oct 2005 15:13:53 +0200 (CEST) (envelope-from guru@Sisis.de) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to guru@Sisis.de using -f Date: Sun, 23 Oct 2005 15:13:52 +0200 To: freebsd-mobile@freebsd.org Message-ID: <20051023131352.GA935@rebelion.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE (i386) Subject: 5.4-REL && noteboock F/S AMILO-D && S4 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: guru@Sisis.de List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2005 13:14:01 -0000 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/