[BUG] GPU not detected (AMD)

[datWeazel]

Current Behavior

AMD GPU (6950xt) isn't detected. Drop-down menu in plasmoid config is empty.

Plasma System Monitor shows the sensors under GPU 2.

lspci output:

weazel@weazel-endeavour ~$ lspci | grep ' VGA '            
2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] (rev c0)

Expected Behavior

GPU should be detected and sensor infos be show.

Steps To Reproduce

-

Screenshots

No response

Logs

weazel@weazel-endeavour ~$ plasmawindowed org.kde.resourcesMonitor-fork
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Plasma Windowed" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Makes the plasmoid stay alive in the Notification Area, even when the window is closed." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Force loading the given shell plugin" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The applet to open." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Arguments to pass to the plasmoid." msgid_plural: "" msgctxt: ""
Loading default layout
kf.plasma.core: requesting config for "Resources Monitor (fork)" without a containment!
kf.plasma.quick: Applet preload policy set to 1
Using KRun from QML is deprecated (since 5.88). Use Qt.openUrlExternally, or the KIO::OpenUrlJob/KIO::ApplicationLauncherJob classes from C++ instead.
qml: 0
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:126:5: QML ScrollView: Binding loop detected for property "implicitWidth"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height"
qt.core.qabstractitemmodel.checkindex: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
file:///home/weazel/.local/share/plasma/plasmoids/org.kde.resourcesMonitor-fork/contents/ui/components/GpuDetector.qml:9:33: QML ListModel: set: index -1 out of range

Versions

- Widget:2.10.1
- KDE Plasma: 5.27.7
- KDE Framework: 5.109.0

Additional context

No response

[orblazer]

Hello, Whats it's exact result when you run lspci | grep ' VGA ' | tail -n 1 | cut -d' ' -f 1 ? and whats you have when you add GPU > GPU X > GPU X Name sensors in "SystemMonitor" apps ?

Thanks.

[datWeazel]

weazel@weazel-endeavour ~$ lspci | grep ' VGA ' | tail -n 1 | cut -d' ' -f 1
2d:00.0

GPU 2 Name Sensor outputs: Navi 21 [Radeon RX 6950 XT]

[orblazer]

Hum ok, could you tell me the sensors used for GPU 2 Name in page you have create (that files is storage in ~/.local/share/plasma-systemmonitor/) AND have you an GPU 1 Name ? This is for confirm my theory and my potential fix for the issue.

I think i need to found an more robust solution for found all gpus because you seam have an sensor like gpu/gpu1/ name BUT seem to have only 1 CG, or my CMD is invalid.

[RafaelLinux]

As I wrote in original issue thread, despite it's working (widget shows correctly graphs for GPU) and GPU is selectable in widget config, thre is nothing to select. In my case, using NVIDIA GPU, output is: 02:00.0

[datWeazel]

Hum ok, could you tell me the sensors used for GPU 2 Name in page you have create

[Face-94039565856208][Sensors]
highPrioritySensorIds=["gpu/gpu1/usage"]
lowPrioritySensorIds=[]
totalSensors=["gpu/gpu1/temperature","gpu/gpu1/usage"]

AND have you an GPU 1 Name ?

Nope can't select any other GPU sensors in plasma-systemmonitor.