Jean Delvare wrote: > On Tue, 15 Sep 2009 15:11:39 +0200, Martin MOKREJŠ wrote: >> Jean Delvare wrote: >>> This is exactly the symptom described in the blog post I sent you to. >>> http://hansdegoede.livejournal.com/7932.html >>> Did you read it? >> I did and therefore it seemed to me the problem is with the driver. >> I haven't figured out I am using a wrong one. :( So I should probably >> go and read the FAQ again. ;-) >> >>>> $ dmesg >>>> [cut] >>>> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 >>>> [cut] >>>> >>>> $ sensors >>>> ds1621-i2c-4-4c >>>> Adapter: SMBus I801 adapter at e800 >>>> temp: +51.00°C (low = +51.0°C, high = +51.0°C) ALARM (LOW) >>> You don't really have a DS162x chip on your system, do you? The output >>> above is rather suspicious. Does the temperature value ever changes? >> At the moment I have under 2.6.30.6: >> >> # sensors >> ds1621-i2c-4-4c >> Adapter: SMBus I801 adapter at e800 >> temp: +64.00°C (low = +64.0°C, high = +64.0°C) ALARM (HIGH) > > Once again, input = low = high, this doesn't make any sense. This has > to be a misdetection. So I suggest that you stop loading the ds1621 > driver. > > As this was the only chip seen by sensors-detect on your system, this > simply means that lm-sensors' native drivers are of no use on your > system. The good news is that this means the ACPI conflicts policy > change in recent kernels doesn't affect you much. > >> (...) >> Once again, it is ASUS L3C/S laptop. > > On laptops, thermal management is almost always handled by ACPI. So > your best chances are the acpi "thermal" driver and its bridge driver > to lm-sensors (thermal_sys, CONFIG_THERMAL=m or y and > CONFIG_THERMAL_HWMON=y). > > And there are also a number of drivers dedicated to Asus systems, such > as asus_atk0110, asus-laptop and asus_acpi. You should try them if you > haven't already. $ gzip -dc /proc/config.gz | grep THERMAL CONFIG_ACPI_THERMAL=y CONFIG_THERMAL=y CONFIG_THERMAL_HWMON=y $ gzip -dc /proc/config.gz | grep ATK CONFIG_KEYBOARD_ATKBD=y CONFIG_SENSORS_ATK0110=y $ These I have already in the kernel, so I can drop the whole SMbus thing? Could sensors-detect give me an advice like this? Are these hidden in the dmesg output I have provided recently? I am sorry for the silly questions. M. _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
