Date: Sun, 10 Nov 2013 12:34:54 -0500 From: Daniel Eischen <deischen@freebsd.org> To: "dt71@gmx.com" <dt71@gmx.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: new Xorg (KMS, etc.) for Radeon 9600 Message-ID: <C7DDC881-C320-4C7D-B869-A9273429AF47@freebsd.org> In-Reply-To: <527FC05D.8080703@gmx.com> References: <527F95BE.7080908@gmx.com> <Pine.GSO.4.64.1311101135590.9459@sea.ntplx.net> <527FC05D.8080703@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C7DDC881-C320-4C7D-B869-A9273429AF47>