Skip to main content

How can we update BerryBoot images for rpi4? /boot/firmware missing?

475 viewsCustom Image Errors/Issues
0
0 Comments

I have tested various Berryboot Images for RPI4, but the main problem come when i try to update OS, seems something is missing (or not mounted) in /boot/firmware…

Any Workarround?

Regards,

Answered question
Add a Comment
0
Damian (anonymous) 1 Comment

Hi There

I am using a raspberry pi 4 with berryboot and the ubuntu server image as an iscsi initiator and I assume I have the same issue as Dave. When I run sudo apt full-upgrade, I always get

Setting up u-boot-rpi:arm64 (2019.07+dfsg-1ubuntu4~18.04.1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package u-boot-rpi:arm64 (--configure):
installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
u-boot-rpi:arm64
E: Sub-process /usr/bin/dpkg returned an error code (1)

and after adding tmpfs /boot/firmware tmpfs rw 0 0 to /etc/fstab, reboot is still successful but I get the following:

Setting up u-boot-rpi:arm64 (2019.07+dfsg-1ubuntu4~18.04.1) ...
md5sum: /boot/firmware/config.txt: No such file or directory
grep: /boot/firmware/config.txt: No such file or directory
Migrating boot configuration...grep: /boot/firmware/config.txt: No such file or directory
cat: /boot/firmware/config.txt: No such file or directory
dpkg: error processing package u-boot-rpi:arm64 (--configure):
installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
u-boot-rpi:arm64
E: Sub-process /usr/bin/dpkg returned an error code (1)

From your answer, it seems like there is no work around. Could you please confirm? Installing an upgraded image is impractical in my case since it would result in a fresh installation (in my understanding).

Best regards

Damian

Posted new comment
Alexander G

Hi Damian, yes, that’s a common error since to convert Berryboot images, first, you must unmount boot and rootfs partitions in the fstab file and this because Berryboot run its own custom kernel and ignore native kernel from images. You can mount berryboot partition as boot on Ubuntu but when you run that apt full-upgrade command Berryboot kernel with be replaced with the Ubuntu kernel and from that point, Berryboot will not boot again. A workaround can be: don’t upgrade the firmware. No matter if ubuntu has firmware upgrades, under Berryboot, images will always run Berryboot custom kernel.

Add a Comment
You are viewing 1 out of 2 answers, click here to view all answers.
Write your answer.