From: Yasuaki Kudo <yasu@yasuaki.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org, Joshua Branson <jbranso@dismail.de>
Subject: Re: Two more computers unable to start X with GDM
Date: Mon, 29 Mar 2021 17:06:04 +0900 [thread overview]
Message-ID: <4E82389E-CF2A-4E52-B236-06CB748D38CB@yasuaki.com> (raw)
In-Reply-To: <YF94Zaf+Xsz0Za/Y@jasmine.lan>
I read a little bit about the current state of video cards, etc - man this seems like an uphill battle😅 Basically no manufacture sympathizes with the concept of total transparency.
I was just thinking what the practical end-game of this might be - do you think at some point there will be an FPGA+power+various I/O ports kit that can be totally programmed to provide CPU and video acceleration? Something like that might be the only way to end this nonsense😅
Then the battle will be proprietary vs free software rather than hardware. But then again, I don't know what kind of nasty patents there might be...
-Yasu
> On Mar 28, 2021, at 03:25, Leo Famulari <leo@famulari.name> wrote:
>
> On Sat, Mar 27, 2021 at 10:14:05AM -0400, Bone Baboon wrote:
>> X server worked fine with this NVIDIA GeForce FX 5200 GPU when Debian
>> was installed on this computer. It also looks like Debian uses a
>> deblobbed kernal based on this Wikipedia article.
>> https://en.wikipedia.org/wiki/Binary_blob
>
> The Guix kernel (linux-libre) and the Debian kernel (Linux) have
> different hardware support and, in general, Linux supports more hardware
> than linux-libre.
>
next prev parent reply other threads:[~2021-03-29 8:08 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
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 [this message]
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=4E82389E-CF2A-4E52-B236-06CB748D38CB@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
--cc=leo@famulari.name \
/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).