bug fix: long standing issue, if mobo temp undefined, was showing

temp 0, not N/A as intended.
This commit is contained in:
Harald Hope 2021-07-11 20:49:31 -07:00
parent 9ff2bd262f
commit 994ab96b7a
2 changed files with 6 additions and 3 deletions

5
inxi
View file

@ -19427,9 +19427,8 @@ sub set_temp_unit {
sub process_data {
eval $start if $b_log;
my (%sensors) = @_;
my ($cpu_temp,$cpu2_temp,$cpu3_temp,$cpu4_temp,$index_count_fan_default,
$index_count_fan_main,$mobo_temp,$psu_temp) = (0,0,0,0,0,0,0,0);
my ($fan_type,$i,$j) = (0,0,0);
my ($cpu_temp,$cpu2_temp,$cpu3_temp,$cpu4_temp,$mobo_temp,$psu_temp);
my ($fan_type,$i,$j,$index_count_fan_default,$index_count_fan_main) = (0,0,0,0,0);
my $temp_diff = 20; # for C, handled for F after that is determined
my (@fan_main,@fan_default);
# first we need to handle the case where we have to determine which temp/fan to use for cpu and mobo:

View file

@ -73,6 +73,10 @@ etc for zfs.
6. Failed uptime report data due to yet another random syntax change in the
data. See Code Change 1 for details on the fix.
7. A change at some point made sensors show 0 instead of N/A due to improperly
setting undefined sensor values as 0. This in particular happened with mobo
temps on systems without known mobo temp sensors.
--------------------------------------------------------------------------------
ENHANCEMENTS: