From owner-freebsd-hackers Tue Jul 29 05:07:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA07232 for hackers-outgoing; Tue, 29 Jul 1997 05:07:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA07219 for ; Tue, 29 Jul 1997 05:07:20 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA13070; Tue, 29 Jul 1997 21:36:40 +0930 (CST) From: Michael Smith Message-Id: <199707291206.VAA13070@genesis.atrad.adelaide.edu.au> Subject: Re: FreeBSD, APM and laptops In-Reply-To: <199707291146.NAA20155@vader.runit.sintef.no> from "Havard.Eidnes@runit.sintef.no" at "Jul 29, 97 01:46:17 pm" To: Havard.Eidnes@runit.sintef.no Date: Tue, 29 Jul 1997 21:36:40 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Havard.Eidnes@runit.sintef.no stands accused of saying: > > It's a Dell Latitude XPi. FWIW, I had NetBSD installed prior to > installing FreeBSD on this laptop, and there suspending worked > just fine (modulo PCMCIA issues). Their code is quite possibly better. > > Are you enabling APM first, with 'apmconf -e'? > > No. Do I need to? I didn't need to do that when my laptop ran > NetBSD, and foolishly (?) I assumed I didn't have to fiddle > anything extra to enable power management in FreeBSD either. Yes. For some time, automatically enabling power management was risky because the APM interface would spontaneously explode on the first call, making the kernel unbootable on those machines. > It appears problematic to find the default state for the > variables apmconf provide an interface to... I think I unserstand you here. Apmconf should at most be a wrapper to sysctl (but isn't). > Hmm, doing 'apmconf -e' may have solved at least part of my > problem. I think I need to experiment some more before the final > conclusion, but now I have at least once managed to take the PC > into and out of the suspend state, although the behaviour appears > somewhat erratic (sometimes it "auto-resumes" after about a > minute...). I haven't observed this, although I have seen 'zzz' suspend and then immediately resume again. If you have any time to investigate/work on this, your support would be greatly appreciated. If not, keep in touch so that the issues you've raised don't get lost. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[