데스크미니 X300 온도 센서 드라이버 문제 (ft. M SHELL for TCRP)

# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

# sensors-detect

# sensors-detect version 3.6.0
# Board: ASRock X300M-STX
# Kernel: 4.4.180+ x86_64
# Processor: AMD Ryzen 5 5600G with Radeon Graphics (25/80/0)

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...                             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): 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 NCT6793D 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-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
modprobe: FATAL: Module i2c-piix4 not found.
Failed to load module i2c-piix4.

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

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

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
Copy prog/init/lm_sensors.service to /usr/lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.

# systemctl status cpufreq-userspace-scaler.service

 cpufreq-userspace-scaler.service - ACPI cpufreq userspace scaler
   Loaded: loaded (/etc/systemd/system/cpufreq-userspace-scaler.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2023-05-18 04:54:46 KST; 17min ago
  Process: 29066 ExecStart=/usr/sbin/scaler.sh (code=exited, status=1/FAILURE)
 Main PID: 29066 (code=exited, status=1/FAILURE)

May 18 04:54:46 X300_DS923 systemd[1]: Started ACPI cpufreq userspace scaler.
May 18 04:54:46 X300_DS923 systemd[1]: Starting ACPI cpufreq userspace scaler...
May 18 04:54:46 X300_DS923 scaler.sh[29066]: cat: /sys/bus/platform/devices/coretemp.0/hwmon/hwmon0/temp1_input: No such file or directory
May 18 04:54:46 X300_DS923 systemd[1]: cpufreq-userspace-scaler.service: main process exited, code=exited, status=1/FAILURE
May 18 04:54:46 X300_DS923 systemd[1]: Unit cpufreq-userspace-scaler.service entered failed state.
May 18 04:54:46 X300_DS923 systemd[1]: cpufreq-userspace-scaler.service failed.