You are not logged in.
I have already resolved my issue. I just wanted to share my experience and maybe help anyone with the same issue.
I recently updated my system. After the update, my system would hang indefinitely after leaving the GRUB menu. I didn't know the boot failure was caused by a microcode update. The screen was blank and there were no log/messages that I could use to debug. Thinking back, a blank screen made sense because the kernel probably loads microcode very early on, so there is no log yet. I used the most recent iso to create a USB boot disk and tried booting from USB. I ran into the same issue. I then tried an iso from last year and my system was able to boot successfully. I looked for solutions online and found this thread.
https://bbs.archlinux.org/viewtopic.php?id=292840
I thought I had the same issue, but the solution in the thread didn't work for me. I went on to look for other solutions. Finally, I found that after removing microcode from initrd in GRUB, my system would boot successfully. For recent iso that uses systemd-boot, using dis_ucode_ldr as a kernel parameter also works.
Finally, I have been using Arch Linux for the past 5 years. Since the beginning, Arch Linux has worked wonderfully for me and I love the AUR. Thanks to everyone that contributes to Arch Linux.
Last edited by terrytseng (2024-08-05 08:07:50)
Offline