archinstall icon indicating copy to clipboard operation
archinstall copied to clipboard

Arch Linux installer - guided, templates etc.

Results 441 archinstall issues
Sort by recently updated
recently updated
newest added

### Which ISO version are you using? 2024-10-01 ### The installation log ```json Irrelevant ``` ### describe the problem #### Description of the issue I wanted to use archinstall to...

### Which ISO version are you using? 2024.12.01 ### The installation log ```json Could not determine the filesystem: None Could not determine the filesystem: parted.FileSystem instance -- type: linux-swap(v1) geometry:...

### Which ISO version are you using? 2025.05.01 ### The installation log ```json log is too long for paste, log : https://0x0.st/84n4.log ``` ### describe the problem #### Description of...

### describe the request Currently, the default NTP client in `archinstall` when automatic NTP is enabled is `systemd-timesyncd`, which provides only basic time synchronization capabilities but lacks support for NTS,...

### Which ISO version are you using? 2025-05-01 (latest) ### The installation log ```json http://0x0.st/84qf.log ``` ### describe the problem I'm using best-effort partition split with LVM enabled. All the...

### Which ISO version are you using? archlinux-2025.04.01-x86_64.iso ### The installation log ```json [2025-04-27 04:57:09] - DEBUG - Hardware model detected: HP OMEN by HP Laptop 15-dc0xxx; UEFI mode: True...

The Arch wiki says /efi has to be FAT32 and /boot can be EXT4 (if selecting /efi as the EFI partition.) But archinstall fails if you do that. Can you...

### Which ISO version are you using? 2024-04-01 ### The installation log ```json https://0x0.st/8_-3.log ``` ### describe the problem #### Description of the issue I was installing on a ThinkPad...

### Which ISO version are you using? 2024-11-01 (latest) ### The installation log ```json https://0x0.st/X51v.log ``` i want to install LVM on LUKS setup with ext4

## PR Description: Starting in systemd-boot v257 a `arch-chroot` environment is detected by `bootctl` as a container environment. This will cause `bootctl install` to skip EFI variable setup silently. See...