orblazer / plasma-applet-resources-monitor

Plasmoid for monitoring CPU, memory, network traffic, GPUs and disks IO.
https://www.pling.com/p/2143899/
GNU General Public License v3.0
57 stars 6 forks source link

[BUG] Not detecting GPU #53

Closed den7007 closed 1 year ago

den7007 commented 1 year ago

Current Behavior

Hi, I recently updated to NVIDIA 535.54.03 drivers and just noticed the widget isn't detecting my GPU anymore.

Operating System: EndeavourOS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.1.34-1-lts (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i5-10600K CPU @ 4.10GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2 Manufacturer: ASUS

Expected Behavior

Displays GPU stats

Steps To Reproduce

This happens at boot or even if I disable/enable, uninstall/reinstall

Screenshots

image

Logs

Jun 17 17:03:42 endeavour-os plasmashell[5864]: QString::arg: 2 argument(s) missing in org.kde.kinfocenter
Jun 17 17:03:42 endeavour-os plasmashell[5864]: org.kde.plasma.notifications: Trying to replace notification with id 1547 which doesn't exist, creating a new one. This is an application bug!
Jun 17 17:03:42 endeavour-os plasmashell[5864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5634f77de9f0) QQmlContext(0x5634f423edc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jun 17 17:03:42 endeavour-os plasmashell[5864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5634f77de9f0) QQmlContext(0x5634f423edc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jun 17 17:03:54 endeavour-os plasmashell[5864]: org.kde.plasma.notifications: Trying to replace notification with id 1548 which doesn't exist, creating a new one. This is an application bug!
Jun 17 17:03:54 endeavour-os plasmashell[5864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5634f6bdb9e0) QQmlContext(0x5634f423edc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jun 17 17:03:54 endeavour-os plasmashell[5864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5634f6bdb9e0) QQmlContext(0x5634f423edc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jun 17 17:04:00 endeavour-os plasmashell[5864]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jun 17 17:04:00 endeavour-os plasmashell[5864]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jun 17 17:04:00 endeavour-os plasmashell[5864]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jun 17 17:04:00 endeavour-os plasmashell[5864]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 17 17:04:01 endeavour-os plasmashell[5864]: QString::arg: 2 argument(s) missing in nvidia-settings
Jun 17 17:04:03 endeavour-os plasmashell[5864]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jun 17 17:04:03 endeavour-os plasmashell[5864]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jun 17 17:04:03 endeavour-os plasmashell[5864]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jun 17 17:04:03 endeavour-os plasmashell[5864]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 17 17:04:04 endeavour-os plasmashell[5864]: QString::arg: 2 argument(s) missing in com.leinardi.gwe
Jun 17 17:05:16 endeavour-os plasmashell[5864]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Jun 17 17:05:16 endeavour-os plasmashell[5864]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:126:5: QML ScrollView: Binding loop detected for property "implicitWidth"
Jun 17 17:05:16 endeavour-os plasmashell[5864]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Jun 17 17:05:16 endeavour-os plasmashell[5864]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height"
Jun 17 17:05:16 endeavour-os plasmashell[5864]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jun 17 17:05:16 endeavour-os plasmashell[5864]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int
Jun 17 17:05:16 endeavour-os plasmashell[5864]: file:///home/den/.local/share/plasma/wallpapers/a2n.blur/contents/ui/WindowModel.qml:23:3: Unable to assign [undefined] to QRect
Jun 17 17:05:16 endeavour-os plasmashell[5864]: file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PrinterItem.qml:22:5: Unable to assign [undefined] to bool
Jun 17 17:05:17 endeavour-os plasmashell[5864]: Both point size and pixel size set. Using pixel size.
Jun 17 17:05:17 endeavour-os plasmashell[5864]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout

Versions

- Widget: 2.9.1
- KDE Plasma: 5.27.5
- KDE Framework: 5.107.0

Additional context

No response

Ir0nyPT commented 1 year ago

I'm using in 3 different computers and all have the same issue Two of them with NVIDIA and other with Intel Graphics

orblazer commented 1 year ago

Hello, This issue is due to wrong sensor because gpu is link on gpu1 instead of gpu0. But i have make an fix in v2.10.1 for allowing users select they correct graphic card (https://github.com/orblazer/plasma-applet-resources-monitor/commit/c19317233ff1f8aa68fc2f3c3dff352fa95e7430). so please update the package.

denji commented 1 year ago

@orblazer This is actually an unrelated problem, the new drivers have changed the indents and number of columns for nvidia-smi pmon and nvidia-smi dmon -d 2 -s pucm which use the KDE toolkit to collect system statistics. The statically hardcoded parser does not get the correct number of columns and indents, so fixing the GPU numbering selection will not help us now.

The bug is relevant again, and requires a library codebase fix.:

orblazer commented 1 year ago

@denji ok, so u think the issue look slate until i release v3.x and use new ksysguard version.

denji commented 1 year ago

@orblazer need a fix in ksystemstats (dmon telemetry monitoring for each NVIDIA GPU), libksysguard captures statistics (pmon) on GPU processes only. https://invent.kde.org/plasma/ksystemstats/-/merge_requests/57

RafaelLinux commented 1 year ago

Same here. "GPU" dropdown button is empty, but clickable. Not showing a GPU to select. Nothing at all.

But I must add than even Plasma "System monitor" is not showing GPU info (always shows zero use) with most applications. Example: When playing games like "Zero-K" or "Metro Redux", "System monitor" is not showing in GPU column any activity. It shows activity with "CS:GO". I investigated a few more and discovered than only "nvtop" (installed from repositories) shows real GPU activity with all those games. I told this here but didn't notify it still to Plasma developers.

Operating System: openSUSE Tumbleweed 20230621 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

RafaelLinux commented 1 year ago

So there is a fix but no one knows when it will be available, is it not?

El mié, 28 jun 2023 a las 4:42, Denis Denisov @.***>) escribió:

@RafaelLinux https://github.com/RafaelLinux Reading some values causes segfault, there are no default values for nvidia-smi fields, and the required fix is not yet merged by KDE.

$ kstatsviewer gpu/gpu0/usage gpu/gpu0/usage 0 $ kstatsviewer gpu/gpu0/temperature gpu/gpu0/temperature 0

"kstatsviewer gpu/gpu0/usedVram" is never complete

$ timeout 10s bash -c "kstatsviewer gpu/gpu0/usedVram"

— Reply to this email directly, view it on GitHub https://github.com/orblazer/plasma-applet-resources-monitor/issues/53#issuecomment-1610577346, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDRY74YQZ2PYPOKYNDBFXTXNOKYVANCNFSM6AAAAAAZKDO6LU . You are receiving this because you were mentioned.Message ID: @.***>

denji commented 1 year ago

@RafaelLinux This pull request has not yet been approved/merged into the plasma/ksystemstats repository. A fix should appear in KDE Plasma 5.27.6+

RafaelLinux commented 1 year ago

Fortunately, I use openSUSE TW, so I expect fix will be available before 2 months.

Thank you!!!

El jue, 29 jun 2023 a las 8:36, Denis Denisov @.***>) escribió:

@RafaelLinux https://github.com/RafaelLinux This pull request has not yet been approved/merged into the plasma/ksystemstats repository. A fix should appear in 5.27.6+

— Reply to this email directly, view it on GitHub https://github.com/orblazer/plasma-applet-resources-monitor/issues/53#issuecomment-1612501942, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDRY77OOSOAF3NKQ3ZWLGDXNUPAJANCNFSM6AAAAAAZKDO6LU . You are receiving this because you were mentioned.Message ID: @.***>

dull4h4n commented 1 year ago

This happens for me when using nobara 6.3.11 fsync kernel, but not using anything else. I notice that my video card is detected as "GPU 2", while other kernels recognize it appropriately as GPU 1. I have an amd radeon 6800xt card. Monitor just needs to look for all available cards more broadly.

denji commented 1 year ago

KDE Plasma Version: 5.27.7 The problem for NVIDIA is solved, for pre-GCN-AMD/AMDGPU look for fixes or not approved merge requests ksystemstats & libksysguard.

RafaelLinux commented 1 year ago

Thank you for the info!!!! I'll update now!!! ;)

orblazer commented 1 year ago

Hello, I close this issue due to the issue seem to be fixed.

RafaelLinux commented 1 year ago

Yessss!!! It's working (w/o touching nothing, only upgrading my Tumbleweed). Thank you!!

RafaelLinux commented 1 year ago

Only an additional thing .... GPU still is not selectable. If user click on dropdown button, nothing to select ... it's something weird .... :( ... it works, but that's confusing.

orblazer commented 1 year ago

Only an additional thing .... GPU still is not selectable. If user click on dropdown button, nothing to select ... it's something weird .... :( ... it works, but that's confusing.

Ok, i receive my new RTX in few days so i could try to see if the issue is present for me.

RafaelLinux commented 1 year ago

I imagine you are talking about source code. As user, I can't select or save explicitly nothing (only "Apply", but nothing to select as you can see in screenshot).

[image: image.png]

El lun, 21 ago 2023 a las 2:24, Denis Denisov @.***>) escribió:

@RafaelLinux https://github.com/RafaelLinux Perhaps "orblazer/plasma-applet-resources-monitor" module there is an empty string "0" instead of qpu{index} or "gpu" instead of "gpu0", "gpu1".

— Reply to this email directly, view it on GitHub https://github.com/orblazer/plasma-applet-resources-monitor/issues/53#issuecomment-1685441670, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDRY76FYQTUMY24L2MJF6DXWKTCLANCNFSM6AAAAAAZKDO6LU . You are receiving this because you were mentioned.Message ID: @.***>

orblazer commented 1 year ago

@RafaelLinux Hello, your last issue seem similar to https://github.com/orblazer/plasma-applet-resources-monitor/issues/58, so keep an eye on that.

RafaelLinux commented 1 year ago

@RafaelLinux Hello, your last issue seem similar to #58, so keep an eye on that.

Ok, I'll put my system info there