Date: Mon, 26 Aug 2019 13:22:07 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: Toomas Soome <tsoome@me.com> Cc: greg@unrelenting.technology, "O. Hartmann" <ohartmann@walstatt.org>, Karl Denninger <karl@denninger.net>, freebsd-current@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found Message-ID: <20190826132150.6f748419@freyja> In-Reply-To: <12E83654-1104-408E-9A1E-BE79308B9A92@me.com> References: <20190821232334.433d285c@thor.intern.walstatt.dynvpn.de> <20190821195847.577a165b@thor.intern.walstatt.dynvpn.de> <48D9A1D1-5A54-4FED-8DC8-40C9A5C9BE3A@me.com> <20190821213052.25d61cb4@thor.intern.walstatt.dynvpn.de> <480F8DE0-A38F-4BCA-9F36-0D812CDB7DD8@me.com> <20190821223140.643f6c63@thor.intern.walstatt.dynvpn.de> <f376ad0a-82de-3fca-3d72-7e938e9d1acd@denninger.net> <483d59b24a636d0214555610350b8d73@unrelenting.technology> <20190822050509.64c88a51@thor.intern.walstatt.dynvpn.de> <12E83654-1104-408E-9A1E-BE79308B9A92@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Aug 2019 08:58:55 +0300 Toomas Soome <tsoome@me.com> wrote: > > On 22 Aug 2019, at 06:04, O. Hartmann <o.hartmann@walstatt.org> wrote: > >=20 > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > >=20 > > Am Wed, 21 Aug 2019 22:29:29 +0000 > > greg@unrelenting.technology schrieb: > > =20 > >> August 22, 2019 12:23 AM, "O. Hartmann" <ohartmann@walstatt.org> wrote: > >> =20 > >>> Am Wed, 21 Aug 2019 15:58:24 -0500 > >>> Karl Denninger <karl@denninger.net> schrieb: > >>> =20 > >>>> I would see if you can get REFIND loaded and use that. I have a Len= ovo > >>>> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot > >>>> (e.g. Win10 and FreeBSD) easily. =20 > >>>=20 > >>> mmmhhh, Linux software to make FreeBSD boot? ;-) =20 > >>=20 > >> rEFInd is not "Linux software", I use it to get a nice menu to choose > >> between FreeBSD and Windows on my desktop. No Linux in sight. If anyth= ing, > >> rEFInd has its roots in Macs :) =20 > >=20 > > My apologizes; when searching the net, the first "logo" I see is this s= illy > > penguine face. I'm sorry about making such simple implications. > > =20 > >> =20 > >>> This Lenovo firmware seems very reluctant or the efibootmgr doesn't > >>> operate properly on setting variables: when trying to label the boot > >>> number (e.g. Boot000A) with "-L FreeBSD", it is always set back to > >>> "Boot000A ATA HDD0". On other platforms, like Fujitsu servers or even= the > >>> cheap crap from ASRock a label once set is permenent until deleted. = =20 > >>=20 > >> Many laptops just ignore the boot variables outright. My X240 is the s= ame. > >> I never switched to a proper efibootmgr setup on mine, I just have > >> loader.efi as bootx64.efi and that's it. =20 > >=20 > > I tried copying loader.efi as bootx64.efi - but didn't help. > > =20 > >>>> If there's a way to get into the EFI shell on Lenovo's laptops from = the > >>>> BIOS during the boot I've not found it yet. There's supposed to be = on > >>>> all EFI devices, but you know how "supposed to" works in many cases, > >>>> right? =20 > >>=20 > >> You can just download the EFI Shell from the internet, it's a normal .= efi > >> executable you can "boot". Put it as efi/boot/bootx64.efi onto a USB f= lash > >> drive and enjoy. =20 > >=20 > > I'll give this a chance as soon I have hands on the workitem again. > > =20 >=20 > The reason to try rEFInd and/or EFI shell is to see if we get extra error > messages otherwise hidden by GUI. >=20 > In any case, to get to the root cause, we would need to start to insert m= ore > debug printouts and see what we will find. Once you are ready to go with = it, > you can poke me directly and then we can start=E2=80=A6 >=20 > rgds, > toomas >=20 Hello. I spent the weekend fiddling around with the settings and I found out two things: the most important: my brain is leaking "emory", means: I had the same issue with an APU from PCengines because of enabling "WITH_BEARSSL" in /etc/src.c= onf on the machines where we built the main OS. I did so on the laptop we spoke= of in this thread - and forgot about that fact. the other thing is the weird Lenovo handling of the UEFI vars. The only way= to boot the E540 (after(!) disabling _BEARSSL in src.conf and rebuilding everything) was to set the loader's name to EFI/BOOT/BOOTx64.efi. Setting t= he variable to contain EFI/BOOT/loader.efi failed as well as setting EFI/FreeBSD/loader.efi.=20 I also had to delete the Boot000A variable - it seems Lenovo's UEFI implementation uses fixed variable sets (as I realized when not being able = to name label of the variable Boot000A by something I've choosen). Boot000A is always labeled "ATA HDD0", no matter what I've tried to set it to via option "-L" of efibootmgr. Kind regards, oh=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190826132150.6f748419>