Date: Wed, 21 May 2003 20:15:02 +0800 From: Robert Storey <y2kbug@ms25.hinet.net> To: freebsd-questions@freebsd.org Subject: Re: shutdown -p now Message-ID: <20030521201502.0f00f07b.y2kbug@ms25.hinet.net> In-Reply-To: <3.0.5.32.20030520204643.01366cc0@sage-one.net> References: <20030521092225.5a6a4442.y2kbug@ms25.hinet.net> <3.0.5.32.20030520204643.01366cc0@sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 May 2003 20:46:43 -0500 "Jack L. Stone" <jackstone@sage-one.net> wrote: > At 09:22 AM 5.21.2003 +0800, Robert Storey wrote: > >Dear All, > > > >I'm trying to get my computer to shut down and turn the power off. I'm > >aware of the command "shutdown -p now". It doesn't work for me, and > >after ================ SNIP ============= > Don't know why your switch quit, but if your computer can manage the > shutdown, you need these: > > In the kernel > # device apm0 at nexus? flags 0x20 #Advanced Power Management Dear Jack, Thanks for the information. I went ahead and tried that, but when I tried to configure the new custom kernel, I got this error message: root@sonic:/sys/i386/conf> /usr/sbin/config CUSTOM2 config: CUSTOM2:156: devices with zero units are not likely to be correct I decided to stop there rather than compile a possibly flakey kernel. Is this error message anything to worry about, or am I doing something wrong? regards, Robert > ...and in rc.conf > # apm_enable="YES" > > You should see in the bootup (dmesg): > apm0: <APM BIOS> on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > > Hope it helps... > > Best regards, > Jack L. Stone, > Administrator > > SageOne Net > http://www.sage-one.net > jackstone@sage-one.net > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030521201502.0f00f07b.y2kbug>