07-28-2012
accessing temperatures under Slackware
I have been trying to access bios info regarding temperatures under my Slackware 13.37 OS.
I first looked at /proc/acpi/processor/CPU0/throttling where I found my active state to be T0 and my state count is 16. My understanding is that T0 is 100% throttling of either the CPU fan or the processor and the state count is meaningless to me.
I turned to the lm_sensors then. What I have been able to learn from sensors-detect is that my module should be w83627hf and this is a module (which I loaded via modprobe) and it is an available module.
Then I built /etc/sysconfig/lm_sensors but when it came to starting the sensors I learned only that it could be done via:
/etc/rc.d/init.d/lm_sensors start but init.d is rc.d?? Apparently, I am missing information or have taken an incorrect tack.
Can someone clear my fog about what it is I am reading under /proc and how to start the lm_sensors under Slackware?
Tnanks
---------- Post updated at 03:28 AM ---------- Previous update was at 02:18 AM ----------
By accident or perseverance I have most of the answer.
The sequence I took (the accident) was to run:
sensors -s <my_chip_set>
then per the man page (I do use them)
sensors --bus-list
To verify my results I found "HWMON_MODULES" in my config file:
cat /etc/sysconfig/lm_sensors yielded:
# Generated by sensors-detect on Sat Jul 28 00:54:55 2012
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
HWMON_MODULES="w83627hf"
# For compatibility reasons, modules are also listed individually as variables
# MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.
MODULE_0=w83627hf
I then ran:
sensors
and got:
w83697hf-isa-0290
Adapter: ISA adapter
in0: +1.68 V (min = +1.70 V, max = +2.53 V) ALARM
in2: +3.28 V (min = +4.05 V, max = +3.94 V) ALARM
in3: +3.01 V (min = +4.08 V, max = +2.38 V) ALARM
in4: +3.22 V (min = +1.26 V, max = +3.79 V)
in5: +0.61 V (min = +3.76 V, max = +1.26 V) ALARM
in6: +3.58 V (min = +4.08 V, max = +3.28 V) ALARM
in7: +3.28 V (min = +3.78 V, max = +1.94 V) ALARM
in8: +3.41 V (min = +4.05 V, max = +3.82 V) ALARM
fan1: 4787 RPM (min = 0 RPM, div = 2)
fan2: 0 RPM (min = 0 RPM, div = 4)
temp1: +40.0 C (high = -1.0 C, hyst = -1.0 C) ALARM sensor = thermistor
temp2: +40.5 C (high = +70.0 C, hyst = +67.0 C) sensor = thermistor
beep_enable:enabled
My recollection is that the AMD 2200+ is a single processor if so why do I have 2 temperatures??
Again thanks from a real happy camper
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
:confused:Please I really need help with an assignment question. I need to write a script that will take the input from a file and convert the number from Centigrade(Celcius) to Fahrenheit or vice versa. Thank you so much. I really need it to be detailed. Please remember the input comes from a file. (1 Reply)
Discussion started by: starter101
1 Replies
2. Slackware
Hi!
I've downloaded the static version (skype_static-2.1.0.81.tar.bz2) and extracted it. Then I tried to start the Skype executable file (./skype) via the terminal but nothing happens.
root@xxx:~# ls
skype_static-2.1.0.81/ skype_static-2.1.0.81.tar.bz2
root@xxx:~# cd skype_static-2.1.0.81... (2 Replies)
Discussion started by: intelfan
2 Replies
3. Slackware
I want to know more about the Concurrency(Process Synchronization, Deadlocks) of a slackware, i know already the Concurrency but i want to know further what else is the Concurrency(Process Synchronization, Deadlocks) of a slackware. :cool: (1 Reply)
Discussion started by: green12
1 Replies
4. Slackware
Hello everyone. I am a newbie in operating systems. so far I've been playing with Ubuntu and I like it a lot. I heard about Slackware and I wanna try it. Last night I download the iso but It didn't fit in my usb or Dvd. it is a 4.2 GB. Is there one less than 4.2GB that will fit in my usb or DVD? ... (1 Reply)
Discussion started by: openation1
1 Replies
5. Shell Programming and Scripting
Good day all, I am new the the shell programming and scripting world and I have a question. I need to monitor the hdd temperature of 18 different servers(each with 14 hdd) and I would like to be able to have the information displayed on a single html webpage. What would be the best approach about... (0 Replies)
Discussion started by: Zaffryn
0 Replies
LEARN ABOUT DEBIAN
psensor-server
PSENSOR-SERVER(1) User Commands PSENSOR-SERVER(1)
NAME
psensor-server - Temperature and system monitoring Web server
SYNOPSIS
psensor-server [OPTION]...
DESCRIPTION
psensor-server is an HTTP server for monitoring hardware sensors remotely.
It provides a JSON Web service which can be used by psensor(1) to monitor remotely the hardware sensors of a computer.
It can provide information about:
* the temperature of the motherboard and CPU sensors (using lm-sensors).
* the temperature of the Hard Disk Drives (using hddtemp).
* the rotation speed of the fans (using lm-sensors).
It is also possible to connect to the psensor-server with a browser, a simple Web page is displaying the sensors information and the CPU
usage.
The URL http://hostname:3131/api/1.0/sensors/[id] returns a JSON object containing all information about a sensor. [id] is the uniq identi-
fier of the sensor.
Here is an example of the JSON object of type 'sensor':
{ "id": "lmsensor acpitz-virtual-0 temp1",
"name": "temp1",
"type": 257,
"min": 47.800000,
"max": 60.800000,
"measures": [ { "value": 47.800000, "time": 1311374873 },
{ "value": 49.800000, "time": 1311374878 },
{ "value": 49.800000, "time": 1311374883 } ],
"last_measure": { "value": 49.800000, "time": 1311374883 } }
Fields of the type 'sensor':
* id: the uniq identifier of the sensor.
* name: a humean readable name of the sensor (might not be uniq).
* type: the type of sensor. Look at src/lib/psensor.h for the
different types.
* min: the minimal value of the sensor.
* max: the maximal value of the sensor.
* measures: all measures of the sensor.
* last_measure: the last value of the sensor.
* time: the time of a measure as the number of seconds since
1970/01/01.
The URL http://hostname:3131/api/1.0/sensors returns a JSON array containing all JSON objects of type 'sensor'.
If run in debug mode, psensor-server can be stopped by sending an HTTP request with the URL 'http://hostname:port/api/1.0/server/stop'.
OPTIONS
-h, --help
display this help and exit
-v, --version
display version information and exit
-d,--debug
run in debug mode
-p,--port=PORT
webserver port
-w,--wdir=DIR
directory containing webserver pages
WARNING
psensor-server does not provide any way to restrict the connection to the HTTP server, worst, no effort has been made against malicious
HTTP attacks. You should make the psensor-server port available only to a network or computer you trust by using the usual network secu-
rity tools of the system (for example, iptables(8) ).
REPORTING BUGS
Report bugs to: jeanfi@gmail.com
psensor home page: <http://wpitchoune.net/psensor>
COPYRIGHT
Copyright (C) 2010-2012 jeanfi@gmail.com License GPLv2: GNU GPL version 2 or later <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
SEE ALSO
psensor(1), sensors(1), sensors-detect(8)
psensor-server 0.6.2.17 March 2012 PSENSOR-SERVER(1)