I've set up my interceptor with the Axzez OS, its been running very fine for a couple of months now. I'm only using the WAN ethernet port of the Axzez board.
The setup is such that the main OS is on an SSD (/dev/sda) and a RAID1 running on /dev/sdb & /dev/sdc does hold the main (its a NAS).
My understanding is that the Raspberry CM4 cannot boot directly from SATA and the actual boot partition is still on the eMMC of the CM4 board. That would explain the difference in active kernel vs what the OS attempts to install in /boot on /dev/sda1.
Running lsblk on the OS shows me various partitions on what I believe to be the eMMC, only one of them is mounted:
By now, the main kernel versions have marched on to version 5.15.84-something but the Axzez OS is still on 5.15.32. Am I missing something? My unattended-upgrades keep finding new (mainline) kernels and install them in /boot on /dev/sda1 but the system keeps booting kernel 5.15.32 - naturally.
Now, I'd really like to run more recent kernels to stay up to date security wise.
- maybe I'm simply missing an update channel to have more recent kernels pulled from Axzez, but given that the kernel patch in the download section is still 5.15.32 I doubt a more recent kernel exists?
- what would be a safe way to change the eMMC boot partition back to a mainline kernel and is that even possible while keeping the main system as-is? As mentioned above, I only use the WAN port on the board so my assumption is that a mainline kernel would still recognize that. Are there other differences between mainline and the axzez-patched kernel?
Maybe there are other alternatives I'm not aware of, I'd be curious to learn about.