Type: Self-Compiled Firmware
SDK Package Name: rk356x_linux_release_20230425_v1.3.2c.xml
Modification Content: kernel
Log: trying_nfs_rootfs.txt.gz
I am trying to get kernel via TFTP (which works quite ok) and mount rootfs via NFS. I have commented out
/*bootargs = "earlycon=uart8250,mmio32,0xfe660000 console=ttyFIQ0 root=PARTLABEL=rootfs rootfstype=ext4 ro rootwait overlayroot=device:dev=PARTLABEL=userdata,fstype=ext4,mkfs=1 coherent_pool=1m systemd.gpt_auto=0 cgroup_enable=memory swapaccount=1 swiotlb=0x10000";*/
and have modified u-boot to support TFTP and NFS and timeout to 5 seconds to be able to enter my own bootcmd
setenv bootcmd "setenv ipaddr 169.0.0.7;setenv serverip 169.0.0.1;setenv netmask 255.255.255.0; setenv nfsroot 169.0.0.1:/home/geekay/devel/netboot/nfs_export,vers=3,tcp;setenv root /dev/nfs; setenv rootfstype nfs;tftp ${ramdisk_addr_r} 169.0.0.1:initrd-4.19.232; tftp ${kernel_addr_r} 169.0.0.1:Image-4.19.232; tftp ${fdt_addr_r} 169.0.0.1:rk-kernel.dtb; booti ${kernel_addr_r} - ${fdt_addr_r}"
The NFS export mounts good when I boot from eMMC, but something (maibe a parameter.txt?) is keeping the board from mounting the NFS export. What more should I do to succeed?
tchip_askquestions
RK356x_build_log.tar.gz (2.31 KB)
trying_nfs_rootfs.txt.gz (30.2 KB)