Date: Tue, 22 Jul 2014 04:54:28 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: David Benfell <benfell@parts-unknown.org> Cc: Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org Subject: Re: About the black screen (Otherwise solved) Re: All of a sudden, problems with X Message-ID: <alpine.BSF.2.11.1407220452330.93805@wonkity.com> In-Reply-To: <20140722060749.5487612C10D1@mail.parts-unknown.org> References: <20140722024643.GA29536@munich.parts-unknown.org> <20140722051423.0cf369b9.freebsd@edvax.de> <20140722040440.GA16353@munich.parts-unknown.org> <20140722061900.008b35db.freebsd@edvax.de> <20140722060749.5487612C10D1@mail.parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Jul 2014, David Benfell wrote: > There is a note in UPDATING (did I read it beforehand? Of course not.) about > some video chips--including Intel, which mine is--that says that > Ctrl/Alt/F[n] won't work. Apparently X isn't cleaning up after itself > correctly when exiting either. > > So the message here seems to be, once you start X, you'd better be happy with > it. Because you might not be leaving (short of a reboot). > > But what this also suggests is that, should I need it, the Xorg.conf.new I > generated might actually be okay. Because it's the exit that's screwed up > rather than anything to do with the configuration. The vt(4) console driver included with 10-stable and 9-stable solves this: https://wiki.freebsd.org/Newcons
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1407220452330.93805>