[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
Graham Haddock
2064208 at bugs.launchpad.net
Sat May 4 19:10:16 UTC 2024
I loaded your 'test image' onto an NVMe SSD on a RPi 5, edited the
config.txt file, and it worked!
[RPi5 4 GB, Pimoroni Base, Samsung 256 GB PM9B1 SSD]
I had tried all kinds of things over the last week, different NVMe
cards, different imagers, all unsuccessfully.
24.04 running with the noticeable extra speed of a PCIe/NVMe is sweet!
The only quirk, was that, even though I selected English (US) keyboard
during the initial installation dialog, I ended up on an English (UK)
keyboard. This was easily fixed by going to the settings/Keyboard and
editing.
I would suggest you add some kind of suffix or change to the file name,
since, if this is going to be the only solution to NVMe or USB operation
for a while, you don't want the confusion from two different
functionality files with the same name out in the 'wild'.
Thanks for the fix.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2064208
Title:
Installer crashes when booting from USB on Raspberry Pi
Status in ubiquity package in Ubuntu:
Triaged
Bug description:
After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an
SSD drive with a USB3 interface (specifically; this issue does not
occur when booting from an SD card), booting the drive on a Pi 4 or Pi
5, and running through the installer to the point where the
(corrupted) slide deck starts to display during setup, the installer
crashes.
[ Workaround ]
A test image is now available; please see comment 1 below for details.
At the time of writing, some workarounds have been found, but none
that consistently work on all boards with all drives. One workaround
that has worked on a Pi with a Samsung EVO SSD, and a Crucial SSD is
as follows:
Before booting the image, find config.txt on the boot partition, and
the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these
lines, you want the first one under an "[all]" section. Append
",cma-128" to the line. Specifically, the following section:
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1
Should become:
dtoverlay=vc4-kms-v3d,cma-128
disable_fw_kms_setup=1
Unmount the drive cleanly, boot it, and run through the installer. You
may revert the change (if you wish) after successful installation.
Another workaround, reported as working on a Pi 5 with an NVMe drive
attached over PCIe:
Before booting the image, find config.txt on the boot partition. Under
the first "[all]" section append the following line:
dtparam=pciex1
Unmount the drive cleanly, boot it, and run through the installer.
Please note both workarounds have also been reported as failing with
certain drive combinations.
[ Background ]
Given this crash occurs immediately upon the (corrupted) slide deck
starting, that it only occurs when booting from USB (but the exact
same image works from an SD card), and that merely changing the pre-
allocation of the contiguous memory area affects it, I suspect this at
least related to (if not a duplicate of) LP: #2037015, particularly
since a crash bug is now associated with it too, LP: #2062146.
Still, I'll leave this open as a non-duplicate for now as I'm not
positive of root-cause yet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions
More information about the foundations-bugs
mailing list