From: Mathieu Othacehe <othacehe@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Who has had success installing a Guix system on arm?
Date: Wed, 04 Nov 2020 18:44:27 +0100 [thread overview]
Message-ID: <87sg9p585g.fsf@gnu.org> (raw)
In-Reply-To: <260d2ed2-2af6-73f0-be62-27d25098bef2@gmail.com> (Jesse Gibbons's message of "Wed, 4 Nov 2020 09:44:24 -0700")
Hello Jesse,
> -> Which board did you get working with guix system (banana pi m2u, novena,
> beaglebone black, pine64-plus, etc.)?
> -> Did you build natively or cross-build from a different system?
> -> What version of guix did you use? (what did guix describe say?)
> -> If the board you got working can boot from an internal (emmc) or external
> (microsd) drive, which one did you get working?
> -> Would you mind sharing the operating-system definition that was successful?
The situation is slowly improving. Since recently, you should be able to
build a barebones image for pine64 lts this way:
--8<---------------cut here---------------start------------->8---
guix system disk-image -t pine64-raw os.scm
--8<---------------cut here---------------end--------------->8---
with os.scm that looks like:
--8<---------------cut here---------------start------------->8---
(use-modules (gnu system images pine64))
pine64-barebones-os
--8<---------------cut here---------------end--------------->8---
Note that this very image is also build by the CI and available here:
https://ci.guix.gnu.org/search/latest/image?query=spec:guix-master+status:success+system:x86_64-linux+pine64
You should be able to flash this image on a microsd and directly boot
from it.
I will try to improve the documentation accordingly, but until then you
can also read this:
https://othacehe.org/the-guix-system-image-api.html.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-11-04 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 16:44 Who has had success installing a Guix system on arm? Jesse Gibbons
2020-11-04 17:44 ` Mathieu Othacehe [this message]
2020-11-05 14:23 ` Jesse Gibbons
2020-11-04 19:32 ` Julien Lepiller
2020-11-05 6:44 ` Jan Nieuwenhuizen
2020-11-05 17:10 ` Vagrant Cascadian
2020-11-05 14:24 ` Timothy Sample
2020-11-05 14:43 ` Jesse Gibbons
2020-11-05 17:07 ` Vagrant Cascadian
2020-11-05 19:20 ` Timothy Sample
2020-11-06 14:29 ` Simon South
2020-11-06 15:12 ` Tobias Geerinckx-Rice
2020-11-06 17:39 ` Enrico Schwass via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg9p585g.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=help-guix@gnu.org \
--cc=jgibbons2357@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).