Silencing lm-sensors alarms

This guide might help you configure your lm-sensors.

This example is made using an Intel DH61AG motherboard.

After installing lm-sensors on my Ubuntu machine, I had some strange readings and alarms in the sensors output:

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +37.0°C  (high = +82.0°C, crit = +102.0°C)
Core 0:         +30.0°C  (high = +82.0°C, crit = +102.0°C)
Core 1:         +31.0°C  (high = +82.0°C, crit = +102.0°C)

nct6775-isa-0290
Adapter: ISA adapter
Vcore:          +0.74 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +1.09 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.34 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.34 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:           +3.34 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.26 V  (min =  +2.70 V, max =  +3.63 V)
fan1:             0 RPM  (min =    0 RPM, div = 128)
fan2:          1318 RPM  (min =    0 RPM, div = 64)  ALARM
fan3:             0 RPM  (min =    0 RPM, div = 128)
fan4:             0 RPM  (div = 128)
SYSTIN:         +46.0°C  (high = +0.0°C, hyst = +0.0°C)  ALARM  sensor = CPU diode
CPUTIN:         +38.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
AUXTIN:          -2.5°C    sensor = CPU diode
PECI Agent 0:   +35.5°C  (high = +80.0°C, hyst = +75.0°C)
PCH_CHIP_TEMP:  +58.0°C  (high = +80.0°C, hyst = +75.0°C)
PECI Agent 1:    +0.0°C  (high = +80.0°C, hyst = +75.0°C)
cpu0_vid:      +0.000 V
intrusion0:    OK

What's worse, I discovered that the system log was getting spammed with ALARM error messages like this:

sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: SYSTIN: 46.0 C (limit = 0.0 C, hysteresis = 0.0 C) [ALARM]
sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: in1: +1.09 V (min = +0.00 V, max = +0.00 V) [ALARM]
sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: in4: +1.02 V (min = +0.00 V, max = +0.00 V) [ALARM]
sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: in5: +1.02 V (min = +0.00 V, max = +0.00 V) [ALARM]
sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: in6: +1.06 V (min = +0.00 V, max = +0.00 V) [ALARM]
sensord[ ]: Sensor alarm: Chip nct6775-isa-0290: fan2: 1278 RPM (min = 0 RPM, div = 32) [ALARM]

First, I needed some more information on these strange readings. The following command reveals all the available config parameters:

sensors -u

The output is something like this:

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 36.000
  temp1_max: 82.000
  temp1_crit: 102.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 30.000
  temp2_max: 82.000
  temp2_crit: 102.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 31.000
  temp3_max: 82.000
  temp3_crit: 102.000
  temp3_crit_alarm: 0.000

nct6775-isa-0290
Adapter: ISA adapter
Vcore:
  in0_input: 0.736
  in0_min: 0.000
  in0_max: 1.744
  in0_alarm: 0.000
AVCC:
  in2_input: 3.344
  in2_min: 2.976
  in2_max: 3.632
  in2_alarm: 0.000
+3.3V:
  in3_input: 3.344
  in3_min: 2.976
  in3_max: 3.632
  in3_alarm: 0.000
3VSB:
  in7_input: 3.344
  in7_min: 2.976
  in7_max: 3.632
  in7_alarm: 0.000
Vbat:
  in8_input: 3.264
  in8_min: 2.704
  in8_max: 3.632
  in8_alarm: 0.000
fan2:
  fan2_input: 1318.000
  fan2_min: 0.000
  fan2_alarm: 0.000
  fan2_div: 64.000
SYSTIN:
  temp1_input: 46.000
  temp1_max: 0.000
  temp1_max_hyst: 0.000
  temp1_alarm: 0.000
  temp1_type: 1.000
  temp1_offset: 0.000
CPUTIN:
  temp2_input: 38.000
  temp2_max: 80.000
  temp2_max_hyst: 75.000
  temp2_alarm: 0.000
  temp2_type: 1.000
  temp2_offset: 0.000
AUXTIN:
  temp3_input: -2.500
  temp3_alarm: 0.000
  temp3_type: 1.000
  temp3_offset: 0.000
PECI Agent 0:
  temp6_input: 35.500
  temp6_max: 80.000
  temp6_max_hyst: 75.000
PCH_CHIP_TEMP:
  temp7_input: 58.000
  temp7_max: 80.000
  temp7_max_hyst: 75.000
PECI Agent 1:
  temp8_input: 0.000
  temp8_max: 80.000
  temp8_max_hyst: 75.000
cpu0_vid:
  cpu0_vid: 0.000
intrusion0:
  intrusion0_alarm: 0.000


Now we know the real names of these mysterious readings, and can silence the alarms by creating a custom configuration file:

/etc/sensors.d/custom.conf

The file would eventually look like this:

chip "nct6775-isa-0290"
    ignore fan1
    ignore fan3
    ignore fan4
    ignore in1
    ignore in4
    ignore in5
    ignore in6
    ignore temp8
    ignore cpu0_vid
    ignore intrusion0
    set fan2_min 200
    set temp1_max 80
    set temp1_max_hyst 75

The fan1-fan4 readings were showing 0 RPM since they don't exist. They needed to be ignored.

Voltages in1, in4, in5 and in6 were unknown, so I decided to just ignore them.

The only connected fan "fan2" was also giving an ALARM. This was because the fan2_min wasn't set. I set the minimum to 200 RPM, which seems to be a popular choice.

For SYSTIN I set a maximum temperature of 80 and a hysteresis of 75 degrees (temp1_max and temp1_max_hyst). This got rid of the ALARM.

The temp8, cpu0_vid, intrusion0 readings were nonsensical, so i just ignored them as well.

After creating the custom config file, reload the configuration by typing:

sensors -s

After all this, the sensors output is much nicer:

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +36.0°C  (high = +82.0°C, crit = +102.0°C)
Core 0:         +30.0°C  (high = +82.0°C, crit = +102.0°C)
Core 1:         +31.0°C  (high = +82.0°C, crit = +102.0°C)

nct6775-isa-0290
Adapter: ISA adapter
Vcore:          +0.74 V  (min =  +0.00 V, max =  +1.74 V)
AVCC:           +3.34 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.34 V  (min =  +2.98 V, max =  +3.63 V)
3VSB:           +3.34 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.26 V  (min =  +2.70 V, max =  +3.63 V)
fan2:          1318 RPM  (min =  200 RPM, div = 64)
SYSTIN:         +46.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
CPUTIN:         +38.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
AUXTIN:          -3.5°C    sensor = CPU diode
PECI Agent 0:   +35.5°C  (high = +80.0°C, hyst = +75.0°C)
PCH_CHIP_TEMP:  +58.0°C  (high = +80.0°C, hyst = +75.0°C)


Comments

Post a Comment

Popular posts from this blog

How to fix the weird audio bug in Kingdom Come: Deliverance

Image
  Kingdom Come: Deliverance has a bug which makes the sound come out muffled or like the characters were talking far away or through a tunnel. This seems to be because the game thinks you are using multichannel surround sound. There seems to be no option to change the audio mode in-game. Instead, you should change your audio settings in Windows by following these directions: Press the windows key Type "Choose your output device" and select the search result. Select "Device properties" under the Output caption. Select "Additional device properties" This dialog will differ depending on your audio hardware. Go to the Advanced tab. There should be a selection for the default audio format. You should select something like this: 2 channel 44100 Hz audio. I had my Focusrite audio interface set up with 8 channels 24bit 44100 Hz, and that caused Kingdom Come to think I have surround sound. After changing the channel amount to 2 the audio started working correctly.
Read more

Minecraft recv failed error... fixed!

Image
OK. A lot of people seem to have this problem. Finally, I managed to fix it for myself! This problem is quite common with Minecraft Survival Multiplayer. Basically, the problem goes like this: you connect to a server, maybe manage to do something for some minutes, and then you eventually hang up with the message: Internal exception: java.netSocketException: Software caused connection abort: recv failed For some, this comes instantly. Some fall straight into the void and cannot communicate through the chat, although they see the others talk. Some even get to mine something for a while. But then it all ends with this message. It seems that this problem is due to two things: certain integrated network adapters and their old / buggy drivers, and the current buggy state of Minecraft multiplayer mode. Also, some people report that the problem may occur due to incorrect port forwarding. With me, this was not the case. Solutions that work for some people (but didn't work...
Read more

Where does uTorrent keep its .torrent files?

NOTE: uTorrent cannot be trusted anymore. It is known to install Yandex, Ask Toolbar, a bitcoin miner and displayed ads among other fishy stuff. Don't use uTorrent! I recommend using qBittorrent instead, which is an open-source alternative. If you deleted uTorrent and want to remove all of its files, you might want to know where it stores them. On Windows 7, uTorrent stores .torrent files by default in: C:\Users\%USERNAME%\AppData\Roaming\uTorrent ...where %USERNAME% is your Win7 username, and assuming your Windows 7 installation is on C: drive. If you can't browse to this directory, write it on the address bar of Explorer. Another way is to show hidden files by going to Win7 control panel's "folder options" - then you can see the AppData folder.
Read more

How to install and play Curse of Monkey Island on Android

Image
There are some great adventure games on Android already. I can warmly recommend Thimbleweed Park or The Silent Age for example. But what if you wanted to play an old classic that cannot be found on Google Play? ScummVM is an app that can emulate these games, if you have the data files. And Curse of Monkey Island is one of these classics. Installation Purchase Curse of Monkey Island from gog.com or Steam (costs about 5€) Download and install it with the GOG Galaxy launcher ... Or Steam Locate the Curse of Monkey Island install directory on your PC Copy the directory to your Android phone, either with a USB cable or on the SD card with an adapter Install the ScummVM app on your phone Start ScummVM and press "Add game" Find the game folder on your phone, select it and click OK.  If you have trouble finding the folder, I made a separate guide for that. Now you can start enjoying Curse of Monkey Island! These instructions should also work on an iPhone. Controls The game is or...
Read more

How to get rid of coil whine just by tweaking BIOS

Finally. No more ringing in my ears! I had a really bad case of coil whine with my computer. In the end I fixed it just by tweaking the BIOS! The coil whine was at it's worst when the PC was idling or under a light load.  Coil whine is a high-pitched sound that is produced by coils resonating at a high frequency. It is really hard to sense where exactly it's coming from. This is because humans cannot sense direction for high-pitched sounds. At first I thought it was my graphics adapter. So I bought a new used one. But the ringing was still there after the upgrade. Next up, I suspected my PSU was the culprit. So I changed the power supply to a newer 80 Plus Platinum model. I hate changing the PSU. And it didn't help. So it looked like my motherboard was the cause. It's an older ASUS motherboard, P8H67-V.  After googling around a bit, I found people talking about ASUS motherboards and coil whine when power-saving features are on in the BIOS . The so-called "C-state...
Read more

Running Black Dahlia on modern PCs

I just played through the old PC adventure game Black Dahlia. It's a good game, well worth a look if you like adventure games. It's a full-motion video (FMV) based game spanning 8 CDs, with some OK acting and an entertaining (but confusing and sometimes illogical) plot. The game was made in 1998 for Windows 95/98 and it's not that trivial to get it to work flawlessly. Here's how to do it. If you are running a Windows version above Windows XP If you are using any of these: Windows Vista Windows 7 Windows 8 Windows 10 Windows 11 ...you most probably can't make the game work without a virtual machine. But still I recommend you to try it yourself, using the below game installation guide. Installing Win95 / 98 on a virtual PC 1) Install Oracle VM Virtualbox and create a virtual PC 2) Install Windows 95 or 98 on the virtual PC Get hold of a copy of Windows 95 or 98. Maybe the easiest to install is the Windows 95 floppy disk version. Here's a guide to help you with ...
Read more