From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: Understanding boot process.
Date: Mon, 23 Nov 2020 11:21:43 +0000 [thread overview]
Message-ID: <D83E65B4-6BEE-4832-9579-051BE90038A6@ipfire.org> (raw)
In-Reply-To: <175f0787c94.bb87d67e129373.3395557773525029114@fkardame.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
Hello Furkan,
Thanks for signing up and posting :)
I suppose we are talking about ARM64:
We currently only support systems that use EFI. If there is an EFI BIOS, it will launch GRUB and hopefully return all required configuration to the kernel.
> On 22 Nov 2020, at 15:00, Furkan Salman <tech(a)fkardame.com> wrote:
>
> Hello IPFire Team,
>
> I would like to understand how do you get the grub to work on the arm images.
>
> I have RockPiE which is not supported by your project but I am willing to add support it by myself.
>
> Afaik I should be able to get it to boot with other Rk3328 board dtb i have its mainline uboot.
>
> It seems to get stuck on grub after selecting the ipfire version it doesnt boot further.
Do you have any output from the bootloader/kernel?
> I suspect that the bootscripts are designed for a specific arm board as every board will have different addr for kernel load.
No, we only support a generic way to boot, because it is simply not feasible for us to provide hundreds of different images for all ARM boards out there.
> Where can I find the source code for the boot script package?
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/grub;h=811c2f745e267e5ff6c246b66bc5f2196e12b780;hb=HEAD
This is how we install GRUB on x86 and ARM64.
Best,
-Michael
>
> Thank you.
>
> _______________________________________________
> SIG-ARM mailing list
> SIG-ARM(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/sig-arm
next parent reply other threads:[~2020-11-23 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175f0787c94.bb87d67e129373.3395557773525029114@fkardame.com>
2020-11-23 11:21 ` Michael Tremer [this message]
[not found] <175f4da243f.ac5db1e8157491.8173564156224748900@fkardame.com>
2020-11-23 11:31 ` Michael Tremer
[not found] <175f4e27305.b8b9531c157234.25158576621006220@fkardame.com>
2020-11-23 11:36 ` Michael Tremer
[not found] <175f4e98299.12656e473157546.5087885004816305076@fkardame.com>
2020-11-23 15:02 ` Michael Tremer
[not found] <175f6be62c6.b92ec548182277.4850897972109008957@fkardame.com>
2020-11-24 10:59 ` Michael Tremer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D83E65B4-6BEE-4832-9579-051BE90038A6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.org \
/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