Date: Sat, 26 Sep 2020 08:43:40 +0000 From: myfreeweb <greg@unrelenting.technology> To: freebsd-arm@freebsd.org, Michael Sierchio <kudzu@tenebras.com> Subject: Re: AWS Graviton1 Graviton2 Message-ID: <56F00B87-F169-4B6F-8C36-5AD98E084C7F@unrelenting.technology> In-Reply-To: <CAHu1Y72=sxWTTdfzCrCAha_Uo_OKbcFZfxSCs53%2BS-5J1Vqq3g@mail.gmail.com> References: <CAHu1Y72=sxWTTdfzCrCAha_Uo_OKbcFZfxSCs53%2BS-5J1Vqq3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On September 26, 2020 12:54:59 AM UTC, Michael Sierchio <kudzu@tenebras=2E= com> wrote: >I'm using an instance based on the marketplace AMI: ami-01d2b8af277052bcc= =2E4 >and trying >to come up with a partition scheme on a new disk that works=2E No joy so= far=2E > >Must I use MBR as the scheme? No of course not=2E It's actually really stupid that the official AMIs use= MBR=2E I used GPT when I first booted FreeBSD on the Graviton instances=2E You should use GPT=2E >Is EFI boot the only way? Yes=2E What else would you even want? :) FreeBSD does not support any other kind of boot on arm64=2E Even embedded = crap devices load the EFI loader from u-boot=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F00B87-F169-4B6F-8C36-5AD98E084C7F>