renard

I confirm that it boots well: v25.2.2 for Orange Pi 4 LTS running Armbian Linux 6.12.21-current-rockchip64

@Marco Schirrmeister I've tried `apt upgrade` - it still suggest to upgrade kernel packages. Anyway I just put it on hold with: `apt-mark hold linux-image-current-rockchip64 linux-dtb-current-rockchip64 linux-headers-current-rockchip64` and it helped. Just strange that it does not work with that SY203 for some reason.

@MaxT As I said above I don't use EMMC, and not sure that my OPi4LTS even has one.

@Michael Robinson BTW for some reason "SY203 - Disable Armbian kernel updates" does nothing for me. Does it suppose to change into "Enable" after I set it? In my case it does not and I still get the option to upgrade the kernel: # apt list --upgradable Listing... Done linux-dtb-current-rockchip64/jammy 25.2.2 arm64 [upgradable from: 24.11.1] linux-headers-current-rockchip64/jammy 25.2.2 arm64 [upgradable from: 24.11.1] linux-image-current-rockchip64/jammy 25.2.2 arm64 [upgradable from: 24.11.1] linux-u-boot-orangepi4-lts-current/jammy 25.2.2 arm64 [upgradable from: 22.08.10] selinux-policy-default/scar,scar,scar 2:2.20241008-1volian1 all [upgradable from: 2:2.20210908-1volian1]

@MaxT >Seems to be innovative way to get positive attention of the team to issues you face. Good luck with that. Nono. There was no cruelty, or irony or any hidden negativeness here I really don't know your pipeline, maybe there is maybe there is not! I assumed that there might be. >If you have u-boot on emmc I am booting from sd, not emmc.

>i'm showing current download on rolling release @ 6.12.17 Hm. That did not work for me. On 2 different OPi4LTS and 2 different sd cards. Both from upgrade and rolling. Though I tried with 6.12.16 that moment, maybe it is fixed with 6.12.17...

@Michael Robinson Thanks. This is done (or better say was like that), but looks like "SY201 - Install alternative kernels" requires disabling "SY203 - Disable Armbian kernel updates". What is the correct way to 1) upgrade to the certain kernel and 2) halt on that version; via `armbian-config`? Maybe we might need to add it to the manual. I mean, I did it "manually" with `apt install` (gosh, the guys 15 years ago meant other things with words "manual kernel update" ). Anyway this is kinda off-topic to the thread subject.

Seems like the kernel 6.12.16 just does not boot - either updated regularly or from "rolling" minimal image. Steps to reproduce: - 1 way - just burn and run current "rolling" minimal image (Armbian_25.5.0-trunk.115_Orangepi4-lts_plucky_current_6.12.16_minimal). Result: Getting no records on UART after "Starting kernel..." and only red led shining. - 2 way Enabling kernel updates from already up to date Armbian v25.2.2 with older 5.15.76-rockchip64 (`# sudo armbian-config` -> System -> Kernel -> SY201 - Install alternative kernels) Result: same as above - 3 way Enabling kernel updates from older Armbian 22.08.10 without Armbian update itself. Result: same as above -- Tested with 2 different Orange Pi 4 LTS, same behavior on both of them. With two different Samsung A1 cards (with what had no problems before). -- 6.6.62 seems to work fine from the snapshot (Armbian_24.11.1_Orangepi4-lts_noble_current_6.6.62-kisak.img.xz). -- Do you guys have some CI tests on the real hardware for rolling kernels? I am sure you do. But... -- Stupid question. Is there a safer way to somehow fix updating to exact kernel, say 6.6.62 and stay there. I would rather do it from `armbian-config`, rather than manually: ``` $ sudo apt install linux-image-current-rockchip64=24.11.1 linux-dtb-current-rockchip64=24.11.1 linux-headers-current-rockchip64=24.11.1 $ dpkg -l | grep linux-image ii linux-image-current-rockchip64 24.11.1 arm64 Armbian Linux current kernel image 6.6.63-current-rockchip64 # It actually installed 6.6.63 instead expected 6.6.62, but seems fine $ sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr # After reboot: $ uname -a Linux mxopi4lts01 6.6.63-current-rockchip64 #2 SMP PREEMPT Fri Nov 22 14:38:37 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux ``` --