public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh-bQi0YA1h5vk@public.gmane.org>
To: Geert Uytterhoeven
	<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
	Roger Luethi <rl-7uj+XXdSDtwfv37vnLkPlQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Linux Kernel Development
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Vaio doesn't poweroff with 2.4.22
Date: Sun, 21 Sep 2003 16:50:18 +0200	[thread overview]
Message-ID: <200309211650.18881.josh@stack.nl> (raw)
In-Reply-To: <Pine.GSO.4.21.0309191053140.4488-100000-Q9iLAqk50tFNk+PO8Cj175kigfUh6rMo@public.gmane.org>

On Saturday 20 Sep 2003 15:17, Geert Uytterhoeven wrote:
> If I turn off CONFIG_X86_UP_APIC I get:
> | ACPI disabled because your bios is from 00 and too old
> | You can enable it with acpi=force
> | Sony Vaio laptop detected.
>
> and ACPI is disabled. Halt doesn't work.
>
> If I then pass `acpi=force' to explicitly enable ACPI, `halt' works again
> and powers off the machine, but `reboot' causes a black screen with IDE
> disk spun down, but no restart.
>
> Gr{oetje,eeting}s,

My PIII 650 with 2000 BIOS boots linux with acpi disabled for the same reason, 
unless force ACPI support. It reboots fine with ACPI forced. The ACPI support 
of this Intel BX mobo is good, so this is a false negative IMHO. (I wonder if 
the check is correct, shouldn't it say 2000 instead of 00 ?)

Jos

  parent reply	other threads:[~2003-09-21 14:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030915224136.GA11666@k3.hellgate.ch>
     [not found] ` <20030915224136.GA11666-NW/W/tFpkLjPJA67Yv3YjA@public.gmane.org>
2003-09-20 13:17   ` Vaio doesn't poweroff with 2.4.22 Geert Uytterhoeven
     [not found]     ` <Pine.GSO.4.21.0309191053140.4488-100000-Q9iLAqk50tFNk+PO8Cj175kigfUh6rMo@public.gmane.org>
2003-09-20 13:58       ` Willy Tarreau
2003-09-21 14:50       ` Jos Hulzink [this message]
     [not found]         ` <200309211650.18881.josh-bQi0YA1h5vk@public.gmane.org>
2003-09-22  6:44           ` Geert Uytterhoeven
2003-09-21 15:40       ` Markus Gaugusch
2003-09-23 12:23       ` Pavel Machek
2003-09-15  6:43 Geert Uytterhoeven
     [not found] ` <Pine.GSO.4.21.0309150835480.3191-100000-Q9iLAqk50tFNk+PO8Cj175kigfUh6rMo@public.gmane.org>
2003-09-15  7:03   ` Gerardo Exequiel Pozzi
     [not found]     ` <20030915040318.1f8bfd18.djgeray2k-/E1597aS9LQMlKAeRRkD2Q@public.gmane.org>
2003-09-15  7:09       ` Geert Uytterhoeven
2003-09-16 20:06   ` Pavel Machek
     [not found]     ` <20030916200655.GG602-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-09-17  9:21       ` Geert Uytterhoeven
     [not found]         ` <Pine.GSO.4.21.0309171120290.3644-100000-Q9iLAqk50tFNk+PO8Cj175kigfUh6rMo@public.gmane.org>
2003-09-17 10:31           ` Pavel Machek
     [not found]             ` <20030917103135.GL1205-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-09-17 12:46               ` Geert Uytterhoeven

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=200309211650.18881.josh@stack.nl \
    --to=josh-bqi0ya1h5vk@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rl-7uj+XXdSDtwfv37vnLkPlQ@public.gmane.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