Re: ACPI Problem: "acpi_tz0:_TMP value is absurd"

2008-03-12 Thread B J
I located a file for upgrading the BIOS for my Compaq machine but it requires Windows to install it. I deleted the Windows that came with the machine several months ago, so, for now, that option is out. I created a file with the following commands: sysctl hw.acpi.thermal.user_override=1 sysctl h

ACPI Problem: "acpi_tz0:_TMP value is absurd"

2008-03-06 Thread B J
A few weeks ago, I upgraded my Compaq Presario desktop machine from FreeBSD 6.2 to 6.3. I soon noticed this message on the screen. Apparently, the system is measuring the temperature of absolute zero. At first, I thought it to be an installation error on my part, but reformatting the hard drive

"acpi_tz0: _TMP value is absurd" Message

2010-04-21 Thread B J
I have a Compaq Presario SR2180NX, which uses a P5LP-LE motherboard. When I bought the machine second hand three years ago, I originally installed and ran FreeBSD 5.5 without the error message. I recall that it began appearing after I installed and ran 6.3, though I don't think it did under 6.2

Re: "acpi_tz0: _TMP value is absurd" Message

2010-04-22 Thread B J
> > I've looked at some of the ACPI code file and didn't > notice anything obvious which might be responsible for the > error message. A quick solution I've used is running a > file with: > > > > hw.acpi.thermal.user_override: 0 -> 1 > > hw.acpi.thermal.polling_rate: 10 -> 1800 > > hw.acpi.ther

Re: "acpi_tz0: _TMP value is absurd" Message

2010-04-22 Thread B J
> I was able to set the temperature of > hw.acpi.thermal.tz0._CRT by > changing hex values in my ASL, but _CRT is hard coded > whereas _TMP is > set dynamically (in my ASL). There is also a problem that > the value of > _CRT is output by sysctl so I could watch the results of my > changes, wherea

Re: "acpi_tz0: _TMP value is absurd" Message

2010-04-22 Thread B J
> >>> One thing I did notice, however, is when I > compiled > >> that file and got > >>> two errors arising from: > >>> > >>> Store (Local0, Local0) > >>> > >>> where Local0 hadn't been defined in that part > of the > >> code. I have no > >>> idea how that came about, but it successfully > com