All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: davidsen@tmr.com (bill davidsen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lockup with 2.4.9-ac10 on Athlon
Date: Fri, 21 Sep 2001 12:42:12 +0100	[thread overview]
Message-ID: <10119.1001072532@redhat.com> (raw)
In-Reply-To: <200109202208.f8KM8o902962@deathstar.prodigy.com>
In-Reply-To: <200109202208.f8KM8o902962@deathstar.prodigy.com>


davidsen@tmr.com said:
>  Look for BIOS updates. I have a BP6 (dual Celeron) system, and I am
> really disappointed that the only way I can power it down under
> software control is to boot to another o/s. You may be able to get a
> BIOS which works.

Strange - mine works. Either with APM and 'apm=power-off' on the command 
line, or with ACPI and a hack to work around the incompetence of Abit's 
BIOS engineers.

Me: "There's a one-char typo in your ACPI bytecode which prevents it from 
	working. This is the fix...."
Abit: "You can work around that by turning off ACPI support in the BIOS 
	setup"
Me: "But that just disables it, and makes it continue to not work. To make
	it work, it needs to be enabled - but there's a simple typo which
	prevents it from working."
Abit: <silence>

Sometimes it amazes me just how stupid some people can be and still 
actually keep their job.

--
dwmw2



  parent reply	other threads:[~2001-09-21 11:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 18:01 Lockup with 2.4.9-ac10 on Athlon Ignacio Vazquez-Abrams
2001-09-09 22:09 ` Ignacio Vazquez-Abrams
2001-09-10  0:24   ` Ignacio Vazquez-Abrams
2001-09-10  0:49     ` Kurt Garloff
2001-09-10  4:16     ` Ignacio Vazquez-Abrams
2001-09-20 22:08       ` bill davidsen
2001-09-20 22:32         ` Ignacio Vazquez-Abrams
2001-09-21 11:42         ` David Woodhouse [this message]
2001-09-21 14:17           ` Bill Davidsen
2001-09-21 14:39             ` David Woodhouse

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=10119.1001072532@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=davidsen@tmr.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.