12-07-2018, 12:02 AM
Does anyone have any hints on how to get an NFS mount working? I am using kernel 4.20 since it recently had rockpro64 support added. My kernel parameters look like the following:
console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=/dev/nfs rw nfsroot=10.10.0.1:/export/sysroot,proto=tcp,vers=3 ip=10.10.0.2:10.10.0.1::255.255.255.0:rockpro64:eth0:off raid=noautodetect nfsrootdebug
and I am loading my kernel and kicking it off from u-boot with:
tftpboot 0x2000000 <kernel Image>
tftpboot 0x20000000 rk3399-rockpro64.dtb
booti 0x2000000 - 0x20000000
The NFS debug spits out:
NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,proto=tcp,vers=3,nolock,addr=10.10.0.1'
NFS: parsing nfs mount option 'vers=2'
NFS: parsing nfs mount option 'udp'
NFS: parsing nfs mount option 'rsize=4096'
NFS: parsing nfs mount option 'wsize=4096'
NFS: parsing nfs mount option 'proto=tcp'
NFS: parsing nfs mount option 'vers=3'
NFS: parsing nfs mount option 'nolock'
NFS: parsing nfs mount option 'addr=10.10.0.1'
NFS: MNTPATH: '/export/sysroot'
NFS: sending MNT request for 10.10.0.1:/export/sysroot
NFS: failed to create MNT RPC client, status=-101
NFS: unable to mount server 10.10.0.1, error -101
I am not convinced that the network interface is coming up. For starters, I never see anything like the following on the console:
IP-Config: Complete:
device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255,
host=myboard, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
which is what I thought using the ip= parameter was supposed to do and when I turn on:
rpcdebug -m nsfd all
rpcdebug -m rpc all
and watch /var/log/messages on my server, nothing happens - it looks like my devices aren't talking.
I assumed that the in kernel realtek drivers would be sufficient, but I noticed that in the 4.4 kernel, there is an actual rockchip ethernet driver - does that need to be used in the 4.20 kernel? I tried copying it and adding it to my config, but some of the timer interfaces changed, so it does not compile.
Any hints would be helpful.
Thanks!
console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=/dev/nfs rw nfsroot=10.10.0.1:/export/sysroot,proto=tcp,vers=3 ip=10.10.0.2:10.10.0.1::255.255.255.0:rockpro64:eth0:off raid=noautodetect nfsrootdebug
and I am loading my kernel and kicking it off from u-boot with:
tftpboot 0x2000000 <kernel Image>
tftpboot 0x20000000 rk3399-rockpro64.dtb
booti 0x2000000 - 0x20000000
The NFS debug spits out:
NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,proto=tcp,vers=3,nolock,addr=10.10.0.1'
NFS: parsing nfs mount option 'vers=2'
NFS: parsing nfs mount option 'udp'
NFS: parsing nfs mount option 'rsize=4096'
NFS: parsing nfs mount option 'wsize=4096'
NFS: parsing nfs mount option 'proto=tcp'
NFS: parsing nfs mount option 'vers=3'
NFS: parsing nfs mount option 'nolock'
NFS: parsing nfs mount option 'addr=10.10.0.1'
NFS: MNTPATH: '/export/sysroot'
NFS: sending MNT request for 10.10.0.1:/export/sysroot
NFS: failed to create MNT RPC client, status=-101
NFS: unable to mount server 10.10.0.1, error -101
I am not convinced that the network interface is coming up. For starters, I never see anything like the following on the console:
IP-Config: Complete:
device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255,
host=myboard, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
which is what I thought using the ip= parameter was supposed to do and when I turn on:
rpcdebug -m nsfd all
rpcdebug -m rpc all
and watch /var/log/messages on my server, nothing happens - it looks like my devices aren't talking.
I assumed that the in kernel realtek drivers would be sufficient, but I noticed that in the 4.4 kernel, there is an actual rockchip ethernet driver - does that need to be used in the 4.20 kernel? I tried copying it and adding it to my config, but some of the timer interfaces changed, so it does not compile.
Any hints would be helpful.
Thanks!
