The factory build and the sysupgrade build can be pulled from
and
I have NOT tried the factory build but tested a few times the upgrade and it works just fine - thanks to @boretom and many others on the developing side of the WAX206
@giuliomagnifico
At the moment I have installed the factory image from you which you send me for 11 days
I could now just install the sysupgrade from Fin over it right?
Sorry if a stupid question but I am new and this would be the first time I install a sysupgrade version.
No, it's not a stupid question - when You're new to openwrt it is a bit confusing all the terms - I'm new to this my self and has done a lot of reading on many of the foras here - I have 3 devices that runs openwrt - all different.
But to Your question : if You're factory build runs fine then perhaps wait until @guiliomagnifico has upgraded the version You got from him - if something is not as expected then he knows how to deal with it and You may benefit from that.
Since I was bored to reinstall all my packages every update with *your ( ) images, I just compiled mine but it's very minimal, to use the WAX206 as AP only, it comes without dnsmasq... but with some collectd and Prometheus exporter, because I build lots of stats in Grafana from OpenWrt, example.
Now if I have some time I can make another image with wan, pope, etc.. I don't remember who need what, just ask (since the Oracle's CPU power is free )
Edit: oh, I noticed that I forgot to remove the pppoe packet and support (damn ) so it has it, if someone needs the pppoe support, it has the support (but remember to install dnsmasq, because I'm sure it doesn't have it).
....and now I have to make another build for me
Figured I'd stop by to check on the merge status, seems like it's still some way off sadly.
When building from commit 097e9bf9d842dc20932e85e38f9034ab58f499d9 I eventually run into what appears to be a conflict between different TLS/SSL libraries. Has something about the build procedure changed? I've simply tried doing this again since it seemed to work for people.
Collected errors:
* check_data_file_clashes: Package libustream-wolfssl20201210 wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib/libustream-ssl.so
But that file is already provided by package * libustream-mbedtls20201210
* opkg_install_cmd: Cannot install package libustream-wolfssl20201210.
* check_data_file_clashes: Package px5g-wolfssl wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/usr/sbin/px5g
But that file is already provided by package * px5g-mbedtls
* opkg_install_cmd: Cannot install package px5g-wolfssl.
make[1]: *** [package/Makefile:70: package/install] Error 255
make[1]: Leaving directory '/home/pngu/src/github.com/boretom/openwrt-fork'
make: *** [/home/pngu/src/github.com/boretom/openwrt-fork/include/toplevel.mk:231: package/install] Error 2
Normally I'd just dig in and figure out how to resolve the conflict, but given that it's not just one, but 3 cryptographic libraries causing trouble on a flavor of Linux I'm not terribly familiar with tells me I should rather ask for help
Yes, I encoutered the same error few hours ago when I was building my images. I simply deselected the conflicting libraries (in my case was just libustream-wolfssl) but obviously it dependes on your config.
Does the build system, or the KConfig part of it, tell you if something depends on a library you remove? I had a quick browse and found this post about the switch from mbetTLS to WolfSSL which makes me think sticking with the latter might be the better play. Quite frankly though, I have no idea if that's a valid conclusion.
I don't think in the menuconfig but if you remove the wrong library you will have another error when compiling as the error you already have (I think, I have never tried).
I have no idea too, all I can tell you is that I have both installed in the end, probably only a dependences issue, see my .config:
CONFIG_DEFAULT_libustream-wolfssl=y
CONFIG_PACKAGE_libustream-mbedtls=y
# CONFIG_PACKAGE_libustream-openssl is not set
# CONFIG_PACKAGE_libustream-wolfssl is not set
I had to disable one Libraries/libustream and one Utilities/Encryption/px5g. I kept those using wolfssl.
The build did not throw any errors afterwards.
I compared the original firmware and the openwrt firmware partition situation seems to be different, I do not know which of the several partitions to modify mt4, mt5, mt6, mt7, mt8 in the openwrt partition
Hi guys, I've been experimenting with the various releases people have graciously put online for others to try, but I am running into issues installing extra packages for what I want to be testing because the kernel is a little outdated compared to the official builds.
Can anyone make a sysupgrade package with the latest kernel (and matching kernel release designation?) so I can install the latest packages from the official repositories?
So far, I have run into the issue that installing takes a little more hassle then anticipated, the first flash failed but most importantly, I did not realise the interface would become available on the 4 port switch and not on the WAN port. Just a small FYI for anyone running into the same issue
The installed version of package kernel is not compatible, require 5.15.92-1-b7cf82a6… while 5.15.90-1-66604566… is installed.
I've made one this morning but it has the 5.15.90 kernel (same as the one you are using, because of the fork...), anyway I think the issue is not the kernel version but if the package you are trying to install has the Module support in the kernel.