On Sun, 05 Mar 2017 15:14:52 -0800 "Chris H" <bsd-li...@bsdforge.com> wrote
> On Sun, 5 Mar 2017 10:48:32 +0000 Dexuan Cui <de...@microsoft.com> wrote
> > > From: Alex Deiter
> > > Sent: Sunday, March 5, 2017 03:32
> > >
> > > Hello,
> > >
> > > Screenshot: boot with patched loader:
> > > Video: boot with patched loader:
> > Hi Alex,
> > Thanks for the info!
> > Unluckily it looks the delay() in my patch didn't work here somehow, so the
> > screen scrolled up so quickly that we're unable to see the output
> > clearly... :-(
> > Luckily we can use this new method:
> > When you reach the "OK " prompt in your screenshot
> > (http://picpaste.com/IMG_1768-PnmZAtBZ.JPG), please run "memmap" command
> > and share the output with me. Please press space to show the complete info
> > and share the screenshots.
> > E.g. in my side, the memmap command shows:
> I'm experiencing the same problem.
> I've taken several screen shots, but not sure I got all of them.
> I guess the first, and last will maybe the most important. I'll
> clean them up, and post a link to them.
> In the meantime, is there any way to get the system to boot again?
> Is it possible to simply boot the install DVD, and replace the
> efi image on the system, with the one on the install DVD. Or
> can the offending commit simply be reverted.
OK copying the boot.efi from the install DVD will only
hose the system (EFI).
So how long till (u)efi is again supported on FreeBSD?
Sorry for the frustration. But getting a working FreeBSD
on this system has become an unusually long, and expensive
process, this time around -- even for CURRENT.
Thanks, for all your time, and consideration!
> > Thanks,
> > -- Dexuan
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"