Ubuntu Pi Flavour Maker

boot over network after updating & rebooting

Bug #1697637 reported by Yolan Chériaux
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu Pi Flavour Maker
New
Undecided
Unassigned

Bug Description

My Raspberry works perfectly with Ubuntu Classic Server 16.04 for Raspberry 3 downloaded here : https://ubuntu-pi-flavour-maker.org/download/

After updating the system (apt-get update then upgrade) and restarting it, there is still a package which requires an update : linux-firmware
After another upgrade & reboot, the raspberry tries to boot over network (PXE). It fails eventually and gives me a UBOOT prompt. From this point I don't know how to start the system.

Am I the only one who encounters this ? Is there a way to solve it ?

Tags: server ubuntu
Revision history for this message
Stijn Vanouplines (svouplin) wrote :

Same problem here! After fresh install then update/upgrade+reboot

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

There is a bug in the `linux-firmware-raspi2` package, which shares one file with `linux-firmware` (`/lib/firmware/brcm/brcmfmac43430-sdio.bin`).

It may work to hold the package (`apt-mark hold linux-firmware`), but I need to test it - unfortunately, the testing cycle (burn image, modify, reboot, and again and again) is very time consuming.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

I've done a few tests, and the `linux-firmware`/`linux-firmware-raspi2` are a red herring - they're unrelated to the bug, as I can't boot even if I hold those packages.

The conflict on the file `/lib/firmware/brcm/brcmfmac43430-sdio.bin` is still valid though; I'll file it as separate bug.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

I've opened a separate bug (https://bugs.launchpad.net/ubuntu-pi-flavour-maker/+bug/1717809) for the apt problem mentioned.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

The bug is in the boot update (I guess initramfs/flash-kernel).

There is no workaround for users who want to perform routine upgrades; the only option is to hold updates (`apt-mark hold`) on packages triggering a boot update, but they are far too many (20+).

Right now, the only way to make a system "stable" is to disable the automatic updates:

    perl -i -pe 's/"1"/"0"/' /etc/apt/apt.conf.d/20auto-upgrades

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.