Date: Thu, 22 Aug 2019 00:17:51 +0300 From: Toomas Soome <tsoome@me.com> To: "Clay Daniels Jr." <clay.daniels.jr@gmail.com> Cc: Karl Denninger <karl@denninger.net>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found Message-ID: <C60D0229-526E-437B-899F-24F7DEF1CDBC@me.com> In-Reply-To: <CAGLDxTWfF_in9hRgZNb8NBDD5fReYrNvUgUFXEtoVUG67XG=gg@mail.gmail.com> References: <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> <CAGLDxTWfF_in9hRgZNb8NBDD5fReYrNvUgUFXEtoVUG67XG=gg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 22 Aug 2019, at 00:07, Clay Daniels Jr. <clay.daniels.jr@gmail.com> = wrote: >=20 > I would agree with Karl & Steffen about using rEFInd. It really gives = you a > lot more control of your computers boot. Take a look at Rod Smith's = pages: > http://www.rodsbooks.com/refind/ >=20 > I use it to triple boot Windows 10, MX Linux, and FreeBSD. >=20 > Clay rEFInd is fancy menu to start real boot loader, it really does not help = if your boot loader is broken. In worst case, you can get fragmented = memory from having rEFInd and native boot loader (depending on how = stupid/buggy the firmware is). rgds, toomas >=20 > On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger <karl@denninger.net> = wrote: >=20 >> ----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA256 >>>=20 >>> Am Wed, 21 Aug 2019 22:34:21 +0300 >>> Toomas Soome <tsoome@me.com> schrieb: >>>=20 >>>>> On 21 Aug 2019, at 22:30, O. Hartmann <ohartmann@walstatt.org> = wrote: >>>>>=20 >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA256 >>>>>=20 >>>>> Am Wed, 21 Aug 2019 22:14:46 +0300 >>>>> Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> schrieb: >>>>>=20 >>>>>> If you drop into efi shell, can you start efi/boot/bootx64.efi >>> manually? you should have >>>>>> fs0: or like for ESP. >>>>>>=20 >>>>>> rgds, >>>>>> toomas >>>>>=20 >>>>> Hello, >>>>>=20 >>>>> I can't even stop to gain access to the shell; there is no >>> timeframe to hit any key to >>>>> stop by and access the efi shell. >>>>>=20 >>>>> Kind regards, >>>>> oh >>>=20 >>>=20 >>>> hm? efi shell should be available from boot device menu, so you >>> mean, you can not even get >>>> into firmware setup? >>>=20 >>>> rgds, >>>> toomas >>>=20 >>> Sorry, >>> I confused loader prompt and EFI shell. >>>=20 >>> I do not have a EFI shell on that type of laptop, not to know about >>> it. I can access the >>> firmware setup and already performed a reset and switched back to >>> default settings. No effect. >>>=20 >>> I just downloaded the newest CURRENT mem stick and extracted both >>> boot1.efi and loader.efi and >>> installed those into the ESP as described, setting the efibootmgr = env >>> accordingly. Still the >>> same error. >>>=20 >>> It seems that there is indeed no EFI/UEFI shell. There are Lenovo >>> specific EFI boot options, >>> like "diagnostics" and so on, if selected, the UEFI boots into a >>> firmware embedded diagnostic >>> menu. I tried several from the list given via efibootmgr show -v, = but >>> there is no shell from >>> which I could access/boot an alternative loader. >>>=20 >>> How I'm supposed to achive the access to this EFI shell? I doubt = that >>> on the E540 (beware of >>> the E, it is not a L or T model) does have such a shell. >>>=20 >>> Regards, >>> oh >>=20 >> I would see if you can get REFIND loaded and use that. I have a = Lenovo >> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot >> (e.g. Win10 and FreeBSD) easily. >>=20 >> I've not had trouble with 12.x on it, and I do use the >> geli-encrypted-aware loader.efi..... >>=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 >> -- >> Karl Denninger >> karl@denninger.net <mailto:karl@denninger.net> >> /The Market Ticker/ >> /[S/MIME encrypted email preferred]/ >>=20 >>=20 >>=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C60D0229-526E-437B-899F-24F7DEF1CDBC>