From: Vagrant Cascadian <vagrant@debian.org>
To: Simon South <simon@simonsouth.net>
Cc: help-guix@gnu.org
Subject: Re: Building installation image for ROCK64
Date: Sun, 26 Apr 2020 10:09:02 -0700 [thread overview]
Message-ID: <87zhayyy1d.fsf@ponder> (raw)
In-Reply-To: <87o8reb9ob.fsf@simonsouth.net>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On 2020-04-26, Simon South wrote:
> From there, log in to the ROCK64 as the superuser. Using fdisk, prepare
> a microSD card (/dev/mmcblk0) with a GPT partition table and a single
> partition beginning at sector 2,048.
With your current layout, parts of the bootloader may be written to the
same offsets as files in your first partition... you may have gotten
lucky for now, but it's only a matter of time till something breaks your
bootloader!
You really want to have the loader1 (start sector 64, 2.5MB size) and
loader2 (start sector 16384, 4MB size) partitions listed in:
http://opensource.rock-chips.com/wiki_Partitions
gptfdisk/gdisk should be able to write such a partition table (at least
the loader2 partition, some tools refuse to create the loader1 partition
starting at sector 64).
Glad you made good progress! It would be nice to eventually be able to
create installer images for aarch64/armhf... there's been a lot of
progress on being able to create cross-compiled installation images, so
the day may not be so far off!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-04-26 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 19:48 Building installation image for ROCK64 Simon South
2020-04-11 21:12 ` Vagrant Cascadian
2020-04-12 16:19 ` Simon South
2020-04-26 14:31 ` Simon South
2020-04-26 17:09 ` Vagrant Cascadian [this message]
2020-04-27 13:19 ` Simon South
2020-04-27 17:22 ` Vagrant Cascadian
2020-04-12 10:18 ` Pierre Langlois
2020-04-12 10:27 ` Pierre Langlois
2020-04-12 16:25 ` Simon South
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhayyy1d.fsf@ponder \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=simon@simonsouth.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).