Date: Thu, 12 Jul 2018 16:00:51 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Greg V <greg@unrelenting.technology> Cc: freebsd-arm@freebsd.org Subject: Re: Netbooting ROCK64 Message-ID: <20180712160051.ab6447bad4d97395552c3a5d@bidouilliste.com> In-Reply-To: <1531392570.1456.0@hraggstad.unrelenting.technology> References: <1531333209.1596.0@hraggstad.unrelenting.technology> <20180712120405.a16a2733473400e899f34d2f@bidouilliste.com> <1531392570.1456.0@hraggstad.unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 Jul 2018 13:49:30 +0300
Greg V <greg@unrelenting.technology> wrote:
>
>
> On Thu, Jul 12, 2018 at 1:04 PM, Emmanuel Vadot <manu@bidouilliste.com>
> wrote:
> > On Wed, 11 Jul 2018 21:20:09 +0300
> > Greg V <greg@unrelenting.technology> wrote:
> >>
> >> FreeBSD/arm64 EFI loader, Revision 1.1
> >> (Mon Jul 9 18:05:19 UTC 2018 root@releng3.nyi.freebsd.org)
> >> Load Path: loader.efi
> >> Load Device: MAC(06d4ce39aa76,0x0)
> >> BootCurrent: 0000
> >> BootOrder: 0008 0000[*] 0000[*] 0000[*] 2f10 0000[*] 0000[*]
> >> 0000[*]
> >> 0000[*] 0000[*] 2f30 0000[*] 3b50 fcf0 0000[*] 0000[*] 4ddc fef4
> >> 0000
> >> [*] 0000[*] 3b10 fcf0 0000[*] 0000[*] 4da8 fef4 0000[*] 0000[*] 3ba0
> >> fcf0 0000[*] 0000[*] 2d40 fef4 0000[*] 0000[*] 8cf7 dffe b6f3 7f3d
> >> 39b0
> >> 5d06 b2e7 17d8 3b80 fcf0 0000[*] 0000[*] 0c30 fef7 0000[*] 0000[*]
> >> 0000[*] 0000[*] 0000[*] 0000[*] 0003 0000[*] 0000[*] 0000[*] 06e8
> >> fefa
> >> 000
> >> 0[*] 0000[*] 3be8 fcf0 0000[*] 0000[*] a108 fef6 0000[*] 0000[*]
> >> 57dc
> >> 5baf d956 2fed d6a0 fcf4 0000[*] 0000[*] 5fe3 ff37 62bf 9568 3c90
> >> fcf0
> >> 0000[*] 0000[*] a25c fef6 0000[*] 0000[*] 06e8 fefa 0000[*] 0000[*]
> >> 0000[*] 0820 0000[*] 0000[*]
> >> Can't find device by handle
> >> Failed to find bootable partition
> >
> > ^^^^
> >
> > This is your problem.
> > Do you have a nfs export serving the freebsd files ?
>
> Yeah, of course.
>
> And the u-boot script is explicitly configured to use it:
>
> env set serverip 192.168.1.2
> env set baudrate 115200
This is a wrong baudrate, RK SoC is using 1.5Mbps
> env set bootargs boot.nfsroot.server=${serverip}
> boot.nfsroot.path=<PATH> comconsole_speed=${baudrate}
> tftpboot ${kernel_addr_r} loader.efi
> bootefi ${kernel_addr_r} ${fdtcontroladdr}
I've never used nfs with loader like this, do you control the dhcp ?
If so just set the correct rootpath in it and in uboot just do :
setenv boot_targets dhcp
saveenv
> It's not getting to NFS. tcpdump shows no nfs activity from the board's
> IP address. Only ARP, TFTP and some weird UDP ports, all before
> loader.efi starts.
>
> A Raspberry Pi 3 boots fine with about the same setup (minus baudrate,
> plus fdt from file).
>
> Also, just checked: the nfs command in U-Boot actually tries to
> connect, 'sunrpc' and 'cadlock2' show up on tcpdump.
> Nothing shows up with loader.efi, and it terminates *instantly*.
> It clearly cannot find the Ethernet device itself.
>
> Could you please send me the loader.efi that works for you?
> And which version of U-Boot you use it with.
I use loader.efi from head and u-boot from ayufan.
--
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?20180712160051.ab6447bad4d97395552c3a5d>