unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Who has had success installing a Guix system on arm?
Date: Thu, 05 Nov 2020 09:24:29 -0500	[thread overview]
Message-ID: <87o8kbg9uq.fsf@ngyro.com> (raw)
In-Reply-To: <260d2ed2-2af6-73f0-be62-27d25098bef2@gmail.com> (Jesse Gibbons's message of "Wed, 4 Nov 2020 09:44:24 -0700")

Hi Jesse,

Jesse Gibbons <jgibbons2357@gmail.com> writes:

> Has anyone in this mailing list successfully used the Guix system on
> an armhf or aarch64 computer?

I don’t have a lot of details for you, but I can confirm that I’ve used
Guix on three armhf boards: BeagleBone Black, veyron_speedy (ASUS C201),
and veyron_minnie (ASUS C100PA).

For the BeagleBone, it required using an older version of U-Boot.
Upstream U-Boot has stopped supporting it.  Our package patches support
back in, but it didn’t work for me.  I believe I’ve tried to use Guix on
it three times and only succeeded once.  If you have a BeagleBone Black
and want to use Guix, let me know.  I could track down my notes and see
if I can still produce a usable image.

For the Veyron boards, it is starting to work quite well.  The current
version of U-Boot can boot these boards, but you can also boot U-Boot
from the stock firmware (which is Depthcharge).  This is needed because
the Guix initial RAM disk is too big for Depthcharge to boot directly.

The point I’m trying to make is that Guix can be made to work on armhf,
but it is not at all smooth sailing.  There are usually one or two
things that need fixing before it will work.  IME, we are close to
having a decent experience, but we’re definitely not there yet.  The
saving grace is that Guix makes working on these things pretty painless.


-- Tim


  parent reply	other threads:[~2020-11-05 14:24 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 [this message]
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=87o8kbg9uq.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --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).