Could you build with linux-image-edge-arm64

[MX10-AC2N]

I use with beelink gtking-pro (S/N : SA9H...) on sd-card
I can boot with linux-image-edge-arm64 kernel 5.15.y and 5.16.y but i can't boot flippy kernel 5.15.y (boot only flashed on usb stick..)
Can you try a new build with linux-image-edge-arm64

config-5.16.10-arm64.zip
System.map-5.16.10-arm64.zip
vmlinuz-5.16.10-arm64.zip

uInitrd-5.16.zip It's a .zip splitted into 3 with winrar first download and rename the 2 other files before unzip..
uInitrd-5.16.z01.zip just rename without ".zip"
uInitrd-5.16.z02.zip just rename without ".zip"
dtb-linux-image-edge-arm64-amlogic.zip

[ophub]

1. Since there are too many, only some of them are built by default.
2. The kernel of each series can be switched freely through updates. from 5.4.180 change to 5.16.10, such as armbian-update 5.16.10
3. You can also specify the kernel such as sudo ./rebuild -d -k 5.15.24_5.16.10 when building.
4. If you customize the kernel and need to maintain the integrity of the kernel file group, you can use the custom kernel function in the repository to make it

[MX10-AC2N]

When I do armbian-update 5.15.24 the reboot failed so I delete all files of 5.15.24 in /BOOT and copy all files of 5.4.166-flippy-68+0 that I've a copy on my pc and reboot is ok without hdmi but ssh connection work so I update with sudo apt install linux-image-arm64 and adjust /boot (problem with symlink impossible on fat)..
Can boot with linux-image-arm64 5.15.0-0.bpo.3-arm64 #1 SMP Debian 5.15.15-2~bpo11+1 (2022-02-03) aarch64 GNU/Linux
cat /etc/ophub-release return kernel 5.15.24 but I can't boot this release on my sd-card..

Nice !

[ophub]

There is no need to install linux-image-edge-arm64, nor to manually change the files under boot. There are 4 files in the kernel package. You cannot only modify the files under /boot. Other modules files are a complete set.

You manually changed the integrity and consistency of the system kernel. It is also not possible to update with armbian-update later. I don't understand the point of your so confusing use, there is a proper way to update the kernel.

[MX10-AC2N]

Hello @ophub and thank you again for everything you do..

Indeed this I only tested to see if I can run armbian under kernel 5.15.y which is LTS because with my A2 sd card when I try an armbian-update to 5.15.y (flippy) my box gtking_pro bug on reboot, (I wonder if this is not due to the A2 of my sd card) anyway with an apt remove linux-image-edge-meson64 followed by an apt install linux-image-edge-arm64 some adjustments in the boot partition because the armbian update process creates symbolic links which is not possible under FAT so I just recreate the uInitrd and zImage files from the new Initrd-5.15.y- arm64 and vmlinuz-5.15.y-arm64 newly present in /BOOT and /boot/dtb from /usr/lib/linux-image-edge-arm64/

During my tests I noticed that if I install linux-image-edge-arm64 (armbian) during the installation the FAT partition (/BOOT) is dismounted and therefore the installation of the new files is found under the folder /boot present on the ROOTFS partition (ext4) I had to transfer the new img files to the BOOT partition (fat) there is also a new boot.ini file boot.cmd boot.scr but they are not usable bug au startup. I also copied the dtb folder from /usr/lib/linux-image-edge-arm64/amlogic/ in order to use the correct .dtb (that of the kernel 5.15.y flippy not working.
On the other hand, if linux-image-arm64 (debian) is installed, the installation proceeds correctly on the FAT /BOOT partition, only the symbolic link problem is reported.
With these 2 images I managed to start from my 5.15 sd card but if I understand what you are telling me by doing this I break a lot of things.

So which command "armbian-update" launched to have an update to kernel 5.15.y other than flippy for example linux-image-arm64 and it would be best for me because the updates will not unmount the partition /BOOT (fat)

Thank you again for everything, hoping not to bother too much, there are not many people who can answer my questions.
Oops in fact all that is to be able to install yunohost over armbian which is supposed to work correctly however I have some problems with the releases that you provide because when installing yunohost there is a full update system is therefore a problem with the /boot (fat) partition which is unmounted during the upgrade, I had to do my little manipulation of files between the 2 partitions to restart yunohost then during the update made under yunohost I have always this concern kernel updates are done despite that I freeze the updates under armbian-config..

Have a nice day ;-)

[ophub]

The official armbian supports a lot of boxes. This project is an attempt at some officially unsupported boxes. Because some devices lock the bootloader, the latest official boot settings cannot be used.

The content of the boot partition currently used is to take into account the purpose of reloading u-boot to achieve the purpose of using kernels above 5.10. If you change to the official extlinux and other settings, there is still no good way to help these special amlogic boxes to use armbian.

This is a compromise. Maybe many years later, all kinds of boxes will not lock the bootloader, and they will be devices with an open spirit, allowing everyone to freely modify their system, then this project can be deleted.

Your method of updating the kernel will work on your device, because the current gtking is open, allowing you to remove his system. If you are familiar with the operation of armbian, this use is appropriate.

[MX10-AC2N]

Thank again @ophub
Is it possible to adjust the installation procedure during apt upgrades in order to take care of the fact that /boot is a (fat) partition and therefore make copies of the image files rather than wanting to make symbolic links?

[ophub]

I don't have a good way, you search the Internet more