public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Juraj Bednar <juraj@bednar.sk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: smp_num_cpus redefined? (compiling 2.2.18 for non-SMP?)
Date: Wed, 7 Feb 2001 00:59:20 +0100	[thread overview]
Message-ID: <20010207005920.C949@werewolf.able.es> (raw)
In-Reply-To: <20010207005203.A19812@rak.isternet.sk>
In-Reply-To: <20010207005203.A19812@rak.isternet.sk>; from juraj@bednar.sk on Wed, Feb 07, 2001 at 00:52:04 +0100


On 02.07 Juraj Bednar wrote:
> Hello,
> 
> 
>   the same for vanilla 2.4.1 and 2.4.1ac3. Everything works ok until I turn
> off SMP
> support (which is required to make it possible to turn off the machine using
> APM, since
> ACPI is completely broken in 2.4.1 for me).
> 

You do not need to do that. Enable both SMP and APM (just APM support, no
ACPI nor any other apm option). And add to your lilo.conf file a line:
append="apm=power-off".

At boot you will see a log message like:

apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
apm: disabled - APM is not SMP safe (power off active).

So kernel diables APM but lets the power-off feature active.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.1-ac4 #1 SMP Tue Feb 6 22:06:38 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-07  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 23:52 smp_num_cpus redefined? (compiling 2.2.18 for non-SMP?) Juraj Bednar
2001-02-06 23:59 ` J . A . Magallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-07  0:17 Juraj Bednar
2001-02-06  0:06 Miller, Brendan
2001-02-06  6:39 ` Keith Owens

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=20010207005920.C949@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=juraj@bednar.sk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox