You are not logged in.
Pages: 1
Hi folks,
I wanted to run Devuan ascii on armhf as I did previously with jessie. However, it seems like the new embedded images do not use a packaged kernel anymore. Instead, the kernel is built "hardcoded" at image generation time. I noticed that the regular kernel packages are in the repository as well (linux-image-armmp-lpae) but I didn't figure out how to configure u-boot for using them. Seems like the Devuan kernel does not use initrd either, so at least I would need to load this in before booting.
Or asking more in general: What is the way Devuan users are supposed to (automatically) receive kernel updates for production server running on armhf boards?
Cheers
Last edited by kuleszdl (2018-11-03 21:28:21)
Offline
That's on my wishlist too: https://dev1galaxy.org/viewtopic.php?pid=8975#p8975
*๐๐๐๐๐๐!*
Offline
After spending some time with trial and error, I am able to give the answer myself. It is possible to use the armmp-lpae kernel from stable (or if the board is too new like in my case - from backports). Just check whether your board is included or not in the dtbs-directory of the stable kernel e.g. here: [https://packages.debian.org/stretch/arm โฆ e/filelist]).
Proceed as follows (assuming you don't use a separate /boot partition and everyhting is on /dev/mmcblk0p1):
apt-get -t ascii-backports install linux-image-armmp-lpae
cd /boot
mv boot.scr boot.scr.ORIG
mv boot.cmd boot.cmd.ORIG
Now adapt your boot.cmd.ORIG and adapt the paths/add a line for the initrd. In my case:
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait panic=10 ${extra}
load mmc ${devnum}:${partition} ${kernel_addr_r} vmlinuz
load mmc ${devnum}:${partition} ${fdt_addr_r} boot/dtbs/${fdtfile}
load mmc ${devnum}:${partition} ${ramdisk_addr_r} initrd.img
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
Then install u-boot-tools:
apt install u-boot-tools
And create an updated boot.scr:
cd /boot
mkimage -C none -A arm -T script -d boot.cmd boot.scr
On the next reboot, the kernel you previously installed should be booted (the hardcoded kernel does not hurt as it resides in a different path, but you can wipe it away if it bothers you). Verify you are running the backport-kernel with uname -a:
root@devuan:~# uname -a
Linux devuan 4.18.0-0.bpo.1-armmp-lpae #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) armv7l GNU/Linux
Last edited by kuleszdl (2018-11-04 02:40:36)
Offline
Pages: 1