You are not logged in.
Pages: 1
Hi,
I've been having a strange issue for months now since installing Arch. When i cold boot into arch everything works fine but if I then reboot, there is no display during post or in grub. It will continue to boot without any display output until it reaches the Arch desktop then it works fine again.
This isn't a major issue but is annoying if I want to enter the uefi settings as I have to then power off the pc completely and cold boot again to regain video output during post/boot.
Anyone have any ideas what could be causing this? I should add that if I boot windows 11 everything works as it should.
My specs are:
9800x3d
nvidia 4090
32gb ddr5
MSI x870
Various NVMe drives
Currently running Arch 6.13.5.arch1-1 and Cachyos-znver4 6.13.6-2 both have the same issue and previous versions too. I have the latest nvidia drivers, utils etc. but again the problem has persisted no matter what version of driver I have used.
Thanks in advance
Offline
Disable the integrated GPU, make sure CSM compat mode is disabled in your UEFI are the two main things I see that might have an impact on this, maybe also add
nvidia_drm.modeset=1
to your https://wiki.archlinux.org/title/Kernel_parameters to ensure the display isn't stolen by simpledrm.
Offline
I have exact same issue for half a year now on a similar hardware (IntelCPU+NvidiaGPU)
Disable the integrated GPU, make sure CSM compat mode is disabled in your UEFI are the two main things I see that might have an impact on this, maybe also add
nvidia_drm.modeset=1
to your https://wiki.archlinux.org/title/Kernel_parameters to ensure the display isn't stolen by simpledrm.
This didn't help for me
I've also tried nvidia.NVreg_PreserveVideoMemoryAllocations=0 as kernel parameter, as well as MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm) in /etc/mkinitcpio.conf (both regenerated of course).
I also searched several topics/archwiki on black screens (they were all similar but not 1to1), but none of the solutions there worked for me.
This is the only thread that describes the issue exactly as mine.
Offline
This is basically a UEFI firmware bug, another alternative that can potentially help is an UEFI upgrade. there's generally little the OS can do about firmware init failures like these. FWIW MSI is somewhat notorious for weird firmware/boot issues so if this is the common thread here this might be related. Also since the OP mentions Windows and in case you have that as well, make sure that https://wiki.archlinux.org/title/Dual_b … ibernation
Last edited by V1del (2025-10-12 19:58:57)
Offline
This is basically a UEFI firmware bug, another alternative that can potentially help is an UEFI upgrade. there's generally little the OS can do about firmware init failures like these. FWIW MSI is somewhat notorious for weird firmware/boot issues so if this is the common thread here this might be related. Also since the OP mentions Windows and in case you have that as well, make sure that https://wiki.archlinux.org/title/Dual_b … ibernation
Thanks for your insight!
As is OP, I'm on MSI motherboard too, as well as dual-booting windows.
I tried https://wiki.archlinux.org/title/Dual_b … ibernation with no luck. I also tried some tinkering with BIOS power/suspend options to no avail.
And I'm on the latest UEFI available.
Until next patch from MSI, I guess. (
Offline
Pages: 1