see e.g. how the recent u-boot change broke older kernels, same holds for DTB changes. Just look at the diffs between 4.18 and linux-next. It'd like to see really good reasons and a plan how this will pan out
To me the very thing of u-boot changes potentially breaking booting would seem as a strong reason to not just use one hardware boot partition, but both (redundant) hardware boot1/boot2 partitions, aka "A/B Updates".
See OS-issues#347 with some reasons and planning. I would suggest to add all new info there.
I tried using the keyboard on my NextDock360, but I'm unable to switch VTs
It has worked at some point in the past
As you don't seem to involve librem5-flash-image
let's mmove it here. Can you attach a usb keyboard and see if you can switch VTs to get more logs?
(SDCard boot isn't continuously tested so I'm not that surprised it's not working out of the box)
I have a Librem5 currently running u-boot 2022.10 and pmOS.
After downloading plain (no LUKS) image from https://storage.puri.sm/librem5/images I run the following to flash it to an SD card
unxz ./librem5r4.img.xz
sudo dd if=./librem5r4.img of=/dev/sdb bs=4M iflag=fullblock oflag=direct conv=fsync status=progress
I can then boot the image by holding volume down while powering on the Librem5.
I see the boot splash from PureOS, but it never completes the boot. I can then press the power down button and I see the log attached:
pmOS doesn't use systemd, so the PureOS rootFS is clearly being mounted, but it doesn't work correctly.
I have tried a range of different images yet still nothing works. I have tried both LUKS and plain images, from Jenkins and older PureOS releases. It's a brand new SD card, so it shouldn't be failing either.
I'm not sure what is wrong exactly: https://arm01.puri.sm/job/Images/job/Image%20Build/7432/console
Seems related to:
No install report found.
Makefile:42: recipe for target 'tmp/qemu-x86_64.img.stamp' failed
Builds fixed since a while now so closing.
The landing based arm64 builds boot on the Librem5 too so I've adjusted the MR title. Builds are available from
librem5-flash-image --dist=landing --variant=plain --image-job="Images/Image Builds landing"
v2:
landing
imageThe later now has all the packages to bootstrap so once this is merged we can enable periodic image builds for development purposes.
devkit also pulls in the development tools so likely the same trigger as #69
Sebastian Krzyszkowiak (b44f37c6) at 27 Jun 20:17
Merge branch 'devkit' into 'master'
... and 1 more commit
It runs out of space
It runs out of space
Thanks @twrightsman I'll have a look!
I've bumped the size 1G in !203 for that. The x86 installs development librem5-dev-tools
so that
could be a trigger but we also seem to pull in more Purism artwork.
Let's merge this so the builds pass again and this only affects the x86 vm image.
It runs out of space.
Currently testing if this is enough.
Guido Gunther (18591efb) at 25 Jun 19:00
Merge branch 'x86-space' into 'master'
... and 1 more commit
It runs out of space.
Currently testing if this is enough.
do you have your work available some where?
Yes, it is still on sourcehut. I haven't touched it in a few months, unfortunately, other things keep coming up... If you guys are eyeing this for crimson then that could be the motivation I need to push the finishing touches on it.
If you could follow a similar layout
I basically stole borrowed your repository layout to help me build this for the Librem 5
PureOS for Laptops also uses debos
to build ISO images. If you could follow a similar layout like in https://source.puri.sm/pureos/infra/pureos-image-recipes (build.sh
and prepare.sh
are the important files) or maybe even integrate your changes there, then Laniakea could autobuild phone images just like it does for Laptop install images as well :-)