You are not logged in.
Hello guys. I'm following this tutorial to install a newer kernel on my recently installed devuan machine. When I did this process with devuan running inside a Virtual Machine, everything went great but there I had only one big partition with all directories. Now, in my real machine, I installed the OS using LVM and it setup for me a 255MB /boot partition separeted from the encrypted one. Because of this it is not being possible to update my kernel, when I run:
sudo make modules_install install
it fails with:
DEPMOD 4.17.0-rc4+
sh ./arch/x86/boot/install.sh 4.17.0-rc4+ arch/x86/boot/bzImage \
System.map "/boot"
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.17.0-rc4+ /boot/vmlinuz-4.17.0-rc4+
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.17.0-rc4+ /boot/vmlinuz-4.17.0-rc4+
update-initramfs: Generating /boot/initrd.img-4.17.0-rc4+gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.17.0-rc4+ with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
arch/x86/boot/Makefile:155: recipe for target 'install' failed
make[2]: *** [install] Error 1
arch/x86/Makefile:319: recipe for target 'install' failed
make[1]: *** [install] Error 2
Makefile:273: recipe for target '__build_one_by_one' failed
make: *** [__build_one_by_one] Error 2
Does anyone knows a simple solution for that? I don't know what I could safely delete from /boot tbh and I don't think reformatting the computer would be the best one.
Offline
gzip: stdout: No space left on device
I know this might sound crazy, but it might be failing because the build computer needs more storage space.
By the way, this tutorial explains how to also create .debs of the kernel. They can be installed with dpkg or gdebi (or backed-up in case of system failure/reinstallation) in other devuan systems of the same architecture.
https://debian-handbook.info/browse/sta … ation.html
Last edited by siva (2018-05-12 17:07:42)
Offline
Hey Siva, thank you for your answer. Indeed, it was boot partition that hadn't enough space when I ran the install command, which for me seems a little weird since the initrd.img is no more than 23MB and I had more than 200MB available in this partition. That's why I opened this question to find out if there was some way to generate this file elsewhere and later manually place it boot. But now I followed this tutorial from debian-handbook you posted and worked easily
Thank you very much
Offline
Glad to hear you got it working I ran into a similar problem the first time I tried compiling a kernel.
Offline