The picture was generated using the GPU even though it was configured as an iGPU.
The picture was generated using the GPU even though it was configured as an iGPU.
Despite setting the "Initial Display Output" to IGFX in my BIOS, most displays still originate from the discrete GPU. This pattern repeats: after turning on the PC, I observe video coming through DisplayPort (the iGPU port) rather than HDMI (the port I normally use). I operate normally, reboot without switching back to HDMI, then power off and back on—after sleeping—I wake up with HDMI once more. Last night my dad tried a power meter he purchased; we connected it during a DP session, but after reconnecting to the wall it switched back to DisplayPort. I haven’t managed to reproduce this sequence.
For reference, I plan to rely on the iGPU as my main display so I can run Arch Linux daily and use Windows KVM with GPU Passthrough instead of switching between Windows and Arch. System details: Intel i7 12700k, Gigabyte Aorus Ultra z690, BIOS v24a, RAM Kingston Fury Beast 2x16 DDR5, Corsair RM 80+ gold 850W power supply, GPU Gigabyte 5600xt, 1TB Samsung 970 EVO Plus, 1TB SanDisk SSD.
It's generally not recommended to connect cables directly to both the motherboard and GPU without proper setup. Most systems rely on storage for booting, not the graphics card. This should work fine with laptops, but desktops usually require different configurations depending on the use case.
Probable assumption is that a complete power cut might have activated a consumer verification mode, letting the motherboard choose based on what’s connected. It seems the system assumed a GPU with a plugged-in device would work better, which is why it functioned as expected for you but not in your scenario. Typically outputs follow a priority sequence and different GPU configurations behave differently, so order isn’t always straightforward. Depending on your games, you might avoid using KVM entirely. Lutris and Proton often run non-native software, while Bottles offers another alternative.
The issue occurs during the POST phase, before GRUB or the Windows bootloader is initialized. I’m not sure how to summarize your initial comment, but I believe the iGPU functions similarly to a regular GPU. I know multi-monitor configurations use two GPUs, so I thought a similar approach could work with the iGPU. Thanks for clarifying.
Multi-monitor configurations rely on either the integrated graphics unit (iGPU) or a dedicated GPU. Using both isn't advised. When you have multiple monitors and a dedicated GPU, connect them together to that unit. The igpu tool is mainly for diagnosing issues if the dedicated GPU encounters problems.