You are not logged in.
Pages: 1
lm_sensors doesn't detect Ryzen's temperature sensors. I installed the it87-dkms-git package from the aur but it didn't fix the state of lm. Does anyone have any suggestions for getting these temperatures reported at the moment? For reference I have the MSI x370 carbon motherboard, and a 1700.
Offline
Just to confirm, you actually loaded the module too?
Offline
Yes, it is loaded under /etc/modules-load/*
Offline
I googled around a bit, and the it87 module is apparently not for you. Your board uses a different family of chips, managed by this project here: https://github.com/groeck/nct6775
This nct6775 module is in the normal kernel. It does not support your particular chip. Check out this thread here for what's going on: https://github.com/groeck/nct6775/issues/49
There's posts somewhere in that thread that describe how to force the nct6775 module to try to interact with that particular chip you (probably) have on your board and things should then work.
Offline
I googled around a bit, and the it87 module is apparently not for you. Your board uses a different family of chips, managed by this project here: https://github.com/groeck/nct6775
This nct6775 module is in the normal kernel. It does not support your particular chip. Check out this thread here for what's going on: https://github.com/groeck/nct6775/issues/49
There's posts somewhere in that thread that describe how to force the nct6775 module to try to interact with that particular chip you (probably) have on your board and things should then work.
Ok, thank you. I'll try it and write back!
Edit: Still no luck. Even with the manual ID inputs, I still get the message:
"Sorry, no sensors were detected."
Last edited by thelongdivider (2017-04-21 19:32:06)
Offline
Did you try running "sudo sensors-detect" after loading the module? (I don't really understand what it does, but maybe it's needed.)
Last edited by Ropid (2017-04-22 02:44:02)
Offline
https://aur.archlinux.org/packages/nct677x-git/ will install the git module in the correct location to use it over the older version in the kernel package. Have you built it and rebooted and still met with failure to detect?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Still no sensors detected with any of these suggestions.
Offline
Then either that is not the correct sensor for your hardware or it is simply not yet supported.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I've been able to get Ryzen temperature readings through lm_sensors by manually compiling and installing the it87 module from git. This is what works for me (YMMV):
$ sudo pacman -S linux-headers # you might have this already
$ git clone git://github.com/groeck/it87.git
$ cd it87
## Edit the Makefile and change KERNEL_BUILD to point towards ${KERNEL_MODULES}/build instead of /usr/src/linux-headers-${TARGET}. It should already be there but commented out by default.
$ make
$ sudo cp /proc/kallsyms /boot/System.map-`uname -r`;
$ sudo make install
$ sudo modprobe it87
Note that you have to repeat this process every time there's a kernel update, so it's most definitely not an optimal solution.
Offline
Great, but it87 is not the driver for nuvoton super IOs.
OP, find this damn nuvoton chip on the motherboard and see what's the exact model number printed on it (likely NCT6xxxsomething) so you know what of the stuff you find on the 'net applies to you and what doesn't.
Also, rmmod all stock and custom-compiled modules you tried, modprobe them again and then run dmesg and paste any messages from these drivers that you will find in the last few lines of dmesg. Maybe it's just some stupid ACPI conflict.
And BTW, did AMD kill the k10temp sensor in Ryzen?
Offline
Great, but it87 is not the driver for nuvoton super IOs.
OP, find this damn nuvoton chip on the motherboard and see what's the exact model number printed on it (likely NCT6xxxsomething) so you know what of the stuff you find on the 'net applies to you and what doesn't.
Also, rmmod all stock and custom-compiled modules you tried, modprobe them again and then run dmesg and paste any messages from these drivers that you will find in the last few lines of dmesg. Maybe it's just some stupid ACPI conflict.
And BTW, did AMD kill the k10temp sensor in Ryzen?
The chip, according to the MSI spreadsheet, is the Nuvoton NCT6795D-M.
Offline
The chip, according to the MSI spreadsheet, is the Nuvoton NCT6795D-M.
Did you try what the people in that nct6775 github issue talk about? I mean this here, with the nct677x-git package installed:
I force ID like nct 6793D
modprobe nct6775 force_id=0xd120
Last edited by Ropid (2017-04-26 23:20:07)
Offline
thelongdivider wrote:The chip, according to the MSI spreadsheet, is the Nuvoton NCT6795D-M.
Did you try what the people in that nct6775 github issue talk about? I mean this here, with the nct677x-git package installed:
I force ID like nct 6793D
modprobe nct6775 force_id=0xd120
Yes. I tried that immediately. I will likely just wait until 4.11 to see if the issue is fixed.
Offline
Why wait? Rc8 is good enough... no new features. Try Linux-mainline in the aur. I doubt it will help though...
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Why wait? Rc8 is good enough... no new features. Try Linux-mainline in the aur. I doubt it will help though...
Because it isn't necessary enough for me to install all the nvidia-DKMS drivers, bootloader, etc. Just something that is easily read in UEFI and impossible to detect in OS, regardless of the fans spinning up when it is put under load.
Offline
Pages: 1