Just to throw in an add'l tryout of the instructions above and their
results on my Pi3, here's the output after disabling tmp.mount and
reboot:
Last login: Wed Jun 24 08:29:25 2026 from 10.67.4.2
edgar@fruendtpi3:~$ ls -lh /boot/initrd.img*
lrwxrwxrwx 1 root root 27 Jun 5 16:46 /boot/initrd.img ->
initrd.img-7.0.0-1011-raspi
-rw------- 1 root root 5.6M Jun 5 16:54 /boot/initrd.img-6.17.0-1018-raspi
-rw------- 1 root root 5.4M Jun 5 17:00 /boot/initrd.img-7.0.0-1011-raspi
lrwxrwxrwx 1 root root 28 Jun 5 16:46 /boot/initrd.img.old ->
initrd.img-6.17.0-1018-raspi
edgar@fruendtpi3:~$ findmnt /tmp
edgar@fruendtpi3:~$ sudo -i
[sudo: authenticate] Password:
root@fruendtpi3:~# dracut --force /boot/initrd.img-6.17.0-1018-raspi
6.17.0-1018-raspi
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
root@fruendtpi3:~# dracut --force /boot/initrd.img-7.0.0-1011-raspi
7.0.0-1011-raspi
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
root@fruendtpi3:~# ls -lh /boot/initrd.img*
lrwxrwxrwx 1 root root 27 Jun 5 16:46 /boot/initrd.img ->
initrd.img-7.0.0-1011-raspi
-rw------- 1 root root 57M Jun 24 09:11 /boot/initrd.img-6.17.0-1018-raspi
-rw------- 1 root root 64M Jun 24 09:17 /boot/initrd.img-7.0.0-1011-raspi
lrwxrwxrwx 1 root root 28 Jun 5 16:46 /boot/initrd.img.old ->
initrd.img-6.17.0-1018-raspi
root@fruendtpi3:~# free -h
total used free shared buff/cache available
Mem: 896Mi 444Mi 348Mi 3.0Mi 184Mi 452Mi
As you can see, I get a much larger size for both images.
Before I reboot now with fingers crossed, I need to know - Dave - what
did you mean with 'copy it to the boot partition' in your instructions.
Thx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2155094
Title:
RPi 3B, Zero 2W, 4B: New boot assets in /boot/firmware/new failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2155094/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
