Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: AMD x370 sensors not working

  1. #1

    Question AMD x370 sensors not working

    Hello to everyone!

    Can you help me with sensors?

    I have MSI Gaming Pro MB with X370 chipset, AMD Ryzen 1500x CPU. Leap 15, clean, kernel is 4.12.14-lp150.12.7-default, DKMS is installed 2.3-lp150.1.3

    I have just installed Leap 15, sensors was 3.4.0-lp150.2.7 and they were not detecting my k10temp and nct6775 modules, that must be loaded, as I know today.

    My current version of sensors is: 3.4.0git20180510.1c48b19-lp150.2.1, sensors-detect look's like this:

    Code:
    # sensors-detect revision $Revision$
    # System: MSI MS-7A33 [2.0]
    # Board: MSI X370 GAMING PRO (MS-7A33)
    # Kernel: 4.12.14-lp150.12.7-default x86_64
    # Processor: AMD Ryzen 5 1500X Quad-Core Processor (23/1/1)
    
    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 17h thermal sensors...                           Success!
        (driver `k10temp')
    AMD Family 15h power sensors...                             No
    AMD Family 16h power sensors...                             No
    Intel digital thermal sensor...                             No
    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'...                                      No
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor/ITE'...               No
    Trying family `SMSC'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
    Found `Nuvoton NCT6795D Super IO Sensors'                   Success!
        (address 0xa20, driver `nct6775')
    
    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):  
    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): YES
    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):  
    Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
    Module i2c-dev loaded successfully.
    
    Next adapter: AMDGPU i2c bit bus 0x90 (i2c-0)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x91 (i2c-1)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x92 (i2c-2)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x93 (i2c-3)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x94 (i2c-4)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x95 (i2c-5)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x96 (i2c-6)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: AMDGPU i2c bit bus 0x97 (i2c-7)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: card0-DP-1 (i2c-8)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-9)
    Do you want to scan it? (yes/NO/selectively): YES
    Client found at address 0x1c
    Probing for `Texas Instruments TMP421'...                   No
    Probing for `Texas Instruments TMP441'...                   No
    Probing for `SMSC EMC1072'...                               No
    Probing for `SMSC EMC1073'...                               No
    Probing for `SMSC EMC1074'...                               No
    Probing for `ST STTS424'...                                 No
    Probing for `ST STTS424E'...                                No
    Probing for `ST STTS2002'...                                No
    Probing for `ST STTS3000'...                                No
    Probing for `NXP SE97/SE97B'...                             No
    Probing for `NXP SE98'...                                   No
    Probing for `Analog Devices ADT7408'...                     No
    Probing for `IDT TS3000/TSE2002'...                         No
    Probing for `IDT TSE2004'...                                No
    Probing for `IDT TS3001'...                                 No
    Probing for `Maxim MAX6604'...                              No
    Probing for `Microchip MCP9804'...                          No
    Probing for `Microchip MCP9808'...                          No
    Probing for `Microchip MCP98242'...                         No
    Probing for `Microchip MCP98243'...                         No
    Probing for `Microchip MCP98244'...                         No
    Probing for `Microchip MCP9843'...                          No
    Probing for `ON CAT6095/CAT34TS02'...                       No
    Probing for `ON CAT34TS02C'...                              No
    Probing for `ON CAT34TS04'...                               No
    Probing for `Atmel AT30TS00'...                             No
    Probing for `Giantec GT30TS00'...                           No
    Client found at address 0x52
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    Client found at address 0x53
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 Yes
        (confidence 8, not a hardware monitoring chip)
    
    Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-10)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-11)
    Do you want to scan it? (yes/NO/selectively): YES
    
    Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-12)
    Do you want to scan it? (yes/NO/selectively): YES
    
    
    Now follows a summary of the probes I have just done.
    Just press ENTER to continue:  
    
    Driver `nct6775':
      * ISA bus, address 0xa20
        Chip `Nuvoton NCT6795D Super IO Sensors' (confidence: 9)
    
    Driver `k10temp':
      * Chip `AMD Family 17h thermal sensors' (confidence: 9)
    
    Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):  
    Unloading i2c-dev... OK
    Unloading cpuid... OK
    
    
    After that my /etc/sysconfig/lm_sensors look's like this:

    Code:
    # Generated by sensors-detect on Fri Aug  3 00:18:00 2018
    ## Path: Hardware/Sensors
    ## Description:         Defines the modules to used
    ## Type:                string
    ## ServiceRestart:      lm_sensors
    ## Default:             ""
    #
    # This file is sourced by /etc/init.d/lm_sensors and defines the modules to
    # be loaded/unloaded.
    #
    # The format of this file is a shell script that simply defines variables:
    # HWMON_MODULES for hardware monitoring driver modules, and optionally
    # BUS_MODULES for any required bus driver module (for example for I2C or SPI).
    
    HWMON_MODULES="k10temp nct6775"
    
    When I restarts lm_sensors I've got this:

    Code:
    systemctl status lm_sensors    
     lm_sensors.service - Initialize hardware monitoring sensors
       Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled; vendor preset: disabled)
       Active: active (exited) since Fri 2018-08-03 00:18:00 MSK; 4min 39s ago
      Process: 9803 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
      Process: 9789 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
     Main PID: 9803 (code=exited, status=0/SUCCESS)
    
    авг 03 00:18:00 BlackDragonCAVE systemd[1]: Starting Initialize hardware monitoring sensors...
    авг 03 00:18:00 BlackDragonCAVE systemd[1]: Started Initialize hardware monitoring sensors.     
    
    Modprobed them manualy and I'v got:

    Code:
    # sudo modprobe k10temp
    # sudo modprobe nct6775
    modprobe: ERROR: could not insert 'nct6775': No such device
    # sudo modprobe nct6775 force_id=0xa20
    modprobe: ERROR: could not insert 'nct6775': No such device                                    
    
    I have inserted this in grub:
    Code:
    GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
    - does not worked.

    lsmod says only about k10temp, but no nct6775. But I have both of them in System:

    Code:
    # sudo find /lib/modules/4.12.14-lp150.12.7-default -name k10temp*  
    /lib/modules/4.12.14-lp150.12.7-default/kernel/drivers/hwmon/k10temp.ko
    # sudo find /lib/modules/4.12.14-lp150.12.7-default -name nct6775*
    /lib/modules/4.12.14-lp150.12.7-default/kernel/drivers/hwmon/nct6775.ko
    


    And, finaly, this is my sensors output:

    Code:
    sensors
    amdgpu-pci-2900
    Adapter: PCI adapter
    fan1:        1244 RPM
    temp1:        +40.0°C  (crit =  +0.0°C, hyst =  +0.0°C)
    


    Tel me, what else can I do?

    P.S.: sorry for eng level

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,840
    Blog Entries
    15

    Default Re: AMD x370 sensors not working

    Hi
    Have you seen this thread from 2016?
    https://forums.opensuse.org/showthre...Adapter+mssing
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Have you seen this thread from 2016?
    https://forums.opensuse.org/showthre...Adapter+mssing
    Hello! Sorry for late reply.

    I have read this topic and, as you see in my first post, did the same things. But, unfortunatly, it does not helps me. Do you have another suggestions?

  4. #4

    Default Re: AMD x370 sensors not working

    Sorry for double posting, but can anybody helps me please?

  5. #5

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by Kilvador View Post
    Sorry for double posting, but can anybody helps me please?
    Hello,

    i've got a new Asus C246 pro motherboard and the same issue:

    root@proxmox:~# sudo modprobe -v nct6775
    insmod /lib/modules/4.15.18-10-pve/kernel/drivers/hwmon/nct6775.ko
    modprobe: ERROR: could not insert 'nct6775': No such device


    Clearly on the board i can see the chip nct6796D... I have no idea whats going wrong here.

    @Kilvador did you find a solution?

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,840
    Blog Entries
    15

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by totototototo View Post
    Hello,

    i've got a new Asus C246 pro motherboard and the same issue:

    root@proxmox:~# sudo modprobe -v nct6775
    insmod /lib/modules/4.15.18-10-pve/kernel/drivers/hwmon/nct6775.ko
    modprobe: ERROR: could not insert 'nct6775': No such device


    Clearly on the board i can see the chip nct6796D... I have no idea whats going wrong here.

    @Kilvador did you find a solution?
    Hi
    That chip is not supported in 4.15.18.... it is in 4.20.6 for Tumbleweed...
    https://elixir.bootlin.com/linux/v4....wmon/nct6775.c
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by totototototo View Post
    Hello,

    i've got a new Asus C246 pro motherboard and the same issue:

    root@proxmox:~# sudo modprobe -v nct6775
    insmod /lib/modules/4.15.18-10-pve/kernel/drivers/hwmon/nct6775.ko
    modprobe: ERROR: could not insert 'nct6775': No such device


    Clearly on the board i can see the chip nct6796D... I have no idea whats going wrong here.

    @Kilvador did you find a solution?
    Hello!

    I'l try new version by the last post in this tread and reply after that.

  8. #8

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by malcolmlewis View Post
    HiThat chip is not supported in 4.15.18.... it is in 4.20.6 for Tumbleweed...
    Uhm ok. I'm using proxmox which is based on Debian 9, I only stumbled upon this similar issue here.
    I have no idea if i can upgrade the kernel without breaking the ve-capabilities... Maybe i'll just wait until proxmox updates to this kernel.

    Anyway thank you for your help!

  9. #9

    Default Re: AMD x370 sensors not working

    Hello to all!

    I've found solution!


    Code:
    sudo modprobe nct6775 force_id=0xd120
    Before:

    Code:
    # sensors
    amdgpu-pci-2900
    Adapter: PCI adapter
    fan1:        1251 RPM
    temp1:        +31.0°C  (crit =  +0.0°C, hyst =  +0.0°C)
    


    After:

    Code:
    # sudo modprobe nct6775 force_id=0xd120
    # sensors
    amdgpu-pci-2900
    Adapter: PCI adapter
    fan1:        1250 RPM
    temp1:        +31.0°C  (crit =  +0.0°C, hyst =  +0.0°C)
    
    nct6793-isa-0a20
    Adapter: ISA adapter
    in0:                    +1.41 V  (min =  +0.00 V, max =  +1.74 V)
    in1:                    +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in2:                    +3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in3:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in4:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in5:                    +0.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in6:                    +0.80 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in7:                    +3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in8:                    +3.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in9:                    +1.84 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in10:                   +0.00 V  (min =  +0.00 V, max =  +0.00 V)
    in11:                   +0.52 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in12:                   +0.90 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in13:                   +0.59 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    in14:                   +1.55 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
    fan1:                     0 RPM  (min =    0 RPM)
    fan2:                   801 RPM  (min =    0 RPM)
    fan3:                   976 RPM  (min =    0 RPM)
    fan4:                   738 RPM  (min =    0 RPM)
    fan5:                   984 RPM  (min =    0 RPM)
    SYSTIN:                 +37.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode
    CPUTIN:                 +38.0°C  (high = +113.0°C, hyst = +88.0°C)  sensor = thermistor
    AUXTIN0:                +37.5°C  (high = +113.0°C, hyst = +88.0°C)  sensor = thermistor
    AUXTIN1:               -128.0°C    sensor = thermistor
    AUXTIN2:                +56.0°C    sensor = thermistor
    AUXTIN3:                 -4.0°C    sensor = thermistor
    SMBUSMASTER 0:          +49.5°C   
    PCH_CHIP_CPU_MAX_TEMP:   +0.0°C   
    PCH_CHIP_TEMP:           +0.0°C   
    PCH_CPU_TEMP:            +0.0°C   
    intrusion0:            ALARM
    intrusion1:            ALARM
    beep_enable:           disabled

  10. #10
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,840
    Blog Entries
    15

    Default Re: AMD x370 sensors not working

    Quote Originally Posted by Kilvador View Post
    Hello to all!

    I've found solution!


    Code:
    sudo modprobe nct6775 force_id=0xd120
    Hi
    Good news just add that to a modprobe conf file and should be good to go
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •