From owner-freebsd-x11@FreeBSD.ORG Wed Sep 24 16:55:35 2014 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34C5FA19 for ; Wed, 24 Sep 2014 16:55:35 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::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 A91E5AFD for ; Wed, 24 Sep 2014 16:55:34 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id b6so5727623lbj.26 for ; Wed, 24 Sep 2014 09:55:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=DtUI0jKX5mGBczLL1e4s4drHiaBG6N45iyHJCdC79bQ=; b=w08JZiQEVBitZ5nouO/Ct1av+xzZ4lXPDhWGt3Ve5jWRIIlO1MZ2EkvoECJNeweE9w cN/wZwiA53cmuVkmWO3oDcFxKa8hCoS5hKlZ0vqRad5zpOcJiVrQw5ddk1NRhJiH+sZE eA/TDX78VQhK7B3eqCBI50lAImO/NXUH4aMktz7rV9kSqR0yJ0jY8Ikr+QSE1XpPgEm8 7Tzj2oKOnYa7RGnWY44EyWq4LBomOkaV4wqrDekfSHp2jYwJUDXZo1j0rNBJhnwrPb6z bPUjxHMv3G4pqFbtPCliNpmhtbK9RIv6jLeVPiECnK4JkuVGwUBZgTdg3w9dhvx68Ptn h3Ww== X-Received: by 10.112.146.103 with SMTP id tb7mr7521199lbb.26.1411577732314; Wed, 24 Sep 2014 09:55:32 -0700 (PDT) Received: from [192.168.255.112] (91-158-78-126.elisa-laajakaista.fi. [91.158.78.126]) by mx.google.com with ESMTPSA id q10sm2561091lah.5.2014.09.24.09.55.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Sep 2014 09:55:31 -0700 (PDT) Message-ID: <5422F779.7030307@gmail.com> Date: Wed, 24 Sep 2014 19:55:21 +0300 From: Arto Pekkanen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: Unable to start X.org with KMS in FreeBSD 10.0 without using the new_xorg repo References: <5422DFB5.4070605@gmail.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7hFWftBr3vaQg8AqAgSLlrbrhrKrQB9uF" Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2014 16:55:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7hFWftBr3vaQg8AqAgSLlrbrhrKrQB9uF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 24.9.2014 19:24, Kevin Oberman wrote: > I just looked at the wiki page and I fail to see anything saying that t= he NEW_XRG packages are in the default repository. That is the reason the= new_xorg repo exists. The wiki does say that WITH_NEW_XORG is now the de= fault for all supported branches except 8. The goal is, indeed to get the= NEW_XORG working with all supported versions and remove the old code, bu= t I see no indication that it has been done as of today. Okay :D It seems that I misunderstood what the wiki page actually meant. = Sorry about that. Thanks for info! > I do agree that clear warnings about the need for the new_xorg repo if = KMS is to be used. It also points out that an update of Intel KMS to supp= ort newer GPU is getting REALLY critical! It's getting harder and harder = to find laptops that have supported graphics and while VESA (usually, sor= t of) works, it is not really a good way to run a system. Yeah, a warning about new_xorg repo and KMS plus good examples on how to = do it. I only needed to define the repo in /etc/pkg/0-new-xorg.conf, then= pkg update && pkg upgrade -f -r FreeBSD_new_xorg Anyways, now updating to 10.1-BETA2 to see if I can get VT working with K= MS.=20 > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com --=20 Arto Pekkanen ksym@IRCnet --7hFWftBr3vaQg8AqAgSLlrbrhrKrQB9uF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) iF4EAREIAAYFAlQi934ACgkQDveLgfJxcNRLBwD/aWUXgJMGXfOFHjvTix2xTslH vVEByWtb6bhZk9w4hYQBAK4z066SKaHHAfKW3awwOHIZQZNIRwmJ58wfEIsJkS1S =jvJp -----END PGP SIGNATURE----- --7hFWftBr3vaQg8AqAgSLlrbrhrKrQB9uF--