Display Issue using both X11 and Wayland

I use 3 monitors with my PC and out of the blue only 2 will work. When I try to use Nvidia Server Settings to get third monitor to work in X11, it will ask me to save config to xorg.conf. which seems to be missing in all of my PCs and laptops running Garuda. Running Wayland doesn’t produce any positive results still down to two monitors and no options with NVidia Server settings. When using KDE to adjust monitor it produces an error. It does see the third monitor just can’t enable it.

Providing garuda-inxi:

╭─reggie@garudaK in ~
╰─λ garuda-inxi
System:
Kernel: 6.9.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d0fdb2ba-761e-49b0-a9ea-7bb74e789e50 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.2 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 4204 date: 02/24/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech K350 serial: <filter>
charge: 70% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 3999 high: 4003 min/max: 2200/4918 boost: disabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4000 2: 4000
3: 4000 4: 4000 5: 3999 6: 4000 7: 3987 8: 4000 9: 4003 10: 4000 11: 4000
12: 4000 13: 4000 14: 4000 15: 4000 16: 3998 17: 4000 18: 4000 19: 3999
20: 4000 21: 4000 22: 4000 23: 3999 24: 3996 bogomips: 191991
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: ASUSTeK
driver: nvidia v: 555.58.02 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 4
link-max: lanes: 16 ports: active: none off: DP-1,DVI-D-1,HDMI-A-1
empty: none bus-ID: 04:00.0 chip-ID: 10de:2187 class-ID: 0300
Device-2: Logitech BCC950 ConferenceCam
driver: hid-generic,usbhid,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 5-3.1:5 chip-ID: 046d:0837 class-ID: 0300
serial: <filter>
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 3840x1080
display-ID: 0
Monitor-1: DP-1 pos: right res: 1920x1080 size: N/A modes: N/A
Monitor-2: DVI-D-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
Monitor-3: HDMI-A-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: zink inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1650
SUPER/PCIe/SSE2 memory: 3.91 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1650 SUPER driver: nvidia v: 555.58.02 device-ID: 10de:2187
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4
link-max: lanes: 16 bus-ID: 04:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech BCC950 ConferenceCam audio
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-3.3:8 chip-ID: 046d:0838 class-ID: 0300
serial: <filter>
Device-4: Walmart AB13X Headset Adapter
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 7-4.4:6 chip-ID: 001f:0b21 class-ID: 0300
serial: <filter>
API: ALSA v: k6.9.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82571EB/82571GB Gigabit Ethernet D0/D1 driver: e1000e
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: f020 bus-ID: 09:00.0
chip-ID: 8086:105e class-ID: 0200
IF: enp9s0f0 state: down mac: <filter>
Device-3: Intel 82571EB/82571GB Gigabit Ethernet D0/D1 driver: e1000e
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: f000 bus-ID: 09:00.1
chip-ID: 8086:105e class-ID: 0200
IF: enp9s0f1 state: down mac: <filter>
Device-4: Realtek RTL8152 Fast Ethernet Adapter driver: r8152 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-4.1:4
chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
IF: enp11s0f3u4u1 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: Edimax Bluetooth Adapter driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-3:2 chip-ID: 7392:c611
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 3.64 TiB used: 553.78 GiB (14.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SFYRD2000G
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.6 temp: 37.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 553.78 GiB (29.7%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 553.78 GiB (29.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 553.78 GiB (29.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 553.78 GiB (29.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.71 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 54.6 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.71 GiB used: 9.26 GiB (14.8%)
Processes: 511 Power: uptime: 16m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.04 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 2137 pm: pacman pkgs: 2105 libs: 593 tools: gnome-software,
octopi, pamac, paru pm: flatpak pkgs: 32 Compilers: clang: 18.1.8
gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-05-21
Last full system update: 2024-07-06
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

Does anyone have an idea on this? FYI using a laptop running Garuda without NVidia seems to work on all 3 monitors via docking station. My only other option is to reseat the cables at this point.

I was gonna ask if this was laptop.
Do you want to run 3 external monitor alongside the internal screen. So 4 screens in total?

Some HW is not very well suited for the linux platform. This seems to be varying desktop support with Nvidia GPUs. Again , depends on the goal and the model. Nvidia GPUs are claimed to work well for AI specific applications.

Why not read about Nvidia history, how and why they have been behind on the Linux desktop platform?

It might be easier to run AMD GPU. I happened to run 3 monitors at some point. Worked fine.

Or upgrade to a better supported nvidia card. Do the research and decide for yourself.

Good luck!

No desktop and laptop strictly 3 monitors, also 3 monitors were running fine, not sure if recent update changed settings.

Tested with another distro via live USB and all 3 monitors are functional, so not sure where things went sideways. I may remove the NVIDIA driver to see if that helps and install the Open driver. If that works will need to evaluate if NVIDIA driver is the issue, If yes perhaps I try an older driver to see the outcome.

2 Likes

If the issue only occurs on the DVI port, then you are not the only one with the problem:

1 Like

Yes removing and reapplying NVidia driver did not fix. Wondering if I can go to an older driver. If yes I need to figure out how, don’t think there’s a list of drivers using the hardware tool.

Downgrading to NVIDIA 525.xx has fixed my issues. Hoping 560.xx will not be plagued with current bugs

1 Like