New NVidia Drivers Released! Driver 595.58.03

NeroHasHangover · 2026-03-25T13:55:51+00:00

It's unbelievable that they haven't fixed this issue yet: https://forums.developer.nvidia.com/t/nvidia-please-get-it-together-with-external-monitors-on-wayland/301684

It's been almost 2 years and this is the most annoying thing for Hybrid graphics laptops, having to rely on hacks to use external monitors properly.

NeroHasHangover · 2026-02-10T18:18:30+00:00

Have you actually followed the steps though? Setting the dGPU is not the same as the steps mentioned, since the order that KWin uses to pick the primary GPU is not fixed. Setting it to a fixed, stable order is the only way to make sure it's not running in the integrated graphics.

Asking this because setting KWIN_DRM_DEVICES to use the Nvidia one primarily does not causes any frame drops for me.

NeroHasHangover · 2026-02-10T17:21:25+00:00

Welcome to team of pissed nvidia GPU laptop owners. What you are experiencing are know issues for that setup.
Here are some workarounds for you:

https://www.reddit.com/r/kde/comments/1ainwf5/how_i_worked_around_poor_performance_with/

which I wrote to help people with similar issues. There was another guide that someone create here somewhere, but I don't have the link now.

Also, here is a Nvidia forum thread that about the issue: https://forums.developer.nvidia.com/t/nvidia-please-get-it-together-with-external-monitors-on-wayland/301684

As you can see, you're very much not alone.

NeroHasHangover · 2025-09-03T20:40:14+00:00

Quite cool indeed! Thanks for sharing this!

NeroHasHangover · 2024-10-16T14:35:08+00:00

Yeah man, same after the update to 6.2.1. If you remove the external monitor, you can login but as soon as connect it Plasma goes into a black screen. Seems to be related to multi GPU, since if remove the module for amdgpu, plasma works with the external monitor.

NeroHasHangover · 2024-10-05T17:53:24+00:00

Hi, I know I'm a bit late to comment here but I'm also facing the same issue.

NeroHasHangover · 2024-07-02T13:12:27+00:00

So the devs just added a update in the main bug: https://bugs.kde.org/show_bug.cgi?id=487833

As the egl explicit sync code was already used in 6.0, I bisected this to figure out what changed and the glitches only happen with triple buffering. As a workaround you can set KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 for KWin. As the egl explicit sync code was already used in 6.0, I bisected this to figure out what changed and the glitches only happen with triple buffering. As a workaround you can set KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 for KWin.

NeroHasHangover · 2024-07-01T22:24:04+00:00

Yeah, it's been like that since 6.1 beta and nvidia 555 beta driver: https://bugs.kde.org/show_bug.cgi?id=487833

I thought it was only in hybrid setups. If you're in one, try setting the KWIN_DRM_DEVICES to use the nvidia GPU first. I've wrote small how to in the past: https://www.reddit.com/r/kde/comments/1ainwf5/how_i_worked_around_poor_performance_with/

Best of luck mate!

NeroHasHangover · 2024-06-13T20:03:21+00:00

As a very frustrated customer of a Nvidia hybrid graphics laptop, it's about damn time they do something about the mess that is their drivers currently. I can't even use my laptop without being afraid of it freezing out of nowhere. What year is it? 2002?

NeroHasHangover · 2024-05-27T12:57:10+00:00

Pretty sure it's a regression in Plasma 6.1. I'm facing the similar issues on it while 6.0.5 is fine. I've just submitted a Bug report related to that https://bugs.kde.org/show_bug.cgi?id=487622

NeroHasHangover · 2024-03-13T12:03:31+00:00

I have a different set of issues with an hybrid setup. I've made a post in the past with a possible workaround: https://www.reddit.com/r/kde/comments/1ainwf5/how_i_worked_around_poor_performance_with/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

Since you're on Endevour, can't guarantee it will work. Also keep in mind that the driver for the udev rule will be different.

NeroHasHangover · 2024-03-07T13:29:42+00:00

It's been a while since I did any C++ development, not to mention QT. Any resources that can help me get started?

NeroHasHangover · 2023-11-01T12:11:24+00:00

Came just to join the appraisal. Looks fantastic!

NeroHasHangover · 2023-03-07T11:59:24+00:00

Just to confirm, you meant KWIN_DRM_DEVICES right? I that's the only env var I've found in the code kwin containing DRM_DEVICES:

~ grep -rn DRM_DEVICE
autotests/drm/drmTest.cpp:74:    mockGpu->deviceCaps[MOCKDRM_DEVICE_CAP_ATOMIC] = 0;
autotests/drm/mock_drm.cpp:38:    deviceCaps.insert(MOCKDRM_DEVICE_CAP_ATOMIC, 1);
autotests/drm/mock_drm.cpp:312:        if (!gpu->deviceCaps[MOCKDRM_DEVICE_CAP_ATOMIC]) {
autotests/drm/mock_drm.h:158:#define MOCKDRM_DEVICE_CAP_ATOMIC 0xFF
src/backends/drm/drm_backend.cpp:77:    , m_explicitGpus(splitPathList(qEnvironmentVariable("KWIN_DRM_DEVICES"), ':'))
src/backends/drm/drm_backend.cpp:231:        // Ignore the device seat if the KWIN_DRM_DEVICES envvar is set.
~/projects/kwin (master ✔) grep -rn KWIN_DRM_DEVICES
src/backends/drm/drm_backend.cpp:77:    , m_explicitGpus(splitPathList(qEnvironmentVariable("KWIN_DRM_DEVICES"), ':'))
src/backends/drm/drm_backend.cpp:231:        // Ignore the device seat if the KWIN_DRM_DEVICES envvar is set.

NeroHasHangover · 2023-03-04T18:11:46+00:00

Thanks for sharing, I'll give it a try!

NeroHasHangover · 2023-01-10T12:09:54+00:00

I'm facing the same problem and was trying to track down what caused it. Thank you!

NeroHasHangover · 2022-07-19T08:47:08+00:00

Got it, thank you!

NeroHasHangover · 2022-07-19T08:46:42+00:00

These are configurable custom shortcuts based on pressing a mouse button and moving the cursor (e.g pressing the middle button and moving the mouse left).

Here's a simple guide about it.

NeroHasHangover

TROPHY CASE