Possibly, I think the SDK might be pulling the wrong kernel configuration, even if you downloaded the SDK package for that particular build.
Can you check the feeds.conf.default in the SDK?
If it uses a branch name like:
src-git base https://gitlab.com/traversetech/ls1088firmware/openwrt.git;arm64-2102
Locate the git commit corresponding to the build you are running from the gitlab CI builds page (check /etc/opkg/distfeeds.conf if unsure)
For example, build pipeline 432907590 → 462f4af8b9390e54a30a7efe03784b29d1056f90
src-git base https://gitlab.com/traversetech/ls1088firmware/openwrt.git^462f4af8b9390e54a30a7efe03784b29d1056f90)
Run ./scripts/feeds updates and try building the module again.
I’ll try and get this fixed for new builds. I think it came from OpenWrt’s defaults for release branches.
Yes, the latest build is based on 21.02.1. The OpenWrt builds are slightly ahead (‘21.02.1+’) as there are new patches which appear to fix WiFi issues, I’ll sync them soon.
(Sorry if you were looking at archive.traverse.com.au - the build date next to muvirt was wrong, but the build details are correct)
I found that the ‘magic’ string in the kernel version is defined in include/kernel.mk in the SDK. If it’s still giving you issues you could try to change it:
Almost there! That build still has an older kernel version (as we are using 5.10 instead of 5.4 in upstream 21.02). There is a newer one I will push in a day or so.
We have also changed the NAND setup to implement firstboot / ‘reset to factory defaults’ so NAND users will need to tweak and/or update their U-Boot on 21.02.2.