Hi!
I am using U-Boot to boot Debian Buster arm64 (standard kernel with a
dracut-based initramfs) via an extlinux.conf on my Raspberry Pi 3.
Recently, the Debian kernel grew beyond 16 MiB:
4.13: /boot/vmlinuz-4.13.0-1-arm64 == 16448000 bytes (< 16 MiB) [0]
4.14: /boot/vmlinuz-4.14.0-3-a
Hi!
I just wanted to let you know that I recently upgraded to U-Boot
2018.07 from Debian Experimental [0] and everything works now! Thanks
to everybody involved [1]!
Best regards
Alexander Kurtz
[0] https://tracker.debian.org/pkg/u-boot
[1] https://github.com/u-boot/u-boot/commits/v2018.07/incl
On 02/23/2018 04:58 AM, Alexander Kurtz wrote:
> Hi!
>
> I am using U-Boot to boot Debian Buster arm64 (standard kernel with a
> dracut-based initramfs) via an extlinux.conf on my Raspberry Pi 3.
>
> Recently, the Debian kernel grew beyond 16 MiB:
>
> 4.13: /boot/vmlinuz-4.13.0-1-arm64 == 1
On Fri, Feb 23, 2018 at 04:47:06PM +0900, Jaehoon Chung wrote:
> On 02/23/2018 04:58 AM, Alexander Kurtz wrote:
> > Hi!
> >
> > I am using U-Boot to boot Debian Buster arm64 (standard kernel with a
> > dracut-based initramfs) via an extlinux.conf on my Raspberry Pi 3.
> >
> > Recently, the Debia
On 02/22/2018 12:58 PM, Alexander Kurtz wrote:
Hi!
I am using U-Boot to boot Debian Buster arm64 (standard kernel with a
dracut-based initramfs) via an extlinux.conf on my Raspberry Pi 3.
Recently, the Debian kernel grew beyond 16 MiB:
4.13: /boot/vmlinuz-4.13.0-1-arm64 == 16448000 bytes
+ agraf
On Fri, 23 Feb 2018 09:57:30 -0500
Tom Rini wrote:
> On Fri, Feb 23, 2018 at 04:47:06PM +0900, Jaehoon Chung wrote:
> > On 02/23/2018 04:58 AM, Alexander Kurtz wrote:
> > > Hi!
> > >
> > > I am using U-Boot to boot Debian Buster arm64 (standard kernel with a
> > > dracut-based initram
On Fri, Feb 23, 2018 at 08:00:19PM +0200, Tuomas Tynkkynen wrote:
> + agraf
>
> On Fri, 23 Feb 2018 09:57:30 -0500
> Tom Rini wrote:
>
> > On Fri, Feb 23, 2018 at 04:47:06PM +0900, Jaehoon Chung wrote:
> > > On 02/23/2018 04:58 AM, Alexander Kurtz wrote:
> > > > Hi!
> > > >
> > > > I am using
Hi!
Thanks for confirming this! I see four ways how this can be solved:
1. I can locally adjust the memory locations to make my > 16MiB kernel
work. The commit mentioned by Jaehoon Chung does this via a custom
boot.scr, I did this by bumping $scriptaddr and $ramdisk_addr_r
in
8 matches
Mail list logo