Re: Microcode update prevents boot
>> Could you see >> if the hang persists when boot-time ucode loading is enabled and >> vm.pmap.di_locked=1 is configured? Hi, I can confirm that setting vm.pmap.di_locked=1 and enabling the loading of the cpu microcode at the same time does not cause any trouble. Unfortunately I didn't had the time to patch and compile a custom kernel yet. Leon Dietrich ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: hw.vga.acpi_ignore_no_vga=1 for installation media
It also happens on some supermicro atom boards that definitely don't run Intel reference BIOS software. I can't provide any serial numbers dough since it's Sunday at my location. On 18.03.19 11:22, Konstantin Belousov wrote: > On Mon, Mar 18, 2019 at 05:09:31AM +0700, Eugene Grosbein wrote: >> 18.03.2019 0:34, Konstantin Belousov wrote: >> >>> Can anybody provide an example of machine where the flag is set but VGA >>> works ? For me, it is set on headless NUC when there is no monitor >>> attached, and then BIOS does not configure framebuffer at all. >> http://freebsd.1045724.x6.nabble.com/vt-4-related-hang-of-11-2-td6299125.html >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235 > All of them are about Silvermont/Airmont atoms which probably share reference > Intel BIOS code. > > As I noted above, BIOS on mine machine is somewhat smarter, it reports > NO_VGA only if the display was not connected on boot. > So the proposal is about reversing the set of broken machines, but only >>> in installer ? In other words, if it worked for installer, the installed >>> system would be broken (again) ? >> VGA-based installation session won't event start unless this is fixed. >> >> It should be easy to make installer generate the knob for target machine >> if installer sees wrong ACPI flag with working VGA hardware. > Until installer generates such knob, it is out of question to make > the config of the kernel booted from the installation media different > from the config of the installed system. > > That said, did anybody considered ignoring NO_VGA FACP flag on Silvermonts > only ? Or even better, gather SMBIOS identifications for affected BIOSes > and ignore the flag for them ? signature.asc Description: OpenPGP digital signature
Re: hw.vga.acpi_ignore_no_vga=1 for installation media
Sound's like solid idea. A lot of systems out there lack propper ACPI description for VGA and it would definitly make the installation on such a system much more easy. As far as I can tell it doesn't seam to break other things and even low power system without VGA (like a pcengines apu2) don't seam to suffer. On 17.03.19 13:00, freebsd-stable-requ...@freebsd.org wrote: > Date: Sun, 17 Mar 2019 02:59:12 +0700 > From: Eugene Grosbein > To: FreeBSD stable > Subject: hw.vga.acpi_ignore_no_vga=1 for installation media > Message-ID: <912fc95d-5a5e-012b-7385-0f43f50dc...@grosbein.net> > Content-Type: text/plain; charset=koi8-r > > Hi! > > Since 11.2-RELESE, default console driver vt(4) checks ACPI table for > presence of VGA in the system. > It does not initialize console (no input, no output) if ACPI states there is > no VGA adapter. > > There are PRs describing many cases when VGA is present but ACPI lies > and we have a regression compared with 11.1 and earlier: > FreeBSD cannot be installed interactively onto such a system, leaving aside > serial console. > > vt(4) has loader knob to restore pre-11.2 behaviour and ignore ACPI: > > hw.vga.acpi_ignore_no_vga=1 > > Should we add this unconditionally to the installation media designed for > interactive VGA-based installation? > > > -- > signature.asc Description: OpenPGP digital signature
