From owner-freebsd-x11@freebsd.org Tue Jun 6 12:23:55 2017 Return-Path: Delivered-To: freebsd-x11@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 EAB0FB944CE for ; Tue, 6 Jun 2017 12:23:55 +0000 (UTC) (envelope-from theraven@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 D59F665E0A for ; Tue, 6 Jun 2017 12:23:55 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D1B69B944CD; Tue, 6 Jun 2017 12:23:55 +0000 (UTC) Delivered-To: x11@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 D134CB944CC for ; Tue, 6 Jun 2017 12:23:55 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A83F965E09 for ; Tue, 6 Jun 2017 12:23:55 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.65] (host81-140-166-137.range81-140.btcentralplus.com [81.140.166.137]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id v56CNrTw098948 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 6 Jun 2017 12:23:54 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host host81-140-166-137.range81-140.btcentralplus.com [81.140.166.137] claimed to be [192.168.1.65] From: David Chisnall Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: No heads up for X.org config changes? Message-Id: <93A44203-1B97-4D37-922A-A61F701388D2@FreeBSD.org> Date: Tue, 6 Jun 2017 13:23:47 +0100 To: x11@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 12:23:56 -0000 Hello x11 ports folk, I updated X.org to the latest version at the weekend (actually, a week = or two ago, but I didn=E2=80=99t restart it until then) and discovered = that X would no longer start. The fix appeared to be quite simple in = the end - I had to replace =E2=80=98radeon=E2=80=99 in my driver line = for my device section in xorg.conf with =E2=80=98modesetting=E2=80=99. = Apparently I probably also want Option "AccelMethod" = =E2=80=9Cglamor=E2=80=9D to enable 2D acceleration and need to add Load = =E2=80=9Cglamoregl=E2=80=9D to my modules section. None of this was documented. I looked in the UPDATING entries for = xorg-drivers and xorg, on the freebsd-x11 mailing list archives and in = the form and didn=E2=80=99t find anything relevant. Given that this = update apparently broken any existing xorg.conf files that were = configured to use DRI drivers, I imagine that other people were hit by = it (though anyone using auto config was probably okay), so some public = announcement (ideally in the UPDATING file, telling me I needed to = update my config when I upgraded xorg-drivers) would have been nice. David