lm_sensors version 2.10.1 is required to work properly with kernel 2.6.19.x, please mark stable Reproducible: Always
From www.lm-sensors.org December 5th, 2006: Note to k8temp users. The Linux 2.6.19 kernel features a new hardware monitoring driver, k8temp, which supports all recent AMD K8 CPUs. The driver will load automatically on supported systems. Due to technical specificities of this driver, *upgrade to lm_sensors 2.10.1 is mandatory*. Older versions of libsensors will fail with a "General parse error" message. If you can't upgrade lm_sensors for any reason, you'll have to blacklist the k8temp driver to prevent it from being loaded.
http://www.lm-sensors.org/wiki/Download lm_sensors v2.10.2 This is the latest release of the current project, for Linux 2.4.10+. This is a stable release with support for most devices. Userspace tools support 2.4 and 2.6 kernels. Device drivers are for Linux 2.4 only, for Linux 2.6 they are coming with the kernel itself.
Guess it's prime time for =sys-apps/lm_sensors-2.10.1 ... arches, please stable this version as soon as possible.
x86 done
@Heim, thanks for bringing it up to arches :)
This e-build doesn't build on kernel 2.4 machines as the ebuild requires "! has_version =sys-apps/lm_sensors-modules-${PV}" and the most recent version of lm_sensors-modules is currently 2.10.0. IMHO, adding ebuilds for sys-apps/lm_sensors-modules-2.10.1 and sys-apps/lm_sensors-modules-2.10.2 would be nice for 2.4 users. I will contribute ebuilds for these when I have tested them.
Marked ppc stable.
Created attachment 108382 [details] lm_sensors-modules overlay ebuilds for 2.10.1 and 2.10.2 This overlay will allow 2.4 machines to build lm_sensors for 2.10.1 It contains no changes to the ebuild and associated patches from 2.10.0 other than renaming to 2.10.1 and 2.10.2, marking the 2.10.2 ebuild with ~x86 and manifest and digest regeneration. I have tested this in overlay and it builds lm_sensors.
Version 2.10.2 works flawlessly with gentoo-sources 2.6.19-r2 on amd64.
*** Bug 159214 has been marked as a duplicate of this bug. ***
amd64 stable