From owner-freebsd-acpi@FreeBSD.ORG Mon Oct 24 07:57:11 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCDB516A41F for ; Mon, 24 Oct 2005 07:57:11 +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 87C4143D48 for ; Mon, 24 Oct 2005 07:57:10 +0000 (GMT) (envelope-from guru@Sisis.de) Received: (from mail@localhost) by hunter.Sisis.de (8.8.8/8.8.8) id JAA09468 for ; Mon, 24 Oct 2005 09:55:47 +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 xma009464; Mon, 24 Oct 05 09:55:34 +0200 Received: from rebelion.Sisis.de (rebelion.Sisis.de [193.31.10.34]) by hermes.sisis.de (8.8.8/8.8.8) with ESMTP id JAA16971; Mon, 24 Oct 2005 09:57:04 +0200 (CEST) (envelope-from guru@Sisis.de) Received: (from guru@localhost) by rebelion.Sisis.de (8.13.3/8.13.3/Submit) id j9O7utXb001776; Mon, 24 Oct 2005 09:56:55 +0200 (CEST) (envelope-from guru@Sisis.de) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to guru@Sisis.de using -f Date: Mon, 24 Oct 2005 09:56:55 +0200 To: freebsd-acpi@freebsd.org Message-ID: <20051024075655.GA1425@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: Fwd: 5.4-REL && noteboock F/S AMILO-D && S4 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: guru@Sisis.de List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2005 07:57:12 -0000 Hello, Yesterday I've send the attached e-mail to freebsd-mobile@freebsd.org but perhaps it belongs more to this list here; Meanwhile I did some further steps as advised in the FreeBSD handbook and tried to enable ACPI_DEBUG as said there for trouble shooting; enabling ACPI_DEBUG results in acpi.ko missing a function db_readline() and so I added to the kernel 'options KDB' (I found this hint in Goggle). After re-building all the kernel modules it is now complaining about: $ egrep -i 'uttrace|KLD' /var/log/messages Oct 24 09:22:02 rebelion kernel: link_elf: symbol AcpiUtTrace undefined Oct 24 09:22:02 rebelion kernel: KLD file acpi.ko - could not finalize loading $ but I don't understand this because 'AcpiUtTrace' is in acpi.ko: # nm acpi.ko | fgrep AcpiUtTr 0003e9d0 t AcpiUtTrace 0003e9fc t AcpiUtTracePtr 0003ea2c t AcpiUtTraceStr 0003ea5c t AcpiUtTraceU32 0003dbb8 t AcpiUtTrackAllocation 0003e8d0 t AcpiUtTrackStackPtr 0003f94c t AcpiUtTranslateOneCid # nm utdebug.o | fgrep AcpiUtTr 00000110 T AcpiUtTrace 0000013c T AcpiUtTracePtr 0000016c T AcpiUtTraceStr 0000019c T AcpiUtTraceU32 00000010 T AcpiUtTrackStackPtr # What does this means? And again, is there some overall description how suspend to 'S4OS' should work and how the resume must be initiated? I read in Goggle that for S4OS the RAM is filed to some 'hibernation' file to disk, where this file should appear? and how a re-boot will pick it up? I've 1 GByte of RAM but can't see any file large enough to fit my RAM into; Thanks in advance matthias ----- Forwarded message from guru@Sisis.de ----- From: guru@Sisis.de Date: Sun, 23 Oct 2005 15:13:52 +0200 To: freebsd-mobile@freebsd.org Subject: 5.4-REL && noteboock F/S AMILO-D && S4 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 _______________________________________________ freebsd-mobile@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mobile To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" ----- End forwarded message ----- -- 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/~guru/