Forum / NoMachine for Linux / Kubuntu 26.04 black screens when multiple display cards with monitors
Tagged: Wayland Error
- This topic has 15 replies, 3 voices, and was last updated 7 hours, 31 minutes ago by
Britgirl.
-
AuthorPosts
-
May 15, 2026 at 08:20 #55976
timokParticipantI have Kubuntu 26.04 with two NVIDIA RTX 2000 display cards. Each display card has 4 display cards. Kubuntu desktop shows all 8 monitors OK. I have installed latest 9.7.2 NoMachine into computer and to client. Client is Ubuntu 24.04.
When I connect to the computer, it shows all 8 screens as black. I switched hardcode acceleration off. Still black. I tried setting GPULoadBalancingAlgorithm to load-based and GPU0. Still black.
I removed the monitors on second RTX 2000: now 4 monitors show OK.
Should NoMachine work with this setup?
Any hints?
May 15, 2026 at 09:11 #55978
timokParticipantThe NVIDIA driver version is 595.58.03
May 16, 2026 at 17:00 #55988
everstarParticipantThis looks to be a Wayland/Nvidia issue, even Ubuntu latest version runing Wayland gets the black lifeless screen.
May 18, 2026 at 09:55 #55998
timokParticipantWith NoMachine we can view 4 monitors fine, connected to first display card. But if we connect monitors also to second card, all screens are viewed as black.
P.S.
Fixing the typo in original post:
Each display card has 4 display cards. – >Each display card has 4 monitor outputs.May 21, 2026 at 18:14 #56026
BritgirlKeymasterCan you send us the logs from the server side machine? On the server, go to Server > Security > Take logs, save the file and send that to us. You can submit it here or if you prefer, you can send it to forum[at]machine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
May 22, 2026 at 07:58 #56031
timokParticipantHere are the logs.
Watch the logs just for today (22nd of May)
The sequence made today is
- The computer had 8 monitors connected. NoMachine connection was made. 8 black screens visible.
- The 4 monitors in second display card were disconnected. New connection. 4 black screens visible.
- Computer was booted. New connection. 4 displays shown correctly.
- One monitor was connected to second display card. No boot. New connection made. 5 black screens are shown.
Attachments:
May 25, 2026 at 11:25 #56060
BritgirlKeymasterCan you send us the server logs from the server side? On the server, go to Server > Security > Take logs, save the file and send that to us.
May 25, 2026 at 11:43 #56061
timokParticipantThe logs were in previous post. Is there some problem with those, do they contain correct information?
May 25, 2026 at 13:03 #56062
everstarParticipantThe new Nvidia drivers resolve this issue.
May 25, 2026 at 18:26 #56066
BritgirlKeymasterThe logs were in previous post. Is there some problem with those, do they contain correct information?
Timok, you attached the player logs 🙂 We need the server-side logs, the logs taken from the machine you are connecting to (Settings > Server > Security > button Take logs)
May 25, 2026 at 19:55 #56067
everstarParticipantThe fix is to upgrade your NVIDIA drivers, there is a new release out. Totally fixes this!
May 26, 2026 at 09:17 #56069
timokParticipantHere are the server logs
The sequence made today (May 26) was:
- The computer had 8 monitors connected. NoMachine connection was made. 8 black screens visible.
- The 4 monitors in second display card were disconnected. New connection. 4 black screens visible.
- Computer was booted. New connection. 4 displays shown correctly.
- One monitor was connected to second display card. No boot. New connection made. 5 black screens are shown.
Attachments:
May 27, 2026 at 09:46 #56078
timokParticipantThe fix is to upgrade your NVIDIA drivers, there is a new release out. Totally fixes this!
The driver is currently 595.71.05. I tried to run update/upgrade. The upgrade fails on packages nvidia-dkms-595-open and linux-image-7.0.0-15-generic. Full log below. The computer has Kubuntu 26.04 with all other updates. It has secure boot and hard drive encryption on. I do not know if that is related.
sudo apt upgradeGet another security update through Ubuntu Pro with 'esm-apps' enabled:
libopenexr-3-1-30
Learn more about Ubuntu Pro at https://ubuntu.com/pro
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
2 not fully installed or removed.
Space needed: 0 B / 914 GB available
Continue? [Y/n]
Setting up nvidia-dkms-595-open (595.71.05-0ubuntu0.26.04.1)…
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Removing old nvidia/595.71.05 DKMS files...
Module nvidia/595.71.05 for kernel 7.0.0-14-generic (x86_64):
Before uninstall, this module version was ACTIVE on this kernel.
Deleting /lib/modules/7.0.0-14-generic/updates/dkms/nvidia.ko.zst
Deleting /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-modeset.ko.zst
Deleting /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-drm.ko.zst
Deleting /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-uvm.ko.zst
Deleting /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod... done.
Deleting module nvidia/595.71.05 completely from the DKMS tree.
Loading new nvidia/595.71.05 DKMS files...
Building for 7.0.0-14-generic and 7.0.0-15-generic
Building for architecture x86_64
Building initial module nvidia/595.71.05 for 7.0.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch thunk-Kbuild.patch... done.
Building module(s)........ done.
Signing module /var/lib/dkms/nvidia/595.71.05/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/595.71.05/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/595.71.05/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/595.71.05/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/595.71.05/build/nvidia-peermem.ko
Installing /lib/modules/7.0.0-14-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/7.0.0-14-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod... done.
Building initial module nvidia/595.71.05 for 7.0.0-15-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch thunk-Kbuild.patch... done.
Building module(s).....(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=7.0.0-15-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/7.0.0-15-generic/build LD=/usr/bin/ld.bfd CO
NFIG_X86_KERNEL_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fatal() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-595-open.0.crash'
Error! Bad return status for module build on kernel: 7.0.0-15-generic (x86_64)
Consult /var/lib/dkms/nvidia/595.71.05/build/make.log for more information.
dpkg: error processing package nvidia-dkms-595-open (--configure):
old nvidia-dkms-595-open package postinst maintainer script subprocess failed with exit status 10
Setting up linux-image-7.0.0-15-generic (7.0.0-15.15)…
Processing triggers for initramfs-tools (0.151ubuntu1)…
update-initramfs: Generating /boot/initrd.img-7.0.0-15-generic
Processing triggers for linux-image-7.0.0-15-generic (7.0.0-15.15)…
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/595.71.05 for kernel 7.0.0-15-generic (x86_64)
Applying patch thunk-Kbuild.patch... done.
Building module(s).....(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=7.0.0-15-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/7.0.0-15-generic/build LD=/usr/bin/ld.bfd CO
NFIG_X86_KERNEL_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fatal() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-595-open.0.crash'
Error! Bad return status for module build on kernel: 7.0.0-15-generic (x86_64)
Consult /var/lib/dkms/nvidia/595.71.05/build/make.log for more information.
Autoinstall on 7.0.0-15-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-7.0.0-15-generic (--configure):
old linux-image-7.0.0-15-generic package postinst maintainer script subprocess failed with exit status 1
Errors were encountered while processing:
nvidia-dkms-595-open
linux-image-7.0.0-15-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)May 29, 2026 at 08:44 #56092
BritgirlKeymasterIt looks like a drivers issue and very similar to this problem:
Updating the drivers would be the solution as suggested by everstar. If that’s not possible, you could try changing the screen capture mode by setting this key in node.cfg:
WaylandModes drm,egl,compositorJune 1, 2026 at 06:04 #56097
timokParticipantThe update/upgrade now succeeds without errors. NoMachine has been updated to latest version.
The the Nvidia driver is at latest version (595.71.05) available for this graphic card (RTX 2000).I tried the WaylandModes as suggested, no impact. All 8 displays still black.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.
