I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc. What is the processes for setting this up? Thanks... -- Marc Christensen
On Friday 19 November 2004 22:25, Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
Run, as root, sensors-detect in a konsole window and follow the instructions it gives you
Anders Johansson wrote:
On Friday 19 November 2004 22:25, Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
Run, as root, sensors-detect in a konsole window and follow the instructions it gives you
Well as normal "sensors-detect" in SuSE 9.2 fails. As root it shows the following error. "No i2c device files found. Use prog/mkdev/mkdev.sh to create them." I was a septic. Fine -> "locate mkdev.sh" Which returns a 0 so not found. -- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316
On Sunday 21 November 2004 16:45, Donn Washburn wrote:
Anders Johansson wrote:
On Friday 19 November 2004 22:25, Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
Run, as root, sensors-detect in a konsole window and follow the instructions it gives you
Well as normal "sensors-detect" in SuSE 9.2 fails. As root it shows the following error. "No i2c device files found. Use prog/mkdev/mkdev.sh to create them." I was a septic. Fine -> "locate mkdev.sh" Which returns a 0 so not found.
I thought you told me off-list that the sensors-detect script worked?! Anyways, if the /dev/i2c-* device nodes are missing, try reinstalling the package devs.rpm from the CD or DVD
Donn Washburn wrote:
Anders Johansson wrote:
On Friday 19 November 2004 22:25, Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
Run, as root, sensors-detect in a konsole window and follow the instructions it gives you
Well as normal "sensors-detect" in SuSE 9.2 fails. As root it shows the following error. "No i2c device files found. Use prog/mkdev/mkdev.sh to create them." I was a septic. Fine -> "locate mkdev.sh" Which returns a 0 so not found.
lm_sensors-2.8.8/prog/mkdev/mkdev.sh, downloaded the package from sourceforge.net and did "make user && make user_install". I think the 2.8.7 that was there was from 9.1 as rpm -qf /usr/bin/sensors said it wasn't owned by any package. I also changed the Makefile to point to /usr instead of /usr/local and ($PREFIX)/share/man for the man page path. Also built ksensors from sources as it wasn't installed, runs OK. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
Well folks I found the problem. Something removed /dev/i2c-[1-3] but left the rest 4-31. Running from the source "./prog/mkdev/mkdev.sh showed the error. It created the three missing i2c devices and then "sensors-detect" worked. Question I have is what removed the /dev/i2c- devices.0
Well as normal "sensors-detect" in SuSE 9.2 fails. As root it shows the following error. "No i2c device files found. Use prog/mkdev/mkdev.sh to create them." I was a septic. Fine -> "locate mkdev.sh" Which returns a 0 so not found.
lm_sensors-2.8.8/prog/mkdev/mkdev.sh, downloaded the package from sourceforge.net and did "make user && make user_install". I think the 2.8.7 that was there was from 9.1 as rpm -qf /usr/bin/sensors said it wasn't owned by any package. I also changed the Makefile to point to /usr instead of /usr/local and ($PREFIX)/share/man for the man page path. Also built ksensors from sources as it wasn't installed, runs OK. Regards Sid.
-- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316
Donn Washburn wrote:
Well folks I found the problem. Something removed /dev/i2c-[1-3] but left the rest 4-31. Running from the source "./prog/mkdev/mkdev.sh showed the error. It created the three missing i2c devices and then "sensors-detect" worked. Question I have is what removed the /dev/i2c- devices.0
I had the same error. I don't know why. I did an rpm -V devs and found quite a number of devs missing, so I reinstalled it (i.e. chose upgrade in Yast) and that fixed it. I have no idea why the problem, might have been because I did an upgrade, but it doesn't warrant any more time as it was easily fixed. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Donn Washburn wrote:
Well folks I found the problem. Something removed /dev/i2c-[1-3] but left the rest 4-31. Running from the source "./prog/mkdev/mkdev.sh showed the error. It created the three missing i2c devices and then "sensors-detect" worked. Question I have is what removed the /dev/i2c- devices.0
Begs the question, I have 0-31 here dated 2004-10-02, seems they were generated by 9.2 as both the upgrade boxes and the new install on the P-II/333 laptop have the same dates. Regards Sid.
Well as normal "sensors-detect" in SuSE 9.2 fails. As root it shows the following error. "No i2c device files found. Use prog/mkdev/mkdev.sh to create them." I was a septic. Fine -> "locate mkdev.sh" Which returns a 0 so not found.
lm_sensors-2.8.8/prog/mkdev/mkdev.sh, downloaded the package from sourceforge.net and did "make user && make user_install". I think the 2.8.7 that was there was from 9.1 as rpm -qf /usr/bin/sensors said it wasn't owned by any package. I also changed the Makefile to point to /usr instead of /usr/local and ($PREFIX)/share/man for the man page path. Also built ksensors from sources as it wasn't installed, runs OK. Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH.
Strange there isnt a Yast module for lm_sensors... Hm. -- Marc C.
Marc Christensen wrote:
Joe Morris (NTM) wrote:
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH.
Strange there isnt a Yast module for lm_sensors...
There will be after the sensors-detect tells you to copy and rename the startup script to /etc/init.d. You will see it in the Run Level Editor AFTER you follow the sensors-detect script. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
Marc Christensen wrote:
Joe Morris (NTM) wrote:
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH.
Strange there isnt a Yast module for lm_sensors...
There will be after the sensors-detect tells you to copy and rename the startup script to /etc/init.d. You will see it in the Run Level Editor AFTER you follow the sensors-detect script.
funny thing here is that after running the sensors-detect script I checked /etc/init.d (or linked /etc/rc.d) and found no lm-sensors script. So where is the start at boot script. I did add all of the modules after testing to see if they worked. Next question is what program frontend/GUI is used to watch it? -- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316
On Saturday 20 November 2004 02:39, Donn Washburn wrote:
Joe Morris (NTM) wrote:
Marc Christensen wrote:
Joe Morris (NTM) wrote:
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH.
Strange there isnt a Yast module for lm_sensors...
There will be after the sensors-detect tells you to copy and rename the startup script to /etc/init.d. You will see it in the Run Level Editor AFTER you follow the sensors-detect script.
funny thing here is that after running the sensors-detect script I checked /etc/init.d (or linked /etc/rc.d) and found no lm-sensors script.
The final step in the instructions shown when you ran sensors-detect is to copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse to /etc/init.d/lm_sensors
So where is the start at boot script. I did add all of the modules after testing to see if they worked.
Next question is what program frontend/GUI is used to watch it?
I like to use gkrellm. The KDE native program is KDE system guard, which can be very useful if you want to monitor several computers in a single screen, and there are a few kicker applets that display the values too. Do a search on freshmeat.net or kde-apps.org for sensors, there's a multitude to choose from
Donn Washburn wrote:
funny thing here is that after running the sensors-detect script I checked /etc/init.d (or linked /etc/rc.d) and found no lm-sensors script.
You would have to copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse to /etc/init, renamed to just lm_sensors.
So where is the start at boot script. I did add all of the modules after testing to see if they worked.
Next question is what program frontend/GUI is used to watch it?
You can use sensors in a console, or gkrellm for a gui. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Saturday 20 Nov 2004 02:02, Joe Morris (NTM) wrote:
Donn Washburn wrote:
funny thing here is that after running the sensors-detect script I checked /etc/init.d (or linked /etc/rc.d) and found no lm-sensors script.
You would have to copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse to /etc/init, renamed to just lm_sensors.
So where is the start at boot script. I did add all of the modules after testing to see if they worked.
Next question is what program frontend/GUI is used to watch it?
You can use sensors in a console, or gkrellm for a gui.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
I am using Ksysguard it seems to be ok . YMMV Pete -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..
Joe Morris (NTM) wrote:
Marc Christensen wrote:
Joe Morris (NTM) wrote:
As root, run sensors-detect and follow all the instructions. After you are done, start/enable in Yast>System>Run Level Editor. HTH.
Strange there isnt a Yast module for lm_sensors...
There will be after the sensors-detect tells you to copy and rename the startup script to /etc/init.d. You will see it in the Run Level Editor AFTER you follow the sensors-detect script.
Right, Yast automaticaly allows you to configure runlevel settings for any init script that exists in the init directory. That's not the same as a Yast configuration module for the server (ala MTA, ntp client, samba, etc modules). A Yast config module would provide a Yast front end for configuring sensors, instead of having to drop to a prompt and running the script. I certainly don't mind running the script. It's just not a "unified" admin experience. I understand that not all services have yast modules yet - hopefully the will be sometime... -- Marc Christensen
On Saturday 20 November 2004 7:53 pm, Marc Christensen wrote:
Strange there isnt a Yast module for lm_sensors...
I'll confirm that for 9.2, I did run the sensor-detect, clicked OK.. and ok.. and ok.. so how DO you start it? -- Paul Cartwright Registered Linux user # 367800
On Friday 19 November 2004 8:08 pm, Paul Cartwright wrote:
On Saturday 20 November 2004 7:53 pm, Marc Christensen wrote:
Strange there isnt a Yast module for lm_sensors...
I'll confirm that for 9.2, I did run the sensor-detect, clicked OK.. and ok.. and ok.. so how DO you start it?
Hi, I found that 9.2 has KSensors, which is quite cool. Once you follow the directions in the output of "sensors-detect" just open a terminal/shell and do the following: kstart --alldesktops --ontop --skiptaskbar --skippager ksensors kstart --alldesktops --ontop --skiptaskbar --skippager gkrellm You will have to configure each gkrellm and KSensors to show your system values. You should see an incidence of each on each of your desktops. You can add and remove options to each as you prefer. Below is a 'clip' from the sensors-detect run on mysys. Yours will have different values. this is inserted into a file called 'boot.local' in the /etc/init.d directory. # # ...........I2C ADAPTER Drivers modprobe i2c-viapro modprobe i2c-isa # ...........I2C CHIP Drivers modprobe eeprom modprobe w83627hf sleep 1 /usr/bin/sensors -s Let us know how it works for you. ............ PeterB
On Saturday 20 November 2004 07:01, Peter B Van Campen wrote:
On Friday 19 November 2004 8:08 pm, Paul Cartwright wrote:
On Saturday 20 November 2004 7:53 pm, Marc Christensen wrote:
Strange there isnt a Yast module for lm_sensors...
I'll confirm that for 9.2, I did run the sensor-detect, clicked OK.. and ok.. and ok..
I have started lm_sensors successfully. When I run the 'sensors command I get w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.59 V (min = +1.72 V, max = +1.89 V) +3.3V: +3.35 V (min = +3.14 V, max = +3.48 V) +5V: +5.09 V (min = +4.77 V, max = +5.25 V) +12V: +11.81 V (min = +10.84 V, max = +13.21 V) -12V: -12.50 V (min = -13.16 V, max = -10.77 V) -5V: -5.08 V (min = -5.23 V, max = -4.73 V) V5SB: +5.65 V (min = +4.77 V, max = +5.25 V) VBat: +1.48 V (min = +2.40 V, max = +3.60 V) fan1: 2657 RPM (min = 2657 RPM, div = 2) ALARM fan2: 0 RPM (min = 0 RPM, div = 2) temp1: +39°C (high = +127°C) sensor = thermistor temp2: +39.0°C (high = +80°C, hyst = +80°C) sensor = PII/Celeron diode alarms: Chassis intrusion detection ALARM beep_enable: Sound alarm disabled eeprom-i2c-2-51 Adapter: SiS96x SMBus adapter at 0x1400 Memory type: DDR SDRAM DIMM Memory size (MB): 256 eeprom-i2c-2-50 Adapter: SiS96x SMBus adapter at 0x1400 Memory type: DDR SDRAM DIMM Memory size (MB): 256 Note that my VCore, V5SB,VBat and fan1 seem to be out of range. Is this serious ? Regards Paul -- Paul Hewlett (Linux #359543) Email:`echo az.oc.evitcaten@ttelweh | rev` Tel: +27 21 852 8812 Cel : +27 72 719 2725 FAX: +27 866720563 --
Paul Hewlett wrote:
I have started lm_sensors successfully. When I run the 'sensors command I get
w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.59 V (min = +1.72 V, max = +1.89 V) +3.3V: +3.35 V (min = +3.14 V, max = +3.48 V) +5V: +5.09 V (min = +4.77 V, max = +5.25 V) +12V: +11.81 V (min = +10.84 V, max = +13.21 V) -12V: -12.50 V (min = -13.16 V, max = -10.77 V) -5V: -5.08 V (min = -5.23 V, max = -4.73 V) V5SB: +5.65 V (min = +4.77 V, max = +5.25 V) VBat: +1.48 V (min = +2.40 V, max = +3.60 V) fan1: 2657 RPM (min = 2657 RPM, div = 2) ALARM fan2: 0 RPM (min = 0 RPM, div = 2) temp1: +39°C (high = +127°C) sensor = thermistor temp2: +39.0°C (high = +80°C, hyst = +80°C) sensor = PII/Celeron diode alarms: Chassis intrusion detection ALARM beep_enable: Sound alarm disabled <snip>
Note that my VCore, V5SB,VBat and fan1 seem to be out of range. Is this serious ?
No, it just means that the values used by the sensors developers are different than the motherboard you have. To correct this, you can edit /etc/sensors.conf, and maybe change the multipliers for the voltage readings, and the min setting for the fan. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Saturday 20 November 2004 4:38 am, Paul Hewlett wrote:
On Saturday 20 November 2004 07:01, Peter B Van Campen wrote:
On Friday 19 November 2004 8:08 pm, Paul Cartwright wrote:
On Saturday 20 November 2004 7:53 pm, Marc Christensen wrote:
I have started lm_sensors successfully. When I run the 'sensors command I get
w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.59 V (min = +1.72 V, max = +1.89 V) +3.3V: +3.35 V (min = +3.14 V, max = +3.48 V) +5V: +5.09 V (min = +4.77 V, max = +5.25 V) +12V: +11.81 V (min = +10.84 V, max = +13.21 V) -12V: -12.50 V (min = -13.16 V, max = -10.77 V) -5V: -5.08 V (min = -5.23 V, max = -4.73 V) V5SB: +5.65 V (min = +4.77 V, max = +5.25 V) VBat: +1.48 V (min = +2.40 V, max = +3.60 V) fan1: 2657 RPM (min = 2657 RPM, div = 2) ALARM fan2: 0 RPM (min = 0 RPM, div = 2) temp1: +39°C (high = +127°C) sensor = thermistor temp2: +39.0°C (high = +80°C, hyst = +80°C) sensor = PII/Celeron diode alarms: Chassis intrusion detection ALARM beep_enable: Sound alarm disabled
eeprom-i2c-2-51 Adapter: SiS96x SMBus adapter at 0x1400 Memory type: DDR SDRAM DIMM Memory size (MB): 256
eeprom-i2c-2-50 Adapter: SiS96x SMBus adapter at 0x1400 Memory type: DDR SDRAM DIMM Memory size (MB): 256
Note that my VCore, V5SB,VBat and fan1 seem to be out of range. Is this serious ?
Hi, Look at what the BIOS tells you and write them down for camparison and to adjust the Gkrellm or KSensors or KSysguard multipliers. Shutdown system and have the system go into the MB BIOS setup screens. Look for the "PC Health" screen or whatever your MB manuf calles it. This display shows the correct values tthat the manuf has calibrated. Then after re-booting you can adjust the multipliers to get the same values. PeterB
Marc, On Friday 19 November 2004 13:25, Marc Christensen wrote:
I have installed SuSE 9.1 and now 9.2 on hardware that has sensor hardware but I am confused at how to get sensors working so that I can see CPU tems, fan speeds, etc.
What is the processes for setting this up?
Well, if like me you have an Intel mainboard D865PERL, then "the
process" involves mostly waiting for a driver, which "will be
developped [sic] upon donation of a board" (see
Thanks...
-- Marc Christensen
Randall Schulz
participants (10)
-
Anders Johansson -
Donn Washburn -
Joe Morris (NTM) -
Marc Christensen -
Paul Cartwright -
Paul Hewlett -
Peter B Van Campen -
peter Nikolic -
Randall R Schulz -
Sid Boyce