You are not logged in.
Brand new Arch install won't boot. Text says "x86/cpu: SGX disabled by BIOS".
Arch beginner here. I used refind-install. When that dodn't work, I used refind-install --usedefault /dev/sda1. But still, Arch just won't boot. I followed the Installation Guide on the wiki. Should I stick to GRUB after all?
Last edited by average_scout (2024-06-14 21:17:03)
Offline
This doesn't sound like arch is not booting , but not succesfully reaching graphical mode .
Append systemd.unit=multi-user.target to the kernel command line (probably in refind-linux.conf or refind.conf )
If that brings you to a console login screen , login as root.
Verify you have network access, then run journalctl -b -1 | curl -F 'file=@-' 0x0.st .
post the link it outputs .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
This doesn't sound like arch is not booting , but not succesfully reaching graphical mode .
Append systemd.unit=multi-user.target to the kernel command line (probably in refind-linux.conf or refind.conf )
If that brings you to a console login screen , login as root.
Verify you have network access, then run journalctl -b -1 | curl -F 'file=@-' 0x0.st .
post the link it outputs .
Actually, installing Grub fixed this. Solved.
Offline
This is the absolutely last line?
Can you still boot the rescue.target (2nd link below) along the "nomodeset" parameter?
Edit: Fuck.
Last edited by seth (2024-06-14 21:31:38)
Offline
Have you tried enabling the SGX extensions in your BIOS settings? That *should* at least get rid of the error message. It get the same error booting an(y) Arch ISO unless I enable them.
In my Dell desktop machine, it is just a toggle in the BIOS settings.
Last edited by c00ter (2024-06-15 14:33:21)
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline