Date: Tue, 11 Apr 2017 18:33:18 +0300 From: Toomas Soome <tsoome@me.com> To: Masachika ISHIZUKA <ish@amail.plala.or.jp> Cc: "Hartmann, O." <ohartmann@walstatt.org>, freebsd-current@freebsd.org Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <4E8539E2-B5D9-437E-ADBF-4730ECED0E05@me.com> In-Reply-To: <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 11. apr 2017, at 17:42, Masachika ISHIZUKA <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 > Masachika ISHIZUKA Yea, it seems to be the same issue for both of you, now have some work = to do to identify why this does happen. from loader prompt the lsdev -v output would be helpful - you can send = it directly, we do not need to spam the list:) rgds, toomas=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E8539E2-B5D9-437E-ADBF-4730ECED0E05>