Re: Installation issue on FrameWork laptop.

[Pietro Mele <pietrom16@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3658 bytes --]

Hi Richard,

I tried to install the latest build (from 06/06/2024), and I get the exact
same issue.

I have not been able to copy files to a USB flash drive in the current
system status (even if I have access to the command line, but with an
extremely small set of available commands).

I attached some screenshots.

Thank you for your support.

Kind regards,
Pietro



On Sun, Jun 2, 2024 at 3:51 PM Richard Sent <richard@freakingpenguin.com>
wrote:

> 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.
>

[-- Attachment #2: 20240606_173304.jpg --]
[-- Type: image/jpeg, Size: 757798 bytes --]

[-- Attachment #3: 20240606_172949.jpg --]
[-- Type: image/jpeg, Size: 676271 bytes --]

[-- Attachment #4: 20240606_173026.jpg --]
[-- Type: image/jpeg, Size: 655441 bytes --]