lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

Utini · 2017-10-02 19:09:58

Motherboard: Gigabyte GA-B250N-Phoenix-WIFI
CPU: Intel G4600
Fan: Noctua NF-A15 PWM

Installed "lm_sensors", ran "sudo sensors-detect" and pressed "enter" through all options:

# sensors-detect revision $Revision$
# System: Gigabyte Technology Co., Ltd. B250N Phoenix WIFI [Default string]
# Board: Gigabyte Technology Co., Ltd. B250N Phoenix WIFI-CF
# Kernel: 4.13.3-1-ARCH x86_64
# Processor: Intel(R) Pentium(R) CPU G4600 @ 3.60GHz (6/158/9)

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.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded 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): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8686
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are 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): 
Probing for `National Semiconductor LM78' 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

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Found unknown SMBus adapter 8086:a2a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Next adapter: i915 gmbus dpc (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: i915 gmbus dpd (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: DPDDC-D (i2c-4)
Do you want to scan it? (yes/NO/selectively): 


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): yes
Unloading i2c-dev... OK
Unloading cpuid... OK

How ever, when running "sensors" or "watch sensors" I don't get my chipset output and also no fan speed:

iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +32.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +28.0°C  (high = +80.0°C, crit = +100.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +119.0°C)
temp2:        +29.8°C  (crit = +119.0°C)

Any ideas whats wrong? This might also break "thermald" for me?

Thanks in advance !

dockland · 2017-10-02 19:47:54

Did you press enter at the last question?
The last question asks you if you want to save the result in a config file.
Default is no if i remember correctly.

Utini · 2017-10-02 20:23:59

Default is YES:

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): yes
Unloading i2c-dev... OK
Unloading cpuid... OK

Just tried it again by typing "YES"... same results

graysky · 2017-10-02 20:50:40

Are you certain the board has onboard sensors? Some budget ones (sometimes small form factor) do not have what you'd expect. The other option is you need to compile your own module due to a lack of upstream support. I didn't google your model to see when it was introduced to verify. I would start with trying to determine what hardware monitoring is onboard and if an AUR package is available. For example, a few years ago, I needed to compile my own module until the ntc67xx code was accepted into the kernel. https://aur.archlinux.org/packages/nct677x-git/

Utini · 2017-10-02 22:18:45

Well, I just found out that this command changes something:

modprobe it87 force_id=0x8728

I then get the following output with "sensors":

iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +35.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +29.0°C  (high = +80.0°C, crit = +100.0°C)

it8728-isa-0a40
Adapter: ISA adapter
in0:          +0.71 V  (min =  +0.00 V, max =  +3.06 V)
in1:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.03 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.03 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +0.40 V  (min =  +0.00 V, max =  +3.06 V)  ALARM
in5:          +1.04 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +1.21 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.31 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +3.02 V  
fan1:         150 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
temp1:        +34.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        +45.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +29.0°C  (low  =  +0.0°C, high = +90.0°C)  sensor = disabled
intrusion0:  ALARM

acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +119.0°C)
temp2:        +29.8°C  (crit = +119.0°C)

I am just not sure if those are the correct values now? No idea how "force_id=0x8728" relates to my motherboard?
Fan speed is the same as within BIOS.
Temps are a bit confusing so I am not sure... what is what?

Last edited by Utini (2017-10-02 22:19:25)

mich41 · 2017-10-03 07:52:09

It pretends that it detected some different (supported) chip than the unsupported 8686 you actually have. Whether the results are correct will depend on the degree of compatibility between your 8686 and whatever random chip you forced instead. Hard to tell without detailed technical knowledge.

However, it seems that 8686 support is present in the upstream it87 driver, just not yet integrated in the kernel. Try to use this code

https://github.com/groeck/it87

(download zip, unpack, run "make", load with "insmod ./it87.ko" as root)

There might be a package for that in AUR.

Utini · 2017-10-03 11:13:40

mich41 wrote:

It pretends that it detected some different (supported) chip than the unsupported 8686 you actually have. Whether the results are correct will depend on the degree of compatibility between your 8686 and whatever random chip you forced instead. Hard to tell without detailed technical knowledge.
However, it seems that 8686 support is present in the upstream it87 driver, just not yet integrated in the kernel. Try to use this code
https://github.com/groeck/it87
(download zip, unpack, run "make", load with "insmod ./it87.ko" as root)
There might be a package for that in AUR.

Well I actually only wanted it to work to see my CPU-Fan rpm speed. That works without installing the package from the AUR.
When knowing the CPU-Fan RPM/Speed, I will also know the CPU temps as I mapped the fan settings myself in BIOS.

So if I am happy with my fan settings and won't need to view the fan speed anymore, is there any need of getting this to work correctly?
E.g. is it relevant for thermald or anything else?

Last edited by Utini (2017-10-03 11:14:15)

Arch Linux

#1 2017-10-02 19:09:58

lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#2 2017-10-02 19:47:54

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#3 2017-10-02 20:23:59

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#4 2017-10-02 20:50:40

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#5 2017-10-02 22:18:45

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#6 2017-10-03 07:52:09

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

#7 2017-10-03 11:13:40

Re: lm_sensors -> sensors -> No chipset + values (Gigabyte GA-B250N)

Board footer