From owner-freebsd-stable@FreeBSD.ORG Mon Jul 7 09:45:54 2014 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47443918 for <freebsd-stable@freebsd.org>; Mon, 7 Jul 2014 09:45:54 +0000 (UTC) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow Root Certificate 2010-04-12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC08920FF for <freebsd-stable@freebsd.org>; Mon, 7 Jul 2014 09:45:53 +0000 (UTC) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801::46]) by mta1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s679jkG2005324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <freebsd-stable@freebsd.org>; Mon, 7 Jul 2014 19:45:46 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1404726346; bh=0AxahkioUj/6JaXpg206LOvxIq/oSfetETghKFUnCbU=; h=Date:From:To:Subject:References:In-Reply-To; b=Uv5dxUIUZxsmJIlSd928nE7jYWRHe5nz/xAG8ptBd8sAO+6VwHqOQc3WgNS+05XMJ P+gxMazA7c6UnnKgmW/4wOoSgqcm3XGn5AnBnMOoNxBqII6lbc6OgJOVZbRBN4Bc5T DzyNUhcFcBAQF+yJa5/nZA1I2VDJK5Bd3eldxQ/E= Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117]) (authenticated bits=56) by mail1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s679jfCp005323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <freebsd-stable@freebsd.org>; Mon, 7 Jul 2014 19:45:43 +1000 (AEST) Date: Mon, 7 Jul 2014 19:45:41 +1000 From: John Marshall <john.marshall@riverwillow.com.au> To: freebsd-stable@freebsd.org Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <20140707094541.GA1074@rwpc15.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org References: <53B69B88.4060803@gmail.com> <E1X32XF-000PnU-QG@dilbert.ingresso.co.uk> <CAPyFy2BhARs+wxhOuP-09tcPgzerU00_ARy=o4OyKec9azTOkQ@mail.gmail.com> <20140705103235.GB7680@rwpc15.gfn.riverwillow.net.au> <alpine.BSF.2.11.1407050455010.5138@wonkity.com> <20140706220006.K50382@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <20140706220006.K50382@sola.nimnet.asn.au> OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 07 Jul 2014 09:45:54 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 06 Jul 2014, 23:47 +1000, Ian Smith wrote: > John has a T43 thinkpad, with unstated graphics hardware; intel 915 or=20 > Radeon X300 according to thinkwiki? For the record, Intel 915GM. I included full details a few days ago in my as-yet-unanswered post to -x11@. Troubleshooting my X failure wasn't the purpose of my post to -stable@; but it's sounding like the answer is probably "pre-2009 hardware unsupported by the 9.3 default NEW_XORG". > It seems that if you upgrade from 9.1 or 9.2 you will need to manually=20 > intervene, either way In my case (short story for a user with older hardware): - leaving make.conf as is lands me in X trouble - adding WITHOUT_NEW_XORG to make.conf keeps things working as for 9.2 > Seeing that a perhaps not miniscule proportion of 9.x X users will need= =20 > to do some manual configuration on upgrading to 9.3, a relevant WARNING= =20 > in http://www.freebsd.org/releases/9.3R/relnotes.html should be helpful. Definitely. Highlighting the fact that the 9.3 introduces a default NEW_XORG ports build, pointing out implications for folks with "older" hardware and the availability of the WITHOUT_NEW_XORG knob would, I think, be helpful. The ports infrastructure controls the logic for the NEW_XORG build decision but I think the fact that the result of that decision for 9.3-RELEASE is OPPOSITE to what it is for 9.2-RELEASE, and that building (now-default) NEW_XORG for folks with older hardware WILL break X for them, warrants a note in the 9.3 release documentation. --=20 John Marshall --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO6bEUACgkQw/tAaKKahKIjfwCgsEAs4jClVd9IdVwZIe11Kcaw n5QAniOLuwDEF+Cz04pBF+EcViCZ1h3N =KYOl -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb--