[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#928612: u-boot-sunxi: Enable support for NanoPi NEO2

On Jo, 09 mai 19, 07:58:39, Domenico Andreoli wrote:
> On Wed, May 08, 2019 at 11:07:10PM +0300, Andrei POPESCU wrote:
> > 
> > It is sufficient to just create the partition table, deleting and adding 
> > partitions from the installer (manual partitioning) should be safe.
> Verified, changing the layout from there results in a complete GPT rewrite.
I feel like we are talking past each other. What I mean is that, in my 
experience, having u-boot installed on a media (in my case SD card for 
PINE A64+) and a msdos partition table in the installer one can 
delete/add partitions (manual instead of guided partitioning) and the 
media remains bootable.

Rewriting the partition *table*, even if msdos will make the media 
> > > The installation process goes nicely but grub installation fails,
> > > as it seems to be expected [0]. The board is left unbootable.
> > 
> > Just curios, since I'm not familiar with this particular board, but why 
> > do you need grub if you already have u-boot?
> I wondered the same and in a more hacky attempt I made more than one
> year ago, with older hand-crafted installed with a 4.15 kernel, I came
> to the conclusion that Debian arm64 was u-boot+grub with a scent of UEFI.
Much has happened in a year, in particula a new upstream u-boot with 
much better support out-of-the-box for a lot of devices/SoCs.

> I aim at the most streamlined installation with the most support out
> of the box and least divergence from a standard setup. I've got a fully
> reproducible and, I hope, maintainable installation.

See https://wiki.debian.org/InstallingDebianOn/PINE64/PINEA64 for a 
general outline of my steps.

For devices without a pre-made image with u-boot there are two 
additional steps required: create the partition table (easy) and install 
u-boot (undocumented).

For sunxi devices there is u-boot-install-sunxi64, but it only supports 
a handful of devices.

Hope this helps,

Attachment: signature.asc
Description: PGP signature

Reply to: