All of lore.kernel.org
 help / color / mirror / Atom feed
From: war <war@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: ABIT IC7-G Linux Kernel Power Off Issue
Date: Fri, 10 Oct 2003 08:24:38 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0310100822430.27952@p500> (raw)

Just wanted to let everyone know I finally got a response with this issue:

-> Question, will this be fixed in 2.4?

Thanks to Andrew:

Subject:      Re: ABIT IC7-G Power Off Issue
From:         Andrew Schulman <andrex@deadspam.com>
Newsgroups:   alt.comp.periphs.mainboard.abit
Date:         Thu, 09 Oct 2003 19:59:16 -0400

> After executing: shutdown -i 0 -g 0 -y
> Gets to:
> Flushing hda hdb hdc, etc, then
> Power Down.
>
> But then it stays here, everything stays on, the video, the box, etc.

I used to have this exact problem.  I solved it by forcing the ospm_system
module to load at boot time, by mentioning it in /etc/modules.
ospm_system
is part of ACPI; on your system it might be a different module, e.g. if
you
use APM.

What seems to happen is that at power down, the last thing the kernel
wants
to do is to call ospm_system to turn the power off.  But the kernel module
loader has already been shut down, so if the module hasn't already been
loaded, it can't load and the kernel hangs.

I had this problem with the 2.4 kernels, but I believe it's been solved in
2.6.  I'm running 2.6.0-test4, and now that I look back I find that I
don't
even have an ospm_system module any more.  But the system still powers
down
correctly.  The last message I see on the screen now is "calling
acpi_power_off".  This isn't a module; it seems to be a function that's
built into the kernel when ACPI support is enabled.

Good luck,
Andrew.

-- 
To reply by email, change "deadspam.com" to "alumni.utexas.net"


                 reply	other threads:[~2003-10-10 12:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.58.0310100822430.27952@p500 \
    --to=war@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.