From owner-freebsd-stable@FreeBSD.ORG Sat Jul 5 10:32:52 2014 Return-Path: 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 92531EF for ; Sat, 5 Jul 2014 10:32:52 +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 00F8C2BA1 for ; Sat, 5 Jul 2014 10:32:51 +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 s65AWiY0006681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 5 Jul 2014 20:32:44 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1404556364; bh=9djdC/ugOqIGAutJMdzCD8kOieGM9llRtq4Pa2ocmDA=; h=Date:From:To:Subject:References:In-Reply-To; b=JVpghDKWhUIf2yegzA2kuWk9ahSuihOM5nSKy4ZBEHZyDyeNmfkhQazOvGzhSA4kM d9oZzb1Swbe51SvUCE7aHdf5Soj2yVNRIDsOh0beSxDbSLeQCEa1lsBORk1Z+mlKtQ NhWXNvgXSE3Gx0ZmXHyLBRpx4+v1Y+UmG3EXDEok= 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 s65AWfOG006680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 5 Jul 2014 20:32:43 +1000 (AEST) Date: Sat, 5 Jul 2014 20:32:36 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <20140705103235.GB7680@rwpc15.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org References: <53B69B88.4060803@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WhfpMioaduB5tiZL" Content-Disposition: inline In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2014 10:32:52 -0000 --WhfpMioaduB5tiZL Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 04 Jul 2014, 15:31 -0400, Ed Maste wrote: > In HEAD syscons(4) and vt(4) are now both compiled in by default in > the GENERIC kernel. Syscons remains the default at the moment; you > can set the loader tunable kern.vty=3Dvt to choose vt(4) instead. Vt is > selected automatically if booting via UEFI on amd64. >=20 > Both stable/10 and stable/9 require a recompile to use vt(4). The > plan is to merge these changes from HEAD in time for 10.1, but 9.3 > will not have them. So, perhaps 9.3 should remain "opt in" like 9.2 and not build NEW_XORG by default? > Note that vt(4) enables vty switching from Xorg, but WITH_NEW_XORG > generally should not depend on vt(4). X should work fine, just > without the ability to switch back to a vty. If WITH_NEW_XORG fails > on certain hardware I think it'll be independent of the use of sc(v) > vs vt(4). Thank you, Ed, for taking the time to explain all that. I had been under the impression that NEW_XORG depended on vt(4), which was why I modified my 9.3 kernel. sc(4) worked fine after my initial upgrade, vt(4) works fine; it's just X that doesn't. Perhaps my "X no longer works" scenario is due to "certain hardware"? Is there a list somewhere of hardware on which NEW_XORG will not work, so that folks running 9.2 with that hardware can set WITHOUT_NEW_XORG BEFORE they upgrade to 9.3 and save themselves grief? --=20 John Marshall --WhfpMioaduB5tiZL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO31EMACgkQw/tAaKKahKKEsACgwXYI74a+srKvvc87sw1tZcmU ebwAn2JIo1aHEE8gxdxH3j6edw0g3x+L =ndRF -----END PGP SIGNATURE----- --WhfpMioaduB5tiZL--