[Dec 07] DietPi(v6.18) - Pinebook / Manjaro KDE (preview3) / Manjaro LXQT (preview3) - Pinebook |[Dec 06] Armbian Debian Stretch (5.67) / Armbian Ubuntu 18.04 Bionic Desktop (5.67) - RockPro64 |[Dec 05] DietPi(v6.18) - 1080P Pinebook | [Nov 28] Slackware Aarch64 Miniroot (20181126) / Slackware Aarch64 XFCE (20181126) - RockPro64 / Manjaro KDE (preview3) / Manjaro LXQT (preview3) /Q4OS (2.6-r6) - 1080P Pinebook

Project Inspiration | Get Started | IRC Logs | Forum Rules/Policy


Rockpro64 NFS root mount (kernel 4.20) - ethernet help?
#1
Hi all

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!
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  NVMe and new kernel bjbb17 0 113 09-25-2018, 03:39 PM
Last Post: bjbb17
  Real-time linux kernel Artyom 45 9,924 09-11-2018, 01:08 AM
Last Post: zzwpine
  DKMS on kernel 3.10.107-pine64 obrienmd 5 305 06-21-2018, 05:45 PM
Last Post: evilbunny
  Kernel for A64 git longsleep 179 49,271 03-25-2018, 03:25 PM
Last Post: Luke
  Gentoo for pine64 - longsleep kernel incoherent 0 570 12-09-2017, 08:14 AM
Last Post: incoherent
  [SOLVED] UEFI + Fedora Mainline Kernel Booting! cztian 0 568 07-13-2017, 08:38 PM
Last Post: cztian
  Mainline kernel [Solved] jeroen79 11 2,443 02-08-2017, 06:19 AM
Last Post: umiddelb
Question Need help : Issue in running compiled kernel with tftp+uboot dinesh.bhoyar 2 551 01-30-2017, 12:44 AM
Last Post: dinesh.bhoyar
Question No more ethernet with linux... Android connection is fine?!?! cr2016 9 1,347 11-12-2016, 07:29 PM
Last Post: cr2016
  Jackd triggers kernel warning cztian 0 861 09-03-2016, 08:16 AM
Last Post: cztian

Forum Jump:


Users browsing this thread: 1 Guest(s)