From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, ryan <rysa88@posteo.net>
Subject: Re: Help installing on Cubox-i/Arm Boards
Date: Thu, 05 May 2022 07:25:31 +0200 [thread overview]
Message-ID: <2398C296-69E4-4D99-8A0E-618A5E6D43CC@lepiller.eu> (raw)
In-Reply-To: <341dbfa19c60b49fd54c77f9f264207d1a8793e2.camel@posteo.net>
Hi Ryan!
Installing on armhf/aarch64 SBCs is not easy. I'm not sure the graphical installer is available for these platforms.
The tarball you found is for installing Guix, the package manager, on top of another distro. It's not the distro itself.
This blog post might help figuring out what you need for generating an installer image for your board: https://guix.gnu.org/en/blog/2019/guix-on-an-arm-board/
For generating the correct image from x86, you'll need to cross-compile the installer with --target=arm-linux-gnueabihf (for armhf).
Good luck!
On May 4, 2022 6:56:26 AM GMT+02:00, ryan <rysa88@posteo.net> wrote:
>Hi all
>
>First of all I am completely new to quix (I use parabola Gnu/linux-
>libre), so my apologies if I ask some questions that might seem very
>obvious.
>
>I would like to build a disk image for a Cubox-i variant that I have,
>it currently has nothing on it. If setup guix on my x86_64
>device/laptop using the guided installer, can I build it from there
>easily using the instructions here?:
>https://guix.gnu.org/manual/en/html_node/Building-the-Installation-Image.html
>I also see there is a binary tarball, but not sure what to do with it?
>
>or am I jumping ahead? I see that uboot in guix is available for the
>cubox-i, but I am not sure where I need to start?
>
>Any help with getting guix setup on the armvh device would be most
>useful and appreciated.
>
>Many Thanks
>Ryan
>
next prev parent reply other threads:[~2022-05-05 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 4:56 Help installing on Cubox-i/Arm Boards ryan
2022-05-05 5:25 ` Julien Lepiller [this message]
2022-05-05 15:26 ` Vagrant Cascadian
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=2398C296-69E4-4D99-8A0E-618A5E6D43CC@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=rysa88@posteo.net \
/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).