Date: Sun, 06 Nov 2016 08:26:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 214261] [uefi] boostrap hangs Message-ID: <bug-214261-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214261 Bug ID: 214261 Summary: [uefi] boostrap hangs Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: emz@norma.perm.ru CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 176675 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176675&action= =3Dedit hangup screen FreeBSD 11.0-RELEASE-p2, generic kernel, Supermicro server (X9SCL-F MB) wit= h a recent BIOS (v2.2). See the attached screen for details. 100% reproducible. Boots fine from GPT/MBR. Isn't affected by the hw.vga.textmode. Furthermore, I cannot make it boot automatically, see my message in the sta= ble@ for details - https://lists.freebsd.org/pipermail/freebsd-stable/2016-August/085280.html: "Recently I've installed FreeBSD 10.3 as an experiment to get the=20 UEFI-enabled system, on one of mine Supermicro servers. The installer=20 worked just fine, but after insttallation I got myself a problem: it=20 cannot boot. If I select to boot the old way, froma disk, BIOS says=20 there's no valid boot device, and I guess i'ts as intended. When I=20 select to boot to the UEFI shell, I got a listing of valid boot deviced=20 identificators, and then an error: =3D=3D=3DCut=3D=3D=3D 'f??('is not recognized as an internal or external command, operable=20 program or batch file Exit status code: Invalid parameter =3D=3D=3DCut=3D=3D=3D and the booting process bails to the shell itself. When I enter =3D=3D=3DCut=3D=3D=3D fs0: EFI\BOOT\BOOTX64.EFI =3D=3D=3DCut=3D=3D=3D FreeBSD boots just fine, but I would rather see it boots automatically." as the final attempt to resolve this I've upgraded the installed system to 11.0-p2 (nothing changed) and upgraded it's BIOS from 2.0b to 2.2 (got this hangup problem). I'm not entirely sure who's problem is that, but FreeBSD totally lacks any documentation about installing UEFI loaders, so at least = this is worth attention. Still both problems can be caused by the FreeBSD UEFI support. Workaround: change to the legacy GPT/MBR bootstrap scheme. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214261-8>