|
Edited by JFL at 2021-12-23 16:51
If you are now on balbes and on linux-image-current-meson64 the extlinux.conf:
- LABEL Armbian
- LINUX /Image
- INITRD /uInitrd
Copy the Code Download meveric-kernel (if you are not compiling any modules yuo might need to install the linux-headers also).
I would suggest you make a copy of all the files related to linux-image-current-meson64 (uImage, uInitrd, Image, vmlinuz, etc) in the /boot partition. This will enable you to quickly switch back if meveric-kernel gives you issue by just renaming these files to their original name or you want to switch between meveric-kernel and meson64 kernel easily.
Then install the with dpkg -i meveric-kernel. This will generate new uIntrd, initrd.img-xxxx, vmlinuz-xxxx. Note, if not mistaken the meveric-kernel does NOT create a new Image (which is the same as vmlinuz).
I think you might have miss this part. Copy the new vmlinuz-5.15.10-arm64 to Image. This should boot.
- Linux arm-64 5.15.10-arm64 #odroid SMP PREEMPT Mon Dec 20 03:43:12 CET 2021 aarch64 GNU/Linux
Copy the Code It might be good idea to "HOLD" linux-image-current-meson64 to prevent it accidently upgrade to current-meson64 v21.08.6.
Edit: You should also use the meson-g12b-gtking-pro.dtb for linux kernel 5.15. It can be found on /lib/linux-image-5.15.10-arm64/amlogic.
Noticed Armbian now have new kernel build like linux-image-edge-arm64 https://imola.armbian.com/apt/pool/main/l/linux-5.15.10-arm64). Wonder if it is the generic kernel for all the arm64 devices like what balbes did in 2020.
|
|