From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
Date: Tue, 20 Mar 2012 00:03:06 -0400 [thread overview]
Message-ID: <20120320000306.aacea86d.frank.peters@comcast.net> (raw)
In-Reply-To: <CAK2H+ed4+1ogGFtWfDGDDnPtEL=FbNM8-JbhWzuN6HxkoEEiPw@mail.gmail.com>
On Mon, 19 Mar 2012 14:40:34 -0700
Mark Knecht <markknecht@gmail.com> wrote:
>
> I have no problem with you or anyone else running nouveau. None at all.
>
> I do have a problem with someone saying 'it's time for everyone to
> give up nvidia-drivers' without demonstrating they know the full
> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
> people who don't need anything other than basic X capabilities should
> consider running nouveau' I wouldn't have even chimed in.
>
I think the main complaint is that the Nvidia drivers are closed
binary blobs while Nouveau is an attempt to create an entirely
open source driver. The spirit of free software demands that we
support these open initiatives.
Actually, until recently, I was very happy using the legacy open
source xorg nvidia driver known simply as as "nv." It is still
available in Gentoo as x11-drivers/xf86-video-nv.
Since I do not do gaming or other intensive graphic activities,
I could get by nicely with just nv. However, the nv driver does
not seem to support the latest hardware too well. On one of
my machines I have a card based on Nvidia GeForce 210. Although
the nv driver works with this card, it does not enable the Xv
extension and consequently the graphic response is poor.
On older cards nv does work quite well for ordinary purposes.
Frank Peters
next prev parent reply other threads:[~2012-03-20 6:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:12 [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Frank Peters
2012-03-19 16:35 ` Mark Knecht
2012-03-19 19:05 ` Frank Peters
2012-03-19 19:16 ` Mark Knecht
2012-03-19 19:30 ` Frank Peters
2012-03-19 20:08 ` Mark Knecht
2012-03-19 20:25 ` Paul Hartman
2012-03-19 19:14 ` Cheng Renquan
2012-03-19 19:17 ` Mark Knecht
2012-03-19 21:28 ` Barry Schwartz
2012-03-19 21:40 ` Mark Knecht
2012-03-20 0:34 ` Barry Schwartz
2012-03-20 4:03 ` Frank Peters [this message]
2012-03-20 6:20 ` Barry Schwartz
2012-03-20 18:31 ` [gentoo-amd64] " Duncan
2012-03-20 18:27 ` Duncan
2012-03-22 16:03 ` [gentoo-amd64] " Mark Knecht
2012-03-22 18:41 ` Frank Peters
2012-03-22 18:58 ` Mark Knecht
2012-03-22 21:18 ` Barry Schwartz
2012-03-22 21:21 ` Barry Schwartz
2012-03-22 21:32 ` Outside of portage (was Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers) Barry Schwartz
2012-03-22 23:04 ` Paul Hartman
2012-03-22 23:28 ` Barry Schwartz
2012-03-22 23:33 ` Harry Holt
2012-03-23 8:42 ` Benny Pedersen
2012-03-23 13:50 ` Harry Holt
2012-03-23 0:14 ` Gary E. Miller
2012-03-23 1:30 ` Mark Knecht
2012-03-23 1:56 ` Barry Schwartz
2012-03-23 4:05 ` [gentoo-amd64] Re: Outside of portage (was " Duncan
2012-03-23 12:41 ` Outside of portage (was Re: [gentoo-amd64] " Frank Peters
2012-03-23 15:49 ` Barry Schwartz
2012-03-23 18:09 ` Dale
2012-03-23 18:28 ` [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Mark Knecht
2012-03-23 19:11 ` Mark Knecht
2012-03-24 0:20 ` Frank Peters
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=20120320000306.aacea86d.frank.peters@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@lists.gentoo.org \
/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