> > >> This morning, I rebooted my old Debian box to start using its new Kernel > > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything > > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am > > >> using a MSI K8N NEO4-F (MS-7125) motherboard. > > > [...] > > >> I looked at the FAQ and saw > > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 > > >> which look like my issue and matches dmesg: http://pastie.org/856424 ... > > >> > > >> I am scared to use the lax method since it is not recommended. Is there > > >> another way to show the datas safely? Or do I have to use this trick or > > >> live without them? > > > > > > Asus provides an ACPI interface for accessing the sensors in a safe > > > way; I don't know what it's used on MSI boards, but I can take a look: > > > please send me a dump of the DSDT table > > > > Nothing interesting in the DSDT; the hwmon chip is used only for > > reading a temperature (TZ). > > I think you can use "acpi_enforce_resources=lax", there not other ways > > to access the sensor data. > > If you do, please make sure to blacklist the ACPI "thermal" driver. Where do I set blacklist it? What is bad about "thermal" driver? Conflict? -- Quote of the Week: "This isn't a war. It never was a war, any more than there's war between man and ants." --artilleryman from H.G. Wells' The War of the Worlds /\___/\ / /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links: http://aqfl.net \ _ / E-mail: philpi@xxxxxxxxxxxxx or ant@xxxxxxxxxx ( ) _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
