Date: Sat, 17 Jun 2006 06:39:10 -0500 (CDT) From: "Jonathan Horne" <jhorne@dfwlp.com> To: freebsd-questions@freebsd.org Subject: Re: freebsd on a newer pc Message-ID: <52628.24.1.139.244.1150544350.squirrel@mail.dfwlp.com> In-Reply-To: <8059E230-1203-47F4-B173-00650DC6078E@shire.net> References: <44125.167.246.36.14.1150464410.squirrel@mail.dfwlp.com> <53137.24.1.139.244.1150499368.squirrel@mail.dfwlp.com> <8F95D008-1650-4EA1-AEBB-F2C6863BCC07@shire.net> <55254.24.1.139.244.1150514984.squirrel@mail.dfwlp.com> <8059E230-1203-47F4-B173-00650DC6078E@shire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Jun 16, 2006, at 9:29 PM, Jonathan Horne wrote: > >>> >>> On Jun 16, 2006, at 5:09 PM, Jonathan Horne wrote: >>>> >>>> well, i figured out that if at the boot selection screen, if i >>>> choose >>>> option 2 "boot with acpi enabled", i can then give 'shutdown -p >>>> now' and >>>> the system will then power off properly. easy enough... >>>> >>>> but how do i set option 2 as my default boot selection? i dont see >>>> anything about this in the handbook. >>> >>> >>> My experience has been that once you boot that way once it becomes >>> the default. Play around with it >>> >> >> i dont think thats the behavior im getting. when i hit 2 to boot: > > It may depend on how known your MB is to support acpi. On my > machines to boot default with acpi and if I tell it not to boot with > acpi at boot, when I reboot that is now the default. > > I am not an expert on this. Maybe your MB is a "known" bad acpi one? > > --- > Chad Leigh -- Shire.Net LLC > Your Web App and Email hosting provider > chad at shire.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" > man i hope thats not the case. the computer im working with here is a fairly new hp dc7100. i know hp does a lot of non-microsoft stuff, so i would hope that their technology has the benefits of trickledown from all the r&d they can afford. my whole point of fighting with this feature, is so that my system can WOL. if i sent 'shutdown -p now' from remote, and then later if i want the system back on again... if its hanging at the "system has shutdown, hit any key to reboot" promt, WOL will do nothing! oh well, ill keep at it. thanks, jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52628.24.1.139.244.1150544350.squirrel>