aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorConrad Meyer <cem@FreeBSD.org>2016-08-30 15:19:57 +0000
committerConrad Meyer <cem@FreeBSD.org>2016-08-30 15:19:57 +0000
commitcc645b642022e988a5d5216112bc7d45995837bb (patch)
treed7bcb0d5c0dddb83d2403eacbfbb95b7bae91774 /UPDATING
parent8c1d7212af79e2ae2b5bbfe7c32f36b7593f6a66 (diff)
downloadports-cc645b642022e988a5d5216112bc7d45995837bb.tar.gz
ports-cc645b642022e988a5d5216112bc7d45995837bb.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING17
1 files changed, 17 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 833aaf4e4693..edeca27791ba 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,23 @@ You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
20160829:
+ AFFECTS: users of x11/nvidia-driver
+ AUTHOR: cem@FreeBSD.org
+
+ The Nvidia driver has been updated to 367.35. In this version of the driver,
+ some important functionality has been broken out into a separate
+ nvidia-modeset.ko.
+
+ Users that experience a hang starting X or observe
+
+ [ 43.243] (II) NVIDIA(0): Validated MetaModes:
+ [ 43.243] (II) NVIDIA(0): "NULL"
+
+ in their Xorg.logs should replace 'nvidia.ko' with 'nvidia-modeset.ko' in
+ their loader.conf or rc.conf configurations. (nvidia-modeset.ko has a
+ MODULE_DEPENDS relationship to nvidia.ko and will bring it in automatically.)
+
+20160829:
AFFECTS: users of security/sshguard
AUTHOR: feld@FreeBSD.org