#Computer refuses to boot after arch installation

36 messages · Page 1 of 1 (latest)

surreal abyss
#

I just decided to take the step of getting rid of windows on my desktop
Installed Arch as i already did several time, it went well.
But after the installation, my computer refuses to boot on it.

I'm using grub, the mkconfig command succeeded, but when I go back to arch via the installation medium everything seems to be in order.
But nothing when rebooting without a key.
I'm on an MSI H310M PRO-M2 PLUS motherboard, that works in UEFI

#

Tried to go back to the installation medium, mounting back my partitions to re-create a grub.cfg but no

vernal tendon
#

can you check your EFI bootloader entries?

surreal abyss
#

In the UEFI or by going back to the installation medium ?

vernal tendon
#

by going back into the install CD

#

you'll have to go there to fix it anyways in most cases

#

also make sure you have Secure Boot disabled

#

that could also fuck up even the bootloader loading

#

(unless Arch is using Canonical's signed GRUB)

surreal abyss
#

For some reason the outputs of boot1 and 2 are absurdly long

vernal tendon
#

I don't think you have a valid EFI bootloader entry

#

let me dig around

#

yeah you have to do something like this

#
efibootmgr --create --disk /dev/sda --part 1 --loader '\EFI\refind\refind_x64.efi' --label 'rEFInd Boot Manager' --unicode
#

adjust your settings to the right ones for your system

#

then reboot

#

also you might want to swap around the boot order

#

.aw uefi

cold muralBOT
vernal tendon
#

4.3.1 details it pretty well

surreal abyss
#

Okay thanks

#

btw i can't even find the secure boot options in my uefi, wtf is this

surreal abyss
vernal tendon
#

and this isn't Gentoo, so there's a low chance of you somehow managing to install a GRUB that isn't EFI-capable

surreal abyss
#

In this command :

efibootmgr --create --disk /dev/sda --part 1 --loader '\EFI\refind\refind_x64.efi' --label 'rEFInd Boot Manager' --unicode

I know that well, /dev/sda becomes /dev/nvme0n1
But what about the \EFI\ etc ?

vernal tendon
surreal abyss
#

I'm in the zsh right when we launch the installation, not chrooted

vernal tendon
surreal abyss
#

I haven't launched any command rn

vernal tendon
#

this is getting directly written into UEFI's boot selection

#

let's just give you a quick example

#

let's say your loader path is /boot/efi/somerandomloader/loader.efi

#

if your ESP is /boot/efi your EFI path to write there is \EFI\somerandomloader\loader.efi