System hangs booting from live USB

Support
1

Hi, I have been using Manjaro for work for several years and I think this is an awesome community, I always have my problems solved just reading other’s posts, but this time, I can’t find a solution for mine. I will try to give as much information as possible and if something is missing, ask for it, thanks.

I am trying to install Manjaro KDE to my main computer and get rid of Windows (10 upgraded to 11), specs:

  • Asus ROG Strix x570-e Gaming Wi-Fi (firmware v5021, the latest)
  • AMD Ryzen 7 2700x
  • 4x G.Skill F4-3200C16-8GTZRX (Memtest86 OK!)
  • GigaByte Radeon RX 6900 XT Gaming OC 16G

I configured BIOS as follow and try, almost, every combination:

  • SATA AHCI Enabled
  • LAN Controllers. Enabled / Disabled.
  • Wi-Fi Controller. Enabled / Disabled.
  • Bluetooth Controller. Enabled / Disabled.
  • AMD fTPM Configuration:
    • Enable Firmware TPM / Enable Discrete TPM.
    • Erase fTPM NV for factory reset. Enable / Disabled.
  • Fast Boot. Enabled / Disabled.
  • Secure Boot. Other OS / Windows UEFI mode. (Also clearing all Secure Boot Keys)
  • Security Device Support. Enabled / Disabled.

I also try to disable all USB ports, except 2, used for USB drive and USB dongle for KB&M. Reset BIOS to optimized defaults and use the clear BIOS external button.
Windows Fast Boot is also disabled.
Also try UEFI and not UEFI option to boot (when selecting device) does not seems to have any effect.

The problem is that the system not boot at all, few seconds after initramfs is loaded, the system hangs and the screen goes to black disconnecting input (“DP Disconnected” also I try with HDMI).
A Manjaro KDE (manjaro-kde-24.2.1-241216-linux612.iso) logs until “Trusted Platform Module” message is showed (sometimes it hangs at the prior “Starting show Plymouth Boot Screen…”)
With Arch (archlinux-2024.12.01-x86_64.iso) logs the following, and have the same behaviour:

running early hook [udev]
Starting systemd-udevd version 256.9-1-arch
running early hook [archiso_pxe_nbd]
Triggering uevents...
[3.91123] hid-generic 0003:1532:0266.0006: No inputs registered, leaving

Such device id is my keyboard Razer Huntsman V2 Analog, if I disconnect it and use another keyboard (I try with 2 different) the message just don’t show up but the system still hangs.

I ask ChatGPT about this and try some options at boot (usb and energy related, I don’t really understand what was doing)

I also try with a Void Linux (void-live-x86_64-20240314-xfce.iso) just to check if systemd is the culprit. And with a Gentoo (livegui-amd64-20241220T192248Z.iso)
Furthermore, I try to install a fresh Manjaro on another hardisk using another (old) computer and connect it to mine, and it does not boot at all, just keep at screen with ROG and Manjaro Logo.
I get out of ideas about what is happening or to do next.

Thanks in advance,
Skraw.

2

It is strongly recommended the last 4 options to be off (ftpm, secure boot, fastboot and maybe security device, not sure what it is). Other than that, and trying bleeding edge image from github (but you are using one from several days ago already) i have no other ideas.
P.s. look at the arch wiki, you can disable plymouth with a toggle at the kernel boot line in grub before boot.

3

These three must be turned off/disabled and all SB keys must be deleted:

If it’s still not working verify checksum of ISO on USB stick.

Make sure to boot the USB stick in UEFI mode.

Randomly trying things get it worse.

1 Like
4

↑ This! ↑

sha256sum -c manjaro-kde-24.2.1-241216-linux612.iso.sha256

… download to and run from within the same directory as you downloaded the .ISO to, as it’s easiest.

Download link for the checksum if you don’t already have it: https://download.manjaro.org/kde/24.2.1/manjaro-kde-24.2.1-241216-linux612.iso.sha256

Also, Ventoy is recommended:

ETA: You can also dump the checksum file on the Ventoy stick itself (or run it from elsewhere by providing the path) so you can check if it got corrupted somewhere along the way.

2 Likes
5
  • Windows Fast Startup – Fast Boot is a BIOS option that has nothing to so with Windows – as @Teo suggests, Fast Boot (the BIOS option) is generally recommended to be disabled for Linux.
  • The Microsoft implementation of Secure Boot is unsupported by Manjaro; it must be disabled.

Every OS must use the same technology to boot – either UEFI or Legacy/CSM – attempting to use both will not succeed. This also extends to partitioning schemes; if using UEFI then disks should use GPT partitioning; if using Legacy/CSM then disks should generally use msdos/mbr based partitioning.

Please, don’t do this.

Did you check the downloaded ISO for consistency against the provided checksum?

As a new forum user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:

The Update Announcements should be checked frequently for important update related information.

These announcements contain a Known Issues and Solutions section and should generally be checked before posting a request for support.

Please provide more useful system information:

Output of the following command formatted according to forum requirements (see links above) may be useful for those wishing to help:

inxi --admin --verbosity=8 --filter --no-host --width

Be prepared to provide more information and outputs from other commands when asked.

Regards.

6

Thank you all for your answers.

Checksum of image I think is not the problem, I “burnt” it with Etcher, I use 2 different USB drives and also 5 different Linux distros. However, I check the checksum for manjaro iso and its OK. I will take a look to Ventoy.

Yeah, about ChatGPT, I was trying in my despair to find the problem. Since the beginning I am thinking about buying a new mobo, because problem maybe comes with my own one, not the model, just my motherboard, it is a very strange problem.

I can’t reach a terminal where to perform dmesg, inxi or anything to get any clue about what is happening, I also try the steps at this guide reach minimal system without luck.

7

Avoid BalenaEtcher if possible.
Consider creating a Ventoy USB as mentioned (more information below).

One point that is sometimes overlooked is that both the OS Installer and the OS itself must be installed and boot using the same technology; so, both must boot as UEFI, or both must boot as MBR; this extends to the partitioning scheme used also; either GPT or MBR but not both.

You seem to keep a number of ISO’s on hand. I do too, which is why I choose to create a Ventoy USB. This has the added advantage of avoiding the possibility of damage when writing an ISO image to random USBs.

Here’s some information I’ve created for reference:

Ventoy

Boot with a Ventoy USB, and ISO files are automatically listed in the Ventoy menu, and can be booted directly. A 32GB capacity USB should allow ample space to store several ISOs of your choice; an 8GB capacity USB might hold one, or two ISO’s; do the math.

Ventoy is available from the official Manjaro extra repository:

sudo pacman -S ventoy

Write the Ventoy system to an empty USB drive;

  • target the device itself /dev/sdX, and not a partition

Create a Ventoy USB (for UEFI mode): :eyes:

sudo sh ventoy -i -r 100 -S -g -L VOLUME /dev/sdX

Create a Ventoy USB (for BIOS mode):

sudo sh ventoy -i -r 100 -S -L VOLUME /dev/sdX
  • Enable -s or disable -S Secure Boot.
  • Substitute VOLUME for a volume label name to use.
  • Substitute /dev/sdX for the location of your USB device.
  • Preserve some space on the target device (example allows 100mb).
Ventoy general usage

Type ventoy (without arguments) to see usage information:

Usage:  Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX  
 CMD:  
  -i  install Ventoy to sdX (fails if disk already installed with Ventoy)  
  -I  force install Ventoy to sdX (no matter if installed or not)  
  -u  update Ventoy in sdX  
  -l  list Ventoy information in sdX  
  
 OPTION: (optional)  
  -r SIZE_MB  preserve some space at the bottom of the disk (only for install)  
  -s/-S       enable/disable secure boot support (default is enabled)  
  -g          use GPT partition style, default is MBR (only for install)  
  -L          Label of the 1st exfat partition (default is Ventoy)  
  -n          try non-destructive installation (only for install)

Update a Ventoy USB:

  • ensure the updated Ventoy version is available in Manjaro; and then:

To update the Ventoy system on an existing Ventoy USB;

sudo ventoy -u /dev/sdX
  • The Ventoy USB update process is non-destructive.

See also: Ventoy (GitHub);

There is a Windows GUI version of Ventoy. If you choose to use it please pay attention to available options in the File menu before creating the Ventoy USB.

I’m sure you will agree Ventoy makes managing bootable ISOs a breeze, compared to the traditional write to USB, cross fingers and hope methods of writing ISOs to USBs.

I hope you find it useful.

Given the time of the year the forum might be slow, but I’m sure someone will help some more when they are able.

Regards.

2 Likes