On Tue, 11 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 Marc Auslander wrote:On 4/10/2023 11:00 PM, David Wright wrote:On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:I'm on Buster. In /boot I keep a copy of the current working linux named by appending -knowngood to the four files. My idea is that if an update fails, I have a recent working linux. This is different from vmlinuz.old which is the previous kernel version. The updates in question are not to the kernel but to initrd.image of course. Suddenly, update-initramfs insists in trying to first update initrd.....-knowngood which of course fails because there are no underling file with that name. This never happened in the past, AFAIK. Once it fails it gives up. There seems no way to force update-initramfs to update the right kernel.
[trim]
# update-initramfs -u # update-initramfs: Generating /boot/initrd.img-5.10.0-21-amd64 # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.10.0-21-amd63-kg Found initrd image: /boot/initrd.img-5.10.0-21-amd63-kg Found linux image: /boot/vmlinuz-5.10.0-21-amd64 Found initrd image: /boot/initrd.img-5.10.0-21-amd64 Found linux image: /boot/vmlinuz-4.19.0-23-amd64 Found initrd image: /boot/initrd.img-4.19.0-23-amd64 Warning: os-prober will be executed to detect other bootable partitions.Its output will be used to detect bootable binaries on them and create new boot entries.done So update-grub didn't seem to complain. I haven't tried booting yet with my "5.10.0-21-amd63-kg" initrd, though. I'll leave that to you, if you want to try.
Boot went fine, but it is worth mentioning that grub-update decided that the "5.10.0-21-amd63-kg" copy of the 5.10.0-21-amd64 kernel should be the default grub entry. -- Hackers are free people. They are like artists. If they are in a good mood, they get up in the morning and begin painting their pictures. -- Vladimir Putin