> From: Chris H [mailto:bsd-li...@bsdforge.com]
> > 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
> > 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.

Thanks! I'm eager to see your screenshots. 
The line whose "Physical" address contains 2MB is the most interesting to me.
And please at least post the other lines around the line.

> 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.
> --Chris
Yes, you can replace the broken system's bad /boot/loader.efi  with a
good version. You can also revert the offending commit ("loader.efi: reduce
the size of the staging area if necessary").

-- Dexuan
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to