Date: Fri, 5 Aug 2005 16:03:23 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: mse_software@charter.net Cc: stable@freebsd.org Subject: Re: ``shutdown -p now'' not working in 5.4 STABLE Message-ID: <p06230922bf1975e2f7f7@[128.113.24.47]> In-Reply-To: <1123213427.786.94.camel@yak.mseubanks.net> References: <1123187556.786.25.camel@yak.mseubanks.net> <p06230918bf183089b61b@[128.113.24.47]> <1123190717.786.49.camel@yak.mseubanks.net> <p0623091bbf1845419177@[128.113.24.47]> <1123213427.786.94.camel@yak.mseubanks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: >On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: > > >> Hmm. The more I think about this, the more I think I tripped >> across something similar once. I think it was something like >> I turned on 'APM' somewhere, or I added it to my kernel, or > > something. For power-down, you need to be using ACPI, not APM. >> But from your dmesg output, it looks like you are using ACPI, > > so I am probably not helping much with that guess either. > >Ok, I built APM into the kernel and gave it a few tries, fiddling >with different things. Sorry, my comments were not as clear as they should have been. What I meant is that my problem was *caused* by adding APM into the mix, when it should not have been there. That's what I meant by: For power-down, you need to be using ACPI, not APM. But all of this is just vague memory anyway. I haven't had any problems with my machines powering down for quite awhile now. (through many different system builds...) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06230922bf1975e2f7f7>