02-08-2021, 10:08 PM
Thank you for posting the patch, it has greatly helped. One quick note, I had to make one further modification to get NFS to compile without error, specifically kmod-fs-nfs-common:
It seems you are creating your builds with glibc, is there a particular reason or benefit there? I am building with the standard openwrt configuration using musl with no problem. I realize that by using an sd card or emmc we are quite a bit less size constrained than the routers with tiny flash that openwrt was originally built for, but we are also building an image with all of the software self-contained or external ipks with heavy reliance on being built within the openwrt development system and not relying on compatible ABIs or 3rd party software to work with the image after the fact. Just wanting to see if I am missing any obvious benefits of choosing glibc over musl in my build.
I am still running into issues with my rtl8153 adapter that I use for testing, even with a powered USB hub and after including both of your recommended ethtool commands. My final setup will use the dual ax88179 adapter though. It seems to be working better than the rtl8153, but is still requiring the powered hub. I am going to try swapping out my stock Rock64 5v 3A power supply with a 4A supply made for a different USB 3.0 hub, as well as taking voltage measurements on the GPIO pins and using an inline USB voltage and current meter on the network adapters to try and squash any power-related issues I may be having.
I'll continue to update on my progress, but I am glad to be able to build an image from scratch with your patches. I see you are including the vendor drivers for rtl8153 and ax88179 so thank you for that.
~Chainu
Code:
diff --git a/package/kernel/linux/modules/fs.mk b/package/kernel/linux/modules/fs.mk
index d43542b17e..327e236e8d 100644
--- a/package/kernel/linux/modules/fs.mk
+++ b/package/kernel/linux/modules/fs.mk
@@ -366,7 +366,8 @@ define KernelPackage/fs-nfs-common
FILES:= \
$(LINUX_DIR)/fs/lockd/lockd.ko \
$(LINUX_DIR)/net/sunrpc/sunrpc.ko \
- $(LINUX_DIR)/fs/nfs_common/grace.ko
+ $(LINUX_DIR)/fs/nfs_common/grace.ko \
+ $(LINUX_DIR)/fs/nfs_common/nfs_ssc.ko
AUTOLOAD:=$(call AutoLoad,30,grace sunrpc lockd)
endefIt seems you are creating your builds with glibc, is there a particular reason or benefit there? I am building with the standard openwrt configuration using musl with no problem. I realize that by using an sd card or emmc we are quite a bit less size constrained than the routers with tiny flash that openwrt was originally built for, but we are also building an image with all of the software self-contained or external ipks with heavy reliance on being built within the openwrt development system and not relying on compatible ABIs or 3rd party software to work with the image after the fact. Just wanting to see if I am missing any obvious benefits of choosing glibc over musl in my build.
I am still running into issues with my rtl8153 adapter that I use for testing, even with a powered USB hub and after including both of your recommended ethtool commands. My final setup will use the dual ax88179 adapter though. It seems to be working better than the rtl8153, but is still requiring the powered hub. I am going to try swapping out my stock Rock64 5v 3A power supply with a 4A supply made for a different USB 3.0 hub, as well as taking voltage measurements on the GPIO pins and using an inline USB voltage and current meter on the network adapters to try and squash any power-related issues I may be having.
I'll continue to update on my progress, but I am glad to be able to build an image from scratch with your patches. I see you are including the vendor drivers for rtl8153 and ax88179 so thank you for that.
~Chainu