| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 4 Mar 2010 10:17:41 +0100 From: Andre Prendel <andre.prendel@....de> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Udo van den Heuvel <udovdh@...all.nl>, linux-kernel@...r.kernel.org, lm-sensors@...sensors.org Subject: Re: [lm-sensors] 2.6.33 on jetway nc81-lf board On Tue, Mar 02, 2010 at 09:37:09PM -0800, Andrew Morton wrote: > (cc lm-sensors) > > On Mon, 01 Mar 2010 19:21:12 +0100 Udo van den Heuvel <udovdh@...all.nl> wrote: > > > Hello, Hi, > > > > I just compiled 2.6.33 on a Jetway NC81-LF board with AMD 235E CPU. > > While trying to get lm_sensors to work I get in dmesg stuff like: > > > > f71882fg: Found f71862fg chip at 0x220, revision 18 > > ACPI: I/O resource f71882fg [0x220-0x227] conflicts with ACPI region > > IP__ [0x225-0x226] > > ACPI: If an ACPI driver is available for this device, you should use it > > instead of the native driver > > ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region > > SOR1 [0xb00-0xb0f] > > ACPI: If an ACPI driver is available for this device, you should use it > > instead of the native driver > > > > > > No other sensor-related modules are loaded. > > > > What could be wrong? See lm-sensors FAQ Chapter3 #39: http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 Regards, Andre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists