From: Vagrant Cascadian <vagrant@debian.org>
To: Andreas Enge <andreas@enge.fr>
Cc: help-guix@gnu.org
Subject: Re: Guix on Novena
Date: Tue, 01 Sep 2020 09:41:04 -0700 [thread overview]
Message-ID: <87eenlo3fj.fsf@ponder> (raw)
In-Reply-To: <20200901093841.GA4371@jurong>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On 2020-09-01, Andreas Enge wrote:
> I would like to put our armhf Novena board back into service for the Guix
> build farm. In the past, I have been using Guix on Debian on the machine.
> Has anyone had success in installing Guix "The GNU System" on a Novena?
> If yes, could you point me to a write-up on what to do or otherwise help
> me get going?
I have one and had a Guix System install on it, but it's been some
months since I've booted it. There's another bug I need to test with it,
so I'll dig it out of the closet sometime soon so I can poke at the
configuration and check the latest status...
The hardest thing was always specifying all the right initrd modules in
the operating system configuration to use "linux-libre", especially as
the modules needed sometimes change between kernel versions. I've
usually had more luck with "linux-libre-arm-generic" which usually works
fine for headless systems and has more things configured as builtins.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-09-01 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:38 Guix on Novena Andreas Enge
2020-09-01 16:41 ` Vagrant Cascadian [this message]
2020-09-01 18:06 ` Andreas Enge
2020-09-02 17:30 ` Vagrant Cascadian
2020-09-02 18:05 ` Andreas Enge
2020-09-02 18:33 ` Vagrant Cascadian
2020-09-06 8:45 ` Andreas Enge
2020-09-06 14:23 ` Vagrant Cascadian
2020-09-07 20:12 ` Andreas Enge
2020-09-07 12:11 ` Andreas Enge
2020-09-08 10:56 ` Andreas Enge
2020-09-08 12:30 ` Efraim Flashner
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=87eenlo3fj.fsf@ponder \
--to=vagrant@debian.org \
--cc=andreas@enge.fr \
--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).