Date: Thu, 6 Dec 2018 23:28:43 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Aleksandr Rybalko <ray@ddteam.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, ed@freebsd.org, Ed Maste <emaste@freebsd.org> Subject: Re: vt(4)-related hang of 11.2 Message-ID: <5C094E3B.5090800@grosbein.net> In-Reply-To: <5C094A7C.1090608@grosbein.net> References: <5C092989.6000007@grosbein.net> <CAJ1Oi8HgwXJMPz7hWJMXrAmzKUnAWfgitZ1fmgbFMV_hv8=B7g@mail.gmail.com> <5C0945AF.3060604@grosbein.net> <5C0947BF.9090500@grosbein.net> <5C094A7C.1090608@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>> In most cases it's just wrong info passed from UEFI firmware about FB. >>>> try to hardcode FrameBuffer params into vt_efb driver, to know exatly. >>> >>> Forgot to add importand detail: it boots and works with vt(4) using FreeBSD 11.1. >>> >> >> r322258 is known working stable/11 revison that booted such a system with default console just fine; >> stable/11 r338465 hangs. > > Looking at the diff, I see I should try hw.vga.acpi_ignore_no_vga=1 that stable/11 got in between... > I'll try next day and respond. hw.vga.acpi_ignore_no_vga=1 solved the problem and now it boots with vt(4) just fine. The question is: why it hangs and does not boot "blind" without this setting? Can it panic maybe? This box has no COM-port at glance (for serial console) but dmidecode reports it has...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5C094E3B.5090800>