PWM sensors for RAMPAGE V EXTREME


2 posts in this topic Last Reply

Recommended Posts

Currently controlling fan speed vis BIOS.

Trying to configure Dynamix Auto Fan Control.

I tried setting up fan sensors for my unRAID box running on a Rampage V Extreme. 

Followed these instructions: https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing

However no luck. 

 

Sensors only show core temp.

Quote

 sensors
coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +46.0°C  (high = +90.0°C, crit = +100.0°C)
Core 0:       +37.0°C  (high = +90.0°C, crit = +100.0°C)
Core 1:       +36.0°C  (high = +90.0°C, crit = +100.0°C)
Core 2:       +42.0°C  (high = +90.0°C, crit = +100.0°C)
Core 3:       +37.0°C  (high = +90.0°C, crit = +100.0°C)
Core 4:       +38.0°C  (high = +90.0°C, crit = +100.0°C)
Core 5:       +36.0°C  (high = +90.0°C, crit = +100.0°C)

 

It found these two drivers using sensors-detect.

Quote

#----cut here----
# Chip drivers
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s
#----cut here----

 

root@Tower:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +46.0°C  (high = +90.0°C, crit = +100.0°C)
Core 0:       +37.0°C  (high = +90.0°C, crit = +100.0°C)
Core 1:       +36.0°C  (high = +90.0°C, crit = +100.0°C)
Core 2:       +42.0°C  (high = +90.0°C, crit = +100.0°C)
Core 3:       +37.0°C  (high = +90.0°C, crit = +100.0°C)
Core 4:       +38.0°C  (high = +90.0°C, crit = +100.0°C)
Core 5:       +36.0°C  (high = +90.0°C, crit = +100.0°C)

root@Tower:~# sensors-detect
# sensors-detect version 3.6.0
# System: ASUS All Series
# Board: ASUSTeK COMPUTER INC. RAMPAGE V EXTREME
# Kernel: 4.19.107-Unraid x86_64
# Processor: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (6/63/2)

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): YES
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...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal 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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6791D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
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): YES
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): YES
Using driver `i2c-i801' for device 0000:00:1f.3: Wellsburg (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 0580 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No


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

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6791D Super IO Sensors' (confidence: 9)

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

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

 

Obviously the driver does not exist or is not being detected, Is there an alternative?

Edited by exist2resist
Link to post

I found this.... https://github.com/lm-sensors/lm-sensors/issues/10

 

How do I go about booting my system with; acpi_enfore_resources=lax ?

Do I just paste the line in go file?

 

Resolved;

needed to edit /boot/syslinux/syslinux.cfg file

Added acpi enforce resources to the first label

Here is what it looks like. I can now read my PWM fans.
 

cat /boot/syslinux/syslinux.cfg 
default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label Unraid OS
  menu default
  kernel /bzimage
  append acpi_enforce_resources=lax initrd=/bzroot
label Unraid OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label Unraid OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Unraid OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

 

Edited by exist2resist
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.