From owner-freebsd-current@freebsd.org Sun May 7 13:36:52 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F567D61925 for ; Sun, 7 May 2017 13:36:52 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DC1D1EC4 for ; Sun, 7 May 2017 13:36:51 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D039DD61924; Sun, 7 May 2017 13:36:51 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFBCDD61923 for ; Sun, 7 May 2017 13:36:51 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7827AEBE for ; Sun, 7 May 2017 13:36:51 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1d7MMi-0006cd-Mp; Sun, 07 May 2017 14:36:48 +0100 Date: Sun, 7 May 2017 14:36:48 +0100 From: Gary Palmer To: Jeffrey Bouquet Cc: current Subject: Re: Some precise procedure... Message-ID: <20170507133648.GA89273@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 May 2017 13:36:52 -0000 On Sun, May 07, 2017 at 05:11:13AM -0700, Jeffrey Bouquet wrote: > Given the following procedure: > > svn up /usr/src > make buildworld > make buildkernel > make installkernel > mergmaster > reboot single user > mergemaster > make installworld > pkg install compatN-i386 > reboot > make check-old > make delete-old > > etc [ pardon the missing stuff and out of order, this is from memory] > > At which precise point either > 1... Xorg fails to work > 2... nvidia-driver fails to work? > Because in my experience unless a minor upgrade, it happens every time, and > I am caught unawares.. so am wanting in the summaries in UPDATING > 3a... do not proceed beyond this without backups, as your video driver may not work... > and am slightly confused. > If I svn, but do not buildworld, is nvidia-driver somehow more unusable? etc etc. > looking at it from an entirely newbie frame of mind, because a more authoritative > source than I may know more about the precise how and why an svn OR a buildworld > should not be attempted if one is more concerned about the driver not breaking > or being unusable 'version mismatch' upon upgrade, than the upgrade itself. > > tl;dr > anyone have an expert summary? if not, just thanks for reading, or throw a concept > at me. > 1... Xorg ceases to work and/or You should add PORTS_MODULES+=x11/nvidia-driver to /etc/make.conf so that the nvidia driver is automatically rebuilt every time you build the kernel to prevent such issues. Add in any other ports that depend on the kernel data structures such as emulators/virtualbox-ose-kmod The kernel ABI is not guaranteed to be stable on the -current branch so any modules you load in to the kernel need to be rebuilt for each kernel. Regards, Gary