Ubuntu 24.04 fails to boot from a USB drive on AMD64 hardware when the GRUB menu or OS logo appears but the system hangs. This issue typically stems from mismatched Secure Boot settings, corrupted installation media, or incorrect kernel parameters passed during the live session initialization.
Verify BIOS and UEFI Settings
The most common cause for a "not live boot" scenario is conflicting firmware security features. Modern motherboards enforce strict security protocols that can block unsigned kernels or prevent proper handoff from the bootloader to the operating system. You must ensure your system is configured to allow third-party bootloaders and disable any aggressive secure boot enforcement that rejects the Ubuntu installer signature.
Navigate to your BIOS/UEFI setup by pressing
F2,
Delete, or
F12 immediately after powering on the machine. Locate the
Secure Boot option, usually found under the
Security or
Boot tab. If it is enabled, change it to
Disabled. Some systems require you to clear existing keys or set a supervisor password before allowing this change. Additionally, ensure that
Fast Boot is disabled, as it can skip hardware initialization steps required for USB devices to be recognized as bootable media. Set the
Boot Mode to match the format of your USB drive; if you created the USB using Rufus in GPT/UEFI mode, the system must be in UEFI-only mode, not Legacy/CSM.
Validate Installation Media Integrity
A corrupted ISO file or an improperly written USB stick will cause the bootloader to load successfully but fail when attempting to mount the root filesystem. This manifests as a freeze after the initial splash screen. Before troubleshooting complex configurations, you must rule out media errors. Download the SHA256 checksum provided on the official Ubuntu download page and compare it against the file you burned to disk. Use tools like
sha256sum in Linux or QuickHash in Windows to verify the integrity.
If the checksums match, the issue likely lies in how the data was written to the USB drive. Standard copy-paste methods do not create bootable drives. Use reliable imaging tools such as
Rufus on Windows or
BalenaEtcher on cross-platform systems. When using Rufus, select the correct partition scheme (GPT for UEFI) and file system (FAT32 for compatibility). Ensure you are writing in "DD Image" mode if standard ISO mode fails, as this bypasses some compatibility layers that might corrupt specific driver packages needed for your AMD64 chipset. For further guidance on maintaining stable system configurations, you may also want to review
How to Connect Bluetooth Permanently in Linux to understand broader driver stability issues in modern Ubuntu releases.
Adjust Kernel Parameters via GRUB
When the GRUB menu appears, press
e to edit the default boot entry. Look for the line starting with
linux. At the end of this line, append specific kernel parameters to force compatible graphics and storage drivers. The most frequent culprit on AMD64 systems is the Nouveau open-source graphics driver, which often causes hangs during the early stages of the live boot process. Add
nomodeset to the end of the linux line. This parameter tells the kernel to use basic VESA display modes rather than loading full GPU drivers, allowing the desktop environment to load successfully.
You can also try adding
acpi=off or
noapic if the hang occurs specifically during ACPI initialization, though these are less common fixes. After appending these parameters, press
F10 or
Ctrl+X to boot with the modified settings. If the system boots successfully, you have identified the problematic component. Note that these changes are temporary for the live session unless you modify the persistence configuration, which is beyond the scope of immediate troubleshooting.
Check Hardware Compatibility and Ports
Physical connection issues can mimic software boot failures. Try connecting the USB drive to a different port, preferably one directly on the motherboard rather than through a hub or front-panel connector. Front-panel ports sometimes lack sufficient power delivery or proper USB 3.0 controller initialization during the pre-boot phase. If you are using a USB 3.0 or 3.1 drive, ensure your BIOS supports XHCI handoff. Disabling XHCI handoff in BIOS forces the system to use legacy USB 2.0 controllers for boot devices, which can resolve recognition issues on older AMD chipsets.
For users experiencing persistent hardware-level boot failures, checking related diagnostic guides can provide additional context. See
Solving the Image Display Issue in Linux Ubuntu 24.04 LTS for deeper insights into graphical subsystem conflicts that may interfere with boot sequences.
Frequently Asked Questions
Why does my Ubuntu USB show the logo but then freeze?
This behavior indicates that the bootloader has loaded but the kernel cannot initialize critical hardware drivers, typically the graphics card. Using the
nomodeset parameter in the GRUB edit menu usually resolves this by forcing basic display output.
Can I keep Secure Boot enabled while live booting Ubuntu?
Generally, no. While newer versions of Ubuntu support signed kernels, many AMD64 motherboards struggle with the validation process during live sessions. Disabling Secure Boot is the most reliable workaround for boot failures.
What should I do if nomodeset causes low resolution?
Low resolution is expected when using
nomodeset because full GPU acceleration is disabled. Once installed to the hard drive, you can install proprietary drivers or switch back to standard modes to restore normal display performance.
Is it safe to use DD mode in Rufus instead of ISO mode?
Yes, DD mode writes the image byte-for-byte, which can fix compatibility issues with certain USB controllers or BIOS implementations that reject standard ISO hybrid images. It is a safe and effective troubleshooting step.
How do I know if my USB port is the problem?
Try switching between USB 2.0 and USB 3.0 ports. If the system boots from a USB 2.0 port but not 3.0, your BIOS may need an update or XHCI handoff adjustment to properly recognize high-speed devices during boot.