From owner-freebsd-current@FreeBSD.ORG  Fri Feb  8 18:38:17 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id DC7272FA;
 Fri,  8 Feb 2013 18:38:17 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 by mx1.freebsd.org (Postfix) with ESMTP id F3AE581D;
 Fri,  8 Feb 2013 18:38:16 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.6/8.14.6) with ESMTP id r18IcAGj068228;
 Fri, 8 Feb 2013 11:38:10 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r18IcAFE068225;
 Fri, 8 Feb 2013 11:38:10 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Date: Fri, 8 Feb 2013 11:38:09 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: Thomas Mueller <mueller23@insightbb.com>
Subject: Re: Xorg totally unusable with KMS and new Xorg on Sandy Bridge
 system: how to undo
In-Reply-To: <4A.4F.09449.72C15115@smtp02.insight.synacor.com>
Message-ID: <alpine.BSF.2.00.1302081134330.67628@wonkity.com>
References: <4A.4F.09449.72C15115@smtp02.insight.synacor.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (wonkity.com [127.0.0.1]); Fri, 08 Feb 2013 11:38:10 -0700 (MST)
Cc: Andrey Fesenko <f0andrey@gmail.com>, freebsd-current@freebsd.org,
 freebsd-ports@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 18:38:17 -0000

On Fri, 8 Feb 2013, Thomas Mueller wrote:

> Thomas Mueller writes:
>
>>  I built the newer Xorg and it falls flat: goes to a nongraphic
>>  screen that is blank except for a rectangular cursor in the upper
>>  left corner, and now I want to get back to the earlier Xorg.
>>
>>  System is Intel Sandy Bridge with i7 CPU.
>
> Robert Huff responds:
>
>>         You don't mention your graphics chip explicitly, but building
>> libdrm with the KMS option was enough to prevent X from starting on
>> a Radeon HD 3300.  ("Experimental", indeed!  :-)
>>         Other will be able to help more if you could post the contents
>> of "/var/log/Xorg.0.log" and your xorg.conf file.
>
> My /var/log/Xorg.0.log has 0 bytes!
>
> To Andrey Fesenko <f0andrey@gmail.com>:
>
> Were you able to start X with
>
> # cat /etc/make.conf
> WITH_NEW_XORG=true
> WITH_KMS=true
>
> X.Org X Server 1.10.6
> Release Date: 2012-02-10
> intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+)
>
> (end of quote from Andrey Fesenko)

After adding those, graphics/libdrm must be rebuilt, and 
x11-drivers/xf86-video-intel must have the KMS option enabled and be 
rebuilt.  If you just added WITH_NEW_XORG, there will be other xorg 
components that need to be updated.