Hi,

I just got my new 1000H and installed Eeebuntu Base on it. I'm quite new to all this stuff and it's a bit confusing since there seems to be more than just one way to control a piece of hardware or to display some information on it, let alone the vast amount of packages that can be chosen from.

So I found the sensors-applet as a neat way to show CPU temperature and fan speed in the Gnome Panel. Normally it works well, but after some time -- say two hours -- the fan speed remains fixed at an arbitrary value no matter how the CPU temperature is. Rebooting the machine brings everything back to normal, but this certainly is not a good choice. What's wrong here?

Make sure that it's not just misreporting by watching /proc/eee/temperature and /proc/eee/fan_speed.

OK, I did this. fan_speed is at 30 for temperatures at about 55°C and at 50 for temperatures at about 65°C. It's interesting that there is much less variation in fan_speed than in the RPMs reported by sensors_applet.

Now, if the fan "freezes" again, fan_speed still reports the correct values, but the fan will no longer change its speed. I could easily confirm this by the noise from the fan; normally it's easy to distinguish between the two speeds. It seems as if sensors_applet is reporting its measurements correctly and the fan itself gets somehow stuck at one setting.

My 900ha is now doing this daily after the most recent eeepc-acpi update. It did do it occasionally before, causing the cpu temp one time to rise to over 170F with no change in the fan speed (it was stuck at a low rpm). Only way to stop it is to reboot the system. If I suspend and reawaken it, it will get stuck at a very low rpm causing a dangerous overheating issue.

This is something related in the asus-eee kernel module itself, I've been looking into it, but I haven't found a fix yet.

I have a 900 with the same problem...

I think this may be 2.6.29 related, I no longer have the issue on 2.6.30.