From: Richard Marz <Richard.marz@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] Shutdown -h now is not powering down system.
Date: Sun, 03 Jun 2007 21:15:25 -0400 [thread overview]
Message-ID: <1180919725.17538.5.camel@localhost> (raw)
In-Reply-To: <AA0639A1EB70AE409130258CE7BDC31806646B9C@messenger.cv63.navy.mil>
halt -dp worked for me...never tried it before. Now, I did do a couple
of things. I upgraded my kernel to 2.6.20r8 and set the acpi=force
kernel parameter. I don't know whether the acpi=force paramenter fixed
the problem. I did see the gentoo shutdown.sh script (which you can view
at the bottom of this message) and it seems to call the halt command
with the options -dp. This means that before the same halt -dp was being
used and the system did not shutdown properly. Now I manually enter the
halt -dp command and it works flawlessly. So, maybe it was the kernel
upgrade or the acpi=force kernel parameter that is causing it to work.
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
opts="-d"
[ "${INIT_HALT}" != "HALT" ] && opts="${opts}p" # here it is
[ "${RC_DOWN_INTERFACE}" = "yes" ] && opts="${opts}i"
[ "${RC_DOWN_HARDDISK}" = "yes" ] && opts="${opts}h"
/sbin/halt "${opts}"
# hmm, if the above failed, that's kind of odd ...
# so let's force a halt
/sbin/halt -f
On Fri, 2007-06-01 at 12:47 +0900, burlingk@cv63.navy.mil wrote:
>
> > -----Original Message-----
> > From: Richard Marz [mailto:Richard.marz@verizon.net]
> > Sent: Friday, June 01, 2007 11:40 AM
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] Shutdown -h now is not powering
> > down system.
> >
> >
> > No. But, I will try it now. I'll let you know if it works in
> > a few minutes because I'm downloading the latests kernel
> > sources. On Thu, 2007-05-31 at 23:30 -0300, Davi wrote:
> > > shutdown -h now -P
> >
> > --
> > gentoo-user@gentoo.org mailing list
> >
>
> If shutodwn -h now -P doesn't work, try
> shutdown -P -h now
>
> I know that is just a matter of symantics, but a lot
> of programs want the "options" all in one spot. ^^;;
> Not sure about this one.
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-04 1:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 3:47 [gentoo-user] Shutdown -h now is not powering down system burlingk
2007-06-04 1:15 ` Richard Marz [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 2:24 Richard Marz
2007-06-01 2:30 ` Davi
2007-06-01 2:39 ` Richard Marz
2007-06-01 4:46 ` Richard Marz
2007-06-01 2:51 ` Norberto Bensa
2007-06-01 4:49 ` Richard Marz
2007-06-01 4:50 ` Richard Marz
2007-06-01 3:57 ` Dale
2007-06-01 5:03 ` Richard Marz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180919725.17538.5.camel@localhost \
--to=richard.marz@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox