Pinebook Pro image broken

  • Open
  • quality assurance status badge
Details
2 participants
  • Gabriel Wicki
  • paul
Owner
unassigned
Submitted by
Gabriel Wicki
Severity
normal
G
G
Gabriel Wicki wrote on 14 Sep 2023 21:51
(address . bug-guix@gnu.org)
874jjwzg6s.fsf@erlikon.ch
Trying to set up my Pinebook Pro with my favorite distribution i found
out that the usual way (invoking `guix system image
gnu/system/images/pinebook-pro.scm` to build an image which is then dd'd
to a micro SD card) does not yield a working result.

Doing the same with guix time-machine on commit
c9c195936d128465030bc05f8c319367602c93b5 generates a bootable image.

Since building with a current checkout does not yield a bootable image
(the pinebooks gracefully falls back to boot from the eMMC memory with
its pre-installed Manjaro) I guess the bootloader broke.
G
G
Gabriel Wicki wrote on 15 Sep 2023 00:47
more info
(address . 65982@debbugs.gnu.org)
871qf0z81n.fsf@erlikon.ch
commit b0d47d9e18e52ff7935aebe6ab37e702f58101be (Update u-boot to
2023.07.02) breaks creation of a bootable image.

Building in a time-machine at commit
d6a53849935f8584e1df57faa79c18c23fbb2aa1 works as expected.
P
P
paul wrote on 7 Oct 2023 11:07
Re: Pinebook Pro image broken
(address . 65982@debbugs.gnu.org)(address . gabriel@erlikon.ch)
14bc146f-1735-5db3-b984-d1630971307c@autistici.org
Hi Gabriel, thank you for taking the time to bisect and find the first
working commit!


I can confirm that

guix time-machine --commit=d6a53849935f8584e1df57faa79c18c23fbb2aa1 --
system image -e '(@ (gnu system images pinebook-pro)
pinebook-pro-barebones-raw-image)' --system=aarch64-linux

is able to build a bootable image, contrary to what happens on master.


I'm not an expert but I'd love to learn more and help solving this.
Please do CC me if someone has some idea about how to fix but doesn't
have the hardware.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 65982@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 65982
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch