hi, sysctl shows __always__ 40?: $ sysctl hw.acpi.thermal.tz0.temperature hw.acpi.thermal.tz0.temperature: 40,0C motherboard is a Asus M2A-VM, version is FreeBSD 7.0-BETA4 amd64 is this a motherboard issue, or a known issue, or a bug, can anybody confirm this behaviour, should i send_pr ? best regards, reinhard -- All I ask of life is a constant and exaggerated sense of my own importance.
On Fri, Dec 14, 2007 at 10:53:20AM +0100 I heard the voice of tequnix@frogmi.net, and lo! it spake thus:> > $ sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 40,0C > > motherboard is a Asus M2A-VM, version is FreeBSD 7.0-BETA4 amd64I have the same board running on i386, and mine always shows 40 too. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
On Fri, Dec 14, 2007 at 10:53:20AM +0100, tequnix@frogmi.net wrote:> sysctl shows __always__ 40?: > > $ sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 40,0C > > motherboard is a Asus M2A-VM, version is FreeBSD 7.0-BETA4 amd64 > > is this a motherboard issue, or a known issue, or a bug, can anybody > confirm this behaviour, should i send_pr ?It's very likely an ACPI configuration problem (with the motherboard/ motherboard BIOS). I have some Asus boards which claim to support the ACPI thermal zone stuff, but an ACPI configuration dump shows the value being returned as a static 40C (e.g. the value is hard-coded and isn't tied to any hardware). You could use acpidump -d to confirm this. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
tequnix@frogmi.net writes:> sysctl shows __always__ 40?: > > $ sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 40,0C > > motherboard is a Asus M2A-VM, version is FreeBSD 7.0-BETA4 amd64 > > is this a motherboard issue, or a known issue, or a bug, can anybody > confirm this behaviour, should i send_pr ?I had the same problem with another Asus board. It was an easy ASL hack to fix. See this thread: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=412963+0+archive/2006/freebsd-acpi/20061029.freebsd-acpi Regards, Bengt