OpenWrt Support for Armor G5 (NBG7815)

kirdes · December 13, 2023, 2:39pm

Please discuss this further in the mentioned PR on github.

Acehigh · December 26, 2023, 4:24pm

@itorK tried the module and compiled openwrt distro. There is a typo in your git README. I think it should read rmmod leds-lp5569 and insmod leds-lp5569.ko.

But the main problem is that there is no folder named
/sys/devices/platform/soc/78b6000.i2c/i2c-0/0-0032
nor
/sys/devices/platform/soc/78b6000.i2c/i2c-0/0-0035/

How can I start using the LEDs?

Under Luci LED config there is only the mmc0:: but I think it should not be used since it provides are reboot.

itorK · December 26, 2023, 10:38pm

Folders:
/sys/devices/platform/soc/78b6000.i2c/i2c-0/0-0032/

/sys/devices/platform/soc/78b6000.i2c/i2c-0/0-0035/

are visible after you load modules:

leds_lp55xx_common.ko (module exists in linux kernel -> https://www.kernel.org/doc/html/v6.1/leds/leds-lp55xx.html)
leds-lp5569.ko (compile from my repo and load by insmod)
probably you also need leds-gpio (also exists in linux kernel -> https://www.kernelconfig.io/config_leds_gpio)

This is because the module lp5569 is the driver for the Linux kernel and you will only see these folders when the module is proper loaded by insmod.

BTW. lp5569 is controlled by i2c line with 78b6000 address

Acehigh · December 27, 2023, 7:47pm

Thank you @itorK. I think the problem was that I tried to compile your lp5569 driver together with the master branch openwrt 5.15.137 (23.05.02). It complained about missing dependency for lp55xx common driver. So I had to follow the steps for LED controller integration commited in nbg7815-nss-5.15. Now it works perfect.

psherman · February 3, 2024, 8:26pm

A post was split to a new topic: Need help with extroot on Armor G5 with asvio's latest build

Acehigh · March 1, 2024, 10:01am

Recently I noted a lot of activity regarding NSS (network sub system). It seems there are branches NSS-wifi and NSS (w/o wifi). Can someone shed some light into the benefits and differences?

I tried the latest nss-wifi builts of @asvio and @AgustinLorenzo last weekend but I could not measure a big difference in terms of wifi throughput compared to a non-nss build.

asvio · March 1, 2024, 10:36am

Hey @Acehigh

My nss (only) branch is based on bitthief's early implementations of nss offloading.

The nss-wifi branch has as its starting point the previous branch to which @qosmio's modifications have been added to implement wifi-offloading.

In the case of the nbg7815, the inclusion of support for Wi-Fi offloading results in a firmware that makes its use practically impossible and leaves the router practically blocked and that most of the time it can only be unlocked through the serial port.
It is for this reason that no compilation with such support has yet been made public.

However, it is possible to use the nss-wifi branch to build a firmware with support for nss-offloading but eliminating the part corresponding to wifi. (That's what I'm currently trying and it seems to work perfectly)

For more information you can read from this post onwards.

With respect to the performance of the Wi-Fi network when this implementation is available, I venture that there will not be a significant increase in performance, but what there will be is a decrease in the processor load that will become practically null when currently the intensive use of wifi can even saturate the CPU.

The biggest increase in Wi-Fi performance will come when 160Mhz support is implemented in this device.

sppmaster · March 1, 2024, 11:47am

Additionally now @KONG is officially part of the IPQ807X community and most probably can contribute a lot to it as he has ever done.
Not to forget anyone else here contributing to the development, testing and using our hardware at its highest level.

asvio · March 1, 2024, 12:18pm

I saw @KONG post in Ipq806x NSS build thread.
This device needs someone that want to develope its singularities.

-firstboot wifi problem after flash keeping setting if blockd package is present

-No 160mhz wifi

-Fan implementation in openwrt main branch.

ath11k still has some problem (at least with this device) with ax210 intel wifi client but not so hard as it was some months ago.

KONG · March 2, 2024, 1:06am

Can you explain the problem "firstboot wifi problem".
I have a intel ax201 in one of my laptops.

asvio · March 2, 2024, 8:19am

If the device already has WLAN configured and has the blockd package included, when you update with a new firmware you will initially not have access to the WLAN network (5G and 2.4G). At that moment you have 2 options: either you wifi up the Wi-Fi network through the eth ports after waiting approximately 50 seconds after the boot process is completed (init complete), or you wait those 50 seconds and turn the router off and on again.
Once you have done this you can restart the router as many times as you want and there will be no problems until you decide to update again with a firmware that includes the blockd package.

If I am not mistaken, the problem is derived from the blocking that the blockd package performs on partitions that prevents the ath11k firmware from being loaded for a time and when the firmware is already loaded there is no longer any process waiting to lift the Wifi.

It is not a serious problem, but it is a problem that can make a beginner user nervous who, when updating their router, sees that they cannot initially connect to the Wi-Fi network after the update.

asvio · March 2, 2024, 8:30am

Problem with Intel ax clients are differents
Sometimes, but not always, they decide not to get a valid IP address.
A few months ago this problem occurred very frequently, now it is very rare.

KONG · March 2, 2024, 8:47am

What hostapd package are you using? Openssl variant or mbedtls,wolfssl.
If your are not already using hostapd-openssl, try and check if it makes a difference.

I recall a problem with blockd with other devices, I know I patched it on some of my older builds to skip certain partitions as it would cause error messages when booting up.

My unit is supposed to arrive today. At first I'll attach a 3.5 jack for my https://ftdichip.com/products/ttl-232r-3v3-aj/ , then I can collect all the info and as usual dump flash contents.

asvio · March 2, 2024, 10:09am

I've used the three ones. No difference between the three.
In the end I stayed with mbedtls (not the basic one)

asvio · March 2, 2024, 11:05am

I hope you have better luck than me opening the device. It's pretty hard. I think I broke 3 of the 9-10 tabs it has.
One piece of advice, start at the back, where the Ethernet ports are.

EDIT:
There are not 9-10 but 11 tabs that it has. Look at this post.

KONG · March 2, 2024, 2:41pm

Yes opening is not as easy as on some others, but it worked without breaking any of the latches. I have opened at least 30 different devices before, experience helps.

Acehigh · March 3, 2024, 5:47pm

I did some testing with Intel cards, a Mediathek MT7922 and a iPhone 12 Pro. The Intel AX201 card did not work at all with the latest ath11k driver (WLAN.HK.2.9.0.1-01890). With the older driver 01862 it worked but the throughput was unstable jumping around between 100 and 400 MBit/s (80 MHz channel width). I do some more testing with the other cards but it was definitely better than AX201.

The Intel AX210 performed better than AX201 but also had some ping lags.

I have two NBG7815 routers. One was flashed with different OpenWrt builds. The other one runs on the original Zyxel factory firmware. Surprisingly the factory firmware performs even worse. Depending what you select for the 5 GHz wifi it comes up or not.

asvio · March 3, 2024, 6:25pm

Can you specify which versions?
openwrt 23.05, openwrt/master, nss.....
The latest versions are much more stable than a few months ago.

Are you using wpa3-sae? I had to change to wpa2 due to connection problems.

asvio · March 3, 2024, 8:34pm

An example of ax210 problem with ath11k firmware WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1.

BusyBox v1.36.1 (2024-02-28 07:10:37 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r25382-37bbed6f95
 -----------------------------------------------------
root@NBG7815:/# uname -a
Linux NBG7815 6.1.79 #0 SMP PREEMPT Sun Mar  3 17:07:47 2024 aarch64 GNU/Linux
root@NBG7815:/#

Sun Mar  3 20:18:39 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:39 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:39 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session 7DA2FBF3BF043CA3
Sun Mar  3 20:18:39 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:18:42 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:18:42 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:18:48 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:48 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:48 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:18:48 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:18:50 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:18:50 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:18:51 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:51 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:51 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:18:51 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:18:53 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:18:53 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:18:54 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:55 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:55 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:18:55 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:18:55 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:18:55 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:18:57 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:18:57 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:18:57 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:18:59 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:59 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:18:59 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:18:59 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:18:59 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:01 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:01 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:19:02 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:02 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:02 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:19:02 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:04 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:04 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:04 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:19:04 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:19:06 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:06 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:06 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session A4E63E11C5146DEE
Sun Mar  3 20:19:06 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:07 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:07 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:19:14 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:14 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:14 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:14 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session B16FF3A5367695D3
Sun Mar  3 20:19:14 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:14 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:14 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:19:19 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:19 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:19 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session 4CC7541F4CFB1894
Sun Mar  3 20:19:19 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:21 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:21 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx
Sun Mar  3 20:19:24 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: authenticated
Sun Mar  3 20:19:24 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx IEEE 802.11: associated (aid 1)
Sun Mar  3 20:19:24 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx RADIUS: starting accounting session 5E94E25DCFEF4314
Sun Mar  3 20:19:24 2024 daemon.info hostapd: phy0-ap0: STA 70:cd:0d:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sun Mar  3 20:19:27 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx
Sun Mar  3 20:19:27 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.10 70:cd:0d:xx:xx:xx NOTEBOOK-xxxxxx

This log is with wpad-mbedtls package and wpa2-psk encryption.

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/c000000.wifi'
	option band '5g'
	option htmode 'HE80'
	option cell_density '0'
	option country 'ES'
	option channel '36'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option mode 'ap'
	option ssid 'my-wlan'
	option encryption 'psk2+ccmp'
	option key 'my-password'
	option network 'lan'
	option macaddr '00:03:7F:xx:xx:xx'
	option ieee80211r '1'
	option reassociation_deadline '20000'
	option ft_over_ds '0'
	option bss_transition '1'
	option ieee80211k '1'
	option ft_psk_generate_local '1'

Acehigh · March 4, 2024, 8:24am

I used several versions but none 23.05 (kernel 5.15.xxx). The last version in my test was the openwrt official main branch from 2024-02-24. Yesterday evening I figured out that the connection problem was somehow related to my config which I always took over when flashing a different version. I flashed the router again with the version mentioned above but this time starting from scratch. The Intel AX201 connected this time without issues. The Mediathek was also connection w/o issues. I used WPA2-PSK and WPA2-WPA3 SAE mixed. Both w/o issues. I use wpad-mbedtls (full) package

I also will test the Intel AX210 comparing my log with the one from @asvio.

I can post my full wifi config after testing.