A Proxmox install freezing at ‘Loading initial ramdisk’ is almost always a kernel graphics handoff problem—add nomodeset or i915.modeset=0 to the GRUB command line and the boot will finish.
Why the ramdisk load hangs
When the kernel hands control to the initial ramdisk, one of the first things it does is initialize the graphics subsystem. On hardware with older or quirky GPUs (especially Intel integrated graphics on consumer boards), the kernel mode-setting driver can lock up the display before the root filesystem is even mounted. The screen freezes on that single line and the system never reaches the login prompt.
The same symptom can appear after a kernel update on a working install, or when booting the Proxmox installer itself. The root cause is the same: the kernel is trying to set a native resolution via a driver that does not play well with your particular chipset or monitor connection.
Diagnostic path
- At the GRUB menu, highlight the Proxmox entry and press e to edit.
- Find the line starting with
linux. It ends withquietorro quiet. - Remove
quietso you can see kernel messages. Addnomodesetright afterro. - Press Ctrl+X or F10 to boot. If the freeze is gone, the issue is confirmed.
If nomodeset works but you want hardware acceleration later (for a display console or GPU passthrough), try i915.modeset=0 instead. That disables only the Intel driver while leaving the basic framebuffer active.
Making the fix permanent
Once the system boots, edit /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"Then run update-grub. On a Proxmox system that uses systemd-boot (rare, but possible on UEFI installs), you would instead edit the loader entry in /boot/efi/loader/entries/ and add the parameter to the options line.
When it is not the GPU
Two other causes can mimic this freeze:
- USB boot media written with Ventoy. Some Ventoy versions inject a graphics mode that conflicts with the Proxmox kernel. Rewrite the ISO with plain
ddor Rufus in DD mode. - UEFI vs. Legacy boot mismatch. If the motherboard is set to UEFI but the disk was partitioned as BIOS/GPT, the bootloader may load the kernel but fail to find the initramfs. Check the firmware boot order and ensure CSM is disabled for a pure UEFI install.
My take
On a home server with no monitor attached 99% of the time, just leave nomodeset in place and move on. The tiny power saving or resolution bump is not worth debugging a kernel module that may break again after the next apt upgrade. If you do need a local console, consider a cheap add-in GPU that the open-source radeon or amdgpu driver handles without drama.
This kind of boot-time quirk is common enough that a USB stick with a known-good Proxmox ISO earns its place in a drawer—it doubles as a rescue disk when a kernel update goes wrong. For a deeper dive into how the boot process interacts with container filesystems, see the post on Sharing TrueNAS Datasets with Unprivileged LXC Containers in Proxmox.
Part of Proxmox in a homelab — the host and hardware section.
