Sponsored Content
Top Forums UNIX for Advanced & Expert Users accessing temperatures under Slackware Post 302678491 by slak0 on Saturday 28th of July 2012 06:28:02 AM
Old 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

Unix shell script converting temperatures.

: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

Skype on Slackware 64

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

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

Slackware 13.

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

HDD temperatures monitoring

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
DBCOOL(4)						   BSD Kernel Interfaces Manual 						 DBCOOL(4)

NAME
dbcool, adm1027, adm1030, adm1031, adt7463, adt7466, adt7467, adt7468, adt7473, adt7475, adt7476, adt7490, emc6d103s -- dbCool(tm) family of environmental monitors and fan controllers SYNOPSIS
dbcool* at ki2c? dbcool* at iic? addr 0x2e DESCRIPTION
The dbcool driver provides support for the Analog Devices dbCool and the SMSC EMC6D103S environmental monitor chips to be used with the envsys(4) API. These chips support up to fifteen sensors. Not all of the following sensors are supported on all chips. Sensor Units Typical Use l_temp uK local chip temperature r1_temp uK CPU temperature r2_temp uK GPU temperature Vccp uV DC CPU Vcore Vcc uV DC Chip's supply voltage 2.5V uV DC 2.5V supply 5V uV DC 5V supply 12V uV DC 12V supply Vtt uV DC PECI ref. voltage (2.25V ref, ADT7490 only) Imon uV DC Current monitor (2.25V ref, ADT7490 only) AIN1 uV DC Analog In (2.25V ref, ADT7466 only) AIN2 uV DC Analog In (2.25V ref, ADT7466 only) fan1 RPM Chassis Fan fan2 RPM Chassis Fan fan3 RPM Chassis Fan fan4 RPM Chassis Fan VID (none) CPU VID code (selected chips only) Each temperature and voltage sensor has programmable hardware high- and low-limits; fan sensors have only a low-limit. These limits can be set using the envstat(8) utility. Due to hardware limitations, the minimum permissible value for the fan speed low-limits is 83 RPM. Temperature sensors also have Tmin, Trange, Thyst, and Ttherm sysctl(8) variables; these values are used by the fan speed controllers. Their values are in units of degC, since this is the unit which is programmed into the device registers. All members of the dbCool family support Pulse-Width Modulated (PWM) fan speed control based on temperature thresholds - the fan will spin up when its associated thermal sensor(s) exceeds its configured Tmin value. The fan will go faster as the temperature rises, and will slow down as the temperature falls. If the temperature exceeds the sensor's Ttherm value, the THERM signal will be asserted, and if enabled the fan will run at full speed. The fan will be turned off when the sensor(s) that triggered it reports a temperature which is at least Thyst degrees below its Tmin threshold. Each fan controller is programmable using the following sysctl(8) variables. hw.dbcool0.fan_ctl_0.behavior hw.dbcool0.fan_ctl_0.min_duty hw.dbcool0.fan_ctl_0.max_duty hw.dbcool0.fan_ctl_0.cur_duty The behavior variable controls the selection of temperature sensors associated with the fan controller. When the associated temperature sen- sor reaches its Tmin value, the fan controller starts the fan at its minimum duty cycle; when the associated temperature sensor reaches its Ttherm value and asserts the THERM signal (or if an external THERM signal is asserted), the fan controller sets the fan speed to a 100% duty cycle. Between these two settings, each temperature sensor is used to calculate a duty cycle linearly based on the slope defined by the tem- perature sensor's range variable. When the associated temperature falls at least Thyst degress below its Tmin value, the fan controller will turn off the fan. (On the ADM1030, the value for Thyst is fixed at 5 degC.) Valid values for the behavior variable are: local (not available on ADM1030) remote1 remote2 (not available on ADM1030) local+remote2 (not available on ADM1030) all-temps full-speed (not available on ADM1030) manual disabled When the behavior variable is set to ``manual'', the cur-duty variable becomes user-writable and can be set to any value between 0 and 100 inclusive to control the fan's duty cycle manually. In all other behavior modes, the cur-duty variable is read-only and updates are ignored. The min-duty and max-duty variables define the range over which the fan controller will manage the fan's duty cycle. On the ADM1030, these values are not separately controllable. The max-duty is fixed at 100%, and the cur-duty variable is used to specify the minimum duty cycle when the fan controller is running in automatic mode. Note that the duty-cycle value does not directly correspond to the fan's speed. That is, a 33% duty cycle does not mean that the fan runs at 33% of its maximum speed; in actuality, a 33% duty cycle drives the fan at a speed close to 50% of its maximum. Fan speed correlates approx- imately to the square root of the duty cycle. EXAMPLES
The envstat(8) utility can be used to determine the sensors supported: Current CritMax WarnMax WarnMin CritMin Unit l_temp: 44.250 degC r1_temp: 41.250 degC r2_temp: N/A Vccp: 0.002 V Vcc: 3.351 V fan1: N/A fan2: N/A fan3: N/A fan4: N/A Using this information, the following commands in /etc/envsys.conf will set appropriate limits for CPU temperature and chip supply voltage, and powerd will be notified if the limits are exceeded: dbcool0 { sensor1 { warning-max = 60C; critical-max = 65C; } sensor4 { critical-min = 3.1; warning-min = 3.2; critical-max = 3.5; } } SEE ALSO
envsys(4), iic(4), envstat(8), powerd(8), sysctl(8) HISTORY
The dbcool device appeared in NetBSD 5.0. BUGS
Although the sensor limit registers can be programmed, there is currently no use of the dbCool chips' ability to generate an SMBus interrupt when the limits are exceeded. Limit checking and event generation are done in software, and are performed only when the sensor values are polled and refreshed. The ADT7466 chip, although officially a member of the dbCool family, is programmed quite differently. The fan controllers on this chip are not currently implemented. The PECI (Processor Environment Control Interface) temperature sensors and the associated PWM behavior modes on the ADT7490 are not currently supported. BSD
March 12, 2011 BSD
All times are GMT -4. The time now is 01:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy