Generic CPU discussion

gordonbb
gordonbb
Joined: 14 May 19
Posts: 26
Credit: 895570568
RAC: 0

Keith Myers wrote: gordonbb

Keith Myers wrote:

gordonbb wrote:

Keith Myers wrote:

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.

Zenpower3 kernel module

Zenmonitor3 monitoring application

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.

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.

Awesome - Thanks Keith - I'll give it a try this weekend.

gordonbb
gordonbb
Joined: 14 May 19
Posts: 26
Credit: 895570568
RAC: 0

Mike Hewson wrote: Sensors

Mike Hewson wrote:

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.

Mike - I don't think the gigabyte_wmi kernal driver is loaded as I'm not seeing the sensors on the motherboard. - see Keith's comment about resource conflicts.

Here the sensors output from one of my Aorus x570 Master motherboards on Ubuntu 20.04 LTS Desktop:

root@dcn01:~# sensors
ucsi_source_psy_0_00081-i2c-0-08
Adapter: NVIDIA GPU I2C adapter
in0:           0.00 V  (min =  +0.00 V, max =  +0.00 V)
curr1:         0.00 A  (max =  +0.00 A)

zenpower-pci-00c3
Adapter: PCI adapter
SVI2_Core:   932.00 mV
SVI2_SoC:    969.00 mV
Tdie:         +39.2°C  (high = +95.0°C)
Tctl:         +39.2°C
Tccd1:        +37.0°C
Tccd2:        +38.5°C
SVI2_P_Core:   6.34 W
SVI2_P_SoC:    3.71 W
SVI2_C_Core:   5.93 A
SVI2_C_SoC:    3.83 A

it8688-isa-0a40
Adapter: ISA adapter
CPU Vcore:     984.00 mV (min =  +0.35 V, max =  +1.45 V)  ALARM
+3.3V:           3.35 V  (min =  +3.21 V, max =  +3.41 V)
+12V:           12.10 V  (min = +11.66 V, max = +12.38 V)
+5V:             5.04 V  (min =  +4.86 V, max =  +5.16 V)
Vcore SoC:     984.00 mV (min =  +0.90 V, max =  +1.26 V)
CPU Vddp:      924.00 mV (min =  +0.85 V, max =  +0.95 V)
DRAM A/B:        1.22 V  (min =  +1.10 V, max =  +1.60 V)
3 Vsb:           3.31 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:            3.24 V
CPU fan:       1614 RPM  (min =  300 RPM)
Sys1_Fan:         0 RPM  (min =  300 RPM)  ALARM
Sys2_Fan:       725 RPM  (min =  300 RPM)
Sys3_PCH_Fan:     0 RPM  (min =  300 RPM)  ALARM
CPU_Opt_Fan:    863 RPM  (min =  300 RPM)
Sys1 Temp:      +33.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
Ambient:        -55.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
CPU Temp:       +39.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = AMD AMDSI
PCIe_x16 Temp:  +45.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
VRM_MOS Temp:   +38.0°C  (low  =  +0.0°C, high = -125.0°C)  sensor = thermistor
PCH Temp:       +47.0°C  (low  = -16.0°C, high = +90.0°C)  sensor = thermistor

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)

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

it8792-isa-0a60
Adapter: ISA adapter
Vin0:                1.78 V  (min =  +0.00 V, max =  +2.78 V)
DDRvtt:            589.00 mV (min =  +0.00 V, max =  +2.78 V)
ChipsetCore:       981.00 mV (min =  +0.00 V, max =  +2.78 V)
Vin3:                3.36 V  (min =  +0.00 V, max =  +5.56 V)
CPU_Vdd08:           1.79 V  (min =  +0.00 V, max =  +2.78 V)
DDR_Vpp/PM_CLD012:   1.18 V  (min =  +0.00 V, max =  +2.78 V)
V3sb:                2.78 V  (min =  +0.00 V, max =  +2.78 V)  ALARM
Vbat:                3.33 V  (min =  +0.00 V, max =  +5.56 V)
Fan_Pump_5:         950 RPM  (min =    0 RPM)
Sys6_Fan:             0 RPM  (min =    0 RPM)
Sys4_Fan:           870 RPM  (min =    0 RPM)
PCIe_x8 Temp:       +37.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
EC2_Temp:           -55.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
SYS2 Temp:          +34.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor

nvme-pci-0100
Adapter: PCI adapter
Composite:    +36.9°C  (low  =  -0.1°C, high = +114.8°C)
                       (crit = +119.8°C)

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18748954793
RAC: 7075251

So Gordon, I am guessing that

So Gordon, I am guessing that the first ISA sensor output for the it8688 is one you scaled from Windows reading through a sensors.conf?

And the next ISA sensors output is the one from the standard nct6775 driver?

I don't however see any sign of the gigabyte-wmi sensor driver.

You should see an entry like this if the kernel module driver is loaded.

gigabyte_wmi-virtual-0

You need to use the force load option. Always check after a modprobe with lsmod to see if the kernel module is loaded afterwards.

I am surprised to see two IT SIO chips on the board.

 

 

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6588
Credit: 318145699
RAC: 397469

Point taken. However one can

Point taken. However one can check for module presence in the kernel by using the --first-time option for modprobe, for example :

mikehewson@fireball-xl5:~$ sudo modprobe --first-time gigabyte-wmi force_load=1
modprobe: ERROR: could not insert 'gigabyte_wmi': Module already in kernel

.... and also appears in the output of the lsmod command. This is curious and suggests that the module is loaded but doesn't report alot when sensors is used.

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

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18748954793
RAC: 7075251

Or you have a Gigabyte model

Or you have a Gigabyte model that is not defined in the module so it is not recognized.

It only covers these for now.

DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("B550M AORUS PRO-P"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("B550M DS3H"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("Z390 I AORUS PRO WIFI-CF"),
+	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("Z490 AORUS ELITE AC"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("X570 AORUS ELITE"),
+	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("X570 AORUS ELITE WIFI"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("X570 GAMING X"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("X570 I AORUS PRO WIFI"),
 	DMI_EXACT_MATCH_GIGABYTE_BOARD_NAME("X570 UD"),

 

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6588
Credit: 318145699
RAC: 397469

Oh, Sad Panda. This suggests

Oh, Sad Panda. This suggests a write your own driver strategy though ? Nah, just kidding, sounds too complex.

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

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18748954793
RAC: 7075251

What board do you have Mike? 

What board do you have Mike?  You can always ask for your board to be included.

 

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6588
Credit: 318145699
RAC: 397469

Well, it's a Gigabyte B550

Well, it's a Gigabyte B550 Aorus Pro AX ( rev 1.0 ). The guy who sold me it said it was a common enough board, for gamers mainly, so maybe it's worth an ask. Who do you ask ?

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

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18748954793
RAC: 7075251

You would post a request to

You would post a request to the 

platform-driver-x86.vger.kernel.org archive mirror

directed to the maintainer Guenter Roeck via this link:

linux-[at]-roeck-us.net

with the subject:

Re: [PATCH v2] platform/x86: add Gigabyte WMI temperature driver' \

 

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6588
Credit: 318145699
RAC: 397469

OK. Will do. Cheers, Mike.

OK. Will do.

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

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.