Date: Thu, 8 Mar 2018 19:49:45 +0300 From: Greg <greg@unrelenting.technology> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org Subject: Re: Rock64 status Message-ID: <20180308164945.p33ofc2njtjhqhj2@unrelenting.technology> In-Reply-To: <20180226224214.64b14ec9f016f713cd8dec6f@bidouilliste.com> References: <20180226224214.64b14ec9f016f713cd8dec6f@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/26, Emmanuel Vadot wrote: >This u-boot is based on 2017.09 which have some problems with EFI block >devices, this means that using boot1.efi or loader.efi from the sdcard >will fail. However netbooting works like a charm and for now this is >perfect for me as I don't want to swap sdcard when doing kernel dev. >I hope that the u-boot status will change soon. Hi! Finally got around to trying to boot my ROCK64. Trying to netboot the March 7 current snapshot, the loader doesn't work: => bootefi ${kernel_addr_r} ${fdt_addr_r} ## Starting EFI application at 02000000 ... Consoles: EFI console efipart_inithandles failed 2, expect failuresCommand line arguments: loader.efi Image base: 0x2000000 EFI version: 2.05 EFI Firmware: Das U-boot (rev 0.00) FreeBSD/arm64 EFI loader, Revision 1.1 (Wed Mar 7 17:24:53 UTC 2018 root@releng3.nyi.freebsd.org) ## Application terminated, r = 14 Replacing loader.efi with an older one (the one I use on the RPi3) gets me into the loader prompt, but the network doesn't work: FreeBSD/arm64 EFI loader, Revision 1.1 (Thu Jan 11 15:18:47 UTC 2018 root@releng3.nyi.freebsd.org) Speed: 1000, full duplex \ can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. The u-boot version is: U-Boot 2017.09-ga0a2b48 (Mar 04 2018 - 20:21:36 +0000), Build: jenkins-linux-build-rock-64-193
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180308164945.p33ofc2njtjhqhj2>