laptop doesn't power off
tim.matthews7 at gmail.com
Tue Aug 11 08:07:34 UTC 2009
My problems appears to be the same as
http://www.freebsd.org/cgi/query-pr.cgi?pr=124412 as originally reported
here by someone who has more experience than me
If that pr gets fixed then I suspect my problem will too as it is described
like mine with the need to remove the battery to power off. Also my laptop
has an express card slot and memory stick duo slot which is a TI device and
not working last time I tested. That pr is using 1386, I am using amd64 but
I have just tried a i386 install disk and it couldn't shutdown either.
Thanks a lot.
Below is the message I sent to bf but forgot to send to the mailing list
On Tue, Aug 11, 2009 at 3:38 PM, Tim Matthews <tim.matthews7 at gmail.com>wrote:
> On Tue, Aug 11, 2009 at 1:22 AM, b. f. <bf1783 at googlemail.com> wrote:
>> On 8/10/09, Tim Matthews <tim.matthews7 at gmail.com> wrote:
>> > On Mon, Aug 10, 2009 at 12:47 AM, b. f. <bf1783 at googlemail.com> wrote:
>> > Setting hw.acpi.disable_on_reboot to 1 does nothing to help my power off
>> > problem. Just a reminder: my rebooting works fine or is this sysctl just
>> > named inappropriately?
>> Not exactly. It's a bit more complicated than that. I'll describe it
>> in more detail later. For the moment, try this: In
>> /boot/loader.conf, set
>> Now reboot the computer, using a verbose boot. Save the dmesg output
>> and look for any new acpi-related messages that weren't present in the
>> last dmesg you posted. acpi-related errors will usually consist of
>> strings starting with AE_. For example, you could see something like:
>> pcib4: could not get PCI interrupt routing table for \\_SB_.PCI0.BR12
>> - AE_NOT_FOUND
>> Let us see them if there are any. Now try the following:
>> shutdown -p now
>> shutdown -h now
>> shutdown -r now
>> You'll have to cut power manually if your computer fails to execute
>> any of them properly. What happens in each case -- what messages are
>> printed on the console?
>> Now try dropping to a shallow sleep state:
>> acpiconf -s 1
>> Again, what happens, and what messages, if any appear?
> I have tried different combinations of a lot of things and powering off not
> working, everything else working fine with no sign of acpi errors in logs.
> acpiconf -s 1 (or any other number) operation not supported. I am now very
> sure that my bios is up to date. Is there any thing that can be done to make
> freebsd's acpi behave like linux's acpi?
More information about the freebsd-acpi