From: Pierre Langlois <pierre.langlois@gmx.com>
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:27:29 +0200 [thread overview]
Message-ID: <875ze5atim.fsf@gmx.com> (raw)
In-Reply-To: <877dylaty5.fsf@gmx.com>
Pierre Langlois writes:
> Hi Simon,
>
> Simon South writes:
>
>> Has anyone successfully built an installation image for a PINE64 ROCK64
>> ARM SBC?
>
> I managed to setup a ROCKPRO64 a few months ago (rk3399 chipset instead
> of rk3328), maybe I can help :-).
>
>>
>> There's a definition for it in gnu/system/install.scm, but building the
>> image with
>>
>> guix system disk-image --system=aarch64-linux \
>> -e "(@ (gnu system install) rock64-installation-os)"
>
> 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,
> say using fdisk & mkfs.ext4, and then use the 'guix system init' command
> to install guix on it:
>
> $ mount /dev/mmcblk0 /mnt
> $ guix system init my-config.scm /mnt
Oh, also, when doing this make sure my-config.scm has the correct target
in the bootloader entry, to prevent accidentally writing the bootloader
on the wrong SD card (from personal experience breaking the host system
that lived on that other SD card :-D).
next prev parent reply other threads:[~2020-04-12 10:27 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 [this message]
2020-04-12 16:25 ` Simon South
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=875ze5atim.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=help-guix@gnu.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).