From owner-freebsd-x11@FreeBSD.ORG  Tue Nov  4 06:22:53 2014
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 889D2A70
 for <freebsd-x11@freebsd.org>; Tue,  4 Nov 2014 06:22:53 +0000 (UTC)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com
 [IPv6:2607:f8b0:400d:c01::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 497FD877
 for <freebsd-x11@freebsd.org>; Tue,  4 Nov 2014 06:22:53 +0000 (UTC)
Received: by mail-qc0-f181.google.com with SMTP id w7so10285165qcr.40
 for <freebsd-x11@freebsd.org>; Mon, 03 Nov 2014 22:22:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=9lCoAcWtT8sGNI7Fk7vwAGWml6p+zS5SRRqQjKfQ4hI=;
 b=pk5pcEoqdRxWU4foZSAfd4uKh4lKN95nYgT/Zmf6MhgD5gNZXDoexZUY69ltQ0Iqmk
 r0SnbZOBTTv7YQ48Zp3IZwetucmrRCpbIxW8xnlmfokRWK+2LMKHi+/tbrCTaButZAwg
 BOgwnMimtzlAgAAEgsmow5ZlWbSz8sXNDtzk9OIfSAiQVa7ST/jBE7SCebPdV1sc6YJq
 M8A2k5vjjwlOdqizRYTmBILPZaVhEHE3kEX4X7MXZMDg12DQHZQ6DHQ7RKEMcuUE0QJ6
 wHOEWxPyEUC9KWBYjkmxIfb8bADKQ6nqMCNuohBLFLMji4dXWrxvEJVGpuoE1SturI63
 a4zw==
MIME-Version: 1.0
X-Received: by 10.224.24.131 with SMTP id v3mr73485500qab.81.1415082172290;
 Mon, 03 Nov 2014 22:22:52 -0800 (PST)
Received: by 10.229.12.196 with HTTP; Mon, 3 Nov 2014 22:22:52 -0800 (PST)
In-Reply-To: <5457F75F.4080205@riseup.net>
References: <CAOrhW_Az4Qr2srmpdUWhxGMH26g4DDgaKg+eTG5mRAmNKr2RcA@mail.gmail.com>
 <5457F75F.4080205@riseup.net>
Date: Tue, 4 Nov 2014 08:22:52 +0200
Message-ID: <CAOrhW_BBaDGuyLsfH79Qspj883htON=hw+rvo8QphEnj30VN3w@mail.gmail.com>
Subject: Re: Issue with DRI after latest update
From: xtremyst inxtremo <xtremyst.in.xtremo@gmail.com>
To: freebsd-x11@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 06:22:53 -0000

Thanks a lot for taking the time to reply Piotr, I have tried building
these ports in the past without the "WITHOUT_NEW_XORG" flag, but I kept
ending up with no working DRI.
As i wrote two posts back, the closest I've come to a working DRI so far is
by rebuilding the xorg-server every time I want to startx.
I will give it another try though, according to your suggestions, as soon
as I have time and I'll report back.
Best regards

On Mon, Nov 3, 2014 at 11:45 PM, Piotr Kubaj <pkubaj@riseup.net> wrote:

> See
>
> https://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html
> Basically, just remove WITHOUT_NEW_XORG="YES" from /etc/make.conf and
> rebuild whole Xorg stack and Mesa. Since you use Radeon GPU, for best
> experience you should  upgrade to 10.1 (RC4 at the moment) and use vt(4).
>
>