From owner-freebsd-questions@freebsd.org Sat Sep 23 14:14:37 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A45DE06450 for ; Sat, 23 Sep 2017 14:14:37 +0000 (UTC) (envelope-from bsdlite@yahoo.com) Received: from sonic312-20.consmr.mail.bf2.yahoo.com (sonic312-20.consmr.mail.bf2.yahoo.com [74.6.128.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59FB474B72 for ; Sat, 23 Sep 2017 14:14:36 +0000 (UTC) (envelope-from bsdlite@yahoo.com) X-YMail-OSG: kgQaOpgVM1nMaGLKb1bMmTHrLUSBiqbsaq95lO32gJdcVx5URB.TdxQEdx8bRuf VFxbNx3vnQ68nBr4SIdi_hL4711smVSecWqS9ekqEjdm2DaJvAWwWBuYc3SeQ0uBYhuMsyzY6XCQ uZEF1RkQOVnxFCJdQlxjWashbhjqlXD62BknmR9MLJ1kvkMV0ptymha5LxQFvz8wUqJQTy1ciWtf RoKU_..kIEwlV0OQeecXredj9vJ.rnG6eVruaz.FYGcOAV0JtrOqtitnQ8bVKfOslV7qQRyD5EJw pnY6RQkswEKc62Wjn189z3veqnjgDUaGOYHpU3TKz3jcKIM10i9Rotn0.ZUHinB1waqrFn3yke0m nl9eLSRTvX9g0HYIu54B7WT0h_W2U4dkyRtST7oPO1QyL3A6T08JhCBOfFFhfi650SNbJgvj0BEQ Nsf1RcyqIGeTjM_2_nz2KXValeaVM2myoyhUTCKHJWisTOpY02O0ZWaDf3ZyKPcdi42mLn0nJXSc SPnVkow60RVDBvCfY.OMyGHQtbzdxtx8u5xLKLuE6BwYbEtU- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Sat, 23 Sep 2017 14:14:30 +0000 Received: from [127.0.0.1] by smtp226.mail.bf1.yahoo.com with NNFMP; 23 Sep 2017 07:14:35 -0000 X-Yahoo-Newman-Id: 76127.19899.bm@smtp226.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: kgQaOpgVM1nMaGLKb1bMmTHrLUSBiqbsaq95lO32gJdcVx5 URB.TdxQEdx8bRufVFxbNx3vnQ68nBr4SIdi_hL4711smVSecWqS9ekqEjdm 2DaJvAWwWBuYc3SeQ0uBYhuMsyzY6XCQuZEF1RkQOVnxFCJdQlxjWashbhjq lXD62BknmR9MLJ1kvkMV0ptymha5LxQFvz8wUqJQTy1ciWtfRoKU_..kIEwl V0OQeecXredj9vJ.rnG6eVruaz.FYGcOAV0JtrOqtitnQ8bVKfOslV7qQRyD 5EJwpnY6RQkswEKc62Wjn189z3veqnjgDUaGOYHpU3TKz3jcKIM10i9Rotn0 .ZUHinB1waqrFn3yke0mnl9eLSRTvX9g0HYIu54B7WT0h_W2U4dkyRtST7oP O1QyL3A6T08JhCBOfFFhfi650SNbJgvj0BEQNsf1RcyqIGeTjM_2_nz2KXVa leaVM2myoyhUTCKHJWisTOpY02O0ZWaDf3ZyKPcdi42mLn0nJXScSPnVkow6 0RVDBvCfY.OMyGHQtbzdxtx8u5xLKLuE6BwYbEtU- X-Yahoo-SMTP: C2b9fHiswBB3UdwM4tOKmyqAy4EW4h41DDQa9ljGLxvSC3QhRHUsiSPpeYxQi5337oCwTsY- Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.3.2163) Message-ID: <20170923071432.6316115.79872.468@yahoo.com> Date: Sat, 23 Sep 2017 17:14:32 +1000 Subject: Re: Restoring sc console look and feel with vt From: Simon Maurice In-Reply-To: References: <20170916020243.B81507@sola.nimnet.asn.au> <20170915200315.289b3fdf.freebsd@edvax.de> <20170917011446.F81507@sola.nimnet.asn.au> <20170916185812.0ccc21a1.freebsd@edvax.de> <20170923033444.Q35468@sola.nimnet.asn.au> To: Warren Block , Ian Smith Cc: Steve O'Hara-Smith , Polytropon , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Sep 2017 14:14:37 -0000 =C2=A0 Original Message =C2=A0 From: Warren Block Sent: Saturday, 23 September 2017 05:19=E2=80=8E To: Ian Smith Cc: Steve O'Hara-Smith; Polytropon; freebsd-questions@freebsd.org Subject: Re: Restoring sc console look and feel with vt On Sat, 23 Sep 2017, Ian Smith wrote: > On Fri, 22 Sep 2017 11:14:13 -0600, Warren Block wrote: > > > On Sat, 16 Sep 2017, Polytropon wrote: > > > > > On Sun, 17 Sep 2017 02:21:51 +1000 (EST), Ian Smith wrote: > > > > Are you sure there's no way to use sc(4) with X on 10.3? > > > > > > The reason why I switched to vt was exactly that reason: with sc > > > in place, X wouldn't start anymore. This happened at some point > > > during the "updating trail" of 10.1 -> 10.3 with ports updated > > > (via pkg). Something that worked for months suddenly stopped > > > working, which always is a terrible experience. When I switched > > > to vt in the loader, X worked again as it did before. > > > > I'm fairly sure that is due to KMS video. vt(4) supports it, sc(4) was = out > > decades before anyone thought of it. > > > > > From another channel, I've been told that persistently setting the gop > > command in the loader is either not implemented or must be done in one = of the > > Forth loader files. I tried some things with no success yet, and have > > inquiries to dteske@. > > Have you tried on an i386 system? My explore indicated that gop(0) only > exists in /usr/src/sys/boot/efi/loader/arch/amd64/framebuffer.c on 10.3, > 11.1 and head. Apparently nothing similar for the i386 loader. > > Polytropon's system also is BIOS|ACPI not EFI, though it wasn't clear to > me that this code position in hierarchy necessarily implies EFI-booting? I don't know. 32-bit i386 had a long, distinguished run, but it's a=20 dying breed, and I have not spent any time on it in quite a while. > > > > We saw lots > > > > about getting proper console switching going (again) using vt and X= on > > > > the stable@ list on earlier 10.x, but I can't recall any details, s= ince > > > > sc still works fine on my 9.3 (amd64) system, where vt(4) first bec= ame > > > > available, including proper suspend/resume support from ttyvN or fr= om X. > > Again, that's an older system; core2duo, no EFI, no KMS (GM4500 graphics > as I recall). So there's a complicated web of older systems being left > behind fairly unceremoniously (with nobody to blame :) at an increasing > rate .. or so it looks to we old farts who value stability over novelty. There's stability. There is also being left behind by an=20 increasingly-distant herd and finding yourself surrounded by=20 metaphorical wolves and alligators. Or literal ones. > > > That is a different problem. Until you start X, sc works perfectly > > > fine. Even in a setting where "sc + startx" is working, shutting > > > down the X session or switching using e. g. Ctrl+Alt+F1 leaves you > > > with a console that works, but without visible text ("blind console"). > > > With vt, at least this problem is gone, even though the console now > > > is visible only with the tiniest letters. > > > > I just tested this on a Haswell notebook with 11-stable. The mode setti= ng is > > either lost after leaving X, or it just keeps the resolution chosen in = X. > > > > > > However, vidfont and vidcontrol work to select a larger font. > > > > vidfont -p > > > > to print available font names. Then > > > > vidcontrol -f vgarom-16x32 > > > > to choose one of them. This can be set in /etc/rc.conf with > > > > allscreens_flags=3D"-f vgarom-16x13" > > > > It does not take effect until late in the startup, so the boot messages= are > > in the default or gop-set mode. > > Does 'uga' command also in mentioned MFC work at your loader prompt? It says: uga: UGA Protocol not present (error=3D14) > > I'm not sure where this should be documented in the Handbook. > > Seems it would by now need distinguishing between architectures, classes > of graphics and perhaps whether and where EFI boot or support is needed? Maybe a separate article, then. I'm not sure whether any of this=20 applies to newer architectures like ARM. _______________________________________________ freebsd-questions@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" .