From owner-freebsd-ports Fri Feb 28 16:19:31 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA00137B401 for ; Fri, 28 Feb 2003 16:19:29 -0800 (PST) Received: from haystack.lclark.edu (lclark.edu [149.175.1.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 4903D43F3F for ; Fri, 28 Feb 2003 16:19:27 -0800 (PST) (envelope-from eta@lclark.edu) Received: from [149.175.30.191] ([149.175.30.191]) by haystack.lclark.edu (SAVSMTP 3.0.0.44) with SMTP id M2003022816192306877 ; Fri, 28 Feb 2003 16:19:23 -0800 Subject: Re: konsole causes DRI to fail From: Eric Anholt To: Adam Cc: ports@FreeBSD.ORG In-Reply-To: <1046412897.23606.5.camel@jake> References: <1046412897.23606.5.camel@jake> Content-Type: text/plain Organization: Message-Id: <1046478146.670.40.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 28 Feb 2003 16:22:26 -0800 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 2003-02-27 at 22:14, Adam wrote: > Somehow, if I launch konsole at any time during my WM session (I use > FluxBox), my DRI will fail if I close my WM and re-launch it (without > rebooting). > > This is the error I get: > (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI. > > Once I start getting this error, the only way I can launch my WM (any > WM; I've tried several) and avoid this error is to completely restart > the machine. > > So the question is: What is konsole doing that is causing my DRI to > fail? How do I fix it? Is there a way to fix it "on the fly" without > rebooting? Okay, you're now person #3 to report this. I'm going to be looking at this problem in one of the branches of DRI CVS (filp-0-1-branch, dealing with locking issues which may or may not be related to this), but it won't be for a while because of all the other stuff to do. This error shouldn't be related to whether you can start X (I assume that's your problem) or not. A full log (/var/log/XFree86.0.log) might help. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message