Too bad it wasn't an ASUS board. Those are well supported in the 5.17 kernel.
Though if I remember correctly, you should have a WMI kernel driver for your Gigabyte board also.
You should investigate that and see if I remember correctly.
Or if you don't have sensor support, there is still the zenpower3 out of band kernel driver. That will give you voltages, currents, amperages and clocks for your 5950X.
Keith - if there was a WMI driver for GigaByte sensors I'd be interested. I have 10 Gigabyte boards and have had to install the out-of-mainline it87 packages and roll my own sensors.conf file.
@Mike One of the kids have a GB b550 board if you can't find a WMI driver I can install HWinfo64 on it and create a sensors.conf file for you if your interested.
Too bad it wasn't an ASUS board. Those are well supported in the 5.17 kernel.
Though if I remember correctly, you should have a WMI kernel driver for your Gigabyte board also.
You should investigate that and see if I remember correctly.
Or if you don't have sensor support, there is still the zenpower3 out of band kernel driver. That will give you voltages, currents, amperages and clocks for your 5950X.
Keith - if there was a WMI driver for GigaByte sensors I'd be interested. I have 10 Gigabyte boards and have had to install the out-of-mainline it87 packages and roll my own sensors.conf file.
@Mike One of the kids have a GB b550 board if you can't find a WMI driver I can install HWinfo64 on it and create a sensors.conf file for you if your interested.
Phoronix.com has these articles about the Gigabyte WMI sensor driver.
because there was talk about a conflict in the I/O range it uses and the parameter gets you around that error message. Like you used to have to do with the it87 conflict and having to add the kernel parameter ignore_resource_conflict=1 mmio=1
Give it a try and let me know if it works on your Gigabyte boards. Curious about all sensor solutions in Linux.
I'm not entirely sure what all this means, but I gather I have driver support for hardware sensors .... what's a Windows thingy doing on Linux anyway ? Sounds historical.
gordonbb wrote:
@Mike One of the kids have a GB b550 board if you can't find a WMI driver I can install HWinfo64 on it and create a sensors.conf file for you if your interested.
Thanks, but I think I'm good. Using lsmod I find that 'wmi' is loaded, and in use by 'gigabyte_wmi and 'wmi_bmof'. Also there is a sensors3.conf in /etc
@Keith : FWIW my board is a Gigabyte B550 Aorus Pro AX which has the gigabyte-wmi.ko file in /usr/lib/modules/5.17.5-76051705-generic/kernel/drivers/platform/x86, that being for Pop!_OS 22.04 LTS.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
I think Gordon meant he could load Windows and HwInfo64 to get the scaling values from it so you could apply that in a sensors.conf file for the it87 out of band driver.
Not necessary when you have the provided gigabyte-wmi.ko kernel driver already provided which is already scaled for sensors output.
What does sensors output for you in Pop!_OS 22.04 LTS?
You tuned your 3950x CPU using a lot of granular settings. What was the process for getting to those settings?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Now I've just hit two invalids, but that's when/because I updated the Nvidia drivers mid-stream, as it were. Silly lad that I am ...
Were these invalids that it "self reported"? Or invalids when compared to other tasks?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
You tuned your 3950x CPU using a lot of granular settings. What was the process for getting to those settings?
Tom M
Not sure I understand the question. How to get to Settings. You open the BIOS with DEL or F2 during the boot process.
If you are speaking of individual setting configurations in the BIOS, experience and lots of reading in the ASUS C7H Overclock.net forum. Lots of experimentation by forum members to determine what works best.
<core_client_version>7.18.1</core_client_version>
<![CDATA[
<stderr_txt>
putenv 'LAL_DEBUG_LEVEL=3'
2022-06-22 09:16:49.4906 (2671) [normal]: This program is published under the GNU General Public License, version 2
2022-06-22 09:16:49.4906 (2671) [normal]: For details see http://einstein.phys.uwm.edu/license.php
2022-06-22 09:16:49.4906 (2671) [normal]: This Einstein@home App was built at: Aug 5 2021 17:20:50
2022-06-22 09:16:49.4906 (2671) [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/einstein_O3AS_1.01_x86_64-pc-linux-gnu__GW-opencl-nvidia'.
[DEBUG} GPU type: 1
[DEBUG} got GPU info from BOINC
[DEBUG} got VendorID 4318
2022-06-22 09:16:49.7114 (2671) [debug]: Flags: LAL_DEBUG, OPTIMIZE, HS_OPTIMIZATION, GC_SSE2_OPT, X64, SSE, SSE2, GNUC X86 GNUX86
2022-06-22 09:16:49.7114 (2671) [debug]: glibc version/release: 2.33/release
2022-06-22 09:16:49.711489 - mytime()
2022-06-22 09:16:49.7118 (2671) [debug]: Set up communication with graphics process.
2022-06-22 09:16:49.7131 (2671) [normal]: Parsed user input successfully
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.21.0.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALPulsar: 1.18.2.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALApps: 6.25.1.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
2022-06-22 09:16:49.7132 (2671) [normal]: Initialise compartments with freqWidth = 0.05 and candidates per compartment = 3000.
2022-06-22 09:16:50.0562 (2671) [normal]: Reading input data ...
2022-06-22 09:16:50.0563 (2671) [normal]: Loading SFTs matching '../../projects/einstein.phys.uwm.edu/h1_0691.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.40_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.40_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.60_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.60_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.80_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.80_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0692.00_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0692.00_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0692.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0692.20_O3aC01Cl1In0' into catalog ...2022-06-22 09:16:50.5071 (2671) [normal]: done.
2022-06-22 09:16:50.5074 (2671) [normal]: Validating SFTs (detectors: H1, L1, ) ... success.
2022-06-22 09:16:52.9877 (2671) [normal]: Search FstatMethod used: 'ResampGPU'
2022-06-22 09:16:52.9879 (2671) [normal]: Recalc FstatMethod used: 'DemodSSE'
2022-06-22 09:16:52.9889 (2671) [normal]: GPU Device used for Search/Recalc and/or semi coherent step: 'NVIDIA GeForce RTX 3060 ( Platform: NVIDIA CUDA )'
2022-06-22 09:16:52.9890 (2671) [normal]: GPU Backend used for Search/Recalc and/or semi coherent step: 'OpenCL'
2022-06-22 09:16:52.9890 (2671) [normal]: GPU version is used for the semi-coherent step!
2022-06-22 09:17:10.7316 (2671) [normal]: Number of segments: 37, total number of SFTs in segments: 11745
2022-06-22 09:17:10.7837 (2671) [normal]: Finished reading input data.
% --- GPS reference time = 1246070525.0000 , GPS data mid time = 1246070525.0000
2022-06-22 09:17:10.7838 (2671) [normal]: dFreqStack = 2.000000e-06, df1dot = 1.500000e-10, df2dot = 0.000000e+00, df3dot = 0.000000e+00
% --- Setup, N = 37, T = 432000 s, Tobs = 15809012 s, gammaRefine = 250, gamma2Refine = 4653, gamma3Refine = 1
DEPRECATION WARNING: program has invoked obsolete function InitDopplerSkyScan(). Please see XLALInitDopplerSkyScan() for information about a replacement.
2022-06-22 09:17:17.7293 (2671) [normal]: INFO: No checkpoint checkpoint.cpt found - starting from scratch
% --- Cpt:0, total:2000, sky:1/100, f1dot:1/20
DEPRECATION WARNING: program has invoked obsolete function FreeDopplerSkyScan(). Please see XLALDestroyDopplerSkyScan() for information about a replacement.
Code-version: %% LAL: 6.21.0.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALPulsar: 1.18.2.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALApps: 6.25.1.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
FPU status flags: PRECISION
2022-06-22 09:30:15.0126 (2671) [debug]: worker done. return(0) to caller
2022-06-22 09:30:15.0126 (2671) [normal]: done. calling boinc_finish(0).
09:30:15 (2671): called boinc_finish
</stderr_txt>
]]>
So no error per se, but required a quorum of 3 to reconcile :
So all as it should be then. Notice how the awarded rigs were running different OS and video card manufacturers
( linux/ATI vs Windows/Nvidia ) yet produced agreeable answers : a testament to the OpenCL standard, the driver writers and the application programmers. I guess my rig simply returned well formed nonsense, not an error state. But no great time lost. I will leave the video driver ( Nvidia 515.48.07 ) alone for a while now. Next time I'll exit out of BOINC before updating, I think that will do the trick.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
This is what I meant by "self reported" Validation state: Invalid (I think)
If it is "invalid" compared to your "wing (person)" I think it is reported differently.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Keith Myers wrote:Too bad
)
Keith - if there was a WMI driver for GigaByte sensors I'd be interested. I have 10 Gigabyte boards and have had to install the out-of-mainline it87 packages and roll my own sensors.conf file.
@Mike One of the kids have a GB b550 board if you can't find a WMI driver I can install HWinfo64 on it and create a sensors.conf file for you if your interested.
gordonbb wrote:Keith Myers
)
Phoronix.com has these articles about the Gigabyte WMI sensor driver.
Gigabyte Motherboard WMI Temperature Driver Queued Ahead Of Linux 5.13
Kernel Git pull for Gigabyte WMI driver
Linux 5.19 Adds In Raptor Lake P For Intel PMC Driver, More Gigabyte Boards For Sensors
I just checked my system and the driver is already there as long as you are running the HWE 5.13 kernel in Ubuntu 20.04 LTS or later.
It's in: /usr/lib/modules/5.13.0-51-generic/kernel/drivers/platform/x86$ gigabyte-wmi.ko
All you need to do is modprobe it in
sudo modprobe gigabyte-wmi
or possibly
sudo modprobe gigabyte-wmi.ko force_load=1
because there was talk about a conflict in the I/O range it uses and the parameter gets you around that error message. Like you used to have to do with the it87 conflict and having to add the kernel parameter ignore_resource_conflict=1 mmio=1
Give it a try and let me know if it works on your Gigabyte boards. Curious about all sensor solutions in Linux.
I'm not entirely sure what
)
I'm not entirely sure what all this means, but I gather I have driver support for hardware sensors .... what's a Windows thingy doing on Linux anyway ? Sounds historical.
Thanks, but I think I'm good. Using lsmod I find that 'wmi' is loaded, and in use by 'gigabyte_wmi and 'wmi_bmof'. Also there is a sensors3.conf in /etc
@Keith : FWIW my board is a Gigabyte B550 Aorus Pro AX which has the gigabyte-wmi.ko file in /usr/lib/modules/5.17.5-76051705-generic/kernel/drivers/platform/x86, that being for Pop!_OS 22.04 LTS.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
I think Gordon meant he could
)
I think Gordon meant he could load Windows and HwInfo64 to get the scaling values from it so you could apply that in a sensors.conf file for the it87 out of band driver.
Not necessary when you have the provided gigabyte-wmi.ko kernel driver already provided which is already scaled for sensors output.
What does sensors output for you in Pop!_OS 22.04 LTS?
Curious?
Keith, You tuned your
)
Keith,
You tuned your 3950x CPU using a lot of granular settings. What was the process for getting to those settings?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Sensors gives me
)
Sensors gives me :
mikehewson@fireball-xl5:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +41.0°C
nvme-pci-0300
Adapter: PCI adapter
Composite: +38.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +38.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +43.9°C (low = -273.1°C, high = +65261.8°C)
zenpower-pci-00c3
Adapter: PCI adapter
SVI2_Core: 1.31 V
SVI2_SoC: 969.00 mV
Tdie: +73.6°C (high = +95.0°C)
Tctl: +73.6°C
Tccd1: +69.2°C
Tccd2: +70.0°C
SVI2_P_Core: 70.07 W
SVI2_P_SoC: 7.13 W
SVI2_C_Core: 57.32 A
SVI2_C_SoC: 7.36 A
Where the Nvidia X Server Settings application divulges the GPU temperature as 45o C
Now I've just hit two invalids, but that's when/because I updated the Nvidia drivers mid-stream, as it were. Silly lad that I am ...
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Mike Hewson wrote: Now I've
)
Were these invalids that it "self reported"? Or invalids when compared to other tasks?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Tom M wrote: Keith, You
)
Not sure I understand the question. How to get to Settings. You open the BIOS with DEL or F2 during the boot process.
If you are speaking of individual setting configurations in the BIOS, experience and lots of reading in the ASUS C7H Overclock.net forum. Lots of experimentation by forum members to determine what works best.
https://www.overclock.net/threads/rog-crosshair-vii-overclocking-thread.1685809/
Well, for example, one of the
)
Well, for example, one of the tasks is annotated as follows :
Task 1309557753
x86_64-pc-linux-gnu
Stderr output
2022-06-22 09:16:49.4906 (2671) [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/einstein_O3AS_1.01_x86_64-pc-linux-gnu__GW-opencl-nvidia'.
[DEBUG} GPU type: 1
[DEBUG} got GPU info from BOINC
[DEBUG} got VendorID 4318
2022-06-22 09:16:49.7114 (2671) [debug]: Flags: LAL_DEBUG, OPTIMIZE, HS_OPTIMIZATION, GC_SSE2_OPT, X64, SSE, SSE2, GNUC X86 GNUX86
2022-06-22 09:16:49.7114 (2671) [debug]: glibc version/release: 2.33/release
2022-06-22 09:16:49.711489 - mytime()
2022-06-22 09:16:49.7118 (2671) [debug]: Set up communication with graphics process.
2022-06-22 09:16:49.7131 (2671) [normal]: Parsed user input successfully
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.21.0.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALPulsar: 1.18.2.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALApps: 6.25.1.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
2022-06-22 09:16:49.7132 (2671) [normal]: Initialise compartments with freqWidth = 0.05 and candidates per compartment = 3000.
2022-06-22 09:16:50.0562 (2671) [normal]: Reading input data ...
2022-06-22 09:16:50.0563 (2671) [normal]: Loading SFTs matching '../../projects/einstein.phys.uwm.edu/h1_0691.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.40_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.40_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.60_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.60_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0691.80_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0691.80_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0692.00_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0692.00_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/h1_0692.20_O3aC01Cl1In0;../../projects/einstein.phys.uwm.edu/l1_0692.20_O3aC01Cl1In0' into catalog ...2022-06-22 09:16:50.5071 (2671) [normal]: done.
2022-06-22 09:16:50.5074 (2671) [normal]: Validating SFTs (detectors: H1, L1, ) ... success.
2022-06-22 09:16:52.9877 (2671) [normal]: Search FstatMethod used: 'ResampGPU'
2022-06-22 09:16:52.9879 (2671) [normal]: Recalc FstatMethod used: 'DemodSSE'
2022-06-22 09:16:52.9889 (2671) [normal]: GPU Device used for Search/Recalc and/or semi coherent step: 'NVIDIA GeForce RTX 3060 ( Platform: NVIDIA CUDA )'
2022-06-22 09:16:52.9890 (2671) [normal]: GPU Backend used for Search/Recalc and/or semi coherent step: 'OpenCL'
2022-06-22 09:16:52.9890 (2671) [normal]: GPU version is used for the semi-coherent step!
2022-06-22 09:17:10.7316 (2671) [normal]: Number of segments: 37, total number of SFTs in segments: 11745
2022-06-22 09:17:10.7837 (2671) [normal]: Finished reading input data.
% --- GPS reference time = 1246070525.0000 , GPS data mid time = 1246070525.0000
2022-06-22 09:17:10.7838 (2671) [normal]: dFreqStack = 2.000000e-06, df1dot = 1.500000e-10, df2dot = 0.000000e+00, df3dot = 0.000000e+00
% --- Setup, N = 37, T = 432000 s, Tobs = 15809012 s, gammaRefine = 250, gamma2Refine = 4653, gamma3Refine = 1
DEPRECATION WARNING: program has invoked obsolete function InitDopplerSkyScan(). Please see XLALInitDopplerSkyScan() for information about a replacement.
2022-06-22 09:17:17.7293 (2671) [normal]: INFO: No checkpoint checkpoint.cpt found - starting from scratch
% --- Cpt:0, total:2000, sky:1/100, f1dot:1/20
0.% --- CG:9272015 FG:250000 f1dotmin_fg:-2.717183860529e-09 df1dot_fg:5.97609561753e-13 f2dotmin_fg:0 df2dot_fg:0 f3dotmin_fg:0 df3dot_fg:1
...................
1....................
2....................
3....................
4....................
5....................
6...c
.................
7....................
8....................
9....................
10....................
11....................
12....................
13....................
14....................
15....................
16....................
17....................
18....................
19....................c
20....................
21....................
22....................
23....................
24....................
25....................
26....................
27....................
28....................
29....................
30....................
31....................
32....................
33....................
34....................
35..............c
......
36....................
37....................
38....................
39....................
40....................
41....................
42....................
43....................
44....................
45....................
46....................
47....................
48....................
49....................
50....................
51...................c
.
52....................
53....................
54....................
55....................
56....................
57....................
58....................
59....................
60....................
61....................
62....................
63....................
64....................
65....................
66....................
67..................c
..
68....................
69....................
70....................
71....................
72....................
73....................
74....................
75....................
76....................
77....................
78....................
79....................
80....................
81....................
82....................
83................c
....
84....................
85....................
86....................
87....................
88....................
89....................
90....................
91....................
92....................
93....................
94....................
95....................
96....................
97....................
98....................
99....................
2022-06-22 09:23:47.8781 (2671) [normal]: Finished main analysis.
2022-06-22 09:23:47.8788 (2671) [normal]: Recalculating statistics for the final toplist...
2022-06-22 09:30:14.4978 (2671) [normal]: Finished recalculating toplist statistics.
2022-06-22 09:30:14.4980 (2671) [normal]: Finished in 804.78 s with peak RAM usage: 853.7 MB on CPU 'AMD Ryzen 9 5950X 16-Core Processor ', peak VRAM usage: 889.5 MB on GPU Device: 'NVIDIA GeForce RTX 3060 ( Platform: NVIDIA CUDA )' with backend: 'OpenCL'.
2022-06-22 09:30:14.5038 (2671) [debug]: Writing output ... done.
DEPRECATION WARNING: program has invoked obsolete function FreeDopplerSkyScan(). Please see XLALDestroyDopplerSkyScan() for information about a replacement.
Code-version: %% LAL: 6.21.0.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALPulsar: 1.18.2.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
%% LALApps: 6.25.1.1 (CLEAN 8d0838c264f9ff9adc8c3cdbfa17b5154eaa2994)
FPU status flags: PRECISION
2022-06-22 09:30:15.0126 (2671) [debug]: worker done. return(0) to caller
2022-06-22 09:30:15.0126 (2671) [normal]: done. calling boinc_finish(0).
09:30:15 (2671): called boinc_finish
</stderr_txt>
]]>
So no error per se, but required a quorum of 3 to reconcile :
Workunit 650285448
x86_64-pc-linux-gnu
x86_64-pc-linux-gnu
Gravitational Wave search O3 All-Sky #1 v1.01 (GW-opencl-nvidia)
windows_x86_64
So all as it should be then. Notice how the awarded rigs were running different OS and video card manufacturers
( linux/ATI vs Windows/Nvidia ) yet produced agreeable answers : a testament to the OpenCL standard, the driver writers and the application programmers. I guess my rig simply returned well formed nonsense, not an error state. But no great time lost. I will leave the video driver ( Nvidia 515.48.07 ) alone for a while now. Next time I'll exit out of BOINC before updating, I think that will do the trick.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
This is what I meant by "self
)
This is what I meant by "self reported" Validation state: Invalid (I think)
If it is "invalid" compared to your "wing (person)" I think it is reported differently.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!