SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, I've searched and read a few other threads. I even tried what they suggested, but I'm still not having any luck. Does anyone know how to get lm_sensors working in slack 12.2? I had it working fine in 11. This is what I get:
Code:
root@bipers:/etc/rc.d/init.d# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@bipers:/etc/rc.d/init.d#
Code:
root@bipers:/etc/rc.d/init.d# sensors-detect
# sensors-detect revision 5337 (2008-09-19 17:05:28 +0200)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 0000:00:04.3: VIA Technologies VT82C596 Apollo ACPI
We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus Via Pro adapter at e800 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x2d
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM78-J'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000'... No
Probing for `Analog Devices ADM1027'... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83783S'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83791SD'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... Success!
(confidence 8, driver `w83781d', other addresses: 0x48 0x49)
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L784R/AR/G'... No
Probing for `Winbond W83L785R/G'... No
Probing for `Genesys Logic GL518SM Revision 0x00'... No
Probing for `Genesys Logic GL518SM Revision 0x80'... No
Probing for `Genesys Logic GL520SM'... No
Probing for `Genesys Logic GL525SM'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Philips NE1619'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `VIA VT1211 (I2C)'... No
Probing for `ITE IT8712F'... No
Probing for `ALi M5879'... No
Probing for `SMSC LPC47M15x/192/292/997'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Analog Devices ADM1024'... No
Probing for `Winbond W83791D'... No
Client found at address 0x2f
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM78-J'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83791SD'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1029'... No
Probing for `ITE IT8712F'... No
Probing for `Fintek custom power control IC'... No
Probing for `Winbond W83791D'... No
Client found at address 0x48
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6650/MAX6651'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at e800'
Busdriver `i2c-viapro', I2C address 0x2d (and 0x48 0x49)
Chip `Asus AS99127F (rev.2)' (confidence: 8)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
You should now start the lm_sensors service to load the required
kernel modules.
root@bipers:/etc/rc.d/init.d#
root@bipers:/etc/rc.d/init.d#modprobe processor
FATAL: Error inserting processor (/lib/modules/2.6.27.7-smp/kernel/drivers/acpi/processor.ko): No such device
root@bipers:/etc/rc.d/init.d#
Code:
root@bipers:/etc/rc.d/init.d# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@bipers:/etc/rc.d/init.d#
Please help, I'm starting to get frustrated. Thanks.
Basically, the "sensors-detect" program tests all available sensor-modules and reports which one works.
This depends on your motherboard / chipset / etc.
In your case, the one that worked is w83781d, as can be seen in your output:
Code:
Probing for `Asus AS99127F (rev.2)'... Success!
(confidence 8, driver `w83781d', other addresses: 0x48 0x49)
So all you needed to do is load the kernel module with "modprobe w83781d" and run the sensors program again.
Now you can start playing around with gkrellm and / or conky
Awesome. My computer started beeping intermittently earlier and I was wondering if it had anything to do with the CPU temperature. It started out random then turned into a solid tone. When I'd reboot it would go away but come back for a few minutes. Would that make sense from the readings below? (the BIOS on a reboot, reported the CPU to be 136F degrees.
Code:
bash-3.1$ sensors -f
as99127f-i2c-0-2d
Adapter: SMBus Via Pro adapter at e800
VCore 1: +1.71 V (min = +1.49 V, max = +1.90 V)
VCore 2: +2.45 V (min = +1.49 V, max = +1.90 V)
+3.3V: +3.47 V (min = +2.96 V, max = +3.63 V)
+5V: +5.03 V (min = +4.49 V, max = +5.51 V)
+12V: +11.80 V (min = +9.55 V, max = +14.41 V)
-12V: -2.48 V (min = -0.32 V, max = -4.07 V)
-5V: -1.30 V (min = -0.82 V, max = -1.76 V)
fan1: 3835 RPM (min = 1607 RPM, div = 4)
fan2: 0 RPM (min = 1424 RPM, div = 4)
fan3: 0 RPM (min = 2280 RPM, div = 4)
M/B Temp: +80.6°F (high = +62.6°F, hyst = +213.8°F) ALARM
CPU Temp: +116.6°F (high = +212.0°F, hyst = +197.6°F)
temp3: +31.1°F (high = +251.6°F, hyst = +249.8°F)
cpu0_vid: +1.700 V
beep_enable:enabled
bash-3.1$
At least my Superkaramba theme will show all the right info now.
Well, 116.6°F is not too hot. I live in Rio de Janeiro where the room-temperature can be 110°F and my processor goes to 140°F without problems under heavy load (converting .avi files, compiling kernels, etc...).
Your sensors say that your M/B temp is cause for "ALARM" at 80.6°F but that sounds strange to me.
Check in your BIOS if there are any settings for the minimum or maximum temperature.
Since it starts beeping, it sounds like a BIOS warning, not something from the operating system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.