I had an epiphany and found my way to the kernel downgrade.
`(operating-system (kernel linux-libre-5.10))` is the latest version
before the regression.
Hi Andrew,
Andrew Tropin skribis:
> Those patches introduce a breaking change, but the surface and number of
> people affected should be small if everyone migrated to
> xdg-configuration-files. It removes the special handling of dot files
> in symlink-manager and doesn't add a leading dot
Christopher Baines schreef op di 15-03-2022 om 21:11 [+]:
> grub can't be built for powerpc64le, I believe the same failure
> occurs
> with native builds or cross compilation from x86_64. I think this
> might
> have always been the case.
>
> This is the error from the build log:
>
>
Hi,
On Tue, 15 Mar 2022 21:11:37 +
Christopher Baines wrote:
> grub can't be built for powerpc64le, I believe the same failure occurs
> with native builds or cross compilation from x86_64. I think this might
> have always been the case.
>
> This is the error from the build log:
>
>
Greetings.
On Monday I installed the stable GuixSD on my newly acquired Lenovo
X200 with an Atheros Wi-Fi (ath9 driver). It worked like a charm, so I
decided to install the unstable variant.
Yesterday I lost half a day fighting to install and understand the
development release. The overall
Hi,
There are valid use cases for uninstalling Guix:
- On a Trisquel VM I use Guix to add matterbridge to it with guix pack.
Once the tarball is done with guix pack I remove Guix and install the
pack to limit the attack surface. To do the updates I install Guix
back and re-do a tarball.
-
Hi Maxim,
I lost the context; could you please edit the title according to your
last findings (e.g. wifi driver X not compatible with linux-libre 5.15+)
:-).
That's my confusion as well. My WiFi card (AR9380) uses ath9k, which I
presume is a standard/minimal driver for networking in Linux
Hi Liliana,
Thank you for your response :)
> Alternatively, Guix could take the expression specified via -e and
> write it to disk.
I think this would be the best way to resolve this issue. Also, thanks for your
explanation.
> LOAD_PATH tweaking should be considered harmful and void your
>
