unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>
Subject: Re: Who has had success installing a Guix system on arm?
Date: Thu, 05 Nov 2020 14:20:08 -0500	[thread overview]
Message-ID: <87ft5nfw5z.fsf@ngyro.com> (raw)
In-Reply-To: <87mtzv68bm.fsf@yucca> (Vagrant Cascadian's message of "Thu, 05 Nov 2020 09:07:41 -0800")

Hi Vagrant,

Vagrant Cascadian <vagrant@debian.org> writes:

> On 2020-11-05, Timothy Sample wrote:
>
>> 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.
>
> Curious; I've never been able to get the U-Boot working on the veyron
> speedy,

AIUI, commit fffdf7290cee85232ee522e27c09c7f1178e6219 makes it work.  It
looks like it was included in 2020.07.  I was able to flash U-Boot onto
an ASUS C201 and now it boots nicely (and can be rolled back with a nice
little menu).  (I was gearing up to debug U-Boot myself, and am very
relieved someone beat me to it!)

> but use an old libreboot to boot guix (but only linux-libre
> versions < 5.5, 5.6+ gets stuck in some loop). The initrd size appears
> to be a non-issue for me.

I have the same problem with the kernel, and am using 5.4 currently.

I tried with Libreboot and with stock Depthcharge and had no luck.  I’m
pretty sure it’s a size issue, because every image I built bigger than
16M could not boot, but plenty of smaller ones could (if I made my own
initial RAM disk, say).  IIRC, upstream Depthcharge bumped the size
limit from 16M to 32M and that version should be included in Libreboot.
However, it didn’t work for me in practice.  Either way, I am much
happier using U-Boot.

>> 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.
>
> Yes, I'll definitely agree that it is improving, but maybe not that it
> is close. :)

That’s fair!  My glasses are a bit rosy right now because of my recent
success with U-Boot.


-- Tim


  reply	other threads:[~2020-11-05 19:23 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 [this message]
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=87ft5nfw5z.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=help-guix@gnu.org \
    --cc=jgibbons2357@gmail.com \
    --cc=vagrant@debian.org \
    /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).