You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: ARM Builds » [SOLVED] Upgrading kernel via apt » 2026-10-10 12:42:09
Actually, don't do the above. It booted on the Pi 4 I use as a security camera server, but when I did it on my other Pi 4, used as a media device, I found that neither analog sound nor IR control worked. Even when I added snd-bcm2835 to /etc/modules, no soundcards showed up.
Also the external drive, formatted to ext4, didn't automount from /etc/fstab although I could manually mount it.
I kept backups of kernel8 and initrd.img from /boot and was able to revert just by copying them back.
#2 Re: ARM Builds » [SOLVED] Upgrading kernel via apt » 2026-10-06 14:31:56
I manually updated the kernel in the Devuan Arm image. Now that I know what works, I'll write a script to do it. Ideally, the script would run automatically after apt installs a kernel, but I don't know how to do that yet.
Here are the steps:
1. use apt to install linux-base-x.y.z+deb??-arm64, linux-binary-x.y.z+deb??-arm64 & linux-modules-x.y.z+deb??-arm64
2. copy /lib/modules/x.y.z+deb??-arm64/vmlinuz to kernel8.img in the /boot partition
3. copy /lib/modules/x.y.z+deb??-arm64/config to config-x.y.z+deb??-arm64 in the /boot partition
4. run "update-initramfs -c -k x.y.z+deb??-arm64"
(Step 3 allows update-initramfs to check the config, otherwise it complains. Step 4 creates initrd.img-x.y.z+deb??-arm64 in /boot, but also copies it to initrd.gz which I think will be what the bootloader looks for.)
This created a bootable system. In my case, the x.y.z from "uname -r" is 7.2.6+deb13-arm64, and lsmod shows a long list.
#3 Re: ARM Builds » [SOLVED] Upgrading kernel via apt » 2026-09-29 09:47:57
Thank you. That's very useful.
#4 ARM Builds » [SOLVED] Upgrading kernel via apt » 2026-09-24 11:04:49
- steve_graham
- Replies: 10
About a year ago, I got a Pi 4 and wrote the community-built Devuan image onto its SD card, booted, and everything worked perfectly.
I thought it was time to upgrade to a 7.x kernel and used apt to install the linux-image package and its dependencies. No problems. But when I rebooted, the system was still running the 6.x kernel.
On inspection, it seems that the original SD image has its kernel in the /boot vfat partition as kernel8, and the apt install didn't touch it.
So, clearly, I don't understand how the Pi boot process is supposed to work on a Devuan system. Is the executable in the /boot partition supposed to be a loader that boots the real kernel from the second, ext4 partition?
Or have I just done something stupid? (Quite possible.)
#5 Re: Freedom Hacks » How to Disable the New Apt Pager » 2026-02-04 17:07:09
Found this answer via duckduckgo! "apt list" was actually broken on my system because the pager was stripping the escape characters that were supposed to control the colours. This made the output very difficult to read. Probably something to do with what my default pager is or how it's set up, but the apt end-user documentation is near useless. I was contemplating dowloading the source code.
#6 Re: Installation » [SOLVED] Failing to upgrade from daedalus to excaliber: no Release and Packages » 2025-11-11 17:24:36
Thank you for the subtle spelling correction. 
That works now.
#7 Installation » [SOLVED] Failing to upgrade from daedalus to excaliber: no Release and Packages » 2025-11-11 17:12:28
- steve_graham
- Replies: 2
I updated everything under daedalus, installed usrmerge, and edited sources.list to replace "daedalus" with "excaliber" everywhere. The repo address is deb.devuan.org
When I do "apt update" it fails to find Release for anything, nor Packages. When I look at the repo in a browser, (whatever mirror happens to be selected) the file Release seems to be there. Packages is actually Packages.gz but that worked fine on daedalus.
I'm guessing that I have some sort of unpurged configuration that needs clearing, but I haven't found anything.
Pages: 1
Board footer
