![](https://forum.armbian.com/uploads/set_resources_18/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
![](https://forum.armbian.com/uploads/n2a/n2a-94a2ce0c85dccd66d514e3a5e30a83bcb3f55316.avatars_letters.png)
eselarm
-
Posts
122 -
Joined
-
Last visited
Community Answers
-
eselarm's post in How to install a higher version of kernel ? was marked as the answer
You could run:
sudo apt list | grep linux-image
Besides the vanilla Debian/Ubuntu ones, there are Armbian ones: vendor, current, edge
In your case your installed U-Boot might be incompatible with kernel 6.1.84, I had that for my Rock3A, I installed mainline U-Boot.
If you want all kernels, use http://beta.armbian.com in /etc/apt/sources.list.d/armbian.list
Or build yourself from source. The Armbian build runs fine on my NanoPi-R6C Armbian Bookworm
-
eselarm's post in 6.1.84-vendor-rk35xx Kernel panic was marked as the answer
I found the reason for the crash: the 6.1.84-vendor-rk35xx doesn't work together with the 2024.10 mainline U-boot.
Earlier the SPI-flash was empty and the Rock3a booted from SD-card, a U-boot version from 2017 (Armbian_24.11.1_Rock-3a_noble_current_6.6.62-kisak.img.xz). I put that image in 'beta' mode so I got the 6.1.84-vendor-rk35xx (+ rock-3a-sata.dtbo). That all still worked.
I then put the 2024.10 mainline U-boot in SPI and wiped the sector range 34-32767 from the SD-card. Then I discovered that the 6.1.84-vendor-rk35xx always crashed, independent of SATA modules etc.
I now disabled the SPI and took sector range 34-32767 from the official Radxa image (rock-3a_debian_bullseye_cli_b25.img.xz) and put that on the SD-card with the Armbian Noble (latest beta channel trunk.201) and rebooted. That does not crash and works same as with 6.12.6-edge-rockchip64 that I used before the reboot to write the sector range 34-32767.
Version is: latest-2023.07.02-3-b1eb2bde-gb1eb2bde (Aug 29 2023 - 10:43:04 +0000)
So I guess I need to look at differences in uboot configs and likely also uboot sources.
The other thing is that If I want to be able to boot from a single SATA device with the Rockchip on-chip SATA, the uboot In the SPI-needs to default to SATA for M.2 E-key connector and not the default PCIe-2x1.
Or wait till I got an extra NVME to put in the M.2 M-key connector and load rock-3a-sata.dtbo after uboot together with kernel. That is preferred I think looking at possible future use-cases.
-
eselarm's post in snapper fails to create a btrfs snapshot if --cleanup-algorithm is used was marked as the answer
I do not use quotas, so the fix for this issue is: https://github.com/openSUSE/snapper/issues/894#issuecomment-2054220427