Skip to main content

ArchLinux Installation EFI

Installing ArchLinux with UEFI

The official ArchLinux installation page is very good, but obviously cannot cover all installation scenario.

I had to install with EFI and steps are not straight copy/paste of that page.

I will make the log story short but just pasting the commands and indicate what is needed and not in the guide.

ping archlinux.org
timedatectl set-ntp true
Use parted instead of fdisk
parted /dev/sda
Print existing partitions and clear them all:
(parted) print
(parted) rm 1
(parted) rm 2
(parted) rm ...
Create the EFI partition and fill the remaining
(parted) mklabel gpt
(parted) mkpart ESP fat32 1MiB 1GiB
(parted) set 1 boot on
(parted) mkpart primary btrfs 1GiB 100%
(parted) print
(parted) quit
Note that in "parted", "quit" also saves (in "fdisk", "quit" does not)

Format and mount created partitions
mkfs.fat -F32 /dev/sda1
mkfs.btrfs /dev/sda2
mount /dev/sda2 /mnt
mkdir -pv /mnt/boot
mount /dev/sda1 /mnt/boot
Here is just a small improve of the officiel guide: add some usefull packages to installation
pacstrap /mnt linux linux-firmware nano base base-devel dhclient openssh btrfs-progs grub efibootmgr
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt
The following is just copy/paste of https://wiki.archlinux.org/index.php/Installation_guide
ln -sfv /usr/share/zoneinfo/Indian/Antananarivo /etc/localtime
hwclock --systohc
echo 'en_US.UTF-8 UTF-8' > /etc/locale.gen
locale-gen
echo 'LANG=en_US.UTF-8' >  /etc/locale.conf
echo 'KEYMAP=fr' > /etc/vconsole.conf
echo 'hv-01' > /etc/hostname
echo '127.0.1.1 hv-01.rktmb.org hv-01' >> /etc/hosts
mkinitcpio -p linux
passwd
The EFI flavour "grub-install" is documented, but here it is:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub
grub-mkconfig -o /boot/grub/grub.cfg

You may now just exit the chroot and reboot on your new installation.

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...
Read more

CopilotChat GlobFile Configuration

CopilotChat GlobFile Configuration Want to feed multiple files into GitHub Copilot Chat from Neovim without listing each one manually? Let's add a tiny feature that does exactly that: a file glob that includes full file contents . In this post, we'll walk through what CopilotChat.nvim offers out of the box, why the missing piece matters, and how to implement a custom #file_glob:<pattern> function to include the contents of all files matching a glob. Using Copilot Chat with Neovim CopilotChat.nvim brings GitHub Copilot's chat right into your editing flow. No context switching, no browser hopping — just type your prompt in a Neovim buffer and let the AI help you refactor code, write tests, or explain tricky functions. You can open the chat (for example) with a command like :CopilotChat , then provide extra context using built-in functions. That “extra context” is where the magic really happens. Built-in functio...
Read more

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more