public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Erik Mackdanz <erikmack@gmail.com>
To: "J. Roeleveld" <joost@antarean.org>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Nvidia and optimus
Date: Wed, 17 Dec 2014 07:16:54 -0600	[thread overview]
Message-ID: <87sige4drt.fsf@msi.mackdanz.net> (raw)
In-Reply-To: <6065427.s3vDGgfdQI@andromeda>

"J. Roeleveld" <joost@antarean.org> writes:

> On Tuesday, December 16, 2014 05:46:30 PM Erik Mackdanz wrote:
>> Heiko Baums <lists@baums-on-web.de> writes:
>> > I don't know if, but I don't think that, it will work with
>> > x11-drivers/xf86-video-nouveau.
>> 
>> I used bumblebee for quite a while.  It worked okay, but every upgrade I
>> would have to fiddle with it again.
>> 
>> I switched to the Nouveau driver and I'm very glad I did.  "Conventional
>> wisdom" says Nouveau quality is lower than Nvidia, but I found it worked
>> better on some things (Second Life).
>> 
>> As someone else pointed out, with Nouveau the GPU remains on all the
>> time consuming power.  This is the downside.
>> 
>> If ease-of-use and/or open licensing are more important to you than top
>> rendering quality and power consumption, consider using Nouveau.
>
> I've been using bumblebee for over a year now. (First laptop with Optimus) and 
> not had any issues. It always works as advertised.
>
> What issues did you experience?
>
I remember more than once changing bumblebee.conf during an upgrade,
when the service failed to start.  This is over two years ago now, so I
don't remember any more than that.

You could tell me that bumblebee is now stable and rock-solid, but I
still wouldn't switch from Nouveau.  I've had a good experience, and
open source matters to me.

On top of that, this laptop has only a year or so left before I replace
it, and I know now to avoid Optimus entirely in the future.

> --
> Joost
>

-- 
Erik Mackdanz


  parent reply	other threads:[~2014-12-17 13:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 10:42 [gentoo-user] Nvidia and optimus behrouz khosravi
2014-12-16 11:08 ` J. Roeleveld
2014-12-16 11:55   ` behrouz khosravi
2014-12-16 12:54     ` J. Roeleveld
2014-12-16 18:11       ` behrouz khosravi
2014-12-16 19:49         ` J.  Roeleveld
2014-12-16 20:59           ` behrouz khosravi
2014-12-16 21:29             ` J. Roeleveld
2014-12-17  9:23               ` behrouz khosravi
2014-12-17  9:50                 ` J. Roeleveld
2014-12-17 15:19                   ` behrouz khosravi
2014-12-18  4:53                     ` [gentoo-user] " »Q«
2014-12-16 21:39     ` [gentoo-user] " Heiko Baums
2014-12-16 22:37       ` Sid S
2014-12-16 23:46       ` Erik Mackdanz
2014-12-17  1:40         ` Sid S
2014-12-17  6:35         ` J. Roeleveld
2014-12-17 10:45           ` Heiko Baums
2014-12-17 13:16           ` Erik Mackdanz [this message]
2014-12-17 13:59             ` J. Roeleveld
2014-12-17  9:39       ` behrouz khosravi
2014-12-17  9:53         ` J. Roeleveld
2014-12-17 10:49         ` Heiko Baums
2014-12-17 11:50           ` J. Roeleveld
2014-12-17 14:27       ` Christian Kruse
2014-12-18  5:28   ` behrouz khosravi
2014-12-18 18:40     ` Fábio Emilio Costa
2014-12-18 19:03       ` J.  Roeleveld
2014-12-18 19:34         ` Heiko Baums
2014-12-19  6:48           ` Sid S

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=87sige4drt.fsf@msi.mackdanz.net \
    --to=erikmack@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=joost@antarean.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