Comment 20 for bug 1839317

thanks for the support.
I tried to install shim unsigned but without success.
if the secure boot is active, grub works correctly.
if inactive grub does not launch windows.
tried on my 2 acer notebooks (Aspire E 5 and the v-371)

Il giorno lun 4 nov 2019 alle ore 21:30 Steve Langasek <
<email address hidden>> ha scritto:

> The standard UEFI boot path for Ubuntu is always to boot via shim and
> then to grub.
>
> But we also know that the signed shim binary we currently have for arm64
> is broken on this architecture.
>
> The fixed shim is in the process of being signed and in the meantime
> this is simply an unsupported configuration.
>
> If this is reproducible when chainloading from shim to grub, then it is
> a valid bug and requires further investigation. But there are log
> messages in the bug history suggesting that the lack of shim might be
> the cause, so for the moment I am assuming that is the case and marking
> this as invalid.
>
> Given that you've mentioned having secureboot turned off anyway, you
> could try the unsigned shim binaries from https://launchpad.net/~ubuntu-
> uefi-team/+archive/ubuntu/ppa/+packages
> <https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages>
> to see if you can reproduce the
> problem when booting shim->grub.
>
> ** Changed in: grub2 (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1839317
>
> Title:
> Grub fails to chainload the Windows Boot Manager on aarch64 laptops
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions
>