Created attachment 178184 [details]
Fastfetch Screenshot

Any output when you start it from a terminal?

(In reply to Harald Sitter from comment #2)
> Any output when you start it from a terminal?

qt.qml.typeregistration: Invalid QML element name "Hint"; value type names should begin with a lowercase letter
Failed to load vulkan: Cannot load library vulkan: vulkan: cannot open shared object file: No such file or directory
initInstance: No Vulkan library available
Failed to create platform Vulkan instance
Failed to create vulkan instance
GPU count mismatch (from vulkan) 0 2
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Warning from helper: DMIDecodeHelper: Unable to get system information for  "system-version"


This is what i got

And you are sure your nvidia driver is actually working? Those warnings rather suggest your second device is indeed a CPU renderer based on llvmpipe.

What happens when you run the opengl helper like so (path may be different on fedora):

DRI_PRIME=0 /usr/lib/libexec/kinfocenter-opengl-helper
DRI_PRIME=1 /usr/lib/libexec/kinfocenter-opengl-helper
DRI_PRIME=2 /usr/lib/libexec/kinfocenter-opengl-helper

(In reply to Harald Sitter from comment #4)
> And you are sure your nvidia driver is actually working? Those warnings
> rather suggest your second device is indeed a CPU renderer based on llvmpipe.
> 
> What happens when you run the opengl helper like so (path may be different
> on fedora):
> 
> DRI_PRIME=0 /usr/lib/libexec/kinfocenter-opengl-helper
> DRI_PRIME=1 /usr/lib/libexec/kinfocenter-opengl-helper
> DRI_PRIME=2 /usr/lib/libexec/kinfocenter-opengl-helper


Sorry, I didn't really get what you said, but I ran this

   glxinfo | grep "OpenGL renderer"

OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)

Right.

Now run 

DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

(In reply to Harald Sitter from comment #6)
> Right.
> 
> Now run 
> 
> DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=2 glxinfo | grep "OpenGL renderer"



DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
                        DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
                        DRI_PRIME=2 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)
glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))
glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

these are output respectively

(In reply to Harald Sitter from comment #6)
> Right.
> 
> Now run 
> 
> DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

These are for better aligned outputs


DRI_PRIME=0 glxinfo | grep "OpenGL renderer"

OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)


DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))


DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

> OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

Why does glx manage to initialize vulkan but Qt not? I am at a loss for words

(In reply to Harald Sitter from comment #9)
> > OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))
> 
> Why does glx manage to initialize vulkan but Qt not? I am at a loss for words

😅

Paging Neal. Maybe he has an idea what's up with your vulkan stack.

Ultimately the problem is that the vulkan code fails to work at all and so device enumeration runs through opengl and that has problems for some reason too (though arguably we don't need to care because the vulkan code should provide superior enumeration - if it was working).

Oh, btw another thing I have noticed with my laptop is that if only nouveau drivers are installed then other that fastfetch my GPU doesn't show up anywhere like nvtop or even some applications don't even recognise the mx350 only after installing the proprietary drivers it starts to show up. I guess this is unrelated to the issue, but I thought of letting you know anyway.

Created attachment 178284 [details]
KInfoCenter screenshot from my Framework 16

This seems to work as expected on my system.

Additionally, the helper seems to do the right thing too?

ngompa@fedora ~> /usr/libexec/kinfocenter-opengl-helper
[{"name":"AMD Radeon 780M (radeonsi, gfx1103_r1, LLVM 19.1.0, DRM 3.59, 6.12.11-200.fc41.x86_64)","vkDeviceType":0}]
ngompa@fedora ~> DRI_PRIME=1 /usr/libexec/kinfocenter-opengl-helper
[{"name":"AMD Radeon RX 7700S (radeonsi, navi33, LLVM 19.1.0, DRM 3.59, 6.12.11-200.fc41.x86_64)","vkDeviceType":0}]

I'm inclined to say this might be something specifically broken with the NVIDIA driver. In the Fedora KDE Matrix room, I was pointed to this issue: https://github.com/NVIDIA/egl-wayland/issues/162

Yes this https://github.com/NVIDIA/egl-wayland/issues/162 might be the issue, I can get those same errors on my system too.

mesa tries to load the nouveau userspace gl driver, even though the nouveau kernel driver is not loaded. 
i asked on the egl-wayland issue for the mesa issue, but i think i found it https://gitlab.freedesktop.org/mesa/mesa/-/issues/12462

(In reply to Luan Vitor Simião Oliveira from comment #16)
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/12462

Thanks I will be following that👍🏻

@angad could you try installing vulkan-loader-devel, and checking if the issue is resolved?

(In reply to Luan Vitor Simião Oliveira from comment #18)
> @angad could you try installing vulkan-loader-devel, and checking if the
> issue is resolved?

Well it does get resolved, but how to do know that are you a genius or something??

Created attachment 178307 [details]
infocentre

See yourself looks good

usr/lib64/libvulkan.so is only included with that package and qt is trying to load Vulcan through it instead of /usr/lib64/libvulkan.so.1

Created attachment 178310 [details]
OpenGL (EGL)

(In reply to Luan Vitor Simião Oliveira from comment #21)
> usr/lib64/libvulkan.so is only included with that package and qt is trying
> to load Vulcan through it instead of /usr/lib64/libvulkan.so.1
 
oh ok btw is this normal?

no idea, probably not, since that`s an devel package, either qt needs to load libvulkan.so.1, or libvulkan.so should be moved to the regular vulkan-loader package

I think ultimately the bug is in qtwayland. I mean, there's something wrong with nvidia too, but the main problem is that the vulkan code doesn't enumerate devices and that seems to be simply because qtwayland doesn't try to load libvulkan.so.1 as first choice.

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/232

I'm also experiencing this bug in the newly released Plasma Desktop 6.3.2, I'll post the 2 versions of kinfo with and without sudo

➜  ~ kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor 1: Mesa Intel® HD Graphics 4400
Graphics Processor 2: llvmpipe
➜  ~ 


➜  ~ sudo kinfo
[sudo] senha para joserafael: 
MESA-INTEL: warning: Haswell Vulkan support is incomplete
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor 1: Intel® HD Graphics 4400
Graphics Processor 2: NVIDIA GeForce GT 740M

sudo seems to make it work because it forces kinfocenter to use x11, if you force x11 through some other way it will also "fix" the text

*** Bug 500949 has been marked as a duplicate of this bug. ***

Git commit a18a54d9a513cf633787eb8e7a566c91759109a7 by Harald Sitter.
Committed on 06/03/2025 at 11:36.
Pushed by sitter into branch 'master'.

about: when loading opengl gpus, handle nvidia the nvidia way

- use nvidia's glx library
- set the renderer offload variable

this should produce more reasonable strings on systems where vulkan is
not working for whatever reason

M  +39   -5    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/a18a54d9a513cf633787eb8e7a566c91759109a7

Git commit 4d789b59c4b9e22602e8e03f86fcc7896a6b1f39 by Harald Sitter.
Committed on 06/03/2025 at 11:40.
Pushed by sitter into branch 'Plasma/6.3'.

about: when loading opengl gpus, handle nvidia the nvidia way

- use nvidia's glx library
- set the renderer offload variable

this should produce more reasonable strings on systems where vulkan is
not working for whatever reason
(cherry picked from commit a18a54d9a513cf633787eb8e7a566c91759109a7)

M  +39   -5    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/4d789b59c4b9e22602e8e03f86fcc7896a6b1f39

Created attachment 179177 [details]
packages for only computing installation

If you use nvidia glx library, I fear  you can't detect the nvidia adapter in this following case : only computing installation.

see the capture

I wonder if a a bug that I reported has the same cause or if the fix for this one will affect it in any way:
https://bugs.kde.org/show_bug.cgi?id=500403
Or if there, the fix still need to happen on distros' side.

I apologize, but the problem still applies to me in 6.3.3

Please open a new bug report and post the output of running kinfocenter from a terminal.

So this didn't get fixed after the update 6.3.3 update, although one thing has happened on the nouveau driver it does show GPU:2 now previously it was not even showing the NVIDIA GPU but with proprietary drivers it still shows llvmpipe

Created attachment 179658 [details]
Screenshot after the 6.3.3 update

(In reply to Angad from comment #36)
> Created attachment 179658 [details]
> Screenshot after the 6.3.3 update

I confirm.

Operating System: openSUSE Tumbleweed 20250321
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe
Manufacturer: ASRock
Product Name: B760M-HDV/M.2 D4

Setting back to confirmed since more than one person can reproduce the issue

Is that with comment 18 noted and applied?

(In reply to Harald Sitter from comment #39)
> Is that with comment 18 noted and applied?

no installing vulkan-loader-devel fixes the whole issue, it's without the package installed

It also happens to me:

```
$ kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-arch1-1-surface (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 15.5 GiB of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 620
Graphics Processor 2: llvmpipe

```

But this is the output of `vkcube`:

```
$ vkcube
Selected WSI platform: xcb
Selected GPU 0: NVIDIA GeForce GTX 1060, type: DiscreteGpu
```

In my case using the nvidia adapter only for computing.

:~> kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: openSUSE Tumbleweed 20250321
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe

:~> vkcube
Selected WSI platform: xcb
Selected GPU 0: Intel(R) UHD Graphics 730 (ADL-S GT1), type: IntegratedGpu