Date: Fri, 20 Nov 2009 10:49:48 +0000 From: Jerry Marles <jerry@marles.org> To: freebsd-acpi@freebsd.org Subject: Re: HP Pavillion does not power off Message-ID: <1258714188.3487.38.camel@lenny.internal> In-Reply-To: <1258394735.3278.34.camel@lenny.internal> References: <1257798198.3265.12.camel@lenny.internal> <1257805380.3265.21.camel@lenny.internal> <20091115164712.D65262@sola.nimnet.asn.au> <1258394735.3278.34.camel@lenny.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2009-11-16 at 18:05 +0000, Jerry Marles wrote: > On Sun, 2009-11-15 at 16:58 +1100, Ian Smith wrote: > > On Mon, 9 Nov 2009, Jerry Marles wrote: > > > On Mon, 2009-11-09 at 20:23 +0000, Jerry Marles wrote: > > > > On Sun, 2009-11-08 at 10:41 +0000, Jerry Marles wrote: > > > > Hello, > > > > > > > > > > I have a HP Pavillion desktop PC model g3001.uk. The problem I have is > > > > > that halt -p does not power it off. The light on the power button goes > > > > > off but I can hear that it is still running. If I hold down the power > > > > > button for a few seconds the power can be heard to go off but then it > > > > > boots right back up again. Windows and Linux can power it off > > > > > successfully. > > > > > > > > > > Regards > > > > > > > > > > Jerry Marles > > > > > > > > > > > > > with further investigation I have found that > > > > > > > > acpiconf -s 5 results in invalid sleep type (5) > > > > > > > > but acpiconf -s 4 powers it off successfully so if I could just make > > > > halt -p do whatever acpiconf -s 4 is doing the problem would be solved. > > > > > > > > any advice would be much appreciated. > > > > > > dmesg after boot -v is here http://www.marles.org/acpi/dmesg.txt > > > > > > sysctl hw.acpi is here http://www.marles.org/acpi/hwacpi.txt > > > > > > acpidump is here http://www.marles.org/acpi/acpidump.txt > > > > Seeing noone else has had a go: > > > > It seems pretty strange that acpiconf -s 4 powers it off properly. > > your hwacpi.txt only shows .. > > > > hw.acpi.supported_sleep_state: S1 S3 S4 S5 > > hw.acpi.power_button_state: S5 > > hw.acpi.sleep_button_state: S1 > > hw.acpi.lid_switch_state: NONE > > hw.acpi.standby_state: S1 > > hw.acpi.suspend_state: S3 > > hw.acpi.sleep_delay: 1 > > hw.acpi.s4bios: 0 > > hw.acpi.verbose: 1 > > hw.acpi.disable_on_reboot: 0 > > hw.acpi.handle_reboot: 0 > > hw.acpi.reset_video: 0 > > hw.acpi.cpu.cx_lowest: C1 > > > > .. but s4bios is 0 (no BIOS support for S4) and I wonder what's happened > > to your hw.acpi.thermal settings also, but .. just a long shot .. > > > > What happens if you set sysctl hw.acpi.power_button_state=S4 and then > > try halt -p ? .. probably better off using 'shutdown -p now' actually. > > > > cheers, Ian > > That does change things in that now if I hold down the power button > after halt -p it just goes off rather than booting straight back up > again. So that is an improvement. Thanks. > > Jerry As Windows, Linux and Solaris can power this machine off would it be reasonable to conclude that this is just a feature of FreeBSD and not a fault in my ACPI tables? looking at the source code for acpiconf leads me to conclude that FreeBSD just does not implement ACPI sleep state S5, acpiconf certainly does not. In the handbook 11.16 Using and Debugging FreeBSD ACPI says "This means that we can use acpiconf -s to test S3, S4OS, and S5." That is clearly wrong. I discovered that the motherboard is actually made by Foxconn a 945GZ7MC. Googling Foxconn lead me to all sorts of interesting rants about Linux ACPI. I also found some useful articles about how to go about debugging ACPI tables and wondered if I could contribute something that might be useful to others if I could get to the bottom of the problem. I guess I would probably just waste a lot of time going down that road. I have been using FreeBSD since 2.15 around 1996 so I will be very disappointed to have to confine it to VirtualBox until I replace this hardware. I also find it hard to believe that I am the only one with this problem should I just create a PR? Regards Jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1258714188.3487.38.camel>