Date: Wed, 6 Jan 2021 00:46:08 +0200 From: Toomas Soome <tsoome@me.com> To: John Kennedy <warlock@phouka.net>, Mark Millard <marklmi@yahoo.com>, chrisb <chrisb@fastmail.net>, David Wolfskill <david@catwhisker.org> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: boot loader blank screen Message-ID: <831788F9-F97F-4A02-A6F9-AE05219DA2E9@me.com> In-Reply-To: <66908803-BA6F-4538-9D93-6F85A95108C9@me.com> References: <X/NA4Jk/P%2Bih5WSD@phouka1.phouka.net> <83EB3B04-EAE8-4EC3-820B-2F5C3BADE948@me.com> <66908803-BA6F-4538-9D93-6F85A95108C9@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5. Jan 2021, at 00:59, Toomas Soome <tsoome@me.com> wrote: >=20 >=20 >=20 >> On 4. Jan 2021, at 18:30, Toomas Soome <tsoome@me.com = <mailto:tsoome@me.com>> wrote: >>=20 >>=20 >>=20 >>> On 4. Jan 2021, at 18:22, John Kennedy <warlock@phouka.net = <mailto:warlock@phouka.net>> wrote: >>>=20 >>> This is a little weird. >>>=20 >>> Somewhere between 13.0-g2ff66a915526 (Dec 30th) and -gd03fd8ede2c4 = (Dec 29th), >>> I've lost the screen in the boot loader. This is really weird = because I >>> didn't update the boot loader (in quite a while, actually), but I = suppose it >>> might drag some stuff off of the disk and misbehave. >>>=20 >>> But the system boots, presumably after the countdown that I can't = see, I just >>> have to SSH in from a different machine to tweak things. Just no = screen at >>> all past the GELI encrypted disk password prompt (and some usual = noise as >>> it complains about some padding that I've seen forever). >>>=20 >>> I used to just upgrade the boot loader around ZFS upgrades, and I = haven't >>> done that since OpenZFS got merged. I just got overly conservative = there >>> and may have missed the "all clear" for all combinations of ZFS and = the >>> bootloader recognizing them. >>>=20 >>> The git logs in /usr/src aren't time-sequential, so maybe I = shouldn't trust >>> those dates above (I pulled it ~Jan 3rd and let it compile = overnight), but >>> I'm going to repull all the sources and recompile, just in case. I = might >>> have initiall pulled it during the git conversion and maybe it is = confused. >>>=20 >>=20 >> hi! >>=20 >> Yes, it is known defect, and I=E2=80=99m searching for cause; the = issue is with /boot/loader and BIOS text mode (unfortunately I have the = usual =E2=80=98but it is working for me=E2=80=99 case). For workaround, = you can try to either: 1 (blind) press esc to get out of boot menu, then = enter: vbe on; another option is to add hw.vga.textmode=3D=E2=80=9C0=E2=80= =9D to loader.conf. >>=20 >> Sorry for confusion, >> toomas >>=20 >=20 > the 58661b3ba9eb should hopefully fix the loader text mode issue, it = would be cool if you can verify:) >=20 > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?831788F9-F97F-4A02-A6F9-AE05219DA2E9>