From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-drivers/nvidia-drivers/, x11-drivers/nvidia-drivers/files/
Date: Sun, 6 Dec 2015 05:32:28 +0000 (UTC) [thread overview]
Message-ID: <1449379933.5b59b721ce933854d4f6191fc67536d0f5e0113a.jer@gentoo> (raw)
commit: 5b59b721ce933854d4f6191fc67536d0f5e0113a
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 6 05:32:13 2015 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sun Dec 6 05:32:13 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5b59b721
x11-drivers/nvidia-drivers: Unload nvidia-modeset as needed (bug #566242 by Adam Shea).
Package-Manager: portage-2.2.26
x11-drivers/nvidia-drivers/files/nvidia-rmmod.conf | 3 +++
.../{nvidia-drivers-358.16.ebuild => nvidia-drivers-358.16-r1.ebuild} | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/x11-drivers/nvidia-drivers/files/nvidia-rmmod.conf b/x11-drivers/nvidia-drivers/files/nvidia-rmmod.conf
new file mode 100644
index 0000000..48a8273
--- /dev/null
+++ b/x11-drivers/nvidia-drivers/files/nvidia-rmmod.conf
@@ -0,0 +1,3 @@
+# Nvidia UVM support
+
+remove nvidia modprobe -r --ignore-remove nvidia-modeset nvidia-uvm nvidia
diff --git a/x11-drivers/nvidia-drivers/nvidia-drivers-358.16.ebuild b/x11-drivers/nvidia-drivers/nvidia-drivers-358.16-r1.ebuild
similarity index 99%
rename from x11-drivers/nvidia-drivers/nvidia-drivers-358.16.ebuild
rename to x11-drivers/nvidia-drivers/nvidia-drivers-358.16-r1.ebuild
index 44a9162..e81b1bc 100644
--- a/x11-drivers/nvidia-drivers/nvidia-drivers-358.16.ebuild
+++ b/x11-drivers/nvidia-drivers/nvidia-drivers-358.16-r1.ebuild
@@ -244,7 +244,7 @@ src_install() {
# pkg_preinst, see bug #491414
insinto /etc/modprobe.d
newins "${FILESDIR}"/nvidia-169.07 nvidia.conf
- use uvm && doins "${FILESDIR}"/nvidia-uvm.conf
+ doins "${FILESDIR}"/nvidia-rmmod.conf
# Ensures that our device nodes are created when not using X
exeinto "$(get_udevdir)"
next reply other threads:[~2015-12-06 5:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 5:32 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-31 9:23 [gentoo-commits] repo/gentoo:master commit in: x11-drivers/nvidia-drivers/, x11-drivers/nvidia-drivers/files/ Jeroen Roovers
2016-01-31 19:19 Jeroen Roovers
2016-07-24 11:37 Jeroen Roovers
2016-08-17 5:49 Jeroen Roovers
2016-11-02 7:53 Jeroen Roovers
2016-11-27 10:46 Jeroen Roovers
2017-02-15 6:53 Jeroen Roovers
2017-03-30 7:29 Jeroen Roovers
2017-05-06 10:59 Jeroen Roovers
2017-09-27 16:11 Jeroen Roovers
2017-10-07 9:44 Jeroen Roovers
2017-10-31 11:26 Jeroen Roovers
2018-06-30 8:17 Jeroen Roovers
2019-01-16 10:00 Jeroen Roovers
2019-03-03 13:11 Jeroen Roovers
2019-11-29 1:59 Mike Gilbert
2020-08-25 17:44 Matt Turner
2020-12-07 12:57 David Seifert
2021-03-21 15:53 David Seifert
2021-03-21 15:53 David Seifert
2021-04-21 12:22 David Seifert
2021-07-21 19:44 Ionen Wolkens
2022-05-31 19:11 Ionen Wolkens
2022-09-16 6:15 Ionen Wolkens
2022-12-02 18:13 Ionen Wolkens
2023-02-28 17:00 Ionen Wolkens
2023-06-18 1:53 Ionen Wolkens
2024-01-15 23:03 Ionen Wolkens
2024-02-01 21:06 Ionen Wolkens
2024-02-26 13:23 Ionen Wolkens
2024-09-14 10:52 Ionen Wolkens
2024-11-18 9:06 Ionen Wolkens
2025-01-21 15:33 Ionen Wolkens
2025-01-30 20:59 Ionen Wolkens
2025-02-06 14:33 Ionen Wolkens
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=1449379933.5b59b721ce933854d4f6191fc67536d0f5e0113a.jer@gentoo \
--to=jer@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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