From owner-freebsd-questions@FreeBSD.ORG Tue Jul 22 16:16:19 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 85D28C91 for ; Tue, 22 Jul 2014 16:16:19 +0000 (UTC) Received: from mail.parts-unknown.org (unknown [IPv6:2a02:c200:0:10::404:501]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 465A227CB for ; Tue, 22 Jul 2014 16:16:18 +0000 (UTC) Received: from mail.parts-unknown.org (unknown [127.0.0.1]) by mail.parts-unknown.org (Postfix) with ESMTP id EB05412C0179; Tue, 22 Jul 2014 09:16:15 -0700 (PDT) Received: from android-4723dd398c6c031b (unknown [67.169.2.83]) by mail.parts-unknown.org (Postfix) with ESMTPSA id 8836B12C0178; Tue, 22 Jul 2014 09:16:14 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: 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> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: About the black screen (Otherwise solved) Re: All of a sudden, problems with X From: David Benfell Date: Tue, 22 Jul 2014 09:16:09 -0700 To: Warren Block Message-ID: <89139be6-93e5-40dc-b2e6-fe64588876b4@email.android.com> X-Virus-Scanned: ClamAV using ClamSMTP Cc: Polytropon , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2014 16:16:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On July 22, 2014 3:54:28 AM PDT, Warren Block wrote: >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 This seems very cool. The money quote is "To enable Newcons on i386 or amd64, set the loader tunable kern.vty=vt." Is this in loader.conf? Also, I'm running 10.0 RELEASE. Do I need to upgrade to STABLE? Thanks! - -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQJfBAEBCgBJBQJTzo5JQhxEYXZpZCBCZW5mZWxsICgqc2lnaCouIFRyeWluZyBh Z2Fpbi4pIDxiZW5mZWxsQHBhcnRzLXVua25vd24ub3JnPgAKCRAVeuMeEjZgK+Zf D/4rsnId9YbWEIPdGqxfUmjdaoCTWS6qK77apBjMDAuWBcxaQpIyitmp+jmvJ4Ud giHKI40fvfQErww4h83qLV77Uckg6Jm7JzqLznqEL/3QufhEXHDqLGh6dJAgGRuP eg3jLFJYX3Pyn6F5M/jCIrsDxBe86kKV7ARc49eXMj6NJJxHX6zaquWv9vfyn6q5 B9y2B9AwQSn01g3tFvhG2xoFxJ8qBiAzMPZYO477w/M8Fej5fdIdSh2CSzN7tOKl yy+2cgb55kT1004EtU6+wvt/bBkYQJmit4d1inSkAyXW+pcZh/sZxJooP4Pl4pzr pajKCkIYRpZlyrU1uj5Zjs1kQruqM6e/0CK9Evj8992DH3+NSDMeTFLw5pNMaPcb ISXekd8HMa0MfWI8mxpDrKXuMQLEpaGJaZ+BaejGb1zvs625b9tgihyucMge/WrJ xrFb5eD1mf31b2WqwJP6DR6xnO+E8T8gQHLnCynlT1isq2RPdor+oJ+YAWimS3Dz bCtfGdElARcY9u+ZTZmIgeapnjbBzmSzIyqBYZVkRhLGbafDg/IO29kN0tS3n0MR 63Tx0aknLPOoOyhgTT9AhrjoLDqKvi8lZX5rFM0QQilyceYbqNyohuBfQO9KxIzv TU934+XawzPhwrlq1mNSE9tiVPixRxHOy83rNvh3sDJRWw== =VyJV -----END PGP SIGNATURE-----