Date: Wed, 21 Aug 2019 15:58:24 -0500 From: Karl Denninger <karl@denninger.net> To: freebsd-current@freebsd.org Subject: Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found Message-ID: <f376ad0a-82de-3fca-3d72-7e938e9d1acd@denninger.net> In-Reply-To: <20190821223140.643f6c63@thor.intern.walstatt.dynvpn.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Am Wed, 21 Aug 2019 22:34:21 +0300
> Toomas Soome <tsoome@me.com> schrieb:
>
> >> On 21 Aug 2019, at 22:30, O. Hartmann <ohartmann@walstatt.org> wrote:
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA256
> >>
> >> Am Wed, 21 Aug 2019 22:14:46 +0300
> >> Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> schrieb:
> >>
> >>> If you drop into efi shell, can you start efi/boot/bootx64.efi
> manually? you should have
> >>> fs0: or like for ESP.
> >>>
> >>> rgds,
> >>> toomas
> >>
> >> Hello,
> >>
> >> 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.
> >>
> >> Kind regards,
> >> oh
>
>
> > hm? efi shell should be available from boot device menu, so you
> mean, you can not even get
> > into firmware setup?
>
> > rgds,
> > toomas
>
> Sorry,
> I confused loader prompt and EFI shell.
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> Regards,
> oh
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.
I've not had trouble with 12.x on it, and I do use the
geli-encrypted-aware loader.efi.....
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?
--
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
[-- Attachment #2 --]
0 *H
010
`He 0 *H
00 H^Ōc!5
H0
*H
01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA0
170817164217Z
270815164217Z0{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0"0
*H
0
h-5B>[;olӴ0~͎O9}9Ye*$ g !ukvʶLzN`jL>MD'7U 45CB+kY`bd~b*c3Ny-78ju]9H euέsӬDؽmgwER?&UURj'}9nWD i`XcbGz \gG=u%\Oi13ߝ4
K44pYQr]Ie/r0+eEޝݖ0C15Mݚ@JSZ(zȏ NTa(25DD5.l<g[[Z arQQ%Buȴ~~`IohRbʳڟu2MS8EdFUClCMaѳ !}ș+2k/bųE,n当ꖛ\(8 WV8 d]b yXw ܊:I39
00 U ]^§Q\ӎ0U #0T039N0b01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA @Ui0U 0 0U 0
*H
:P U!>vJ n io -#ן]Wyu jǑR̀Q
nƇ!G ѦF g\ yLx gw=OPycehf[ }ܷ['4ڝ\[p 6\o.B&JF" ZC{;*o*mcCcLY߾`
t*S!(` ]DHP5A~/NPp6=mhk밣'doA$86hm5ӚS@ j ެEgl
)0JG`%k35PaC?σ
׳HEt}!P㏏%*BxbQwaKG$6 h¦Mve; [o-Iی&
I,Tc ߎ#t wPA@l0P+KXBպT zGv;NcI3&J ĬUPNa?/%W6G۟N000 k#Xd\ =0
*H
0{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0
170817212120Z
220816212120Z0W1 0 UUS10U Florida10U
Cuda Systems LLC10U karl@denninger.net0"0
*H
0
T[I-ΆϏ dn;Å@שy.us~_ZG%<MYd\gvfnsa1'6Egyjs"C [{~ _K Pn+<*pv#Q+H/7[-vqDV^U>f%GX)H.|l`M(Cr >е͇6#odc"YljҦln8@5SA0&ۖ"OGj?UDWZ5 dDB 7k-)9Izs-JAv
J 6L$Ն1SmY.Lqw*SH;EF'DĦH]MOgQQ|Mٙג2Z9y@ y]}6ٽeY9Y2xˆ$T=e CǺǵbn֛{j |@LLt1[Dk5:$= ` M 00<+00.0,+0 http://ocsp.cudasystems.net:88880 U 0 0 `HB0U 0 U %0++03 `HB
&$OpenSSL Generated Client Certificate0 U %՞V =;bzQ0U #0]^§Q\ӎϡ01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA H^Ōc!5
H0 U 0karl@denninger.net0
*H
۠A0-j%--$% g2#ޡ1^>{K+uGE v1ş7Af&b&O; .;A5* U)ND2bF|\= ]<sˋL!wrw٧> YMÄ3\mWR hSv!_zvl? 3_ xU%\^#O*Gk̍YI_&Fꊛ@&1n } ͬ:{hTP3B.;bU8:Z=^Gw8 !k-@xE@i,+'Iᐚ:f hztX7/(hY` O.1}a`%RW^akǂpCAufgDix UTЩ/7}%=jnVZvcF<M=
2^GKH5魉
_O4ެByʈySkw=5@h.0z>
W1000{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0
`He E0 *H
1 *H
0 *H
1
190821205825Z0O *H
1B@nk(v,GCsI-"X8+x7[`r8'~MBւ3u6ѣ 0l *H
1_0]0 `He*0 `He0
*H
0*H
0
*H
@0+0
*H
(0 +7100{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0 *H
10{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0
*H
g0/ɋ0W&\E)Cv`f͵b SR8= %uv|e)}䃺cu@S8$FTn)z Ă1郵uU_kV<M-ے StᱝԂ`ɟ!
Q-6_1sFhq7^J>ro: skg"=" ~474&y Vi[K~ %P
13\6Jxq&N
dy
8w~5w7BoT< M%+݉r ,I jg!;+;ח#Ad35> smlײ bѐյQ:XtPWr"̝! J1Q>:dΙN> 3
576` /LUx]S
_!Ub-_9{
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f376ad0a-82de-3fca-3d72-7e938e9d1acd>