Hi Henri,

Le mercredi 2 C  20:48, Henri Kemppainen a C)crit :
>>> I just installed a snapshot (dated Oct 19) of -current on a new
>>> EeePC 1001PXD. The installation itself went fine. However, on the
>>> first boot, even before I can see the login prompt, acpitz decides
>>> to shutdown the machine:
>>> acpitz0: critical temperature exceeded 255C (5282K), shutting down
>
>> `dmesg' with this patch is at:
>> <http://tar-jx.bz/stuff/dmesg.lapin-5.0-nohaltoncrit>
>
> From your dmesg:
>> acpiec _REG failed, broken BIOS
>
> ASUS has a BIOS update (0702; 2011.04.13) with the this description:
>> Update EC firmware
>
> I'd try that.  Tell me if it fixes the problem.

Thanks for the suggestion. I updated the BIOS. The only relevant
difference I see in dmesg is the new version number of the BIOS; I still
have the message about a broken BIOS and acpitz finding the temperature
too high. For the record:

<http://tar-jx.bz/stuff/dmesg.lapin-5.0-nohaltoncrit-newbios>

I've been paying closer attention to the dmesg from Linux and FreeBSD,
and indeed, in both cases, I see messages about flaky things in the
BIOS. However, both Linux and FreeBSD are able to see the correct
temperature. For instanace, under FreeBSD:

# sysctl -a
...
hw.acpi.thermal.tz0.temperature: 57.0C

<http://tar-jx.bz/stuff/dmesg.lapin-freebsd9rc1>
<http://tar-jx.bz/stuff/sysctl-a.lapin-freebsd9rc1>

Linux: <http://tar-jx.bz/stuff/dmesg.lapin-linux>

[    0.168433] ACPI: EC: EC description table is found, configuring boot EC
(I don't know if the EC table was available before the BIOS update; all
I know is that Linux was able to get the correct temperature/)

[    0.249652] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
...
[    0.272921]  pci0000:00: Requesting ACPI _OSC control (0x1d)
[    0.272930]  pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned
control mask: 0x1d

Please do tell me if there is more relevant info I can provide. I am far
from an expert in ACPI; I have no idea what an EC table is, for
instance, and maybe I'm missing something obvious.

--
Fred

Reply via email to