I’m using a KVM switch so I can use my home PC and my work laptop with the same monitor (connected via Displayport). One annoying problem is, that I can’t boot up Manjaro while the monitor is switched to the work laptop. If I do this the monitor will stay black when switching to Manjaro and I haven’t found any way to wake it (If I boot into Windows instead this is no problem, it will just detect the monitor whenever I switch to the machine). Do you know of any way to fix this? Any way that Manjaro will detect an monitor that wasn’t available during boot?
Hi @AllesMeins, unfortunately I don’t have a KVM setup to test this (or Windows, either).
However, it will help if you post your inxi -zv8 output so people who do have such will be in a better position to assist. (Please remember to use proper code formatting).
Cheers! 
Sure thing:
inxi -zv8 ✔
System:
Kernel: 6.18.18-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
root=/dev/mapper/VolumeGroup-root rw systemd.show_status=1 apparmor=1
security=apparmor udev.log_priority=5 intel_iommu=on
vfio-pci.ids=10de:21c4,10de:1aeb,10de:1aec,10de:1aed kvm.ignore_msrs=1
Desktop: KDE Plasma v: 6.5.6 tk: Qt v: N/A info: frameworks v: 6.24.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: H170-PRO v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
Firmware: UEFI vendor: American Megatrends v: 3805 date: 05/16/2018
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 64 GiB available: 62.72 GiB used: 41.92 GiB (66.8%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: None
max-module-size: 16 GiB note: est.
Device-1: DIMM_A1 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-2: DIMM_A2 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-3: DIMM_B1 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-4: DIMM_B2 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3712 min/max: 800/4000 scaling: driver: intel_pstate
governor: powersave cores: 1: 3712 2: 3712 3: 3712 4: 3712 5: 3712 6: 3712
7: 3712 8: 3712 bogomips: 54398
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsa status: Not affected
Type: tsx_async_abort mitigation: TSX disabled
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Micro-Star MSI
driver: nvidia v: 575.64.05 alternate: nouveau,nova_core,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
speed: 8 GT/s lanes: 4 ports: active: none off: DP-1 empty: HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:1d01 class-ID: 0300
Device-2: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Gigabyte
driver: vfio-pci v: N/A alternate: nouveau,nova_core,nvidia_drm,nvidia
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 08:00.0 chip-ID: 10de:21c4 class-ID: 0300
Device-3: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10.1.2:12
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x400mm (27.64x15.75")
s-diag: 808mm (31.81")
Monitor-1: DP-1 mapped: DP-0 note: disabled model: AOC AG326UD
serial: <filter> built: 2025 res: mode: 3840x2160 hz: 60 scale: 100% (1)
dpi: 140 gamma: 1.2 chroma: red: x: 0.671 y: 0.325 green: x: 0.294
y: 0.620 blue: x: 0.141 y: 0.051 white: x: 0.314 y: 0.329
size: 699x395mm (27.52x15.55") diag: 803mm (31.6") ratio: 16:9
modes: 3840x2160, 2560x1440, 1920x1080, 1280x1024, 1280x720, 1024x768,
800x600, 720x576, 720x480, 640x480
EDID-Warnings: 1: parse_edid: unknown tag 112
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.05
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GT 1030/PCIe/SSE2
memory: 1.95 GiB
API: Vulkan v: 1.4.341 layers: 8 device: 0 type: discrete-gpu
name: NVIDIA GeForce GT 1030 driver: nvidia v: 575.64.05
device-ID: 10de:1d01 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio
vendor: ASUSTeK H110I-PLUS driver: snd_hda_intel v: kernel
alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403
Device-2: NVIDIA GP108 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4
bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403
Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK CMI8786
driver: snd_oxygen v: kernel bus-ID: 03:04.0 chip-ID: 13f6:8788
class-ID: 0401
Device-4: NVIDIA TU116 High Definition Audio vendor: Gigabyte
driver: vfio-pci alternate: snd_hda_intel pcie: gen: 1 speed: 2.5 GT/s
lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1
chip-ID: 10de:1aeb class-ID: 0403
Device-5: Generalplus USB Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-10.1.1.1:13 chip-ID: 1b3f:2008 class-ID: 0300
Device-6: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10.1.2:12
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
API: ALSA v: k6.18.18-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.6.2 status: off with: wireplumber status: active
tools: pw-cli,wpctl
Server-4: PulseAudio v: 17.0-98-gb096 status: active with: pulseaudio-alsa
type: plugin tools: pacat,pactl
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: c000 bus-ID: 07:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: br0 state: down mac: <filter>
IF-ID-2: virbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-3: virbr1 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-4: virbr2 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IF-ID-5: virbr3 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-6: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
IF-ID-7: vnet1 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
IF-ID-8: vnet2 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
IF-ID-9: vnet3 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
Info: services: httpd, NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: Unable to run lvs. Root privileges required.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 9.1 TiB used: 3.77 TiB (41.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM000-1F2168
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: CC54 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 2TB
size: 1.82 TiB 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/sdc maj-min: 8:32 vendor: Seagate model: ST4000DM000-1F2168
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: CC54 scheme: GPT
Optical-1: /dev/sr0 vendor: ASUS model: BC-12D2HT rev: 1.00
dev-links: cdrom
Features: speed: 1 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
ID-1: / raw-size: 180 GiB size: 176.11 GiB (97.84%) used: 68.37 GiB (38.8%)
fs: ext4 dev: /dev/dm-1 maj-min: 253:1 mapped: VolumeGroup-root label: N/A
uuid: N/A
ID-2: /boot/efi raw-size: 401 MiB size: 400.2 MiB (99.79%)
used: 340 KiB (0.1%) fs: vfat dev: /dev/sdb2 maj-min: 8:18 label: N/A
uuid: 7B90-C820
ID-3: /home raw-size: 1.28 TiB size: 1.26 TiB (98.35%)
used: 996.06 GiB (77.3%) fs: ext4 dev: /dev/dm-0 maj-min: 253:0
mapped: VolumeGroup-home label: N/A uuid: N/A
ID-4: /home/<filter>/backups raw-size: 2.31 TiB size: 2.27 TiB (98.39%)
used: 1.48 TiB (65.2%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: Backup
uuid: 6a4a8faf-3b9d-435e-ac58-8f7ad273b102
ID-5: /run/media/VolumeGroups/downloads raw-size: 1.91 TiB
size: 1.88 TiB (98.42%) used: 1.11 TiB (59.0%) fs: ext4 dev: /dev/dm-4
maj-min: 253:4 mapped: VolumeGroup3-downloads label: N/A uuid: N/A
ID-6: /run/media/VolumeGroups/server raw-size: 437.62 GiB
size: 430.56 GiB (98.39%) used: 33.82 GiB (7.9%) fs: ext4 dev: /dev/dm-2
maj-min: 253:2 mapped: VolumeGroup2-server label: N/A uuid: N/A
ID-7: /run/media/VolumeGroups/videos raw-size: 927.73 GiB
size: 912.1 GiB (98.31%) used: 63.45 GiB (7.0%) fs: ext4 dev: /dev/dm-3
maj-min: 253:3 mapped: VolumeGroup2-videos label: N/A uuid: N/A
ID-8: /var/lib/libvirt/images/pool raw-size: 765.89 GiB
size: 765.89 GiB (100.00%) used: 48.24 GiB (6.3%) fs: btrfs dev: /dev/sda3
maj-min: 8:3 label: Linux_Gaming
uuid: be6df855-c77f-4f55-be81-8112fdf6b1cf
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 24.22 GiB used: 8.3 MiB (0.0%)
priority: -2 dev: /dev/sdb8 maj-min: 8:24 label: N/A
uuid: 9486fb7e-a0c2-42ae-ba32-171a0c28c293
Unmounted:
ID-1: /dev/sda1 maj-min: 8:1 size: 1007.01 GiB fs: ntfs label: Win_Daten
uuid: 32DB536A73855E46
ID-2: /dev/sdb1 maj-min: 8:17 size: 350 MiB fs: ntfs label: Recovery
uuid: C218DCFC18DCF101
ID-3: /dev/sdb6 maj-min: 8:22 size: 348.08 GiB fs: ntfs
label: Win_Programme uuid: 33B0857F0E3DF308
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 1-10:2 info: Terminus Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 1a40:0101 class-ID: 0900
Hub-3: 1-10.1:10 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 214b:7250 class-ID: 0900
Hub-4: 1-10.1.1:11 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 214b:7250 class-ID: 0900
Device-1: 1-10.1.1.1:13 info: Generalplus USB Audio Device type: audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 1b3f:2008 class-ID: 0300
Device-2: 1-10.1.1.4:14 info: SiGma Micro Hama ECM-500
type: mouse,keyboard driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 1c4f:00a2 class-ID: 0301
Device-3: 1-10.1.2:12 info: Microdia USB Live camera type: video,audio
driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Device-4: 1-10.2:4 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Device-5: 1-10.3:7 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Hub-5: 2-0:1 info: super-speed hub ports: 8 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A gpu: nvidia temp: 44 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 35%
Repos:
Packages: 2129 pm: pacman pkgs: 2127 libs: 432 tools: octopi,pamac,yay
pm: flatpak pkgs: 2
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
2: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
3: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
4: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
5: https://manjaro.ynh.ovh/stable/$repo/$arch
6: https://muug.ca/mirror/manjaro/stable/$repo/$arch
7: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
8: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 360
1: cpu: 172% command: qemu-system-x86_64 pid: 6834
mem: 32181.5 MiB (50.1%)
2: cpu: 47.1% command: firefox pid: 2840 mem: 889.5 MiB (1.3%)
3: cpu: 22.1% command: firefox pid: 3692 mem: 283.2 MiB (0.4%)
4: cpu: 14.9% command: qemu-system-x86_64 pid: 2166 mem: 3195.7 MiB (4.9%)
5: cpu: 4.8% command: ksgrd_network_helper pid: 1792 mem: 6.75 MiB (0.0%)
Memory top: 5 of 360
1: mem: 32181.5 MiB (50.1%) command: qemu-system-x86_64 pid: 6834
cpu: 172%
2: mem: 3195.7 MiB (4.9%) command: qemu-system-x86_64 pid: 2166 cpu: 14.9%
3: mem: 2044.0 MiB (3.1%) command: qemu-system-x86_64 pid: 1736 cpu: 3.1%
4: mem: 889.5 MiB (1.3%) command: firefox pid: 2840 cpu: 47.1%
5: mem: 694.0 MiB (1.0%) command: plasmashell pid: 1439 cpu: 2.1%
Info:
Processes: 360 Power: uptime: 54m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.94 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 259 default: graphical tool: systemctl
Compilers: clang: 22.1.1 gcc: 15.2.1 Shell: Zsh v: 5.9 default: Bash
v: 5.3.9 running-in: konsole inxi: 3.3.40
One word of explanation: I currently have two GPUs in my system (the second one is reserved for some virtual machines and not used for Manjaro) but the problem also existed when I had only one GPU installed.
unfortunately I don’t have a KVM setup to test this
Yeah, I realize that this is an unusual setup. One could probably emulate this by just unplugging the Displayport-cable during bootup, so the system doesn’t “see” the monitor.
1 Like
I see that you are running Plasma in an X11 session. Does the issue also occur in a Plasma Wayland session?
Plasma X11 -> Wayland instructions
You can change your Plasma session from X11 to Wayland by selecting the session type at the login screen (Wayland is now KDE’s default for Plasma).
If you have set up autologin to skip the password screen, you can change to a Wayland autologin session via Plasma’s System Settings.
For users who login via sddm, open System Settings → Colors & Themes (in the Appearance & Style section) → Login Screen (SDDM) → Behavior.
If using plasma-login-manager, then open System Settings → Login Screen (in the Security & Privacy section).
Change the session type to Plasma (Wayland), save the change, and log out. You will be on a Plasma Wayland session the next time you log in.
To see if your current session is running on X11 or Wayland, run the following command in a terminal:
echo $XDG_SESSION_TYPE
For those curious about how Wayland differs from X11:
1 Like
I loaded up a wayland session and did a reboot from there - the problem still occurred. However, as far as I understand changing the session does only influence what happens after I log-in, correct? But the problem already occurs on the login-screen (or even during later stages of the boot process).
It’s been a long time since I used a KVM switch, so I haven’t got anything solid for you.
You could try configuring xorg, but not sure if it’ll work nowadays (because of wayland).
Alternatively, if HDMI is an option you may or may not have better luck with it.
If you have multiple ports on the monitor and can switch between them, you could use a USB switch (or a KVM without the V). However you’d have to switch the monitor manually.
1 Like
I’m hazarding a guess that this is because the KVM switch doesn’t forward the monitor’s EDID signal to the PC when switched to the other input. Therefore, the PC doesn’t know the monitor exists at that point.
Does the laptop behave OK if you switch before booting Manjaro? 
Example: With my monitor (which is also a TV), if I have it in standby or on another input or a TV channel, the laptop I’m using still knows the monitor is there and won’t adjust display settings. I just need to select the PC input and the display is there. But if I unplug it, Plasma sees this and switches to another available display (in my case, the laptop screen).
I would have thought that physically plugging in or using the switch to connect would have the same effect though. Plasma should just detect and be able to use it? 
Yes, I think you’re on the right track here. The laptop behaves okay in all situations (but that is running windows). Plasma also behaves okay, if one monitor was present during boot, it also detects other displays if I connect them during usage. But at least one display has to be connected (or selected with the KVM-switch) during boot. It feels like otherwise the system just thinks: “Oh, no display connected, so I don’t have to care anymore”.
1 Like
I guess you tried switching betweeen Ctrl+Alt+F3, Ctrl+Alt+F2, Ctrl+Alt+F1 ?
If you have a KVM keyboard with laptop functions key combination may differ, eg. Ctrl+fn+Alt+F-key.
Mod edit: Consecutive posts merged.
I assume you are using GPU pass-through for virtualisation, and have your budget GPU on your host?
Why not switch it to the nouveau driver on the host.
If one thing can break things like this (other than this unknown KVM black box), it would be nvidia’s proprietary drivers. Especially for this chipset in particular.
Do you use your high performing GPU for only guests?
Or are you doing something different? Then this is something else entirely..
Yes, nothing - the monitor just stays in standby mode and doesn’t show any reaction at all.
It’s not a problem of the chipset - the same thing happens if I boot up one of the guests (with the newer GPU) without the monitor present. If the guest runs Linux I’m not able to get any picture if the monitor isn’t connected during boot, if the guest runs Windows 10 I can just switch to it at any time and I’ll get a picture.
As for nouveau, I can try this, but I’m pretty sure there was some reason why I det it up with the non-free drivers in the first place. Can’t remember why exactly, but usually I always try the free software first and only switch if there is some reason for it.
So that you are passing this to guests does change things.
Windows GPU drivers are built to survive display hotplug and power state changes. But Linux, at least when using GPU passthrough, cannot do this.
I could be wrong, but I’ve spent 5+ years on this. I have just learned to live with it.
I also have a Nvidia card I passthrough; it’s a different problem, but correlated.
I can always put my monitors to sleep in Windows guests with no hassle. But in Linux, it will crash, or do weird things, like forced 640x480 resolution with no way to go back but reboot.
1 Like
Would restarting the window manager (“systemctl restart sddm.service” via ssh or as a cron job) after establishing the monitor connection on the KVM device activate the graphical display?
Is this shown also with directly connected monitor? Can you exclude a cable problem (by swapping the displayport cables of the two computers for testing purposes)?
Mod edit: Consecutive posts merged.