From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: sig-arm@lists.ipfire.org Subject: Re: Understanding boot process. Date: Mon, 23 Nov 2020 11:21:43 +0000 Message-ID: In-Reply-To: <175f0787c94.bb87d67e129373.3395557773525029114@fkardame.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4164692837723804645==" List-Id: --===============4164692837723804645== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 w= ill launch GRUB and hopefully return all required configuration to the kernel. > On 22 Nov 2020, at 15:00, Furkan Salman wrote: >=20 > Hello IPFire Team,=20 >=20 > I would like to understand how do you get the grub to work on the arm image= s.=20 >=20 > I have RockPiE which is not supported by your project but I am willing to a= dd support it by myself. =20 >=20 > Afaik I should be able to get it to boot with other Rk3328 board dtb i have= its mainline uboot.=20 >=20 > It seems to get stuck on grub after selecting the ipfire version it doesnt = boot further.=20 Do you have any output from the bootloader/kernel? > I suspect that the bootscripts are designed for a specific arm board as eve= ry board will have different addr for kernel load.=20 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? =20 https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dlfs/grub;h=3D811c2f74= 5e267e5ff6c246b66bc5f2196e12b780;hb=3DHEAD This is how we install GRUB on x86 and ARM64. Best, -Michael >=20 > Thank you.=20 >=20 > _______________________________________________ > SIG-ARM mailing list > SIG-ARM(a)lists.ipfire.org > https://lists.ipfire.org/mailman/listinfo/sig-arm --===============4164692837723804645==--