[Bug]: ABL postinst scripts use wildcard expansion for kernel/initrd paths, breaking mkbootimg when multiple kernels exist

[xiaobaoaaaaaa]

What happened?

On a Xiaomi Pad 5 Pro (xiaomi-elish, Snapdragon 870 / SM8250), kernel installation fails during the postinst hook with:

ValueError: Unrecognized arguments: ['/boot/initrd.img-6.18.35-current-sm8250']
run-parts: /etc/kernel/postinst.d/zz-update-abl-kernel exited with return code 1

The device uses Qualcomm's ABL (Android Bootloader) boot chain, which requires generating an Android boot image via mkbootimg after each kernel update. This is handled by the BSP's postinst script /etc/kernel/postinst.d/zz-update-abl-kernel.

The script locates the kernel and initrd using shell wildcards:

/boot/vmlinuz-*-sm8250
/boot/initrd.img-*-sm8250

When multiple kernel versions are present in /boot , the wildcard expands to multiple files — for example:

/boot/initrd.img-6.18.10-current-sm8250
/boot/initrd.img-6.18.35-current-sm8250

This passes two positional arguments where mkbootimg expects only one, and argparse rejects the extra one as unrecognized.

The bug is masked after a fresh install (when only one kernel version exists), but surfaces on the second or later kernel upgrade.

Other affected BSPs (same script, same logic)

BSP	Device
ayn-thor	AYN Odin
oneplus-kebab	OnePlus 8T
ayn-odin2	AYN Odin 2
ayn-odin2mini	AYN Odin 2 Mini
ayn-odin2portal	AYN Odin 2 Portal

How to reproduce?

On xiaomi-elish (or any listed device):

1. Install Armbian from a fresh image.
2. Run the first kernel upgrade — this will succeed (only one kernel in /boot).
3. Run a second kernel upgrade — this will fail with the error above, because /boot now contains both the old and new kernel versions.

Or manually:

ls /boot/vmlinuz-*-sm8250   # shows two or more versions
run-parts /etc/kernel/postinst.d/

Suggested fix
Replace wildcard expansion with the kernel version parameter ($1) passed by the Debian kernel hook mechanism:

version="$1"
kernel="/boot/vmlinuz-${version}"
ramdisk="/boot/initrd.img-${version}"

Optionally:

[ -f "$kernel" ] || { echo "Kernel not found: $kernel" >&2; exit 1; }
[ -f "$ramdisk" ] || { echo "Ramdisk not found: $ramdisk" >&2; exit 1; }

This fix applies identically to all six BSPs.

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Other

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hey @xiaobaoaaaaaa! 👋

Thanks for opening your first issue with the Armbian project — we’re glad to have you here! 🧡
Your input doesn’t just help us improve the project — it benefits everyone who uses Armbian.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo to support the work — and welcome aboard! 🚀

[rorystandley]

I've got a fix for this ready - the scripts now use the version Debian passes to postinst hooks as $1 to build exact paths, instead of the wildcards. Same change across all six ABL scripts. PR coming shortly.

Could someone set the "In Progress" label for me? I can't set labels myself. Thanks