From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 17:48:36 2013 Return-Path: Delivered-To: freebsd-current@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 ESMTP id 6067D3EA for ; Sun, 10 Nov 2013 17:48:36 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DBB712762 for ; Sun, 10 Nov 2013 17:48:35 +0000 (UTC) Received: from [10.0.0.52] (ip-414b102e.ct.fixed.ntplx.com [65.75.16.46]) by mail.ntplx.net (8.14.6/8.14.6/NETPLEX) with ESMTP id rAAHYqi2014243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 10 Nov 2013 12:34:57 -0500 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.ntplx.net [204.213.176.10]); Sun, 10 Nov 2013 12:34:58 -0500 (EST) References: <527F95BE.7080908@gmx.com> <527FC05D.8080703@gmx.com> Mime-Version: 1.0 (1.0) In-Reply-To: <527FC05D.8080703@gmx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11B511) From: Daniel Eischen Subject: Re: new Xorg (KMS, etc.) for Radeon 9600 Date: Sun, 10 Nov 2013 12:34:54 -0500 To: "dt71@gmx.com" Cc: "freebsd-current@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 17:48:36 -0000 On Nov 10, 2013, at 12:20 PM, dt71@gmx.com wrote: >=20 > Daniel Eischen wrote, On 11/10/2013 17:40: >> My -current is still from ~July 3, and I also got panics >> when trying new Xorg. Take the drm devices out of your >> kernel configuration and let X load the necessary drm2 >> devices when it starts. This allowed it to work for me. >=20 > Hmm, works for me to avoid panics and hard reboots. Problems: > 1. Switching to the virtual terminals or shutting down X causes the displa= y to go black and unrevivable -- a (soft) reboot is necessary. > 2. A 3D application crashes with SIGBUS, and the stack gets toasted. Yes, I can get it to crash also when using a Java-based GUI, but it works fo= r all the basic X apps that I need. I also have the virtual terminal switch= ing problem also, but I think that is being addressed with newsyscons. It really does suck not having a functional X. -- DE=