Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893
Title:
Ming,
Trying to use your bootnetaa64.efi file from
http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi
I am not able to test this because I cannot PXE boot:
TianoCore 2.0.0 UEFI 2.4.0 Sep 1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB
On Tue, Nov 3, 2015 at 11:48 PM, Newell Jensen
wrote:
> Ming,
>
> Trying to use your bootnetaa64.efi file from
> http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi
>
> I am not able to test this because I cannot PXE boot:
>
> TianoCore 2.0.0 UEFI 2.4.0 Sep 1
> A build from upstream git shows this problem as well.
Looks it is thought as one AMI firmware's issue, so the patch should be merged
to grub, otherwise
grub can't run on APM's UEFI firmware.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From discussions with Ming, the cvm0 node on which he tested
successfully, may be running with Cavium's UEFI rather than AMI's.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893
Title:
TFTP
On Fri, Oct 23, 2015 at 1:38 AM, Ming Lei <1508...@bugs.launchpad.net> wrote:
> Today I have applied this patch(efinet: open Simple Network Protocol
> exclusively) against grub on wily, looks it
> does fix the issue on mustang/merlin.
>
> Dann, could you build one upstrem grub and test it on
Dann, I just run a quick test on cvm0 and looks the grub.efi built from wily
plug the patch just works fine, and
attached my build commandline.
./autogen.sh
./configure --host=x86_64-linux-gnu --target=aarch64-linux-gnu
--build=x86_64-linux-gnu --with-platform=efi
Today I have applied this patch(efinet: open Simple Network Protocol
exclusively) against grub on wily, looks it
does fix the issue on mustang/merlin.
Dann, could you build one upstrem grub and test it on thunder to see if
there is the synchronous exception issue?
--
You received this bug
I applied just this patch to wily's grub and tested on a thunder
platform w/ AMI UEFI, and it appears to have introduced a regression.
Where a MAAS boot would work successfully before, it now triggers a
Synchronous Exception.
The attached script will create a grub netboot image the same way MAAS
Ming Lei has identified that this issue is fixed with the following
upstream grub patch:
commit 49426e9fd2e562c73a4f1206f32eff9e424a1a73
Author: Andrei Borzenkov
Date: Thu May 7 20:37:17 2015 +0300
efinet: open Simple Network Protocol exclusively
The next step is to
10 matches
Mail list logo