Bug#922101: grub-efi-arm: does not retrieve device-tree from uefi systab and manual devicetree does not work properly to boot armhf kernel

[Da Xue]

The grub in buster already has all of the fixes like Ubuntu 18.04. It
properly loads device tree from systab passed from firmware. This is a
pretty important issue for simply booting arm systems so I don't know if it
is worth it to backport the capability into the current grub or just not
use stretch for any arm systems. We hacked around this but I would imagine
it would save a lot of time for others to backport the arm64/armhf bits I
mentioned.

On Tue, Feb 26, 2019 at 2:32 PM Colin Watson <cjwatson at debian.org> wrote:

> On Tue, Feb 12, 2019 at 01:59:23AM +0000, Da Xue wrote:
> > Package: grub-efi-arm
> > Version: 2.02~beta3-5+deb9u1
> > Severity: important
> >
> > Dear Maintainer,
> >
> >
> >    * What led up to the situation?
> >    Install grub (bootarm.efi) and update-grub on armhf system.
> >
> >    * What exactly did you do (or not do) that was effective (or
> >      ineffective)?
> >    We pass the device tree from u-boot to GRUB2 via UEFI systab. It is
> >    not automatically used by the current version of grub so we have to
> >    manually execute "devicetree" and point it to a device tree binary
> >    file. However even with this manual intervention, the kernel still
> >    hangs. The problem does not occur on arm64 systems or the GRUB2
> >    version in Ubuntu 18.04.
>
> Could you try version 2.02+dfsg1-9 or newer, from buster?  It has a very
> substantial reworking of the Linux loader on arm, so it'd be good to
> determine whether it suffers from the same problem.
>
> Thanks,
>
> --
> Colin Watson                                       [cjwatson at debian.org]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20190623/fe4647e0/attachment.html>