public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Kernel-3.10 Nvidia Emerge Failure And Other Stuff
Date: Thu, 4 Jul 2013 21:28:08 -0400	[thread overview]
Message-ID: <20130704212808.9e4881426be73ebda456a76f@comcast.net> (raw)
In-Reply-To: <kr51ha$502$1@ger.gmane.org>

> 
> My interpretation of this message in the nvidia-drivers ebuild is that
> the maintainers assume that you switch to nouveau.
>

I think it means that the problem occurs so frequently that they
do not want to be bothered with bug reports -- and rightly so.

My great disappointment is that xorg or nvidia or whoever was
responsible had decided to stop the legacy nv driver that was
part of xorg itself.  I don't do gaming and I have no need for
ultra-high performance graphics.  The nv driver was always good
enough for me.

But development stopped on nv a few years ago and it no longer
supports the newer Nvidia cards.

Frank Peters



  reply	other threads:[~2013-07-05  1:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 19:35 [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff Frank Peters
2013-07-01 19:51 ` Mark Knecht
2013-07-01 20:04   ` Dale
2013-07-02  0:57     ` B Vance
2013-07-02  0:38       ` Frank Peters
2013-07-01 20:30   ` Mark Knecht
2013-07-01 20:51     ` Rich Freeman
2013-07-04 23:57     ` Mark Knecht
2013-07-05  1:08       ` Frank Peters
2013-07-01 21:06   ` Frank Peters
2013-07-02 11:29 ` [gentoo-amd64] " Duncan
2013-07-02 16:54   ` Frank Peters
2013-07-03  2:10     ` Duncan
2013-07-04 23:48 ` Sven Köhler
2013-07-05  1:28   ` Frank Peters [this message]
2013-07-05 16:41     ` Sven Köhler

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=20130704212808.9e4881426be73ebda456a76f@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