tpowa/archboot

Archboot is a most advanced, modular Arch Linux boot/install image creation utility to generate bootable media for CD/USB/PXE, designed for installation or rescue operation.

archboot's Issues

Why is Auto-Prepare enforcing that I split / and /home

After some point in development, Archboot is forcing me to separate / and /home after selecting AUTO-Prepare. When i did this previously, I could have / and /home on the same partition. Now i have to manually partition it to have it on the same partition, because I cannot find a way to tell Auto-prepare to keep it in one partition.

can't boot arch linux after installing with archboot on mac m1 with UTM

Hello
on Mac M1 and UTM,
I've tried to install arch linux with archboot.
https://gitlab.archlinux.org/tpowa/archboot/-/wikis/Archboot-Homepage

at first, setting the keymap didn't work so I skipped it.

After installing everything:
in the grub install it said it was successful then I got :

I tried reinstalling grub and efibootmgr and then tried to install the bootloader again.
This time I could see the grub.cfg file.

in the final phase, when installing grub, I got:

when rebooting grub goes up but then displays this message:

Tried looking it up.
Tried pacman -Syu linux

But then I get the error:

Tried looking it up but didn't manage to find a solution.

So I tried to reboot and go to grub.
in grub , using set:

using ls -l:

This is as far as I got and understand.

please help.
I would like to understand why it's so difficult installing arch linux in this way and why I get so many errors.

debug.log

Updating linux-aarch64 does not lead to a newer kernel

Hi,

I am a little stuck and confused on this.
As dynamic resolution for the display failed in my UTM VM after a common kernel update, I noticed that updating linux-aarch64 does not work as expected.

First I though, that mkinitcpio has a problem, as running the hooks shows these error messages:

==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k 6.8.1-1-aarch64-ARCH -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.1-1-aarch64-ARCH'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
==> WARNING: architecture 'aarch64' not supported, skipping hook
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly missing firmware for module: 'msm'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

But these result from the hook "kms" exiting with 1.

After a sudo pacman -S linux-aarch64 I'd expect to run on a newer kernel after a reboot. The first kernel that was installed on installing the VM from the Archboot ISO image was 6.7.5-1. So until I updated from this kernel version, everything was fine.

When I run sudo pacman -S linux-aarch64 now, it updates to 6.8.1-1, but after a reboot, uname -r still shows 6.7.5-1, kernel modules cannot be loaded and problems arise.

What I am missing here?
Does upgrading the kernel require special treatment?

Thanks.

EFI?

Archboot 86_64x doesn't like EFI on VMs.

Is there any way to resolve this?

Edit: I'm gonna try a different ISO, date instead of date-latest

Edit 2: Switching ISO did not help.