I wouldnt count on QCA with error messages, they commonly "forget" to check return values
Will analyze the code a bit and check if I'm missing an additional change... And also compare with qsdk 12
Hi everyone!
Just a quick question, don't want to interrupt your hard work, am I supposed to be able to compile nss-crypto? from what I've read here yes, but it requires nss-drv, which is not compiling here.
I have the build log for nss-drv if needed.
@robimarko OK it could be that the problem is using the 512 mem profile... will try to port another patch and see what happen (should also reduce memory usage in general)
3 Likes
I'm experiencing the exact? same thing.
My setup:
AX3600 - Dumb AP
I need to unplug the Ethernet cable and sometimes even change ports, until the computer gets assigned an IP.
Wireless working flawlessly though.
Any ideas?
1 Like
Hm, why should the 512MB profile matter?
Can this change be made the next time you rebase the branch, please? I think is a fast change and will help a lot updating APs that are connected in mesh. Now they lost the connection to the mesh when upgrading each time.
2 Likes
If I remember, then its not an issue
1 Like
don't know in the patch they do something with the rings but i now think it's not related... i still have to test the dma thing
All they can be doing with rings is setting their size, and we are not doing even that.
512MB patch only sets the FW mode and peer/vdev limits
Excuse me, I am trying to play with nss-cfi stuff, when I build initramfs image the router boots normal but when the size is bigger ¿more than 16MB? It cannot boot the kernel.
IPQ807x# bootm
## Loading kernel from FIT Image at 44000000 ...
Using 'config@ac04' configuration
Trying 'kernel-1' kernel subimage
Description: ARM64 OpenWrt Linux-5.15.33
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x440000e8
Data Size: 17149622 Bytes = 16.4 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x41000000
Entry Point: 0x41000000
Hash algo: crc32
Hash value: 4e04c2df
Hash algo: sha1
Hash value: 5f323ba8f67d74f410338cb181de865ab0234419
Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading fdt from FIT Image at 44000000 ...
Using 'config@ac04' configuration
Trying 'fdt-1' fdt subimage
Description: ARM64 OpenWrt xiaomi_ax3600 device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x4505b0e0
Data Size: 42641 Bytes = 41.6 KiB
Architecture: AArch64
Hash algo: crc32
Hash value: b9bb4b81
Hash algo: sha1
Hash value: 4b227edffeb67584a81c27e91f8eea8f2c951987
Verifying Hash Integrity ... crc32+ sha1+ OK
Booting using the fdt blob at 0x4505b0e0
Uncompressing Kernel Image ... OK
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.3.1-00147
S - IMAGE_VARIANT_STRING=HAACANAAA
S - OEM_IMAGE_VERSION_STRING=xiaoyang-gv
S - Boot Config, 0x000002e5
B - 201 - PBL, Start
B - 2735 - bootable_media_detect_entry, Start
B - 3443 - bootable_media_detect_success, Start
After of Uncompressing Kernel Image ... OK it goes to boot loop.
*Good boot log:
...
Uncompressing Kernel Image ... OK
Loading Device Tree to 4a3f2000, end 4a3ff680 ... OK
Using machid 0x8010010 from environment
Starting kernel ...
Why sometimes it cannot load de Device Tree after uncompress the kernel image?
Use ZSTD compression for initramfs
1 Like
I did some reading, it looks like the 10k-firmware-qca9887-ct (10.1-ct-87-__fW-022-ecad3248) does not support the rawmode.
I tried to install the 10k-firmware-qca9887 with LUCI. The system didn't find the hardware for radio0.
Giving up 
1 Like
After 4 days and an hour of work, it happened that WiFi was turned off again, and the router became unavailable. I am attaching the kernel log. Does anyone have any guess why this happened? This didn't happen before.
I don't know who that is but the official Snapshots are working great for me and others...
https://downloads.openwrt.org/releases/22.03-SNAPSHOT/targets/mediatek/mt7622/
Thank you for your sincere desire to help me. For the past 5 routers I have been buying them, and something is wrong with them. I'm just tired. Every time something is wrong. I think i will buy mini pc with many rj45 ports and will use xiaomi ac2350 only as dumb ap.
Or just spit on everything.
First there was the Archer C7, which lost Ethernet ports and then stopped working altogether. Then there was Lenovo newifi3 d2, which rebooted as soon as I approached it, glitches with the wifi driver. Then there was Armor Z2, which just lost internet with connected devices. And there were a few more, but I almost immediately took them to the store due to various reasons. Just some incredible bad luck to me 
My nickname perfectly reflects what I think. I'm an Openwrt fan, but it frustrates me how many attempts I've made and they all fail.
I'm going to cry.
hehe I understand, I've only had good experience with the few devices I used OpenWrt with, DIR-885L, R7800 and now the Xiaomi AX3200/Redmi AX6S...fingers crossed it stays this way. 
If I find it on the secondary market for a good price, I will definitely be disappointed (crossed out) try it