Date: Sat, 16 Jan 2021 22:14:34 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Subject: Re: boot loader blank screen Message-ID: <20210116221434.0ceb31b2b7a024f6a45bc998@dec.sakura.ne.jp> In-Reply-To: <cca8f61c-0dbb-b84e-7f93-1f0725ad9593@twcny.rr.com> References: <X/NA4Jk/P%2Bih5WSD@phouka1.phouka.net> <83EB3B04-EAE8-4EC3-820B-2F5C3BADE948@me.com> <66908803-BA6F-4538-9D93-6F85A95108C9@me.com> <831788F9-F97F-4A02-A6F9-AE05219DA2E9@me.com> <X/UYcsbSkXf44Yzs@albert.catwhisker.org> <cca8f61c-0dbb-b84e-7f93-1f0725ad9593@twcny.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. It seems that font-to-display-80x24(25?)-chars-on-full-screen is selected automatically for display resolution. How's going on if you set, e.g., screen.font=8x16 on /boot/loader.conf? This helps me by reduced scrolling. If it's too small for you, see /boot/fonts for other sizes. Each font files has .fnt.gz extension, and base file name eliminating .tar.gz extension is what to set to screen.font variable. And the latest loader looks a bit faster than first graphics mode port. But it would be better if it catches up with in-kernel vt(efifb). HTH, maybe not sufficient, though. On Wed, 13 Jan 2021 22:49:26 -0500 monochrome <monochrome@twcny.rr.com> wrote: > I should add my experience to this since its different and haven't seen > anyone else mention it. > I see the new boot loader, it's not blank, but its large text, and it's > very SLOW. > I can see each char drawn, and then when it gets to the bottom and has > to redraw all the lines to scroll up for new lines, it loads so slowly > it's like watching an 8086 on a 300 baud modem, or slower! Takes like an > extra 30 seconds to get through all the loaded modules, then back to > normal speed boot with the same large font. > > added these lines and everything is back to normal with new appearance > and small font like before, and at normal speed. > hw.vga.textmode="0" > vbe_max_resolution=1280x800 > > also removed the old lines for the amdgpu efi problem with no effect so > I assume those are no longer necessary and why I'm seeing this change? > #hw.syscons.disable=1 > #kern.vty=vt > #hw.vga.textmode=1 > > am using X and everything seems fine for now > > system: > AMD Ryzen 5 2400G, using integrated vega GPU > ASRock B450M Pro4 > 13-current > > > > On 1/5/21 8:54 PM, David Wolfskill wrote: > > On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > >> ... > >>> the 58661b3ba9eb should hopefully fix the loader text mode issue, it would be cool if you can verify:) > >>> > >>> thanks, > >>> toomas > >> > >> I think, I got it fixed (at least idwer did confirm for his system, thanks). If you can test this patch: http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch <http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch> it would be really nice. > >> > >> thanks, > >> toomas > > > > I tested with each of the following "stanzas' in /boot/loader.conf, > > using vt (vs. syscons) in each case (though that breaks video reset > > on resume after suspend): > > > > # hw.vga.textmode="0" > > vbe_max_resolution=1280x800 > > > > This works, and provides a graphical console (depth 32). > > > > > > hw.vga.textmode="0" > > # vbe_max_resolution=1280x800 > > > > This also works, and provides a low-resolution (and depth 16) > > graphical console (800x320 or something similar, IIRC). > > > > > > # hw.vga.textmode="0" > > # vbe_max_resolution=1280x800 > > > > (That is, not specifying anything for hw.vga.textmode or > > vbe_max_resolution.) > > > > This boots OK, but I see no kernel probe messages or single- to > > multi-user mode messages. I can use (e.g.) Ctl+Alt+F2 to switch to > > vty1, see a "login: " prompt, and that (also) works. (This is the > > initial symptom I had reported.) > > > > > > hw.vga.textmode="1" > > # vbe_max_resolution=1280x800 > > > > This works -- boots OK, and I see kernel probe (&c.) messages; this is a > > text console (mostly blue text; some white, against a dark background. > > It's a medium-light blue, so it's easy enough to read (unlike a navy > > blue, for example). > > > > > > FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #113 main-c255601-g9fd96b416c45-dirty: Tue Jan 5 17:24:45 PST 2021 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > > > Peace, > > david > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210116221434.0ceb31b2b7a024f6a45bc998>