Mailinglist Archive: opensuse-kde (86 mails)

< Previous Next >
Re: [opensuse-kde] Sensors no longer display in ksysguard after update from SUSE 10.1 to 11.0
  • From: "Rajko M." <rmatov101@xxxxxxxxxxx>
  • Date: Sat, 30 Aug 2008 11:14:24 -0500
  • Message-id: <200808301114.24441.rmatov101@xxxxxxxxxxx>
On Saturday 30 August 2008 08:48:52 am Paul C. Leopardi wrote:
Hi all,
I just upgraded from SUSE 10.1 to openSUSE 11.0. I've noticed that sensors
is now at version 3.0.2-4.1, using lm_sensors 3.0.2. How do I display
information from this new version of sensors, using ksysguard, or
otherwise?
...

On my computer it is still the /etc/sensors3.conf that is not good.
I can see values where min is larger than max value. You can see what sensors
reports with command:
sensors

If there is no output than you should run 'sensors-detect' that will install
kernel drivers, and then adjust whatever is the resulting /etc/sensors3.conf
to show reasonable values.

So far I know, sensors is not really supported by manufacturers of
motherboards. The problem is when sensor chip on the motherboard is connected
in a different way than reference design, given by chip vendor. That is the
reason I don't use them much, and if I do, than only for values that I can
check in BIOS health monitor (or similar named part of BIOS), and windows
utility that can be found on motherboard web site with BIOS updates.

See:
http://www.lm-sensors.org/wiki/Devices
for the list of supported hardware. Note that if it worked in 10.1, it doesn't
mean that it gave correct values for all parameters.

--
Regards, Rajko
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups
References