[SOLVED] my artix install won't boot/appear on boot menu 01 September 2021, 18:07:54 I updated my bios, and my artix install (base install) doesn't boot, or appear as a UEFI boot option in the bios. I reformatted my boot partition, and I'm not sure if I'm missing something. Could someone help, please? Last Edit: 25 September 2021, 10:32:36 by Jemsurfer
Re: my artix install won't boot/appear on boot menu Reply #1 – 01 September 2021, 18:16:43 I had similar problems when I first tried to install Artix. After many (failed) tries here's what worked for me:1) setting "UEFI only" in the BIOS2) giving the BOOT partition the bootable flag while partitioning disks (in my case, I used cfdisk)after that I pretty much followed these instructions, and it worked for me.
Re: my artix install won't boot/appear on boot menu Reply #2 – 01 September 2021, 22:48:55 What I usually do is to run Artix Live ISO (not base) to see whats going on. Once running from live ISO, mount the hardrive root partition (/dev/sda2 or whatever) somewhere (/mnt). then mount the ESP (/dev/sda1 or whatever) somewhere (/mnt/boot/efi), and view what its contents are. Should have /EFI then within that; a /Artix and maybe a /boot directory, with .efi files within those directories. Also look at the base boot directory (/mnt/boot) to make sure the grub install looks ok.Then run efibootmgr -v to see what the BOIS UEFI has to say. This will tell you the boot order, what NVRAM variables you have, and the default boot NVRAM variable. The NVRAM variable that the BIOS boots is "connected" to the entries in the ESP partition /EFI .efi files.Then grub has to have been installed and configured properly, of which I dont know much about other than running it as instructed. Also helps to run blkid (to tie the NVRAM to the actual HD partitions).And as stated by @shako, make sure the boot and esp flags are set on the ESP (/dev/sda1). gparted can be used for this.Your problem could be the NVRAM variables are not setup at all, or an old one/wrong one is getting booted. The x.efi files didnt get installed into /boot/efi/EFI.... Or grub did not get installed correctly. Last Edit: 02 September 2021, 01:44:37 by dxrobertson
Re: my artix install won't boot/appear on boot menu Reply #3 – 01 September 2021, 23:53:15 1st paritition should be a 1M type bios, 2nd should be ESP/EFI partition
Re: my artix install won't boot/appear on boot menu Reply #4 – 02 September 2021, 02:48:03 Quote from: Jemsurfer – on 01 September 2021, 18:07:54 I reformatted my boot partition, and I'm not sure if I'm missing something. Could someone help, please?Perhaps you should run grub-install once more from inside your installation.
Re: my artix install won't boot/appear on boot menu Reply #5 – 03 September 2021, 13:02:15 Quote from: VictorBrand – on 02 September 2021, 02:48:03Perhaps you should run grub-install once more from inside your installation.Follow the other message's direction in booting live, mounting and chroot it, and once you are in, and % df looks as it should, run grub-install /dev/sda (or whatever).The things that people endure with EFI garbage is unbelievable. 21st century dos partitioning to make a unix system run.... even an open/free version of dos... like it wasn't bad enough in the 80s it sticks around.
Re: my artix install won't boot/appear on boot menu Reply #6 – 03 September 2021, 14:23:28 Quote from: Jemsurfer – on 01 September 2021, 18:07:54I updated my biosAlso, check your UEFI options after the update and assure yourself that Secure Boot is turned off.Besides that, some versions of UEFI check bootloaders at boot/bootx64.efi in the EFI partition. If this file is not found by UEFI firmware, it refuses to recognize other bootloaders installed into the partition. At least, my laptop's UEFI behaves in such a way. Artix by default sets up its GRUB loader into artix/grubx64.efi, so try to copy it into boot/bootx64.efi (btw, it's the default name of Debian's shim) and select this file through the UEFI menu.
Re: my artix install won't boot/appear on boot menu Reply #7 – 25 September 2021, 10:24:24 Thanks for all the replies, guys. I ended up just reinstalling. This time I won't do any stupid stuff to my system.