From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: bumblebee: set correct MODPATH_NVIDIA after libglvnd switch
Date: Tue, 31 Dec 2019 15:24:43 +0100 [thread overview]
Message-ID: <20191231142443.xq6jODjO6kEDnCV7JdxtMtlO-fdilwtJ6vGHrnbnHh0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17933@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
There's a merged pull request on the void-packages repository
bumblebee: set correct MODPATH_NVIDIA after libglvnd switch
https://github.com/void-linux/void-packages/pull/17933
Description:
This simple change results in a working bumblebee setup in a `mesa`/`nvidia390` Optimus laptop. After the switch to `libglvnd`, `bumblebee` can be setup correctly because `nvidia390` doesn't attempt to replace `mesa` anymore. Enabling the `bumblebeed` service makes Xorg pick up Mesa's GLX by default, while apps run with `optirun` use NVIDIA's GL. Arch has an additional [patch](https://git.archlinux.org/svntogit/community.git/tree/trunk/0008-libglvnd.patch?h=packages/bumblebee) for `libglvnd` support which sets the __GLVND_DISALLOW_PATCHING env variable but I didn't find it necessary, maybe it's the result of a recent `libglvnd` update. If someone else finds that necessary, we can include it.
Tested on a Optimus laptop with `mesa`/`nvidia390` configuration (but should also work for `mesa`/`nvidia`, although NVIDIA's Prime Render Offload is a much better method performance-wise).
prev parent reply other threads:[~2019-12-31 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 12:31 [PR PATCH] " voidlinux-github
2019-12-31 14:24 ` voidlinux-github [this message]
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=20191231142443.xq6jODjO6kEDnCV7JdxtMtlO-fdilwtJ6vGHrnbnHh0@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).