axyl-iso
axyl-iso copied to clipboard
"ERROR: Hook 'archiso_shutdown' cannot be found" during the building of Axyl-ISO
I'm testing the building of Axyl-ISO by cloning the repo and running installation-scripts/build.sh
with the original files. During the building, in the Hook section, I get:
<SNIP>
(12/32) Rebuilding certificate stores...
(13/32) Updating module dependencies...
(14/32) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'archiso'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.3-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
==> ERROR: Hook 'archiso_shutdown' cannot be found
-> Running build hook: [archiso]
-> Running build hook: [archiso_loop_mnt]
-> Running build hook: [archiso_kms]
==> WARNING: Possibly missing firmware for module: ast
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(15/32) Updating Grub Configuration...
Generating grub configuration file ...
<SNIP>
in particular ==> ERROR: Hook 'archiso_shutdown' cannot be found
. The building of the ISO continues, but maybe this error could lead to misbehaviors.
I found a reference for this error, maybe could be useful for fixing it: https://github.com/u-root/webboot/blob/main/docs/remaster-manjaro-iso.md
Furthermore, when the ISO is created and I mount it in a VM, launching Calamares produce the following error:
This error is not if I download directly the ISO by the releases section, but I'm trying to understand why if I build directly files from GitHub, I'm getting these errors.
A silly suggestion, but does the re-build.sh
maybe sidestep some issues here?