LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Password
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.

Notices


Reply
  Search this Thread
Old 11-12-2004, 06:20 PM   #46
jonr
Senior Member
 
Registered: Jan 2003
Location: Kansas City, Missouri, USA
Distribution: Ubuntu
Posts: 1,040

Rep: Reputation: 47
Eureka! (At least momentarily)


I got my sensors to work and display on gkrellm as before when I was using Mdk 9.2.

Unfortunately, I'm not sure how I achieved this. I do know I took the information OUT of the files that sensors-detect suggested I put in there. I ran sensors-detect numerous times answering "yes" or "no" various ways to the different proposals. The last time was the charm.

Now if I can just refrain from running sensors-detect again, I ought to be OK.
 
Old 11-12-2004, 07:10 PM   #47
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
You first need to make sure that the sensors daemon is started at boot.

The lm_sensors package installs the daemon, but make sure it's enabled to start as root. Check the startup service via the MCC.

If it's enabled typing "sensors" at a prompt should dump the information read back from the sensors.

If "sensors" cannot see this, neither can gkrellm.

The next minor issue is that there is not always a one to one correspondence to what gkrellm assigns and what the sensors actually are.

Again sensors comes in handy so you can set up the sensors plugin in gkrellm.

Often you also have to not only assign the correct sensors to the plugin, but also set values to adjust the displayed output to be within the correct range.
 
Old 11-12-2004, 07:16 PM   #48
xavierh
Member
 
Registered: Feb 2004
Location: Denton, TX
Distribution: Mandriva 2005 LE
Posts: 221

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by opjose
You first need to make sure that the sensors daemon is started at boot.

The lm_sensors package installs the daemon, but make sure it's enabled to start as root. Check the startup service via the MCC.

If it's enabled typing "sensors" at a prompt should dump the information read back from the sensors.

If "sensors" cannot see this, neither can gkrellm.

The next minor issue is that there is not always a one to one correspondence to what gkrellm assigns and what the sensors actually are.

Again sensors comes in handy so you can set up the sensors plugin in gkrellm.

Often you also have to not only assign the correct sensors to the plugin, but also set values to adjust the displayed output to be within the correct range.
hey opjose, I found how to disable that image....it is the kde menu side image...so that I can at least disable it in the kde control center...now If I could change the actual image...
 
Old 11-12-2004, 07:18 PM   #49
xavierh
Member
 
Registered: Feb 2004
Location: Denton, TX
Distribution: Mandriva 2005 LE
Posts: 221

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by jonr
Still no sensors found last time I rebooted after removing those modules. However, I
didn't take those lines out of sysinit.rc first. I've now removed them and next time I
boot I'll see what happens. (I also removed the modules with modprobe -r again.
By the way, though sensors-detect finds MAX6650 with a "confidence 4" for max6650
module, modprobe doesn't like either spelling, or other variants I tried, and keeps
saying "FATAL" not found. Oh, well.

You spent a lot of time trying to help me. Thanks! I've got a few other things to do,
believe it or not, but I'll keep experimenting and see if I can get the sensors to work
eventually. If not, it's not too important; I just like to keep an eye on the temperature
of the CPU, mainly.
no problem dude.....glad to do it.....
again pcheck the website that I gabve you and post your questions there....chances are they would know what to do amigo.....
 
Old 11-12-2004, 07:22 PM   #50
jonr
Senior Member
 
Registered: Jan 2003
Location: Kansas City, Missouri, USA
Distribution: Ubuntu
Posts: 1,040

Rep: Reputation: 47
The daemon was starting up OK most of the time when the sensors weren't able to display their data. I could also stop and restart it from a terminal but it didn't do any good. Now everything's working OK, though, so if I just don't break it it will be OK.

I've never been really sure which sensor is measuring what: output of "sensors" command is now:
Code:
via686a-isa-6000
Adapter: ISA adapter
CPU core:  +1.68 V  (min =  +2.00 V, max =  +2.50 V)   ALARM
+2.5V:     +2.51 V  (min =  +2.33 V, max =  +3.00 V)   
I/O:       +3.31 V  (min =  +4.10 V, max =  +2.56 V)   ALARM
+5V:       +5.13 V  (min =  +1.27 V, max =  +1.76 V)   ALARM
+12V:     +12.06 V  (min = +15.36 V, max = +11.59 V)   ALARM
CPU Fan:  2986 RPM  (min = 2667 RPM, div = 2)          
P/S Fan:     0 RPM  (min = 8544 RPM, div = 2)          
SYS Temp:  +29.4C  (high =   +45C, hyst =   +40C)   
CPU Temp:  +27.6C  (high =   +60C, hyst =   +55C)   
SBr Temp:  +22.4C  (high =   +65C, hyst =   +60C)
...and it seems strange that the CPU temperature would be lower than the "SYS" temperature. I take CPU to mean the Pentium chip itself, which should normally be by far the hottest spot in the computer.

But my gkrellm values are close enough for assurance that a safe temperature is being maintained.
 
Old 11-12-2004, 11:45 PM   #51
xavierh
Member
 
Registered: Feb 2004
Location: Denton, TX
Distribution: Mandriva 2005 LE
Posts: 221

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by jonr
The daemon was starting up OK most of the time when the sensors weren't able to display their data. I could also stop and restart it from a terminal but it didn't do any good. Now everything's working OK, though, so if I just don't break it it will be OK.

I've never been really sure which sensor is measuring what: output of "sensors" command is now:
Code:
via686a-isa-6000
Adapter: ISA adapter
CPU core:  +1.68 V  (min =  +2.00 V, max =  +2.50 V)   ALARM
+2.5V:     +2.51 V  (min =  +2.33 V, max =  +3.00 V)   
I/O:       +3.31 V  (min =  +4.10 V, max =  +2.56 V)   ALARM
+5V:       +5.13 V  (min =  +1.27 V, max =  +1.76 V)   ALARM
+12V:     +12.06 V  (min = +15.36 V, max = +11.59 V)   ALARM
CPU Fan:  2986 RPM  (min = 2667 RPM, div = 2)          
P/S Fan:     0 RPM  (min = 8544 RPM, div = 2)          
SYS Temp:  +29.4C  (high =   +45C, hyst =   +40C)   
CPU Temp:  +27.6C  (high =   +60C, hyst =   +55C)   
SBr Temp:  +22.4C  (high =   +65C, hyst =   +60C)
...and it seems strange that the CPU temperature would be lower than the "SYS" temperature. I take CPU to mean the Pentium chip itself, which should normally be by far the hottest spot in the computer.

But my gkrellm values are close enough for assurance that a safe temperature is being maintained.

you may have to do some fine tuningwith the factors in gkrellm but is sensors are working you should be ok...
 
Old 11-13-2004, 12:12 AM   #52
jonr
Senior Member
 
Registered: Jan 2003
Location: Kansas City, Missouri, USA
Distribution: Ubuntu
Posts: 1,040

Rep: Reputation: 47
Quote:
Originally posted by xavierh
you may have to do some fine tuningwith the factors in gkrellm but is sensors are working you should be ok...
Yeah, some day I might plug in values to the formulas gkrellm developers provide for figuring the skew values, but since the readings displayed seem to be within 4 or 5 degrees F. of the values seen in the BIOS, that's close enough for government work, as we used to say when I worked for the government.

Thanks again for all the help! Even when suggestions don't work, at least they keep me plodding away towards a solution, and usually I find something that works.
 
Old 11-13-2004, 12:22 AM   #53
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
Quote:
Originally posted by xavierh
hey opjose, I found how to disable that image....it is the kde menu side image...so that I can at least disable it in the kde control center...now If I could change the actual image...
Ok, here you go...

Instead of typing out instructions, here are some replacement side images...

http://www.kde-look.org/content/show.php?content=5368

http://www.kde-look.org/content/show.php?content=9505

Note: if you put it into /usr/share/apps/kicker instead it works for all users.
 
Old 11-13-2004, 12:25 AM   #54
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
Quote:
Originally posted by jonr
The daemon was starting up OK most of the time when the sensors weren't able to display their data. I could also stop and restart it from a terminal but it didn't do any good. Now everything's working OK, though, so if I just don't break it it will be OK.

I've never been really sure which sensor is measuring what: output of "sensors" command is now:
Code:
via686a-isa-6000
Adapter: ISA adapter
CPU core:  +1.68 V  (min =  +2.00 V, max =  +2.50 V)   ALARM
+2.5V:     +2.51 V  (min =  +2.33 V, max =  +3.00 V)   
I/O:       +3.31 V  (min =  +4.10 V, max =  +2.56 V)   ALARM
+5V:       +5.13 V  (min =  +1.27 V, max =  +1.76 V)   ALARM
+12V:     +12.06 V  (min = +15.36 V, max = +11.59 V)   ALARM
CPU Fan:  2986 RPM  (min = 2667 RPM, div = 2)          
P/S Fan:     0 RPM  (min = 8544 RPM, div = 2)          
SYS Temp:  +29.4C  (high =   +45C, hyst =   +40C)   
CPU Temp:  +27.6C  (high =   +60C, hyst =   +55C)   
SBr Temp:  +22.4C  (high =   +65C, hyst =   +60C)
...and it seems strange that the CPU temperature would be lower than the "SYS" temperature. I take CPU to mean the Pentium chip itself, which should normally be by far the hottest spot in the computer.

But my gkrellm values are close enough for assurance that a safe temperature is being maintained.
That's the problem.

lm-sensors doesn't actually know what returned value belongs to what device.

It pays to find out.

I ran my CPU at high utilization, then quickly rebooted and dropped into the bios to record the max temps reported by the bios (which tend to be correctly assigned).

I then brought up Linux again and went back to a high utilization program and ran sensors to establish which sensor was reporting what.

Then I adjusted the labels and sensors in gkrellm (plus offsets) so everything displayed correctly.

It's a bit of a hassle because neither lm_sensors nor gkrellm maintain a motherboard database like other programs do, to help determine what each returned value corresponds to.
 
Old 11-13-2004, 01:19 AM   #55
xavierh
Member
 
Registered: Feb 2004
Location: Denton, TX
Distribution: Mandriva 2005 LE
Posts: 221

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by opjose
Ok, here you go...

Instead of typing out instructions, here are some replacement side images...

http://www.kde-look.org/content/show.php?content=5368

http://www.kde-look.org/content/show.php?content=9505

Note: if you put it into /usr/share/apps/kicker instead it works for all users.

you the man!!!!

Imanaged to rename the picture.....questions, how does kde know which picture to display?
 
Old 11-13-2004, 05:55 PM   #56
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
KDE uses the kside image from the kicker folder.

For other icons, it will select an icon of the same name from the currently selected theme giving precedence to themes in ~/.kde

So most themes have a kmenu.png icon for the star on the kicker menu, etc.
 
Old 11-14-2004, 09:48 PM   #57
xavierh
Member
 
Registered: Feb 2004
Location: Denton, TX
Distribution: Mandriva 2005 LE
Posts: 221

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by opjose
KDE uses the kside image from the kicker folder.

For other icons, it will select an icon of the same name from the currently selected theme giving precedence to themes in ~/.kde

So most themes have a kmenu.png icon for the star on the kicker menu, etc.
ok but how does kde know which banner to select : I have in that kicker folder banners for powerpack and other verions of mandrake besides the download. how does it know which one to choose?
 
Old 11-14-2004, 09:57 PM   #58
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
It selects the one found in the kicker folder originally.

In other words if you replace that file with one of the same name, then it becomes the kside image.
 
Old 11-25-2004, 04:38 PM   #59
S.Fart
LQ Newbie
 
Registered: Nov 2004
Distribution: mandrake 10.1
Posts: 5

Rep: Reputation: 0
posted in error

Last edited by S.Fart; 11-25-2004 at 04:41 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
mandrake 10.1 official jag2000 Mandriva 2 11-18-2004 10:09 PM
Mandrake 10.1 Official xavierh Mandriva 5 11-08-2004 03:58 PM
mandrake 10.0 official vs. mandrake 9.0 is it worth the upgrade? Perquisitor Mandriva 7 07-14-2004 01:28 PM
Should i upgrade from mandrake 10 community to mandrake 10 official? Braveheart1980 Mandriva 7 06-21-2004 02:49 PM
Mandrake 8.0 vs. official 2.4.3 anajmi Linux - Distributions 1 04-03-2002 03:31 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva

All times are GMT -5. The time now is 06:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration