[RESOLVED] System monitoring apps don't see my GPU

Jotunn · 2024-04-27 00:28:47

I have tried the System Monitor app that comes bundled with KDE and I have tried Btop++
Both of these apps detect my system resources accurately but I cannot get them to display any information about my GPU.
My displays are all connected through my GPU not mobo so I know it is at least functioning on a hardware level.

I ran this just to make sure my GPU was being detected correctly by the system:

[jotunn@catalyst ~]$ glxinfo | grep OpenGL
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 17.0.6, DRM 3.54, 6.6.28-1-lts)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.0.5-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.5-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.5-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Last edited by Jotunn (2024-05-01 03:50:46)

Mr Green · 2024-04-27 07:58:26

A quick online search would help you more but I use radeontop to give some realtime info.

Jotunn · 2024-04-29 01:55:27

radeontop is an awesome tool but it does nto show temps which is the main thing I want to see.

I have done a fair bit of googling and I see some people monitoring their temps with sensors:
https://wiki.archlinux.org/title/Lm_sensors

However, when I try to run it I am getting some errors I don't understand:

[root@catalyst jotunn]# sensors-detect --auto
# sensors-detect version 3.6.0+git
# Board: ASUSTeK COMPUTER INC. ROG STRIX X670E-I GAMING WIFI
# Kernel: 6.6.28-1-lts x86_64
# Processor: AMD Ryzen 5 7600X 6-Core Processor (25/97/2)

Running in automatic mode, default answers to all questions
are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
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
AMD Family 19h 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): 
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 unknown chip with ID 0xd802
    (logical device B has address 0x290, could be sensors)
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'...                                      Yes
Found unknown chip with ID 0x8883
    (logical device 4 has address 0x290, could be sensors)

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): 
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): 
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): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x4b
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Analog Devices ADT7481'...                     No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x73
Probing for `FSC Poseidon I'...                             No
Probing for `FSC Poseidon II'...                            No
Probing for `FSC Scylla'...                                 No
Probing for `FSC Hermes'...                                 No
Probing for `FSC Heimdal'...                                No
Probing for `FSC Heracles'...                               No
Probing for `FSC Hades'...                                  No
Probing for `FSC Syleus'...                                 No
Probing for `FTS Teutates'...                               No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-3)
Do you want to scan it? (YES/no/selectively): 

Next adapter: AMDGPU SMU 0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU SMU 1 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-8)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-9)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 1 (i2c-11)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 2 (i2c-12)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-13)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-14)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-15)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 1 (i2c-16)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 2 (i2c-17)
Do you want to scan it? (yes/NO/selectively): 

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

I followed that link to the HWMon Wiki page but don't really understand what that page is instructing me to do.

jl2 · 2024-04-29 05:00:45

Sorry, no sensors were detected.

That's normal. Mostly they already show up in the "sensors" command.

This will show you power draw and temps, but not usage

You can look where those tools get the gpu info from, and check if your gpu shows up there, and then üost back.

Or you can try other monitoring tools: conky, nvtop, missioncenter
https://wiki.archlinux.org/title/List_o … m_monitors

Arch Linux

#1 2024-04-27 00:28:47

[RESOLVED] System monitoring apps don't see my GPU

#2 2024-04-27 07:58:26

Re: [RESOLVED] System monitoring apps don't see my GPU

#3 2024-04-29 01:55:27

Re: [RESOLVED] System monitoring apps don't see my GPU

#4 2024-04-29 05:00:45

Re: [RESOLVED] System monitoring apps don't see my GPU

Board footer