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

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

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"
Read more

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM
Read more