aptosid.com

Upgrade Warnings - [SOLVED] KDE SystemMonitor-Temperature not working after D-U

gangsta - 21.10.2010, 12:47
Post subject: [SOLVED] KDE SystemMonitor-Temperature not working after D-U
In the settings of this add-on does not have sensors.


Thanks for any helps.
hk - 22.10.2010, 01:11
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
Probably related: my cpu fan is at 100% all the time after upgrading to 2.6.36. Running kde.

---

I just noticed that acpi -t says 45 degrees and sensors gives 76 degrees.

=/
hopimet - 22.10.2010, 20:49
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
Same for me: the temperature monitor plasmoid doesn't work anymore with the new kernel.

acpi -t gives 55 and sensors reports 57.
piper - 24.10.2010, 19:37
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
Ok, been on holiday the past 2 weeks, then had internet problems (still do but good enough to surf and do a du now) I have a lot of catching up to do here.

I did du's on both my main (32bit) and 2nd primary (64bit) and KDE System Monitor - Temperature works fine on both, I use fahrenheit instead of celsius on both

here is a snapshot
hk - 25.10.2010, 00:12
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
it appears that /proc/acpi/thermal_zone is missing in 2.6.36 (along with many other things)

anyone want to confirm it?

---

d-u not responsible for the fan thing, apparently one of my media keys maxes the fan out. very very odd.
gerd - 25.10.2010, 06:54
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
Conky and xfce panel plugin for temp. have problems to get the temp. too
finotti - 25.10.2010, 12:58
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
I had this problem with the system monitor widget i KDE. Closing it and opening it again solved the problem. In fact, now it has more temperatures to show than before....
etorix - 25.10.2010, 14:42
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
my gkrellms just needed looking in the Configuration Menu

works fine on 2.6.36

it however appears maybe some sensor-chips have read problem
      Code:

apt-get install --reinstall lm-sensors 
sensors-detect


may help
gangsta - 25.10.2010, 15:25
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
I reinstalled lm-sensors and
      Code:
sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: ASUSTeK Computer Inc. K70IO (laptop)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel Atom thermal sensor...                                No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation nForce SMBus (MCP79)
Module i2c-dev loaded successfully.

Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter  (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: NVIDIA i2c adapter  (i2c-4)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter  (i2c-5)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter  (i2c-6)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 yNo

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK
and
      Code:
# /etc/init.d/module-init-tools start
Loading kernel modules...done.

In settings widget still no sensors.


------------
I did restart Aptosid and now it works:)

Thanks!
hopimet - 25.10.2010, 19:01
Post subject: RE: KDE System Monitor - Temperature not working after D-U.
It works again for me now.
Thx
ikeinthai - 27.10.2010, 09:51
Post subject: how hot is hit?
for me
      Code:
 
sensors-detect

as root, answer "y" to all questions, and reboot was enough.

one install i had to remove the widget from the kde panel and then put it back in.

thanks for the speedy help,

ike.
kb0hae - 27.10.2010, 14:37
Post subject: RE: how hot is hit?
After a d-u last evening on 3 laptops (an IBM T41, an IBM T42, and an HP Pavillion), on all three the temp monitor widget was not working. Removing an re-installing did the trick for all three. Very Happy
ikeinthai - 01.11.2010, 06:32
Post subject: spiffy new widget.
the new version running on my desktop gives a separate temp for my ati graphics card... YAY!

all the best, ike.
meier - 06.11.2010, 12:16
Post subject: RE: spiffy new widget.
Actually, to solve this problem I had to do the following, and I'd like to know if I'm just stating the obvious, or if I have even done something incredibly stupid by inserting stuff by hand and not relying on some better way to get my modules loaded:

(1) apt-get install lm-sensors (which wasn't on my system yet)
(2) run sensors-detect as root
(3) paste its output regarding coretemp into /etc/modules
(4) reboot

Then, and only then, did I regain a working SystemMonitor-Temperature.

Cheers!
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits