On Tue, Feb 28, 2012 at 08:37:59PM +0100, Julien Cristau wrote:
> On Tue, Feb 28, 2012 at 12:52:12 -0500, Jeffrey Sheinberg wrote:
>
> > The result - started up emacs, instant crash in the x-server.
> >
> > Attached is the xorg log file from just after the above
> > crash - it was actually named /var/log/Xorg.0.log.old .
> >
> You have kernel mode setting (kms) disabled. Is this intentional? Why?
Hi Julien,
1. Yes, this is intentional.
2. Because this was the easiest for me way to disable the framebuffer.
I don't like the framebuffer because I find it to be visually disturbing
when it scrolls. I am working on finding a better way to disable the
framebuffer (modinfo for ttm,drm,drm_kms_helper,fbcon).
As far as KMS vs. UMS is concerned, they are both about the same for me,
ie, buggy. It goes like this,
Linux VC <--> Linux VC : always works
Linux VC --> X-server : always works for the first time only (xinit).
X-server --> Linux VC : always works
X-server <--> Linux VC : the X display becomes corrupted and unusable,
it may take up to 3 transitions back and forth, any output on the
Linux VC seems to cause it to occur sooner, there is no mouse pointer,
then I just kill the xinit process from a Linux VC having just lost my
X graphical session.
The KMS corruption basically looks like overlapping rectangles in the
predominant colors currently in use on the display.
The UMS corruption basically shows all of the window borders, however,
their contents is mostly just black.
Thanks,
--
Jeffrey Sheinberg
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120301164159.ga10...@l2.bsrd.net
