Yes success hwinfo now shows quad channel.
Temperature average has increased by 10 degs C so I suspect that we should have greater throughput. I will update after a few days.
Incidentally I have approached ASUS support who confirm there is no PSS (or equivalent) in that BIOS and want to know why I want to turn it off..........
jsm

Tell them you are NOT a gamer. Tell them you do distributed processing on citizen science projects and your computer runs at 100% 24/7 and you have no wish for power savings.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Yes success hwinfo now shows quad channel.
Temperature average has increased by 10 degs C so I suspect that we should have greater throughput. I will update after a few days.
Incidentally I have approached ASUS support who confirm there is no PSS (or equivalent) in that BIOS and want to know why I want to turn it off..........
jsm

I suspect there is a "cool 'n quiet" in there then.

Tom

There is PSS or 'Cool 'n Quiet' in the AMD AGESA code. ALL AMD motherboards start with the AGESA codebase. Whether the motherboard BIOS exposes that option is entirely up to the motherboard BIOS developers. It may be it is not on his motherboard.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Just installed BIOS 1701. Still no PSS showing in advanced cpu config. - ASUS support notified
Temperature at Tctl jumped to average over 90 which I think is high.
performance now about 1.5 x either of the 1800X m/cs still NBG.

Summarise

32gb, 3000Mhz quad channel mode
Core prio running with disassociator ticked and no Ryzen master
Lasso running
Boinc at 40% cpus
no other tasks apart from housekeeping.

I wonder if I should dual boot with Ubuntu 18.04? Does this have any impact overall to suggest I should not go down that route?
Does Ubuntu BOINC software work without tweaking? I ask because I had an old m/c running Ubuntu and BOINC compiled but never ran ):
JSM

I'm not a fan of dual booting because both OS bootloaders tend to step on their opposite OS'. I would suggest just loading Ubuntu 18.04 LTS to its own separate drive. You can pick up a 128GB SSD for $25-30 and is plenty enough in size for the OS, apps and BOINC. Then use your BIOS to select which OS to boot on the BIOS splash screen.

Yes, if you don't want to do any tweaking then just install the Ubuntu repository version of BOINC and BOINC will send you the default Linux apps.

But that is not the best method in my opinion. The repository versions of BOINC install it in two hidden sub-directories with exclusive permissions and group ownership that you don't belong to. That makes editing or doing any file management in the BOINC folder very difficult for Linux newbies.

I think the easiest way to install BOINC on Linux is to use TBar's All-in-One package available from Crunchers Anonymous. The benefit is that the BOINC folder is unpacked onto your Desktop or wherever you want in your /home directory which you own and have permissions to to do what you want with the folder or any file. That makes editing files like cc_config, app_info or app_config easy.

It does however need you to install a few missing dependencies via a couple of sudo apt install statements and checking the five main executable files to be sure they have their execute status set. The version installed in the main BOINC folder is 7.8.3. However the older 7.4.44 version is also included in a zip file in the /docs sub-directory in the BOINC folder. That version has been modified to allow 3000 tasks on board the client instead of the default 1000 tasks. That allows one to bunker or reschedule tasks to make it through Tuesday maintenance outages.

The installation includes all the necessary MB and AP applications for both cpu and gpu tasks with pre-configured app_info.xml file. The MB gpu app is also the "special" CUDA9 app for Nvidia cards which is 10X faster than the stock SoG application. However, I notice you do not have any gpu configured for your TR host so don't know whether that appeals to you or is needed.

The All-in-One package is here. http://www.arkayn.us/lunatics/BOINC.7z

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

The All-in-One package is here. http://www.arkayn.us/lunatics/BOINC.7z

+1

---

A proud member of the OFA (Old Farts Association).

Thank you both for your advice but I have chosen in the first instance to mirror the win10 setup and standard software as a direct comparison before tweaking either hardware or software. Thus I have dual booted Ubuntu 18.04 so that it is operating exactly on the same hardware with the BIOS unchanged. In fact it is actually sharing half of the ssd that has win10 booting.
After the long down time yesterday and today with Boinc/Seti it has at last got going and I have started by allowing 60 threads before dialing back if that is likely to help throughput as for windows. We will see just how the average of 18000 for this m/c changes.

What do you use to monitor temps etc please? HWINFO is so comprehensive that it is difficult to find any equivalent program. I obviously want to keep an eye on the core temps.
jsm

First you need to install the lm-sensors package. That should allow you to look at the default AMD Ryzen cpu sensor called k10temp. It should report the temps for each die. You won't be able to view individual core temps of course being AMD.

The lm-sensors package has a utility called sensors-detect that will probe your hardware looking for known temp monitoring hardware but will find nothing normally. The are a couple of choices for Ryzen and Threadripper sensor monitoring drivers. Depending on your motherboard SIO chip determines which kernel mode driver you need to install. There is the well supported nct6775 driver for nct SIO chips like on my Asrock motherboard and the ITE8665 SIO chips on all the ASUS motherboards. The ITE8665 is supported by the it87 driver or if you have the correct BIOS in your ASUS board by the asus-wmi-sensors driver. That is most full featured sensor driver so far but you need to have a WMI enabled BIOS.

So first question I would ask is what is your brand of motherboard and what is the BIOS level. That would point me in the direction of telling you what and how to install a sensor driver.

All sensor drivers are kernel mode so need to be loaded via a modprobe statement. The basic k10temp driver just shows you the Tdie and Tctrl temps for the die depending on the version of k10temp. Kernels less than 4.15 only report the Tctrl value so you have to mentally subtract the -20 or -27 artificial AMD offset to determine the actual Tdie real temp. Kernels at or above 4.18 get a k10temp driver that reports both the Tdie and Tctrl temps when probed so there is no mental gymnastics involved.

The drivers for the SIO chips can report all the normal Windows sensors values like fan speeds, temps and voltages. Depending on what is exported by the motherboard. Can be almost the same values as in Windows or only 1 or 2 fan speeds and 1 or 2 temps. The asus-wmi-sensor driver reports everything that HwInfo64 does in Windows since it uses the same WMI mechanism that Windows does.

The it87 driver is available on github. Same with the k10temp driver though there is a version shipped with Ubuntu now. The it87 driver along with the nct6775 driver was pulled by the original developer from github but others cloned the repository so they are available. The asus-wmi-sensors driver also is available from github and is actively being developed. I believe the nct6775 is bundled now with Ubuntu too. Look in your
/lib/modules/{kernel level}/kernel/drivers/hwmon directory for all your installed drivers that are available to you for modprobing.

I have it running on my ASUS C7H motherboards and is very nice. This is what it reports. Also you can see the k10temp output too.

keith@Serenity:~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +75.8°C  (high = +70.0°C)
Tctl:         +85.8°C  

asuswmisensors-isa-0000
Adapter: ISA adapter
CPU Core Voltage:         +1.34 V  
CPU SOC Voltage:          +1.11 V  
DRAM Voltage:             +1.40 V  
VDDP Voltage:             +0.67 V  
1.8V PLL Voltage:         +1.81 V  
+12V Voltage:            +11.83 V  
+5V Voltage:              +4.88 V  
3VSB Voltage:             +3.36 V  
VBAT Voltage:             +3.27 V  
AVCC3 Voltage:            +3.36 V  
SB 1.05V Voltage:         +1.11 V  
CPU Core Voltage:         +1.35 V  
CPU SOC Voltage:          +1.13 V  
DRAM Voltage:             +1.41 V  
CPU Fan:                 1739 RPM
Chassis Fan 1:              0 RPM
Chassis Fan 2:           1541 RPM
Chassis Fan 3:              0 RPM
HAMP Fan:                1418 RPM
Water Pump:                 0 RPM
CPU OPT:                 5606 RPM
Water Flow:                 0 RPM
AIO Pump:                2812 RPM
CPU Temperature:          +75.0°C  
CPU Socket Temperature:   +49.0°C  
Motherboard Temperature:  +29.0°C  
Chipset Temperature:      +46.0°C  
Tsensor 1 Temperature:    +36.0°C  
CPU VRM Temperature:      +55.0°C  
Water In:                +216.0°C  
Water Out:               +216.0°C  
CPU VRM Output Current:  +101.00 A  

asus-isa-0000
Adapter: ISA adapter
cpu_fan:        0 RPM

keith@Serenity:~$ 

My Asrock motherboard with my TR has to use the nct6775 driver so does not report as much as the asus-wmi-sensors driver but more than the it87 driver. It all depends on the motherboard SIO chip. This is what my TR reports.

keith@Numbskull:~$ sensors
k10temp-pci-00cb
Adapter: PCI adapter
Tdie:         +67.0°C  (high = +70.0°C)
Tctl:         +94.0°C  

nct6779-isa-0290
Adapter: ISA adapter
Vcore:                  +1.39 V  (min =  +0.00 V, max =  +3.49 V)
in1:                    +1.08 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                   +3.31 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                  +3.31 V  (min =  +2.98 V, max =  +3.63 V)
in4:                    +1.82 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +1.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +1.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                   +3.44 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                   +3.26 V  (min =  +2.70 V, max =  +3.63 V)
in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in10:                   +0.74 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                   +0.73 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                   +0.92 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +0.82 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                  1906 RPM  (min =    0 RPM)
fan2:                  2368 RPM  (min =    0 RPM)
fan3:                  1953 RPM  (min =    0 RPM)
fan4:                  1767 RPM  (min =    0 RPM)
fan5:                   888 RPM  (min =    0 RPM)
SYSTIN:                 +35.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:                 +40.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                 +4.0°C    sensor = thermistor
AUXTIN1:                +40.0°C    sensor = thermistor
AUXTIN2:                +41.0°C    sensor = thermistor
AUXTIN3:                +36.0°C    sensor = thermistor
SMBUSMASTER 0:          +94.0°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

iwlwifi-virtual-0
Adapter: Virtual device
temp1:            N/A  

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +67.0°C  (high = +70.0°C)
Tctl:         +94.0°C  

keith@Numbskull:~$ 

Then when you get finished with installing a sensor driver, I like to make it readily accessible and viewable in a nice desktop monitor program like GkrellM or psensors.
sudo apt install gkrellm or sudo apt install psensors. That puts the information on the desktop much like HwInfo64.

Let us know your hardware so I can assist in installing the correct drivers and apps.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

A lot of info there! Pity there is no immediate live monitor like HWINFO (:

The 2990wx is sitting on an ASUS Zenith Rog Extreme motherboard with latest Bios 1710. The 32mb memory is 4 x 8 and gives quad channel. The O/S's are on an M2 SSD with a 1TB ordinary disk and dvd as backup. The case is an EATX with plenty of external connections and cooling is high end water cooler with a huge radiator. If you need specific model attributes etc I can dig them out from Cyberpower UK who built it for me. I think they are or are a member of Republic of Gamers as it is their logo that comes up when yo oot.
jsm

A lot of info there! Pity there is no immediate live monitor like HWINFO (:

The 2990wx is sitting on an ASUS Zenith Rog Extreme motherboard with latest Bios 1710. The 32mb memory is 4 x 8 and gives quad channel. The O/S's are on an M2 SSD with a 1TB ordinary disk and dvd as backup. The case is an EATX with plenty of external connections and cooling is high end water cooler with a huge radiator. If you need specific model attributes etc I can dig them out from Cyberpower UK who built it for me. I think they are or are a member of Republic of Gamers as it is their logo that comes up when yo oot.
jsm

From what I understand from the posts in the OCN Threadripper thread, the 1710 BIOS has the proper WMI BIOS implementation now after they updated elmor's kludged 1610 partial WMI BIOS implementation. You should be a candidate then for the asus-wmi-sensors driver.
You can download it here. https://github.com/electrified/asus-wmi-sensors
Follow the instructions.
1. Install lm-sensors
2. Clone or download the package.
3. Navigate to the Download directory if you just got the zip package and unpack it or navigate to the asus-wmi-sensors folder that the git clone created.

sudo make dkms
sudo modprobe asus-wmi-sensors

4. Run sensors in Terminal

If successful you should see your sensor output in Terminal.
Decide which desktop GUI app you want to use to monitor readings on the desktop, GkrellM or psensors.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Almost!
All sorts of things missing from the default installation. Needed to install make, gcc a couple of libraries and generic headers.
The driver was downloaded and extracted satisfactorily but when navigated to the directory containing the files and
sudo make dkms
there is always a failure no matter what I do as follows:-

threadripper:~/Downloads/asus-wmi-sensors-master> sudo make dkms
make: dkms: Command not found
Makefile:91: recipe for target 'dkms' failed
make: *** [dkms] Error 127


If you just type sudo make then files are created but presumably not the right ones!

My Linux is a bit rusty but not completely forgotten as I founded the first ISP on the Isle of Man using a cluster of large DEC Alphas and DEC TRU-UNIX but I can't see what is wrong. Perhaps a bit more direction will help..............
jsm

You did run it either with a sudo command or as root? Correct? DKMS is a root app so you need to run it as root. Is the dkms.conf file in your downloaded zip file or in the asus-wmi-sensors folder that the git clone created?

You don't have to run the make dkms if it is not working. You can just run the sudo make and then the sudo modprobe asus-wmi-sensors to install the driver. The dkms file just installs the driver into the dkms list so that it survives installation of new kernels. If you don't have the dkms installation, you will just have to reinstall the driver manually when the kernel updates.

I looked at the dkms file and it looks like it was meant to be installed from the git clone. Is that how you got the github driver or did you just download the zip file and unpack it. If you did the zip file, I can see why the dkms file does not work because the package name is PACKAGE_NAME="asus-wmi-sensors-dkms-git" and for a zip file download would be just PACKAGE_NAME="asus-wmi-sensors-dkms"

[Edit] I was thinking maybe you already ran the make dkms once already and didn't notice any error and forgot about it. If you run it a second time, then you would get a -91 error because the first instance of the make already made the dkms directory and it fails because it can't create it when it is already there. If you do a sudo dkms status does it print out a line asus-wmi-sensors, unknown, 4.15.0-44-generic, x86_64: installed for example along with the dkms line for the nvidia driver?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

yes I downloaded so it was a zip extracted. I nano edited the git off the package name but got same error so removed the ....unknown directory again and just did the make and the modprobe with this result:

threadripper:~/Downloads/asus-wmi-sensors-master> sudo make
Building modules, stage 2.
MODPOST 1 modules
threadripper:~/Downloads/asus-wmi-sensors-master> sudo modprobe asus-wmi-sensors
modprobe: FATAL: Module asus-wmi-sensors not found in directory /lib/modules/4.18.0-15-generic



I am sure I will get there eventually!
jsm

I'm not sure why you are having so many issues. Could just do the make and the modprobe from root terminal.

root@Serenity:/home/keith/Downloads/Utils/asus-wmi-sensors-master# ls
asus-wmi-sensors.c      asus-wmi-sensors.mod.o  LICENSE        Module.symvers
asus-wmi-sensors.ko     asus-wmi-sensors.o      Makefile       README.md
asus-wmi-sensors.mod.c  dkms.conf               modules.order  VERSION
root@Serenity:/home/keith/Downloads/Utils/asus-wmi-sensors-master# make clean
  CLEAN   /home/keith/Downloads/Utils/asus-wmi-sensors-master/.tmp_versions
  CLEAN   /home/keith/Downloads/Utils/asus-wmi-sensors-master/Module.symvers
root@Serenity:/home/keith/Downloads/Utils/asus-wmi-sensors-master# make
  CC [M]  /home/keith/Downloads/Utils/asus-wmi-sensors-master/asus-wmi-sensors.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/keith/Downloads/Utils/asus-wmi-sensors-master/asus-wmi-sensors.mod.o
  LD [M]  /home/keith/Downloads/Utils/asus-wmi-sensors-master/asus-wmi-sensors.ko
root@Serenity:/home/keith/Downloads/Utils/asus-wmi-sensors-master# modprobe asus-wmi-sensors
root@Serenity:/home/keith/Downloads/Utils/asus-wmi-sensors-master# lsmod
asus_wmi_sensors       16384  0
wmi                    24576  4 asus_wmi_sensors,asus_wmi,wmi_bmof,mxm_wmi

Have you tried to see if the driver is installed with an lsmod? Have your tried running sensors yet? Which reminds me . . . you did first install lm-sensors package per the instructions, correct?

[Edit] Unpack the zip file again and don't make any changes to the dkms.conf file. Just run the make command without the dkms. I am thinking even though you aren't using the dkms file, it is possible the makefile refers to it for the directory for installation.
[Edit 2] Yep, the makefile uses the dkms.conf file for the installation directory. So don't edit anything and just run these commands from root terminal.

make
make install
modprobe asus-wmi-sensors

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Sorry for being a pest - and yes I did install lm-sensors before anything else.

Same error. Here is the whole terminal output following yours including my mistakes.

root@threadripper:/home/jsm/Downloads# cd asus-wmi-sensors-master/
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master# ls
asus-wmi-sensors.c asus-wmi-sensors.mod.o LICENSE Module.symvers
asus-wmi-sensors.ko asus-wmi-sensors.o Makefile README.md
asus-wmi-sensors.mod.c dkms.conf modules.order VERSION
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master# make clean
CLEAN /home/jsm/Downloads/asus-wmi-sensors-master/.tmp_versions
CLEAN /home/jsm/Downloads/asus-wmi-sensors-master/Module.symvers
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master# cd ..
root@threadripper:/home/jsm/Downloads# ls
asus-wmi-sensors-master asus-wmi-sensors-master.zip
root@threadripper:/home/jsm/Downloads# unzip asus-wmi-sensors-master.zip
Archive: asus-wmi-sensors-master.zip
fe0ac602b943811f6e9d1a77c93014f1b160d788
replace asus-wmi-sensors-master/.gitignore? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
inflating: asus-wmi-sensors-master/.gitignore
replace asus-wmi-sensors-master/LICENSE? [y]es, [n]o, [A]ll, [N]one, [r]ename: a
error: invalid response [a]
replace asus-wmi-sensors-master/LICENSE? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
inflating: asus-wmi-sensors-master/LICENSE
inflating: asus-wmi-sensors-master/Makefile
inflating: asus-wmi-sensors-master/README.md
inflating: asus-wmi-sensors-master/asus-wmi-sensors.c
inflating: asus-wmi-sensors-master/dkms.conf
root@threadripper:/home/jsm/Downloads# make
make: *** No targets specified and no makefile found. Stop.
root@threadripper:/home/jsm/Downloads# cd asus-wmi-sensors-master/
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master# make
CC [M] /home/jsm/Downloads/asus-wmi-sensors-master/asus-wmi-sensors.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/jsm/Downloads/asus-wmi-sensors-master/asus-wmi-sensors.mod.o
LD [M] /home/jsm/Downloads/asus-wmi-sensors-master/asus-wmi-sensors.ko
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master# modprobe asus-wmi-sensors
modprobe: FATAL: Module asus-wmi-sensors not found in directory /lib/modules/4.18.0-15-generic
root@threadripper:/home/jsm/Downloads/asus-wmi-sensors-master#
jsm

OK. It is building the drivers ok. I think you missed a step. After you make and see the output create the .ko driver file, you need to do a

make install

. That is what actually writes the driver into the kernel modules directory. That is why you are currently getting the modprobe: FATAL: Module asus-wmi-sensors not found in directory /lib/modules/4.18.0-15-generic statement. Then once the driver is in the /lib/modules/4.18.0-15-generic directory, you can then issue the modprobe asus-wmi-sensors command.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

If it still does not install, then you may need to regenerate the module dependency list by running as root:

depmod -ae

Then try the modprobe again.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Success! Sorry could not report before due Seti being down so much. However not without problems as something affected BOINC which stopped working altogether. I had to uninstall (remove) the application and reinstall before it would restart. The info given is something I will have to analyse a bit closer as it reports all the water temoeratures as 216 C which is somewhat disconcerting..............
On another front we now have an answer to the PSS saga as follows from Asus support with my answer.



Well I think this is a mistake. PSS is a function which SHOULD be controlled by the customer and not at the whim of a BIOS developer when it is in the AMD firmware.

jsm


On 07/03/2019 00:38, servicecenter_am@asus.com wrote:

> Thank you for contacting ASUS product support. My name is Jhed C. and it is my pleasure to continue where you left off.
>
> I appreciate your patience and for giving us time to come up with a resolution for your case. After collaborating with our engineers, we are now able to provide you with a recommendation on how to address your concern.
>
> HQ said : PSS is default enabled, and it is a hidden item, user can't adjust it.
>
> And it is no need to adjust, this enabled item will auto help adjust the efficiency of CPU.
> Do let us know if further assistance is needed. Thank you for choosing ASUS. Your case number is:N190323303.
>
> Do you have feedback that you would like to share about your experience with our CEO? We’d love to hear about it! Share your feedback here: Contact our CEO's Office
>
> Regards,
> Jhed C.
>
> ASUS Product Support
>
> http://www.asus.com/us/support/
>

Hi and good going that you got the new asus-wmi-sensor driver working. If you don't have any temp sensor plugged into one of the motherboard headers, then the 216° C reading is correct for an unterminated input.

Do you have a 10K thermistor sensor plugged into one of the temp headers?

keith@Serenity:~$ sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan:        0 RPM

asuswmisensors-isa-0000
Adapter: ISA adapter
CPU Core Voltage:         +1.34 V  
CPU SOC Voltage:          +1.11 V  
DRAM Voltage:             +1.40 V  
VDDP Voltage:             +0.64 V  
1.8V PLL Voltage:         +1.81 V  
+12V Voltage:            +11.83 V  
+5V Voltage:              +4.88 V  
3VSB Voltage:             +3.36 V  
VBAT Voltage:             +3.27 V  
AVCC3 Voltage:            +3.36 V  
SB 1.05V Voltage:         +1.11 V  
CPU Core Voltage:         +1.35 V  
CPU SOC Voltage:          +1.13 V  
DRAM Voltage:             +1.42 V  
CPU Fan:                 1744 RPM
Chassis Fan 1:              0 RPM
Chassis Fan 2:           1551 RPM
Chassis Fan 3:              0 RPM
HAMP Fan:                1412 RPM
Water Pump:                 0 RPM
CPU OPT:                 5593 RPM
Water Flow:                 0 RPM
AIO Pump:                2820 RPM
CPU Temperature:          +76.0°C  
CPU Socket Temperature:   +49.0°C  
Motherboard Temperature:  +33.0°C  
Chipset Temperature:      +49.0°C  
Tsensor 1 Temperature:    +38.0°C  
CPU VRM Temperature:      +56.0°C  
Water In:                +216.0°C  
Water Out:               +216.0°C  
CPU VRM Output Current:  +90.00 A  

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +76.0°C  (high = +70.0°C)
Tctl:         +86.0°C  

keith@Serenity:~$ 

As you can see from my output, the Tsensor 1 temperature is working correctly. That is a 10K thermistor sensor https://www.amazon.com/gp/product/B00CMR38LC/ref=oh_aui_search_asin_title?ie=UTF8&psc=1taped to the endbell of my AIO radiator. For my custom loop rig, I have a G1/4 fitting that plugs into the spare port on the pump. https://www.amazon.com/gp/product/B00CMR3CC2/ref=oh_aui_search_asin_title?ie=UTF8&psc=1

I agree totally with your sentiments. I alone determine how I intend to use my computer and motherboard. For a BIOS developer to make a unilateral decision that prevents me from doing so is wrong.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Here is the output without analysis:-

ath10k_hwmon-pci-0300
Adapter: PCI adapter
temp1: +51.0°C

k10temp-pci-00db
Adapter: PCI adapter
Tdie: +58.4°C (high = +70.0°C)
Tctl: +85.4°C

k10temp-pci-00cb
Adapter: PCI adapter
Tdie: +60.9°C (high = +70.0°C)
Tctl: +87.9°C

nouveau-pci-4100
Adapter: PCI adapter
GPU core: +0.91 V (min = +0.80 V, max = +1.19 V)
temp1: +42.0°C (high = +95.0°C, hyst = +3.0°C)
(crit = +105.0°C, hyst = +5.0°C)
(emerg = +135.0°C, hyst = +5.0°C)

asuswmisensors-isa-0000
Adapter: ISA adapter
CPU Core Voltage: +1.18 V
CPU SOC Voltage: +1.09 V
DRAM AB Voltage: +1.35 V
DRAM CD Voltage: +1.37 V
1.8V PLL Voltage: +1.74 V
+12V Voltage: +11.90 V
+5V Voltage: +4.96 V
3VSB Voltage: +3.33 V
VBAT Voltage: +3.16 V
AVCC3 Voltage: +3.33 V
SB 1.05V Voltage: +1.05 V
CPU Core Voltage: +0.99 V
CPU SOC Voltage: +0.98 V
DRAM AB Voltage: +1.37 V
DRAM CD Voltage: +1.36 V
CPU Fan: 1236 RPM
Chassis Fan 1: 1126 RPM
Chassis Fan 2: 0 RPM
HAMP Fan: 1225 RPM
Water Pump 1: 4787 RPM
CPU OPT: 1243 RPM
Water Flow: 0 RPM
Waterblock Flow: 0 RPM
EXT Fan 1: 0 RPM
EXT Fan 2: 0 RPM
EXT Fan 3: 0 RPM
Cover Fan: 5773 RPM
CPU Temperature: +64.0°C
CPU Socket Temperature: +55.0°C
Motherboard Temperature: +29.0°C
Chipset Temperature: +54.0°C
Tsensor 1 Temperature: +216.0°C
CPU VRM Temperature: +78.0°C
Water In: +216.0°C
Water Out: +216.0°C
Waterblock In: +216.0°C
Waterblock Out: +216.0°C
EXT Tsensor 1: +0.0°C
EXT Tsensor 2: +0.0°C
EXT Tsensor 3: +0.0°C
Tsensor 2 Temperature: +216.0°C
DIMM.2 Tsensor 1 Temperature: +216.0°C
DIMM.2 Tsensor 2 Temperature: +216.0°C
CPU VRM Output Current: +175.00 A

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

k10temp-pci-00d3
Adapter: PCI adapter
Tdie: +60.5°C (high = +70.0°C)
Tctl: +87.5°C

k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +63.0°C (high = +70.0°C)
Tctl: +90.0°C
jsm

Can you confirm you don't have any temp sensors plugged into Tsensor 1, Tsensor 2, Water In and Water Out. Also can you confirm that you saw temp readouts on Dimm.2 Tsensor 1 and Dimm.2 Tsensor 2 in Windows before you switched to Linux. I am assuming those are the normal temperature readout chips in your RAM sticks.

I think you need to post your sensors output to the github issues page for the driver for the developer to look into for further debugging. He probably doesn't have any feedback from someone with the Zenith Extreme motherboard with the latest 1701 BIOS yet. He needs to update his readme about compatibility with the ZE board to show it is working now with the new BIOS.

Ask about the temp header outputs. The 216° C. looks normal to me for an unterminated and floating input. But the EXT Sensor1 - EXT Sensor 3 outputs have me baffled with their 0 °C readout. I can only guess that they use a different mechanism. I believe those would be from the optional external readout board for the ZE.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)