[opensuse-kde] Sensors no longer display in ksysguard after update from SUSE 10.1 to 11.0
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? The following message suggests that a patch has been added to KDE 3.5.9 http://lists-archives.org/kde-devel/15569-ksysguard-to-support-lmsensor-3-x-... I'm currently using ksysguard 1.2.0 with KDE 3.5.10 and cannot see the sensors. Maybe the patch is broken? The problem apparently still occurs in Gentoo: http://bugs.gentoo.org/show_bug.cgi?id=211308 and Arch: http://bugs.archlinux.org/task/8776 This lm-sensors web page http://www.lm-sensors.org/wiki/Download has a pacth to ksysgiard 3.5.8. I don't know if it works or if it has been incorporated into KDE 3.5.10. I upgraded from 10.1 to 11.0 by using the update method rather than by installing openSUSE on a freash partition. Should this have made any difference? I don't want to reinstall just to check if this problem is fixed. Is there any way I can check ksysguard and sensors using a live-CD? Best, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Saturday 30 August 2008 08:48:52 am Paul C. Leopardi wrote:
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@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sun, 31 Aug 2008, Rajko M. wrote:
I've already run sensors-detect. The output of sensors looks like: k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +30.0°C it8712-isa-0290 Adapter: ISA adapter VCore 1: +1.30 V (min = +0.00 V, max = +4.08 V) VCore 2: +2.59 V (min = +0.00 V, max = +4.08 V) +3.3V: +3.33 V (min = +0.00 V, max = +4.08 V) +5V: +2.66 V (min = +0.00 V, max = +6.85 V) +12V: +12.10 V (min = +0.00 V, max = +16.32 V) -12V: -8.09 V (min = -27.36 V, max = +3.93 V) -5V: -5.46 V (min = -13.64 V, max = +4.03 V) Stdby: +4.38 V (min = +0.00 V, max = +6.85 V) VBat: +3.15 V fan1: 2057 RPM (min = 0 RPM, div = 8) fan2: 0 RPM (min = 0 RPM, div = 8) fan3: 0 RPM (min = 0 RPM, div = 8) M/B Temp: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor CPU Temp: +26.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor Temp3: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode cpu0_vid: +0.000 V
I've found the temperature and fan speed readings given by sensors to be very useful. I have a quiet fan and use fancontrol to control its speed, and use the System Guard widget on the panel to see the current Temp3 and Fan1 values. That is, I used to, up until the update from SUSE 10.1 to 11.0.
My motherboard is a Gigabyte K8NNXP nForce3 150 with an AMD Athlon 64 3200+ CPU. It uses a ITE IT8712F-A chip. See (eg.) http://tw.giga-byte.com/Products/Motherboard/Products_Spec.aspx?ProductID=16... http://www.digit-life.com/articles2/roundupmobo/gigabyte-k8nnxp-nforce3pro15... http://www.ocworkbench.com/2003/gigabyte/k8nnxp/k8nnxpgallery2.htm The web page you referred me to says this has been supported by the it87 driver since lm-sensors 2.6.0 and kernel 2.5.69. Best, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Saturday 30 August 2008, Paul C. Leopardi wrote:
The patch on the lm-sensors webpage is included in KDE 3.5.10, however we don't build against the new libsensors. could you please install the KDE from KDE:KDE3 and see if that makes a difference? zypper in kdebase3 with that repo being enabled should be enough. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 03 September 2008, Dirk Müller wrote:
could you please install the KDE from KDE:KDE3 and see if that makes a difference?
Ah, 11.0 uses the ksysguardd from KDE4, and that one wasn't built against sensors due to a packaging error. Fixed now. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, 3 Sep 2008, Dirk Müller wrote:
Hi Dirk, In which repository do I find the fix, or is it in updates? What is the package version? I've upgraded to KDE 4.1. Do I need to downgrade ksysguardd to KDE 4.0.4? # rpm -q -f `which ksysguardd` kdebase4-workspace-ksysguardd-4.0.4-24.6 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 03 September 2008, Paul C. Leopardi wrote:
I've only fixed it for 11.1, so you can find the fix in KDE:KDE4:Factory:Desktop. just installing kdebase4-workspace-ksysguardd from that place should be enough. Please let me know if it doesn't resolve the issue (It was a blind fix, I haven't tested it yet).
package version? I've upgraded to KDE 4.1. Do I need to downgrade ksysguardd to KDE 4.0.4?
No. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, 3 Sep 2008, Dirk Müller wrote:
I downloaded kdebase4-workspace-ksysguardd-4.1.1-56.1 from http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSU... It now works. Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Saturday 30 August 2008 08:48:52 am Paul C. Leopardi wrote:
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@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sun, 31 Aug 2008, Rajko M. wrote:
I've already run sensors-detect. The output of sensors looks like: k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +30.0°C it8712-isa-0290 Adapter: ISA adapter VCore 1: +1.30 V (min = +0.00 V, max = +4.08 V) VCore 2: +2.59 V (min = +0.00 V, max = +4.08 V) +3.3V: +3.33 V (min = +0.00 V, max = +4.08 V) +5V: +2.66 V (min = +0.00 V, max = +6.85 V) +12V: +12.10 V (min = +0.00 V, max = +16.32 V) -12V: -8.09 V (min = -27.36 V, max = +3.93 V) -5V: -5.46 V (min = -13.64 V, max = +4.03 V) Stdby: +4.38 V (min = +0.00 V, max = +6.85 V) VBat: +3.15 V fan1: 2057 RPM (min = 0 RPM, div = 8) fan2: 0 RPM (min = 0 RPM, div = 8) fan3: 0 RPM (min = 0 RPM, div = 8) M/B Temp: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor CPU Temp: +26.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor Temp3: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode cpu0_vid: +0.000 V
I've found the temperature and fan speed readings given by sensors to be very useful. I have a quiet fan and use fancontrol to control its speed, and use the System Guard widget on the panel to see the current Temp3 and Fan1 values. That is, I used to, up until the update from SUSE 10.1 to 11.0.
My motherboard is a Gigabyte K8NNXP nForce3 150 with an AMD Athlon 64 3200+ CPU. It uses a ITE IT8712F-A chip. See (eg.) http://tw.giga-byte.com/Products/Motherboard/Products_Spec.aspx?ProductID=16... http://www.digit-life.com/articles2/roundupmobo/gigabyte-k8nnxp-nforce3pro15... http://www.ocworkbench.com/2003/gigabyte/k8nnxp/k8nnxpgallery2.htm The web page you referred me to says this has been supported by the it87 driver since lm-sensors 2.6.0 and kernel 2.5.69. Best, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Saturday 30 August 2008, Paul C. Leopardi wrote:
The patch on the lm-sensors webpage is included in KDE 3.5.10, however we don't build against the new libsensors. could you please install the KDE from KDE:KDE3 and see if that makes a difference? zypper in kdebase3 with that repo being enabled should be enough. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 03 September 2008, Dirk Müller wrote:
could you please install the KDE from KDE:KDE3 and see if that makes a difference?
Ah, 11.0 uses the ksysguardd from KDE4, and that one wasn't built against sensors due to a packaging error. Fixed now. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, 3 Sep 2008, Dirk Müller wrote:
Hi Dirk, In which repository do I find the fix, or is it in updates? What is the package version? I've upgraded to KDE 4.1. Do I need to downgrade ksysguardd to KDE 4.0.4? # rpm -q -f `which ksysguardd` kdebase4-workspace-ksysguardd-4.0.4-24.6 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 03 September 2008, Paul C. Leopardi wrote:
I've only fixed it for 11.1, so you can find the fix in KDE:KDE4:Factory:Desktop. just installing kdebase4-workspace-ksysguardd from that place should be enough. Please let me know if it doesn't resolve the issue (It was a blind fix, I haven't tested it yet).
package version? I've upgraded to KDE 4.1. Do I need to downgrade ksysguardd to KDE 4.0.4?
No. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (3)
-
Dirk Müller -
Paul C. Leopardi -
Rajko M.