A post was split to a new topic: Trouble with 5GHz wifi on WAX206
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.
If someone want it is here: r21967+openwrt-mediatek-mt7622-netgear_wax206-squashfs-sysupgrade.bin, the .config file is here: https://pastebin.com/PDW2798k
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 
Edit2:
Here's the minimal build without pppoe, dnsmasq, etcc... but with collectd, prmometheus exporters, stats,....
Config: https://pastebin.com/nqb23BKr
Build: r21967-AP-openwrt-mediatek-mt7622-netgear_wax206-squashfs-sysupgrade.bin
1 Like
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
And the current veersion installed on the WAX206
libustream-mbedtls20201210 - 2022-12-08-9217ab46-2
libwolfssl5.5.4.e624513f - 5.5.4-stable-1
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.
1 Like
I want to install more apps in the firmware, but the firmware space is only about 30M, how can I make it bigger? Will there be any bad effects?
Probably won't be able to go back to the Netgear fw.
Need to build your own images, containing the new size.
root@WAX206:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "Preloader"
mtd1: 00040000 00020000 "ATF"
mtd2: 00080000 00020000 "Bootloader"
mtd3: 00080000 00020000 "Config"
mtd4: 00100000 00020000 "Factory"
mtd5: 02600000 00020000 "ImageA"
mtd6: 025e0000 00020000 "Kernel"
mtd7: 002a0000 00020000 "kernel"
mtd8: 02340000 00020000 "rootfs"
mtd9: 00c60000 00020000 "rootfs_var"
mtd10: 02600000 00020000 "Kernel_backup"
mtd11: 00800000 00020000 "CFG"
mtd12: 00400000 00020000 "RAE"
mtd13: 00100000 00020000 "POT"
mtd14: 00400000 00020000 "Language"
mtd15: 00200000 00020000 "Traffic"
mtd16: 00100000 00020000 "Cert"
mtd17: 00100000 00020000 "NTGRcryptK"
mtd18: 00500000 00020000 "NTGRcryptD"
mtd19: 00100000 00020000 "LOG"
mtd20: 00640000 00020000 "User_data"
root@Wax206:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "Preloader"
mtd1: 00040000 00020000 "ATF"
mtd2: 00080000 00020000 "Bootloader"
mtd3: 00080000 00020000 "Config"
mtd4: 00100000 00020000 "Factory"
mtd5: 02600000 00020000 "firmware"
mtd6: 00600000 00020000 "kernel"
mtd7: 02000000 00020000 "ubi"
mtd8: 02600000 00020000 "firmware_backup"
mtd9: 00800000 00020000 "CFG"
mtd10: 00400000 00020000 "RAE"
mtd11: 00100000 00020000 "POT"
mtd12: 00400000 00020000 "Language"
mtd13: 00200000 00020000 "Traffic"
mtd14: 00100000 00020000 "Cert"
mtd15: 00100000 00020000 "NTGRcryptK"
mtd16: 00500000 00020000 "NTGRcryptD"
mtd17: 00100000 00020000 "LOG"
mtd18: 00640000 00020000 "User_data"
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.
you may be right, I was trying to install the mdio LED control for PHY devices...
I want all my LED's to turn off (except the power LED), but I can not control the switch led's despite it saying it can.
If you want to use the mdio control just add this under menu-config before building the image. Then it works without the updated kernel.
Oh, in this case just use this build I've made this morning, it has the mdio support: https://dsc.cloud/40973c/openwrt-mediatek-mt7622-netgear_wax206-squashfs-sysupgrade.bin
(it has other things like collectd, blabla, see here the config: https://pastebin.com/JEzzKZK8 be careful that it has no swap, pppoe, WAN, etc.. support)
PS: I configured the LED just this morning, with the green power on alywas on, and the blue for the WAN blinking with the network activity, now this white piece of cheap plastic is a bit nicer ahah.
3 Likes
I tried to modify the space size of mt4, mt5, mt6, mt7, mt8 in the dts file, and finally compiled a firmware, but the result after the update was that the router restored the original 1.0.3 firmware
What is the dts file? There’s no file, you just have to change it menuconfig with your size and compile it.
My firmware is about 35M if it is completed, but the maximum in the mt7622.mk file can only be 32768K, so every time a complete compilation will report an error, so I modified this limit, but even if the compilation is successful, it cannot be updated normally, so I think it should be The size of each partition is set in the dts file of wax206, which makes it impossible to update. I tried to modify the size of the Root filesystem partition size in Target Images, but it didn’t seem to work. I don’t really understand this, so if you know, I hope you can tell How do I do it, thanks a lot!
Sorry but I'm not understanding what you're doing, I can't help.