all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: Pietro Mele <pietrom16@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Installation issue on FrameWork laptop.
Date: Sun, 02 Jun 2024 10:51:33 -0400	[thread overview]
Message-ID: <87ed9fe6tm.fsf@freakingpenguin.com> (raw)
In-Reply-To: <CAN0Og_CJYYGz7guGaTpf7=ou6q7d_jnXyAQ_2GBfm_NXzVYtBw@mail.gmail.com> (Pietro Mele's message of "Thu, 30 May 2024 22:37:04 +0100")

Pietro Mele <pietrom16@gmail.com> writes:

> I am trying to install GNU Guix System on a new laptop (FrameWork 16, AMD
> Ryzen 7 7840HS).
> I am using this file:
> https://ftpmirror.gnu.org/gnu/guix/guix-system-install-1.4.0.x86_64-linux.iso
>
> At the beginning, I get this warning:
>
> Hardware support warning
> Devices not supported by free software were found on your computer:
>   - 1002 15bf
>
> From that code it should correspond to my integrated GPU not being
> recognized. The reason could be that this APU was released after the
> currently available Guix version.

If the official installer runs, I imagine the installed image should at
least be functional enough to enter a terminal and run an update. You
probably do *not* need to do the following, but I'll mention it just in case:

One solution could be to generate a newer installer image instead of
starting on the 1.4.0 release and use this new image for the
installation. Ordinarily you'd be able to do so from
https://guix.gnu.org/en/download/latest/, but Cuirass seems to not
support downloading build outputs from a web browser for one reason or
another.

If you have an existing Linux system, you can install Guix on a foreign
distribution, ensure it's up-to-date via $ guix pull and $ guix
describe, then generate a new installation iso via $ guix system image
-e '(@ (gnu system install) installation-os)' --image-type=iso9660.

Again, probably not necessary.

> The installation process starts, and these are the last logs produced
> before the failure:
>
> ...
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
> 0.0%
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
> 0.0%
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
> 0.0%
> \builder for `/gnu/store/bwy...ilb-slock-1.4.tar.gz.drv' failed to produce
> output path `/gnu/store/la705...dqf-slock-1.4.tar.gz'
> *build of /gnu/store/bwy...ilb-slock-1.4.tar.gz.drv failed*
> View build log at '/var/log/guix/drvs/bw/...tar.gz.drv.gz'.
> building /gnu/store/br3c...CUnit-2.1-3.tar.bz2.drv...
> cannot build derivation `/gnu/store/256d...slock-1.4.tar.gz.drv': 1
> dependencies couldn't be built
> guix system: *error*: build of `/gnu/store/256d...slock-1.4.tar.gz.drv'
> failed
> Command ("guix" "system" "init" "--fallback"" "/mnt/etc/config.scm" "/mnt")
> exited with value 1

Can you post the output of the build log mentioned in those messages? I
assume the ... was added by you and the full path was printed, but if
not you should be able to get the path via $ guix build --log-file slock.

> View build log at '/var/log/guix/drvs/bw/...tar.gz.drv.gz'.

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.


  reply	other threads:[~2024-06-03  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 21:37 Installation issue on FrameWork laptop Pietro Mele
2024-06-02 14:51 ` Richard Sent [this message]
2024-06-07  9:46   ` Pietro Mele

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed9fe6tm.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=help-guix@gnu.org \
    --cc=pietrom16@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.