resources icon indicating copy to clipboard operation
resources copied to clipboard

Motherboard info and sensors

Open Lassebq opened this issue 7 months ago • 5 comments

Is there an existing issue for this?

  • [x] I have searched the existing issues

Is your feature request related to a problem? Please describe.

I'd like to see a GUI implementation of motherboard sensor monitoring. E. g. chassis and CPU fan speeds, southbridge and VRM temps, vendor and motherboard model name. Do note that sometimes there are fields which are left as "To Be Filled By O.E.M." so fallbacks need to be implemented. Like in my case ASRock B550M Phantom Gaming 4 has the vendor name "ASRock" display as "To Be Filled By O.E.M." in some places like journald but it appears to be fine when viewing System -> About tab in GNOME Settings.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

Here's the relevant sensors output

$ sensors nct6798-isa-0290  
nct6798-isa-0290
Adapter: ISA adapter
in0:                   504.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                     1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.47 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.83 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                     1.11 V  (min =  +0.00 V, max =  +0.00 V)
in6:                     1.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.47 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.81 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    2.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                    1.26 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.09 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  920.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                  904.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                   832 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan6:                     0 RPM  (min =    0 RPM)
fan7:                  1071 RPM  (min =    0 RPM)
SYSTIN:                 +40.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +127.0°C)  sensor = thermistor
CPUTIN:                 +41.5°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +80.0°C)  sensor = thermistor
AUXTIN0:                 +8.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN1:                -61.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +85.0°C)  sensor = thermistor
AUXTIN2:                +12.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +90.0°C)  sensor = thermistor
AUXTIN3:                +31.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN4:                +20.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit =  +0.0°C)
SMBUSMASTER 0:          +43.0°C  (high = +80.0°C, hyst = +75.0°C)
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  
TSI0_TEMP:              +43.6°C  
pwm1:                       38%  (mode = pwm)  MANUAL CONTROL
pwm2:                       28%  (mode = pwm)
pwm3:                       38%  (mode = pwm)  MANUAL CONTROL
pwm4:                       22%  (mode = pwm)
pwm5:                       15%  (mode = pwm)
pwm6:                       38%  (mode = pwm)  MANUAL CONTROL
pwm7:                      128%  (mode = pwm)
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

Lassebq avatar May 19 '25 18:05 Lassebq

Hi, thanks for the suggestion. I'm afraid that I probably won't implement motherboard sensor monitoring because I fear it'd bloat up the GUI with information I doubt many people care about (or can even understand).

nokyan avatar May 20 '25 15:05 nokyan

Why? There's a lot of windows software with motherboard info but almost nothing like that on linux. HWMonitor, HWInfo, AIDA64, all have motherboard info and I'm pretty sure most of them implement live sensor monitoring too.

Lassebq avatar May 20 '25 17:05 Lassebq

Man, a software like HWInfo for Linux would be awesome!!

raulgrangeiro avatar May 20 '25 20:05 raulgrangeiro

There is hardinfo2, I think this should be similar to HWinfo. :) For Resources, I prefer it to be software akin to Task Manager, GNOME System Monitor and so on.

nokyan avatar May 21 '25 16:05 nokyan

GTKStressTesting also shows nice info @Lassebq

peterdk avatar Jul 26 '25 09:07 peterdk