shutdown -p, APM on 5.3
From: Keve Nagy (no_spam_at_poliod.hu)
Date: 02/25/05
- Next message: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Previous message: Mike Scott: "Odd routing problem"
- Next in thread: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Reply: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Reply: Keve Nagy: "Re: shutdown -p, APM on 5.3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Feb 2005 12:35:53 +0000
Hi Everyone,
*Background*:
Two days ago I build my 5.3-STABLE system. This is my first time
using the 5.x series, so please excuse me if I lack some of the trivial
knowledge about it or if I am trying to do things the 4.x way.
*Problem*:
I cannot get "shutdown -p now" to actually power off the PC.
It worked fine on 4.x, but it seems that under 5.x is has to be done in
a different way.
*known*:
On 4.x I needed APM for this, and all I had to do was:
- adding the line 'en apm' to /boot/kernel.conf
- adding the lines 'apm_enable="YES"' and 'apmd_enable="YES"' to
/etc/rc.conf
(and reboot, of course)
#
from this on, dmesg included:
apm0: <APM BIOS> on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
#
and "shutdown -p" did turn the PC off.
*confusion*:
Following the related messages in this newsgroup since 5.0R, backed up
by various other sources, now I believe that ACPI brings in a lot of
reliability problems and most of the time it does not work.
This is enlarged by the fact that I have never used ACPI before, so as
every primitive tribesman I fear the unknown.(thus trying 5x only now).
As far as I undestand the 5.x series is kind of _forcing_ the use of
ACPI instead of APM, and as a consequence of this APM is not "available"
as much or easily on 5.x as it was on 4.9R for example.
*approach*:
Reading docs, hadbook, man pages, faq and kernel NOTES gave me very
little useful help in this topic. I found that I have to enable apm in
the kernel so I added "device apm" to my custom kernel. Using "kldload
apm" tells me not to load that module from userland. An attempt of
placing 'apm_load="YES"' in /boot/loader.conf did not load the apm
module, at least kldstat did not reveal it.
In a nutshell, neither of the above nor their combinations gave me
the expected result of being able to power down the PC by issuing
"shutdown -p now".
*questions*:
How can I allow "shutdown -p" to power-down the PC under FreeBSD 5.3?
To achieve the above, can I simply enable APM only (and none of ACPI)
just as I did in 4.9R?
How do I enable APM on 5.3?
What has replaced /boot/kernel.conf? Is it device.hints?
Is ACPI really as unreliable as I believe it is?
If the only thing I need this for is "shutdown -p" to be able to
power off and no other power management requirements exist, is there
still be any advantage by using ACPI instead of APM, or any disadvantage
using APM instead of ACPI?
Any suggestion, pointer, idea, solution or comment in the topic is more
than welcome here.
Thank you!
Keve
-- If you need to reply directly: keve(at)mail(dot)poliod(dot)hu
- Next message: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Previous message: Mike Scott: "Odd routing problem"
- Next in thread: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Reply: Michel Talon: "Re: shutdown -p, APM on 5.3"
- Reply: Keve Nagy: "Re: shutdown -p, APM on 5.3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
