On Mon, Dec 20, 2010 at 02:57:21PM +0100, Jean Delvare wrote: > On Mon, 20 Dec 2010 21:44:34 +0800, Mikael Ström wrote: > > Hi, > > > > I know nothing about the background to the mail below, but if it's of > > any help, macfanctld uses the following hardwired paths, > > > > reading: > > > > /sys/devices/platform/applesmc.768/temp<n>_input > > > > and writing: > > > > /sys/devices/platform/applesmc.768/fan1_min > > /sys/devices/platform/applesmc.768/fan2_min > > /sys/devices/platform/applesmc.768/fan1_manual > > /sys/devices/platform/applesmc.768/fan2_manual > > > > If any of those are to be broken, please advice in advance so i can > > update the source before you break it, avoiding that the users fry their > > MacBooks. > > I would expect the kernel driver to behave sanely in the absence of a > user-space application. Isn't it the case? If not, I consider it a > serious bug in the driver, which should be addressed ASAP. The macbook overheat problems goes way back. All models have automatic heat protection, but it kicks in at temperatures uncomfortable to most users. The severity also depends on when the model was made. The current solution is to use the macfanctld driver, which disables automatic fan control, replacing it with a control loop yielding more workable temperatures. A fan control solution in the kernel would certainly be well received. Henrik _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
