Can't change dual monitor sddm to single monitor

Issues & Assistance KDE
, , ,
1

Sorry if this has been asked before but i’ve searched through the forums and have found nothing that has worked in my use case.

I currently have a 2 Monitor set-up (HDMI-2-A (VERTICAL), DP-3 (LANDSCAPE)) and would like for sddm to only appear on my main monitor (DP-3)

I’ve tried the basic apply plasma settings to sddm after disabling monitor, tried Xsetup in a number of different ways but to no avail. Tried disabling integrated graphics on the off chance that it was a weird Nvidia driver issue but nope.

Was hoping someone could give me a hand or point me in the right direction with this.

Thanks!

GARUDA-INXI

System:
Kernel: 6.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9d512a78-1a5d-4d0f-ba9e-8de2d43b986d rw rootflags=subvol=@ ...
acpi_enforce_resources=lax quiet loglevel=3
Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B650M AORUS ELITE AX v: x.x
serial: <superuser required> uuid: <superuser required> Firmware: UEFI
vendor: American Megatrends LLC. v: F33 date: 03/12/2025
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MCP arch: Zen 5 gen: 5
level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
model-id: 0x44 (68) stepping: 0 microcode: 0xB404023
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 5188 min/max: 603/5272 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 5188 2: 5188 3: 5188
4: 5188 5: 5188 6: 5188 7: 5188 8: 5188 bogomips: 75054
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: Gigabyte driver: nvidia
v: 580.105.08 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-3,HDMI-A-2 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2208 class-ID: 0300
Device-2: Elgato Systems GmbH Game Capture HD60 S+
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1:3 chip-ID: 0fd9:006b
class-ID: 0102 serial: <filter>
Device-3: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.2.1.1:7
chip-ID: 1532:0e05 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
d-rect: 5360x2520 display-ID: 0
Monitor-1: DP-3 pos: bottom-l model: Samsung Odyssey G85SB
serial: <filter> built: 2022 res: mode: 3440x1440 hz: 175 scale: 100% (1)
dpi: 108 gamma: 1.2 size: 810x350mm (31.85x13.94") diag: 883mm (34.8")
modes: max: 3440x1440 min: 640x480
Monitor-2: HDMI-A-2 pos: top-right model: AOC 27B2 serial: <filter>
built: 2021 res: mode: 1920x1080 hz: 60 scale: 178% (1.78) to: 1080x1920
dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
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: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2
memory: 11.72 GiB display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 19 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 3080 Ti driver: nvidia v: 580.105.08 device-ID: 10de:2208
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.6 256 bits)
driver: mesa llvmpipe v: 25.3.1-arch1.2 (LLVM 21.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl,nvidia-smi
wl: wayland-info,wlr-randr x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 10:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: Elgato Systems GmbH Game Capture HD60 S+
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1:3 chip-ID: 0fd9:006b
class-ID: 0102 serial: <filter>
Device-4: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.2.1.1:7
chip-ID: 1532:0e05 class-ID: 0102
Device-5: Audio-Technica AT2020USB+
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 7-1.2.1.2:8 chip-ID: 0909:001c class-ID: 0300
API: ALSA v: k6.17.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.4.9 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 RTL8852CE PCIe 802.11ax Wireless Network
driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: e000 bus-ID: 07:00.0 chip-ID: 10ec:c852 class-ID: 0280
IF: wlp7s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 08:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 0bda:0852
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 3.68 TiB used: 241.52 GiB (6.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK51.2 temp: 48.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 043 scheme: GPT
Partition:
ID-1: / raw-size: 1.41 TiB size: 1.41 TiB (100.00%) used: 96.32 GiB (6.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 31.5 MiB (32.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-4: /var/log raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-5: /var/tmp raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.95 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.1 C mobo: 40.5 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.95 GiB used: 5.2 GiB (16.8%)
Processes: 344 Power: uptime: 26m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.33 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: 1912 pm: pacman pkgs: 1903 libs: 500 tools: octopi,pamac,paru
pm: flatpak pkgs: 9 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash
v: 5.3.8 default: fish v: 4.2.1 running-in: konsole inxi: 3.3.40
Garuda (2.11.1-1):
System install date:     2025-11-20
Garuda release:          251103
Last full system update: 2025-12-10
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard
Windows dual boot:       Probably (Run as root to verify)
Failed units:
--- System Health Check Report ---
25/26 checks run in 0.40 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.

I feel like i should also add that whenever I use the ‘Log out’ feature on KDE, it goes to a black screen with the flashing text cursor and i can activate the terminal with CTRL+ALT+F2, which seems like it might be causing the DE to crash or something, and wont start back up with systemctl commands. Not sure if this may be related but i thought i would add this info in case it is.

2

Sorry, where is your garuda-inxi ? Without, no help is possible in your case.
The reason is : relevant info for Hardware, DE, etc is missing.

  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>), or put three tildes (~) above and below the text
7 Likes
3

I’m not sure this will be a complete solution, but I too have a dual-monitor setup, and I wanted to disable sddm greeter screen on the non-primary monitor - which sddm was treating as a mirror, not an extension. After some sleuthing, I found that the monitor settings for sddm are stored in: /var/lib/sddm/.config/kwinoutputconfig.json

In my specific use case - I had to change two settings to effectively “turn off” the secondary monitor. I had to find the “outputs” section of the json file and then change the "enabled": true, to "enabled": false, and then "priority": 0, to "priority": -1,.

After a save and reboot, my secondary monitor remains powered but shows a black screen until I sign in. Hopefully you can do a little bit of digging around (AND SAVE BACKUPS) before you tweak your changes. See if this helps!

2 Likes
4

Just checked the file and unfortunately its already configured like that but i’ve still got the same issue :frowning:

5

Sorry first post didn’t realise, here it is

System:
Kernel: 6.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9d512a78-1a5d-4d0f-ba9e-8de2d43b986d rw rootflags=subvol=@ ...
acpi_enforce_resources=lax quiet loglevel=3
Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B650M AORUS ELITE AX v: x.x
serial: <superuser required> uuid: <superuser required> Firmware: UEFI
vendor: American Megatrends LLC. v: F33 date: 03/12/2025
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MCP arch: Zen 5 gen: 5
level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
model-id: 0x44 (68) stepping: 0 microcode: 0xB404023
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 5188 min/max: 603/5272 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 5188 2: 5188 3: 5188
4: 5188 5: 5188 6: 5188 7: 5188 8: 5188 bogomips: 75054
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: Gigabyte driver: nvidia
v: 580.105.08 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-3,HDMI-A-2 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2208 class-ID: 0300
Device-2: Elgato Systems GmbH Game Capture HD60 S+
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1:3 chip-ID: 0fd9:006b
class-ID: 0102 serial: <filter>
Device-3: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.2.1.1:7
chip-ID: 1532:0e05 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
d-rect: 5360x2520 display-ID: 0
Monitor-1: DP-3 pos: bottom-l model: Samsung Odyssey G85SB
serial: <filter> built: 2022 res: mode: 3440x1440 hz: 175 scale: 100% (1)
dpi: 108 gamma: 1.2 size: 810x350mm (31.85x13.94") diag: 883mm (34.8")
modes: max: 3440x1440 min: 640x480
Monitor-2: HDMI-A-2 pos: top-right model: AOC 27B2 serial: <filter>
built: 2021 res: mode: 1920x1080 hz: 60 scale: 178% (1.78) to: 1080x1920
dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
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: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2
memory: 11.72 GiB display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 19 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 3080 Ti driver: nvidia v: 580.105.08 device-ID: 10de:2208
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.6 256 bits)
driver: mesa llvmpipe v: 25.3.1-arch1.2 (LLVM 21.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl,nvidia-smi
wl: wayland-info,wlr-randr x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 10:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: Elgato Systems GmbH Game Capture HD60 S+
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1:3 chip-ID: 0fd9:006b
class-ID: 0102 serial: <filter>
Device-4: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.2.1.1:7
chip-ID: 1532:0e05 class-ID: 0102
Device-5: Audio-Technica AT2020USB+
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 7-1.2.1.2:8 chip-ID: 0909:001c class-ID: 0300
API: ALSA v: k6.17.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.4.9 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 RTL8852CE PCIe 802.11ax Wireless Network
driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: e000 bus-ID: 07:00.0 chip-ID: 10ec:c852 class-ID: 0280
IF: wlp7s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 08:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 0bda:0852
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 3.68 TiB used: 241.52 GiB (6.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK51.2 temp: 48.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 043 scheme: GPT
Partition:
ID-1: / raw-size: 1.41 TiB size: 1.41 TiB (100.00%) used: 96.32 GiB (6.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 31.5 MiB (32.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-4: /var/log raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-5: /var/tmp raw-size: 1.41 TiB size: 1.41 TiB (100.00%)
used: 96.32 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.95 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.1 C mobo: 40.5 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.95 GiB used: 5.2 GiB (16.8%)
Processes: 344 Power: uptime: 26m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.33 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: 1912 pm: pacman pkgs: 1903 libs: 500 tools: octopi,pamac,paru
pm: flatpak pkgs: 9 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash
v: 5.3.8 default: fish v: 4.2.1 running-in: konsole inxi: 3.3.40
Garuda (2.11.1-1):
System install date:     2025-11-20
Garuda release:          251103
Last full system update: 2025-12-10
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard
Windows dual boot:       Probably (Run as root to verify)
Failed units:
--- System Health Check Report ---
25/26 checks run in 0.40 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.
6

Please, post full garuda-inxi.

7

should be the whole thing there

1 Like
8

Really important for this motherboard is to make a bios update. Version 37 is out.

https://www.gigabyte.com/Motherboard/B650M-AORUS-ELITE-AX-rev-10-11/support#dl

After this, think on the right bios settings UEFI not CSM; AHCI not Raid; Secure - Fastboot off, Resizebar enabled. If windows is installed pls also there fastboot off.

N

Not shure but for this cpu the bogomips are very low. (my mind)
Default like this

bogomips: 150113

I “see” also only 8 kernels → default 16.

perhaps as info + help

My knowledge to “ctrl+alt+ F2” is wrong, if “ctrl+alt+F3” and higher"

2 Likes
9

You may wish to look through the rest of the settings and try to tweak each setting until something does what you want it to do. If you’d like to post the output of the config file to https://bin.garudalinux.org/ and share the link, I’d be happy to look through it and see if I identify anything that could be helpful.

2 Likes
10

8 kernels? :astonished_face: :grinning_face_with_smiling_eyes:

The CPU has 8 cores and 16 threads, but SMT seems to be disabled in the BIOS:

That explains the meagre bogomips.

3 Likes
11

Just checked and SMT is on Auto

12

Thanks, just checked now. Almost all the bios settings were configured that way except for secure boot which I’ve disabled now too. SMT was also on auto (no enabled option)
How do I investigate the Kernels? (8/16)

13

https://bin.garudalinux.org/?b9a4889c0ff29356#HnVmBZvurdJZWSJXvpfiqnJshvWcWjEwQcVRZxpbQQjY

14

Let’s see if I’m interpreting the json correctly. The system is detecting 3 display outputs:

  1. HDMI-A-2 with an EDID of “AOC 9986 19342 47 2021 0”, dimensions of 1920x1080
  2. DP-1 with an EDID of “SAM 29426 0 8 2022 0”, dimensions of 3440x1440
  3. Another DP-1(which seems odd, not sure) with an EDID of “SAM 29428 0 8 2022 0” same dimensions as #2 above.

#2 and #3 have 2 unique UUIDs as well. Not sure why it’s showing that the third monitor is plugged into the same display port as the second monitor.

That said, the next set of 3 “outputs” refer to the same displays in the same order as above, so, first, you’ll need to identify which of the monitors you actually want “off” when the SDDM greeter loads, then change the "enabled": parameter to false on the one you want to have “off”, and then also change the "priority": value to -1. You will note, however, that each display has TWO sets of “outputs”, I believe you need to make these changes to the first of the two for each set.

In the output you shared, it seems like you applied these changes to the first monitor, the AOC connected to HDMI-A-2. Is this monitor not “off” when you reboot and the SDDM first loads? I also don’t see configuration settings for the 3rd monitor in the “outputs” section - so not sure what’s up with that.

Perhaps someone more versed in this configuration file can add their thoughts to this…

Edit: Curious, what happens when you run xrandr --query in terminal? Can you post the output?

15

Yeah despite those settings both monitors still display the login, another odd thing is the AOC monitor is in portrait mode but when in login it is in landscape. Not sure if this is regular behavior or something normal. I also obviously only have the SAMSUNG monitors so I have no idea why it also appears twice. Could it be ever since i changed the monitor from DP-3 to DP-1?

Here’s the

xrandr --query
Screen 0: minimum 16 x 16, current 4520 x 1920, maximum 32767 x 32767
DP-1 connected primary 3440x1440+0+228 (normal left inverted right x axis y axis) 810mm x 350mm
3440x1440    174.91*+
1920x1440    174.89
1600x1200    174.78
1440x1080    174.83
1400x1050    174.81
1280x1024    174.81
1280x960     174.83
1152x864     174.80
1024x768     174.65
800x600      174.74
640x480      174.69
320x240      174.26
1920x1200    174.84
1680x1050    174.76
1440x900     174.75
1280x800     174.81
1152x720     174.79
960x600      174.57
928x580      174.52
800x500      174.50
768x480      174.34
720x480      174.75
640x400      174.52
320x200      172.22
2560x1440    174.89
2048x1152    174.92
1920x1080    174.80
1600x900     174.80
1368x768     174.62
1280x720     174.89
1024x576     174.79
864x486      174.55
720x400      174.58
640x350      174.17
HDMI-A-2 connected 1080x1920+3440+0 right (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080     59.96*+
1440x1080     59.99
1400x1050     59.98
1280x1024     59.89
1280x960      59.94
1152x864      59.96
1024x768      59.92
800x600       59.86
640x480       59.38
320x240       59.29
1680x1050     59.95
1440x900      59.89
1280x800      59.81
1152x720      59.97
960x600       59.63
928x580       59.88
800x500       59.50
768x480       59.90
720x480       59.71
640x400       59.95
320x200       58.14
1600x900      59.95
1368x768      59.88
1280x720      59.86
1024x576      59.90
864x486       59.92
720x400       59.27
640x350       59.28
16

Xrandr is not function on wayland, consider this.

17

Can you try creating a launch script in

/usr/share/sddm/scripts/Xsetup

I did this to have my SDDM show the left monitor rotated. You may be able to do the same but to disable a monitor instead. See the thread gampel linked for the full description.

Check the ArchWiki SDDM page as this helped me with the above solution

18

I asked for the output more as a sanity check on the detected monitors - I imagine xrandr would still be useful and accurate for that, despite running a Wayland DE?

19

xrandr itself has been replaced by compositor-specific tools like kscreen-doctor and the GUI system settings for your desktop environment, so it will be up to your desktop environment to provide tools to do exactly what "example xrandr" --brightness has done in the past. (my knowledge)

20

Cool, TIL that xrandr --query is replaced by kscreen-doctor --outputs for similar output information. Thank you!