From: Simon South <simon@simonsouth.net>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Who has had success installing a Guix system on arm?
Date: Fri, 06 Nov 2020 09:29:38 -0500 [thread overview]
Message-ID: <87pn4qeey5.fsf@simonsouth.net> (raw)
In-Reply-To: <260d2ed2-2af6-73f0-be62-27d25098bef2@gmail.com> (Jesse Gibbons's message of "Wed, 4 Nov 2020 09:44:24 -0700")
Jesse Gibbons <jgibbons2357@gmail.com> writes:
> Has anyone in this mailing list successfully used the Guix system on
> an armhf or aarch64 computer?
Yes; I'm currently running up-to-date versions of Guix System on a
ROCK64 and a Pinebook Pro, both AArch64 systems from PINE64
(https://pine64.org/).
I wrote at the time about my experience getting the ROCK64 up and
running, including a sample operating-system definition:
https://lists.gnu.org/archive/html/help-guix/2020-04/msg00153.html
This is still essentially current, except there is no need for the
ridiculous dance involving moving a jumper around; turns out U-Boot
offers a command that makes it easy to start up from one device but
finish booting from another.
As others have noted, AArch64 support in Guix is generally quite good
now, but a certain amount of patience is required.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-11-06 14:34 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
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 [this message]
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=87pn4qeey5.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--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).