Hi @agoins , that’s a pretty valid question. I had already tested it a while ago, but it surely deserved a fresh test. I removed all nvidia packages (dnf remove \*nvidia\*) and did some further testing.
First of all, I went through BIOS settings looking for something that could influence boot behavior. Couldn’t find any entry explicitly related to iGPU x dGPU, but I did turn off fastboot, which was enabled (not sure if it was related, but wouldn’t hurt to try).
Here’s what I found out while running on nouveau:
- I can boot on battery. However, I had to set
GSK_RENDERER=nglon/etc/environmentin order to be able to run GNOME apps (I use it set tovulkanwith the Nvidia driver) - whenever I boot on battery, GNOME shows internal display with its refresh rate fixed to 60Hz. If I plug an external monitor, internal display is labeled ‘unknown 23"’; If I boot while charging, it is properly recognized and listed as “Built-in display”, and it offers all refresh rates way up to its max 144Hz.
I then reinstalled nvidia drivers from Negativo17.org, and tried to repeat the process. I still cannot boot on battery without an external monitor plugged. When I boot on battery with an external display plugged, it also is unable to properly detect the internal display, showing the same ‘unknown 23"’ label and fixing the refresh rate to 60Hz.
On both cases (nouveau and nvidia), booting on battery with an external monitor plugged sets it as primary (login fields are shown on it). Once I log in, though, GNOME preferences are applied and the internal display appears as primary. On the other hand, booting while charging sets the built-in display as primary right from the start.
This is all pretty messed up, I can’t seem to make any sense out of it. Since both nvidia and nouveau share this same weird behavior, I’m wondering if this couldn’t be a kernel (or hardware) issue. If anyone has any clue or suggestion on additional tests I could make, it will be much welcome…