Hi,
I had the same problems, however, there is one more regression after
these changes. It stably reproduces if you use EFI_STAGING_SIZE.
I have custom FreeBSD distributive which has a sufficiently large
mfsroot which is loaded through UEFI mode.
To solve the problem, it was suggested to
On 7 Mar 2017, at 16:50, Chris H wrote:
On Tue, 07 Mar 2017 16:27:59 -0330 "Jonathan Anderson"
wrote
Hi,
On 5 Mar 2017, at 20:31, Chris H wrote:
OK copying the boot.efi from the install DVD will only
hose the system (EFI).
Before I attempt to do the same thing...
> From: Alex Deiter [mailto:alex.dei...@gmail.com]
> Hello Dexuan,
> This issue reproduced at least for 4 different HW platform
> How can I help you resolve this issue ?
>
> The same result for r314862:
Hi guys,
Sorry, I had to commit a new patch (r314891) just now to really fix
the off-by-one
;yaneurab...@gmail.com>; Michael Tuexen
> <tue...@freebsd.org>; Roberto Rodriguez Jr <rob.rodz@gmail.com>; Guido
> Falsi <m...@madpilot.net>; Warner Losh <i...@bsdimp.com>; Ultima
> <ultima1...@gmail.com>; Sepherosa Ziehau <se...@freebsd.org>
&g
AN <a...@neu.net>; Ngie Cooper
>> (yaneurabeya) <yaneurab...@gmail.com>; Michael Tuexen
>> <tue...@freebsd.org>; Roberto Rodriguez Jr <rob.rodz@gmail.com>; Guido
>> Falsi <m...@madpilot.net>; Warner Losh <i...@bsdimp.com>; Ultima
>> <ultima1.
On Tue, 07 Mar 2017 16:27:59 -0330 "Jonathan Anderson"
wrote
> Hi,
>
> On 5 Mar 2017, at 20:31, Chris H wrote:
>
> > OK copying the boot.efi from the install DVD will only
> > hose the system (EFI).
>
> Before I attempt to do the same thing... what do you mean by "hose
Hi,
On 5 Mar 2017, at 20:31, Chris H wrote:
OK copying the boot.efi from the install DVD will only
hose the system (EFI).
Before I attempt to do the same thing... what do you mean by "hose the
system"? Is the correct recovery path to build a new USB image with
"make release" post-r314828?
On Mon, 6 Mar 2017 04:01:04 + Dexuan Cui wrote
> > From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> > curr...@freebsd.org] On Behalf Of Dexuan Cui
> > Hi Chris,
> > Thank you very much for the screenshots!!!
> >
> > On the host there is a 1MB LoaderData
> From: Dexuan Cui
> I committed r314770 just now to minimize the impact:
> https://svnweb.freebsd.org/base?view=revision=314770
>
> Please let me know in case this can't solve the issue.
Sorry, r314770 has a bug, so I had to commit r314828 for this:
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Dexuan Cui
> Hi Chris,
> Thank you very much for the screenshots!!!
>
> On the host there is a 1MB LoaderData memory range, which splits
> the big Conventional Memory range into a small one (15MB)
> From: Dexuan Cui
> Sent: Monday, March 6, 2017 13:10
> Can you please try the below patch?
> https://reviews.freebsd.org/D9904
> You can find the URL of the "Download Raw Diff" in the page and
> 'wget' the patch and then apply it.
>
> It should be able to fix the recent UEFI-boot issue
On Mon, 6 Mar 2017 04:01:04 + Dexuan Cui wrote
> > From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> > curr...@freebsd.org] On Behalf Of Dexuan Cui
> > Hi Chris,
> > Thank you very much for the screenshots!!!
> >
> > On the host there is a 1MB LoaderData
On Mon, 6 Mar 2017 03:00:20 + Dexuan Cui wrote
> > From: Chris H [mailto:bsd-li...@bsdforge.com]
> > Sent: Monday, March 6, 2017 09:57
> > > Thanks! I'm eager to see your screenshots.
> > > The line whose "Physical" address contains 2MB is the most interesting to
> > >
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Dexuan Cui
> Hi Chris,
> Thank you very much for the screenshots!!!
>
> On the host there is a 1MB LoaderData memory range, which splits
> the big Conventional Memory range into a small one (15MB)
> From: Chris H [mailto:bsd-li...@bsdforge.com]
> Sent: Monday, March 6, 2017 09:57
> > 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.
> OK. Her you go.
Thank you verymuch for the reply, Dexuan!
On Mon, 6 Mar 2017 00:34:19 + Dexuan Cui wrote
> > 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
> From: Chris H [mailto:bsd-li...@bsdforge.com]
> OK copying the boot.efi from the install DVD will only
> hose the system (EFI).
Do you mean copying the boot.efi from the install DVD doesn't work?
If so we need to build a good boot.efi with the CURRENT code + reverting
the offending commit.
> So
> 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:
On Sun, 05 Mar 2017 15:14:52 -0800 "Chris H" wrote
> On Sun, 5 Mar 2017 10:48:32 + Dexuan Cui wrote
>
> > > From: Alex Deiter
> > > Sent: Sunday, March 5, 2017 03:32
> > >
> > > Hello,
> > >
> > > Screenshot: boot with patched loader:
> > >
On Sun, 5 Mar 2017 10:48:32 + Dexuan Cui 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
> 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
On Fri, Mar 03, 2017 at 02:30:08PM +0100, Michael Tuexen wrote:
> > On 3 Mar 2017, at 12:59, Dexuan Cui wrote:
> >
> >> From: Dexuan Cui
> >> Sent: Friday, March 3, 2017 19:50
> >>> From: Alex Deiter
> >>> Sent: Friday, March 3, 2017 17:22
> >>> Hello,
> >>> The same issue
Hello,
Screenshot: boot with patched loader: http://picpaste.com/IMG_1768-PnmZAtBZ.JPG
Video: boot with patched loader: https://youtu.be/thzyRk0D36w
Thank you!
Alex Deiter
alex.dei...@gmail.com
> On 3 Mar 2017, at 16:37, Dexuan Cui wrote:
>
>> From: Michael Tuexen
>>
Hello Dexuan,
Thank you for the patch!
I’ll test it and let you know the result.
Thank you!
Alex Deiter
alex.dei...@gmail.com
> On 3 Mar 2017, at 14:49, Dexuan Cui wrote:
>
>> From: Alex Deiter
>> Sent: Friday, March 3, 2017 17:22
>>
>> Hello,
>> The same issue with
> On 3 Mar 2017, at 12:59, Dexuan Cui wrote:
>
>> From: Dexuan Cui
>> Sent: Friday, March 3, 2017 19:50
>>> From: Alex Deiter
>>> Sent: Friday, March 3, 2017 17:22
>>> Hello,
>>> The same issue with FreeBSD 12.0-CURRENT-r314563:
>>> elf64_loadimage: could not read symbols -
> From: Michael Tuexen
> Sent: Friday, March 3, 2017 21:30
> > BTW, I understand it's really annoying to boot the host first...
> > I'm really sorry for this.
> >
> > I suppose you're able to build or find a good 'loader.efi' binary on
> > another host,
> > and then manage to replace the bad
> From: Dexuan Cui
> Sent: Friday, March 3, 2017 19:50
> > From: Alex Deiter
> > Sent: Friday, March 3, 2017 17:22
> > Hello,
> > The same issue with FreeBSD 12.0-CURRENT-r314563:
> > elf64_loadimage: could not read symbols - skipped!
> >
> > I suspect regression after:
> >
> > Revision 314547 -
> From: Alex Deiter
> Sent: Friday, March 3, 2017 17:22
>
> Hello,
> The same issue with FreeBSD 12.0-CURRENT-r314563:
> elf64_loadimage: could not read symbols - skipped!
>
> I suspect regression after:
>
> Revision 314547 - Directory Listing
> Modified Thu Mar 2 07:25:50 2017 UTC (25 hours, 54
Hello,
The same issue with FreeBSD 12.0-CURRENT-r314563:
elf64_loadimage: could not read symbols - skipped!
http://picpaste.com/IMG_1764-vfZl1l5o.JPG
I suspect regression after:
Revision 314547 - Directory Listing
Modified Thu Mar 2 07:25:50 2017 UTC (25 hours, 54 minutes ago) by dexuan
On Thu, 2 Mar 2017 21:32:39 -0800 "Ngie Cooper (yaneurabeya)"
wrote
> > On Mar 2, 2017, at 21:16, Chris H wrote:
> >
> > On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote
> >
> >> Hi:
> >>
> >> I'm having a major problem after
> On Mar 2, 2017, at 21:16, Chris H wrote:
>
> On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote
>
>> Hi:
>>
>> I'm having a major problem after updating a 12-current machine today.
>> After buildworld/kernel/install cycle on reboot I'm getting the
On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote
> Hi:
>
> I'm having a major problem after updating a 12-current machine today.
> After buildworld/kernel/install cycle on reboot I'm getting the following
> failure:
>
> "/boot/kernel/kernel text=0xb7716f data=0x100548+0x398358
Hi:
I'm having a major problem after updating a 12-current machine today.
After buildworld/kernel/install cycle on reboot I'm getting the following
failure:
"/boot/kernel/kernel text=0xb7716f data=0x100548+0x398358
elf64_loadimage: read failed
can't load file '/boot/kernel/kernel':
33 matches
Mail list logo