From owner-freebsd-stable@FreeBSD.ORG Fri Oct 3 08:30:56 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF8592BB; Fri, 3 Oct 2014 08:30:56 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A4C1A75; Fri, 3 Oct 2014 08:30:56 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id hi2so1358915wib.8 for ; Fri, 03 Oct 2014 01:30:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=Gbfk01H76B9sM4CLetTV9K2Qktmd4WiHkV3UzGHAJ4c=; b=u//OEBPQrX6iSIF682XhJ9QmneESqvvvmr315IowJBur7pWAJCodUP9Ek0rRj6bzkw DK0+xFp5flm1CUgwWjfkVqNsPF1CkJ0bHTnWfIMff+LnAFr4BIpkYFbQbZvnQfUfFnXp F+tr2fypzGfVlJbn69f5GuX9RdAM1oeHY1JOSWI2pCp+16OaMNGydVwNBRdF++7tqApN BmLi6gLRfbMfOZsRawwl/hNAtUCc0Ij6rpmgkUYnhd5VSqh9W5gELZfqo4DKwc2Nma/i P4JfhpMCIzLN3zH5qNw2KlkS9yIwBQLGCOjD/rCnZ2mxWKAemqQYp7M2JKBRB4p+1FSZ XiGg== X-Received: by 10.180.96.161 with SMTP id dt1mr10631721wib.1.1412325054355; Fri, 03 Oct 2014 01:30:54 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id s1sm1331020wiw.6.2014.10.03.01.30.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Oct 2014 01:30:53 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 3 Oct 2014 10:30:51 +0200 From: Baptiste Daroussin To: ports@FreeBSD.org, stable@FreeBSD.org Subject: Removal of legacy X.Org (aka non-WITH_NEW_XORG) Message-ID: <20141003083051.GA52332@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 08:30:56 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, As you may know, the ports tree currently provides two versions of the X.Org server and related pieces of software: 1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 We are about to remove the older set. The primary reason is the maintenance cost. The Graphics team is small and it's a nightmare to test changes. The consequence is infrequent updates to those packages and, of course, way more work each time we decide to jump to a later version. All this time spent on keeping the legacy stack in a working state isn't invested on improving the current one and today's hardware support. The recent update to Cairo is a good example of this unsustainable situation: we tested what we could with the time we had and we sent a "Call for testers" on freebsd-x11@ and freebsd-current@ mailing-lists as well as asking for help on several Quarterly Status Reports. The benefit (if not the requirement) of the update and the lack of failure reports were instrumental in the final decision. Unfortunately, many users of the old X.Org server on Intel GPUs are now having crashes with any Gtk+ applications or the X.Org server itself. This time, we won't revert anything or spend more time on trying to fix the old stack. Now, what does it change for the community? What are the benefits of this solution? 1. No more headache with WITH_NEW_XORG, alternate pkg(8) repository, mismatching ABI versions between xf86-input-* and xserver. 2. More frequent and independant updates (ie. no need to update the whole stack in one pass). 3. KDE and, in the near future, GNOME 3 available as packages in the main repository and on install medias. Great, but what does it break? The only regression is for users of Intel GPUs and FreeBSD 8.x and 9.0. Those versions of FreeBSD lack the required kernel driver and therefore xf86-video-intel won't work (the last UMS-aware version doesn't work with xserver 1.12). Users can still use xf86-video-vesa if they can't/don't want to update their FreeBSD workstation. To install xf86-video-vesa, run: pkg install xf86-video-vesa or portmaster x11-drivers/xf86-video-vesa There won't be any regression for owners of Radeon GPUs because xf86-video-ati 6.14.6 (the last one with UMS support, which fortunately works with xserver 1.12) is provided as a separate port. To install this UMS driver: pkg install xf86-video-ati-ums or portmaster x11-drivers/xf86-video-ati-ums In the longer term, we suggest you update to FreeBSD 10.x (10.1-RELEASE is around the corner). For example, you can find instructions to update to 10.0-RELEASE here: https://www.freebsd.org/releases/10.0R/installation.html Note that there's a know regression with syscons and kernel video drivers: you can't switch back to a console once an X.Org session is started. A new console driver called vt(4) fixes this issue while bringing nice features. It's available in FreeBSD 9.3-RELEASE and 10.1-RELEASE but isn't enabled by default. To enable it, put the following line in your /boot/loader.conf: kern.vty=vt Note official packages reflecting this sitation will start building on Wednesday 8th of October and hit your mirrors as soon as possible for both quarterly branch and regular head. regards, Bapt on behalf on the X11 team --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQuXrsACgkQ8kTtMUmk6Ey8UQCeLqfukwHvHV3zcLLarN0ws9X/ tioAnj2/fnS14ANgaYUsVm0XBNNvQAE6 =PuNN -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--