grub-install cannot find the uefi-directory and whenever a device prefix is entered grub cannot find the canonical path. I'll read through the grub wiki probably tomorrow and find what I can find there. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Thu, 5 Oct 2023, Martin Rys wrote:

What have you tried? You can follow the grub wiki page for instructions. If archinstall created an ESP partition, you likely used UEFI boot mode so it installed as such.

Martin

On Thu, Oct 5, 2023, 02:58 Jude DaShiell wrote:

...

I used it earlier since I couldn't make sense of the efi and uefi encyclopedias in the Installation-guide. I now have a disk with two partitions on it first one being fat32 esp. The machine is uefi 64 capable. For that reason I can't figure out how to run grub-install on the latest update of grub. Does archinstall install for bios by default? If so, I think I can have grub-install ignore platform and install in /boot/grub with a couple options. I used the archinstall that was on the latest arch release and managed to get a working system by putting enough packages on the essential packages line.

-- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.

grub-install cannot find the uefi-directory

Without your full input and full output, it's impossible to provide advice. Post lsblk output too while you're at it. On Thu, Oct 5, 2023 at 2:38 PM Polarian wrote:

Hello,

Personally I would recommend systemd-boot, it is a lot more simple to deal with, and also is a hundred times more reliable than grub.

I am aware there is a lot of people who are against using systemd "bloat", but systemd-boot "just works", its configuration files are simpler too.

See the following wiki page:

https://wiki.archlinux.org/title/Systemd-boot

Note, you should have the following setup before attempting to follow this:

ESP partition mounted to /boot (https://wiki.archlinux.org/title/Installation_guide#Mount_the_file_systems), this MUST be FAT32, and MUST have the correct partition type (EFI system).

This allows for it to be properly detected and read.

You MUST have UEFI booted, and not booted via CSM (or bios if your device is REALLY old), otherwise the efivars will be missing, see: https://wiki.archlinux.org/title/Installation_guide#Verify_the_boot_mode

Now the other things are optional, you could have a swap partition with the type of "Linux Swap".

You must also have a filesystem with type "Linux Filesystem", this can be ext4, btrfs, whatever floats your boat.

Optional partitions can be made, for example a lot of people like to make a separate partition for /home, detachable home directories allow for reinstallation without overwriting your user data, so in other words, you can preserve your rice and documents while changing the underlying system.

Personally, I think that people still promoting grub are causing many issues, sure grub is useful (especially when you do not support efivars), but for UEFI boots, systemd-boot is so much more convenient.

Personally I use EFISTUB most of the time, I think one of my servers is systemd-boot'ed simply because I was lazy that day :P

Hope this helps, in general you will get there eventually, so good luck :)

Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev

The only reason I used grub was since you can turn on a sound once grub comes up. I wouldn't have a problem with other boot loaders since I can probably put abeep in /etc/rc.d/rc.local and have it do the same thing for me with the bonus I know alsa is up and working. Grub uses the pc speaker which provides no assurance alsa will work after boot. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Thu, 5 Oct 2023, David Rosenstrauch wrote:

On 10/5/23 8:29 AM, pete wrote:

...

For boot for the longest time now i have used syslinux for boot gave up on grub it became stupid

Same here. I only use either syslinux or refind.

DR

Am 05.10.23 um 18:01 schrieb Jude DaShiell:

Mystery solved! grub-install --efi-directory=/boot/grub worked.

This worked by pure luck. Next time use just /boot, not /boot/grub Best regards.

that is what was recommended with the latest grub update both to run grub-install and grub-mkconfig -o /boot/grub/grub.cfg. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Thu, 5 Oct 2023, Markus Schaaf wrote:

Am 04.10.23 um 21:00 schrieb Jude DaShiell:

...

I now have a disk with two partitions on it first one being fat32 esp. The machine is uefi 64 capable. For that reason I can't figure out how to run grub-install on the latest update of grub.

Why do you want to run grub-install again? Pacman is able to update Grub. No manual fiddling needed.

If installing manually, I would mount ESP as /boot and run

grub-install --efi-directory=/boot

Best regards.