Date: Thu, 13 Apr 2017 09:13:49 +0300 From: Toomas Soome <tsoome@me.com> To: Chris H <bsd-lists@bsdforge.com> Cc: freebsd-current@freebsd.org Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <B96A42E2-730C-4423-A18C-436BE4E7A8B4@me.com> In-Reply-To: <f5cca229ae70c6b2cce978438e650a27@ultimatedns.net> References: <AC12F921-A8BE-496A-A482-31A24913B0B6@me.com> <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> <f5cca229ae70c6b2cce978438e650a27@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 12. apr 2017, at 22:48, Chris H <bsd-lists@bsdforge.com> wrote: >=20 > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > <ish@amail.plala.or.jp <mailto:ish@amail.plala.or.jp>> wrote >=20 >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>>=20 >>> copied /boot/loader.efi from the r315864 snapshot USB image >>> into /boot/loader.efi of the broken systems. >>>=20 >>> Aprt from the fact that I don't know which one is broken, the boxes = are >>> booting again. >>>=20 >>> Conclusion: UEFI loader is broken! >>=20 >> Hi. >>=20 >> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. >=20 > I was going to also report similar findings. > After reporting the problem && submitting additional info to help > diagnose the situation. > I found that the most efficient way to overcome the issue, was to > move loader.efi aside, and copy loader.efi from the install DVD. > I've since lowered the priority of (u)efi in the BIOS, taking > legacy as the higher priority. Because I had additional problems > with vt. In the end, I find I have no issues simply booting to > syscons(4) -- Xorg even works more harmoniously with it. :-) >=20 I believe we did identify the problem, the fix is posted as = https://reviews.freebsd.org/D10381 <https://reviews.freebsd.org/D10381>; = please review, if you can confirm the fix by testing, it would also be = really helpful - the issue is, the problem appears to be system specific = and not always manifesting itself. thanks, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B96A42E2-730C-4423-A18C-436BE4E7A8B4>