unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon South <simon@simonsouth.net>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: help-guix@gnu.org
Subject: Re: Building installation image for ROCK64
Date: Sun, 12 Apr 2020 12:25:55 -0400	[thread overview]
Message-ID: <878sj0isbw.fsf@simonsouth.net> (raw)
In-Reply-To: <877dylaty5.fsf@gmx.com> (Pierre Langlois's message of "Sun, 12 Apr 2020 12:18:10 +0200")

Pierre Langlois <pierre.langlois@gmx.com> writes:
> You probably noticed this takes a *long* time to run, making it quite
> tedious to test changes (I believe this is being worked on though).
>
> In the meanwhile, what you can do instead is setup the SD card
> manually...

Thanks, this should be a BIG help. It takes around three hours and
twenty minutes to build a new image on the ROCK64 itself which, as you
say, slows down testing considerably. (I assume the main reason is that
KVM support is explicitly disabled for aarch64 in gnu/system/vm.scm, but
that's a separate issue.)

> It was quite some back-and-forth to figure out what was needed. What I
> did was to boot a different distro, I think it was Arch at the time, and
> look at the dmesg output to see what drivers were loading that I didn't
> see with guix.

This sounds like a good plan.

Thanks very much for the tips, Pierre. I'll give them all a shot and
report the results.

-- 
Simon South
simon@simonsouth.net

      parent reply	other threads:[~2020-04-12 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 19:48 Building installation image for ROCK64 Simon South
2020-04-11 21:12 ` Vagrant Cascadian
2020-04-12 16:19   ` Simon South
2020-04-26 14:31   ` Simon South
2020-04-26 17:09     ` Vagrant Cascadian
2020-04-27 13:19       ` Simon South
2020-04-27 17:22         ` Vagrant Cascadian
2020-04-12 10:18 ` Pierre Langlois
2020-04-12 10:27   ` Pierre Langlois
2020-04-12 16:25   ` Simon South [this message]

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=878sj0isbw.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=help-guix@gnu.org \
    --cc=pierre.langlois@gmx.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).