public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Terminals not closing after exit anymore
Date: Sat, 30 Nov 2013 01:20:46 +0200	[thread overview]
Message-ID: <5299214E.7010904@gmail.com> (raw)
In-Reply-To: <201311291944.04030.michaelkintzios@gmail.com>

On 29/11/2013 21:43, Mick wrote:
> On Friday 29 Nov 2013 16:39:11 Chris Stankevitz wrote:
>> On Sun, Nov 24, 2013 at 6:14 AM, Marc Stürmer <mail@marc-stuermer.de> wrote:
>>> When working under X11 in a terminal and I type "exit" in the shell, the
>>> terminal does not close itself anymore.
>>
>> I had the same problem and fixed it with:
>>
>>   echo =x11-drivers/nvidia-drivers-331.20 >> /etc/portage/package.mask
>>
>> This downgraded me to:
>>
>>   x11-drivers/nvidia-drivers-325.15  USE="X acpi (multilib) tools
>> -pax_kernel"
> 
> I'm reading all these messages about Nvidia driver versions causing problems 
> and I'm wondering if for my next box I should just stick with radeon, which 
> has not really given me any trouble for as long as I can remember.
> 

nVidia's stuff is not too bad actually, and nouveau is adequate for a
desktop if you don't need fancy 3D.

Two things give nVidia a bad rap (both unfairly IMHO)

1. The latest greatest drivers do often give trouble. What nVidia
considers stable is not what the world considers stable, it's better
described as "good enough to be released for testing".IOW about the same
as ~arch. Graphics hardware is hard to test, there's just so many of
them, so many code paths and so many X-server versions out there. nVidia
usually gets it right eventually, where "eventually" is definitely
"longer than one week"

2. They drop support quite early in current drivers for old cards and
relegate it to legacy drivers. This is their marketing strategy, they
chase the latest and greatest (it's a fast moving market and if you
snooze you lose). If your card is old enough to have no realistic
support at all, there's Nouveau.

So basically it a lot like the kernel. If you want the latest stuff, use
the latest driver and deal with any fallout. If you want stability, stay
two versions behind at least

-- 
Alan McKinnon
alan.mckinnon@gmail.com



  parent reply	other threads:[~2013-11-29 23:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 14:14 [gentoo-user] Terminals not closing after exit anymore Marc Stürmer
2013-11-24 15:53 ` meino.cramer
2013-11-24 16:09   ` Marc Stürmer
2013-11-24 16:43     ` meino.cramer
2013-11-25 14:15 ` Randy Barlow
2013-11-25 16:15   ` Marc Stürmer
2013-11-25 21:05     ` Peter Weilbacher
2013-11-26 12:20       ` Marc Stürmer
2013-11-26 12:28         ` Dale
2013-11-26 12:30           ` Marc Stürmer
2013-11-26 13:00             ` Dale
2013-11-26 16:45         ` Peter Weilbacher
2013-11-29 16:39 ` Chris Stankevitz
2013-11-29 19:43   ` Mick
2013-11-29 20:31     ` Peter Humphrey
2013-11-29 21:13     ` Chris Stankevitz
2013-11-29 21:34       ` Dale
2013-11-29 22:55         ` Mick
2013-11-29 23:24           ` Alan McKinnon
2013-11-30  1:04           ` Chris Stankevitz
2013-11-29 23:20     ` Alan McKinnon [this message]
2013-11-29 23:47       ` Dale

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=5299214E.7010904@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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