Hello SuSE people, Running 10.0 on AMD64. After installing the package, I ran sensors-detect in Konsole. Did all of the probing, testing, etc. Then it suggested additions to two config files before it finished. The following is a paste from the Konsole. To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here---- Question is What file does that get added to. I have only an rc.status file and a rc.splash. Doesn't look like that statement should go into either of them. Once that is done and the program is configured how is the program called? Just type "sensors" in the Konsole? Bob S. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Bob S wrote:
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
Question is What file does that get added to.
Maybe /etc/init.d/boot.local ?
Once that is done and the program is configured how is the program called? Just type "sensors" in the Konsole?
For instance. But also check "man sensors". /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
Question is What file does that get added to.
I've been pondering this for a while this morning (don't have access to my Linux computer today so i can't actually check it out). I used to have to manually add it to /etc/inet.d/boot.local 9as suggested by Per, but... since 10.0 I haven't had to do anything at all except run sensors-detect (as root). I'm assumign that something in the detect script adds the info where needed... never bothered to look into it since it "just worked". It's possible you'll find it works with no more intervention from you too :-)
Once that is done and the program is configured how is the program called? Just type "sensors" in the Konsole?
That's one way. You can also use loads of other GUI based apps to call up and present the info. gkrellm is included on the SUSE disks... that works... SuperKaramba also has LOADS of desktop widgets that poll and display sensors info (I use the Cynapses plugin for SuperKaramba on all my Linux desktops). C. . -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 31 July 2006 04:17, Per Jessen wrote:
Bob S wrote:
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
Question is What file does that get added to.
Maybe /etc/init.d/boot.local ?
Once that is done and the program is configured how is the program called? Just type "sensors" in the Konsole?
For instance. But also check "man sensors".
/Per Jessen, Zürich
I made up an /etc/init.d/rc.sensors file and execute it from boot.local. < in the /etc/init.d/boot.local file> # Sensors /etc/init.d/rc.sensors -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
* Bruce Marshall <bmarsh@bmarsh.com> [07-31-06 08:58]:
I made up an /etc/init.d/rc.sensors file and execute it from boot.local.
< in the /etc/init.d/boot.local file> # Sensors /etc/init.d/rc.sensors
the package sensors-2.10.0-11.1 provides /etc/init.d/lm_sensors. All that is necessary to have the 'rclm_sensors start...' to work is a sym-link, "ln -s /etc/init.d/lm_sensors /sbin/rclm_sensors" of course, after running sensors-detect and allowing it to write the configuration. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Bob S wrote:
Running 10.0 on AMD64.
After installing the package, I ran sensors-detect in Konsole. Did all of the probing, testing, etc. Then it suggested additions to two config files before it finished. The following is a paste from the Konsole.
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
For suse, that should be auto created in /etc/sysconfig/lm_sensors
Question is What file does that get added to. I have only an rc.status file and a rc.splash. Doesn't look like that statement should go into either of them.
It also makes a file in /usr/share/doc/packages/sensors/prog/init called lm_sensors.init.suse, which you should manually copy to /etc/init.d. Rename it to lm_sensors (personal preference), and make sure it is executable. For niceness, create a symlink in /usr/sbin called rcsensors, i.e. cd /usr/sbin, ln -s /etc/init.d/lm_sensors rcsensors. Then you can start and stop it like many other services, i.e.rcsensors start, etc. You may want to check /etc/init.d/lm_sensors to make sure it looks ok for you as far as starting dependencies, then either use Yast, System, Runlevel Editor to start it on boot, or insserv /etc/init.d/lmsensors, or chkconfig --add lm_sensors. HTH -- Joe Morris Registered Linux user 231871 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Bob S wrote:
Hello SuSE people,
Running 10.0 on AMD64.
After installing the package, I ran sensors-detect in Konsole. Did all of the probing, testing, etc. Then it suggested additions to two config files before it finished. The following is a paste from the Konsole.
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
Question is What file does that get added to. I have only an rc.status file and a rc.splash.
You don't need to; it's delivered as part of 10.0. Don't mess around with your system and introduce local patches, just use the SUSE-supplied framework. Check that you have /etc/init.d/lm_sensors, that's the file you're looking for. It's in the package sensors-2.9.1-4, on my 10.0 system. Check /etc/sysconfig/lm_sensors and add these modules to the configuration if they're not already there. In your case, this configuration file should finish with MODULE_0=i2c-viapro MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=w83627hf (I don't remember any more if I put the modules list there myself or if sensors-detect did that already.) Call "/etc/init.d/lm_sensors start" to start the whole thing. Call "sensors" to check if it works. Call "chkconfig -a lm_sensors" to initialize the system at boot time. For the last straw, update /etc/sensors.conf with temperature and fan thresholds to get proper warnings. (You must call "sensors -s" again to activate your changes.) Add a sensors service check to your Nagios installation, to get automatically informed when your CPU gets too hot or your fans die. The hardest part of that is to get the information about good thresholds. ;-) Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 31 July 2006 09:27, Joachim Schrod wrote:
Bob S wrote:
Hello SuSE people,
Running 10.0 on AMD64.
After installing the package, I ran sensors-detect in Konsole. Did all of the probing, testing, etc. Then it suggested additions to two config files before it finished. The following is a paste from the Konsole.
To load everything that is needed, add this to some /etc/rc* file:
#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----
Question is What file does that get added to. I have only an rc.status file and a rc.splash.
You don't need to; it's delivered as part of 10.0. Don't mess around with your system and introduce local patches, just use the SUSE-supplied framework.
Check that you have /etc/init.d/lm_sensors, that's the file you're looking for. It's in the package sensors-2.9.1-4, on my 10.0 system.
Check /etc/sysconfig/lm_sensors and add these modules to the configuration if they're not already there. In your case, this configuration file should finish with
MODULE_0=i2c-viapro MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=w83627hf
(I don't remember any more if I put the modules list there myself or if sensors-detect did that already.)
Call "/etc/init.d/lm_sensors start" to start the whole thing.
Call "sensors" to check if it works.
Call "chkconfig -a lm_sensors" to initialize the system at boot time.
For the last straw, update /etc/sensors.conf with temperature and fan thresholds to get proper warnings. (You must call "sensors -s" again to activate your changes.) Add a sensors service check to your Nagios installation, to get automatically informed when your CPU gets too hot or your fans die. The hardest part of that is to get the information about good thresholds. ;-)
Thanks to all who answered. Gave me a handle on what needed to be done. I un-edited what I had done yesterday, started lm_sensors, ran sensors, and got my readouts. I then made a printout of the results and rebooted to check how close the info in the bios was reporting. It was all pretty close. I then rebooted into SuSE 10.0 AMD64 and ran sensors again. Have a few questions as a result of that. Here is the text of the printout and my comment for each line: bob@private:~> sensors w83627thf-isa-0290 Adapter: ISA adapter VCore: +1.53 V (min = +0.94 V, max = +0.96 V) ALARM (Bios reports 1.54v - This the one that worries me) +12V: +12.34 V (min = +10.82 V, max = +13.19 V) ALARM (Bios reports 11.87v - False alarm?) +3.3V: +0.45 V (min = +3.14 V, max = +3.47 V) (Bios reports 3.40v - another false alarm?) +5V: +5.09 V (min = +4.75 V, max = +5.25 V) ALARM (Bios reports 5.25v - another false alarm?) -12V: -14.91 V (min = -10.80 V, max = -13.18 V) (Not reported in bios - Get rid of this?) V5SB: +5.16 V (min = +4.76 V, max = +5.24 V) ALARM (Not reported in bios -don't know what this is - get rid of it?) VBat: +3.62 V (min = +2.40 V, max = +3.60 V) ALARM (Not reported in bios - laptop battery?) fan1: 3245 RPM (min = 25000 RPM, div = 2) (Bios reports as a system fan? at 3245 rpm) CPU Fan: 5818 RPM (min = 675000 RPM, div = 2) (Bios reports at 6026 rpm) fan3: 0 RPM (min = 8035 RPM, div = 2) (Not reported in bios - do have other fans though)) M/B Temp: +49°C (high = +86°C, hyst = +2°C) sensor = thermistor (Bios reports System Temperature 49 to 120 degrees F) CPU Temp: +34.5°C (high = +80°C, hyst = +75°C) sensor = diode (Bios reports 46 to 114 degrees F) temp3: -48.0°C (high = +80°C, hyst = +75°C) sensor = thermistor (Not reported in bios - No idea what it could be - get rid of it?) vid: +0.275 V (VRM Version 9.0) ` (Not reported in bios - get rid of it? - don't know what it means) alarms: beep_enable: Sound alarm disabled (Would be nice to have a warning to check if there is a problem) Sooo... according to Joachim (thank you) I can make edits in /etc/sensors.config to display what is needed. The only thing that worries me is Vcore which seems to be way out of bounds from what lm_sensors is presenting. All ideas and comment are welcomed from the great knowledgeable people on this list. Bob S.
participants (7)
-
Bob S -
Bruce Marshall -
Clayton -
Joachim Schrod -
Joe Morris (NTM) -
Patrick Shanahan -
Per Jessen