Date: Mon, 15 Jul 2019 20:01:27 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Denis Polygalov <dpolyg@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: Booting FreeBSD on Rock64 Message-ID: <20190715200127.4b649877d8baefeb5282df64@bidouilliste.com> In-Reply-To: <169de7cf-32f2-7b7b-c12e-a86a4b6a9e87@gmail.com> References: <169de7cf-32f2-7b7b-c12e-a86a4b6a9e87@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Jul 2019 19:16:30 +0900 Denis Polygalov <dpolyg@gmail.com> wrote: > Here is my attempt to advance this thread: > http://freebsd.1045724.x6.nabble.com/Booting-FreeBSD-on-Rock64-td6312109.html > > by using new release of ayufan's u-boot: > 2017.09-rockchip-ayufan-1063-g29843fbd42 > > and most recent FreeBSD image: > FreeBSD-13.0-CURRENT-arm64-aarch64-20190711-r349909-memstick.img > > Booting from USB drive lead to near the same infinite reset loop: > ... > Found 3 disks > Consoles: EFI console > Reading loader env vars from /efi/freebsd/loader.env > FreeBSD/arm64 EFI loader, Revision 1.1 > > Command line arguments: loader.efi > EFI version: 2.05 > EFI Firmware: Das U-boot (rev 0.00) > Console: efi (0) > Load Path: \efi\boot\bootaa64.efi > Load Device: UNKNOWN(0001,0004) > "Synchronous Abort" handler, esr 0x96000210 > ELR: fbec72c4 > LR: fbe97500 > x0 : 0000000000000000 x1 : 0000000000000000 > x2 : 0000000000000000 x3 : 0000000000000000 > x4 : 00000000fbecf890 x5 : 00000000fbec6838 > x6 : 00000000fbeea150 x7 : 0000000000000000 > x8 : 0000000000000000 x9 : 0000000000000074 > x10: 00000000fbeef8a8 x11: 0000000000000296 > x12: 0000000000000296 x13: 0000000000000000 > x14: 00000000f9f68b90 x15: 0000000000000000 > x16: 0000000000000045 x17: 0000000000000000 > x18: 0000000000000000 x19: 00000000fbee9e48 > x20: 00000000fbece8d3 x21: 0000000000000000 > x22: 0000000000000000 x23: 00000000fbeef8b0 > x24: 0000000000000000 x25: 0000000000000000 > x26: 00000000fbeeeb40 x27: 0000000020001000 > x28: 8000000000000005 x29: 00000000fbee9e00 > > Resetting CPU ... > > Notice however absence of line > "Failed to find bootable partition" > comparing to the first post in original thread. RockChip's vendor u-boot is really broken for efi booting (or maybe we do weird stuff in loader.efi but I doubt it). There have been some progress in mainline u-boot for RockChip recently but I haven't checked yet if we can use it for rock64. > As of the network boot it reaches screen > with ASCII art of the FreeBSD loader and then hangs here: > > Autoboot in 0 seconds, hit [Enter] to boot or any other key to stop > Loading kernel... > /boot/kernel/kernel text=0x93951c data=0x1914c8+0x84ab1c > syms=[0x8+0x1387f8+0x8+0x124a11] > Loading configured modules... > can't find '/boot/entropy' > Using DTB provided by EFI at 0x8200000. > / > > For the network boot I'm using the same image as for USB boot: > FreeBSD-13.0-CURRENT-arm64-aarch64-20190711-r349909-memstick.img > unpacked and served via NFS. > Can someone suggest what is going on here? > Full USB and network boot logs are attached. > > Regards, > Denis. How did you setup the boot ? Do you have tftpd running so u-boot can download the loader and the dtb ? If you don't have the dtb in $TFTPDIR/dtb/rockchip/ that might be the problem, I recall the dtb included in u-boot being incomplete. I've just booted mine after updating to r350003+c99cb2e79ed6 without a problem. -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190715200127.4b649877d8baefeb5282df64>