From: Bone Baboon <bone.baboon@disroot.org>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: help-guix@gnu.org
Subject: Re: Two more computers unable to start X with GDM
Date: Sat, 27 Mar 2021 10:39:14 -0400 [thread overview]
Message-ID: <875z1cu0dp.fsf@disroot.org> (raw)
In-Reply-To: <CDCA4000-D133-415A-8B21-7500735DD912@yasuaki.com>
Yasuaki Kudo writes:
> My apologies if this has been already tried but I personally always
> use regular Linux with black magic binary drivers unacceptable to
> plain Guix distribution. 😅
>
> My AMD (both CPU and Graphics card) computer's visuals will freeze
> without the modification of the settings to avoid LibreLinux that
> comes standard with Guix.
>
> Recent AMD video cards appear to have out of the box native drivers
> built into the Linux Kernel - that's why replaced Nvidia with AMD 😄.
> I have a stress-free graphics environment using Guix OS and Regular
> Linux. (There was text terminal latency issues with X11 so I use
> Wayland - it has its limitations and bugs but works better for me😄
Thank you for your suggestion.
Switching from Linux-libre to Linux with Guix would be a last resort for
me. The deblobbed Linux-libre kernel was one of the key features that
attracted me to Guix.
I would be more inclined to try to make one of these work first:
- Gentoo with a deblobbed kernel
- OpenBSD (has no binary blobs)
- Devuan testing (I think they have a deblobbed kernel)
However I still want to make Guix with Linux-libre work as Guix has
other features that I like that Gentoo, OpenBSD and Devuan do not have.
next prev parent reply other threads:[~2021-03-27 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 0:43 Two more computers unable to start X with GDM Bone Baboon
2021-03-27 2:42 ` Joshua Branson
2021-03-27 6:13 ` Yasuaki Kudo
2021-03-27 14:39 ` Bone Baboon [this message]
2021-03-27 14:14 ` Bone Baboon
2021-03-27 15:29 ` Joshua Branson
2021-03-27 18:24 ` Leo Famulari
2021-03-29 8:06 ` Yasuaki Kudo
2021-03-29 14:32 ` Gary Johnson
2021-03-29 16:24 ` Leo Famulari
2021-03-29 15:13 ` Joshua Branson
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=875z1cu0dp.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.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.
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).