[OpenSource] Fan Control Software for Windows XP and Vista

Did you already check out my aaocontrol command line tool (see http://arnowelzel.de/download/aaocontrol-0.1.zip? This makes it much easier to play around with the EC registers in Windows. I never had to read any register - just write the desired value to register 0x55 - and this will not cause any acpiec errors.

Well - of course after returning from standby or hibernation the fan starts again - but these events can be checked via WMI, so the fan status can be restored, when needed, without polling the EC registers all the time.

Not here - i have a A150L with BIOS v0.3304 and "slow mode" does nothing. The fan starts in the same speed as in "auto" and then stops. But another interesting value: 0xaf will stop the fan in all known BIOS versions.

Well - even with the fan stopped, my CPU stays at about 45-50°C core temperature in idle and even with full load (using cpuburn etc.) for 20 minutes, it just heats up to about 65-70°C core temperature (at 22°C room temperature). Of course you can feel that the device gets warm - but it is still far from "hot" and the Atom N270 is specified to run at 90°C maximum and it has only 2,5 W TDP, so i think most of the time, passive cooling is absolutely OK. The fan is just designed for safety in case, the machine is used in a hotter environment.

 

No slow mode..Bad news

Correction: 0x10 is working. Fan is runnig at slow speed
I use bios 3304.
Reading the temperature cause ACPIEC errors.

 

Many users reported slow mode working on theirs, I don't know what's wrong with yours :/

As for getting the CPU temp without polling the EC and knowing when the computer is back from sleep, I'm greatly intterested, getting rid of those ACPI errors would be nice.

 

The new version is online ;-)

viewtopic.php?f=44&t=3300&p=22065#p22065

Please let me know if it works ;-)

 

I just installed the DDK and was able to compile the PortTalk driver (which i use in my command line tool aaocontrol) - so building some additional kernel stuff to get the MSR read should not be too far away

 

With bios v0.3304 I have found "0xaf" to be the "fan off" setting.

I would appreciate if someone who knows about ms-dos/batch files could correct the following.

Code:

SET fanState=%aaocontrol read 0x55%
IF %fanState%==0xaf (
@aaocontrol write 0x55 0x00
) ELSE (
@aaocontrol write 0x55 0xaf
)

TIA

 

Can anyone explain slow mode to me? I don't understand how to enable it

 

Some persons say that the Aspire One permits you to program the fan in order to make in to go slow...
I think the Aspire One uses this mode automatically and this cannot be setup by the user.

Just uploaded the latest version that contains some fixes and some new enhancements.

Now it should work perfectly ;-)

 

Nice work Davide, thanks.

Could you let me know how you access/use the "Mini" version you speak of on your site?

 

looking forward to trying out the new version

 

its AspireOneTempMini.exe in the mini folder

 

Thanks, I'll give it a try.

 

I've tried the new version but i'm getting ACPIEC errors. is there anyway to fix that?

 

You will get these ACPIEC errors with every existing tool (AA1FanControl as well), since reading the EC to get the CPU temperatur or fan state will cause these errors. Only a kernel driver to read the CPU MSR instead of the EC (or a special driver to access the EC with locking instead of just poking around the I/O ports) would avoid this.

 

I'm using AA1FanControl and I never got that error.

 

Did you check in the event log in control panel/admistration tools ?

 

yes I did and the only error I see is coming from this software

 

ACPIEC error solved.

 

how ? ACPIEC patch ?

 

I just noticed recently that version .4 had been released, however, the binary download doesn't contain the required files. It only contains a subset and does not run at all. I get an error message, "application has failed to start because UNICOWS.DLL was not found." Hasn't anyone else run into this?