mkinitcpio-37-1 upgrade error

[jocris]

[quote="jocris"]1-I have upgraded to 37, got the same error.
2-Downgraded back to 36, image generation reports successful.
3-Rebooted -> failed to boot.

pacman logs ->https://bpa.st/DXVQ
boot error ->https://0x0.st/HwNp.jpg

Can you confirm same problem, even after downgrading mkinitcpio?[/quote]

Actually the reason for the failure to boot is the SD card is just bad . Happened to be a coincidence with this package upgrade.

[chriswyatt]

I did wonder that when I looked at those errors. Looks like stuff I wouldn't expect mkinitcpio to touch.

[phperrer]

Looks related to the recent changes upstream. If I comment out the line starting "add_checked_modules_from_symbol" at `/usr/lib/initcpio/install/kms`, then `mkinitcpio -p linux-aarch64 -v` succeeds.
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/218', '', ' class="postlink"')

[phperrer]

Also why is this forum totally broken.

[petaramesh]

I fell on the same issue (error at the end of mkinitcpio build without previous reported errors), and having kms in the hooks list caused it. Removing both vc4 from the MODULES list and kms from the HOOKS solved it.

[petaramesh]

I fell on the same issue (error at the end of `mkinitcpio` build without previous reported errors), and having `kms` in the hooks list caused it. Removing both `vc4` from the `MODULES` list and `kms` from the HOOKS solved it.

[petaramesh]

I fell on the same issue (error at the end of mkinitcpio build without previous reported errors), and having kms in the hooks list caused it. Removing both vc4 from the MODULES list and kms from the HOOKS solved it.

[petaramesh]

I fell on the same issue (error at the end of mkinitcpio build without previous reported errors), and having kms in the hooks list caused it. Removing both vc4 from the MODULES list and kms from the HOOKS solved it.

[petaramesh]

I fell on the same issue (error at the end of mkinitcpio build without previous reported errors), and having kms in the hooks list caused it. Removing both vc4 from the MODULES list and kms from the HOOKS solved it.

[mcloaked]

If the suggested changes are the fix that works for all users perhaps there will be a new version released that no longer causes the faulty initramdisk file to be generated for any archlinuxarm systems. Interestingly the same version of the mkinitcpio package in the arch Linux repos works fine, and I didn't have the same problem on any of my x86_64 machines, but just on my rock64 archlinuxarm machine.

I haven't checked the two sets of source files to see what, if any, differences there may be between mkinitcpio on arch Linux and archlinuxarm. Certainly it would be essential to have it working and up to date ahead of any new kernel releases for aarch64.