How about firmware crashes, that currently causes new memory allocation without freeing previously allocated memory?
In theory yes, but how many successful recoveries have you seen?
The driver was supposed to clean up the memory even now after a crash
Its not gonna hurt to backport it as well as other dozen or so patches
1 Like
Its a firmware issue that appears to have been resolved in a FW version that is not yet public
Thanks for the answer, I will use the 40 MHz band for now ...
What's the current state of support? What works, what doesn't?
Where can I find a guide with the steps needed to build and flash whatever builds are supported?
In this very thread, you'll know more after reading the last 7079 posts - afterwards the ax9000/ qhora 301w threads might fill in the blanks.
2 Likes
Pretty much everything works except offloading. And even part of offloading works
Well you have to search for it. I just finished working on it 
3 Likes
any timeframe on when it will be public/available in openwrt (no pressure, just checking for a vague ETA so I can plan ahead)
You took the wrong repo ahahahah anyway just read the commit about that... Also I will be busy in the next week so rip pppoe for now... (Hope community can do the rest)
Must be this one:
https://github.com/Ansuel/openwrt/tree/ipq807x-5.15-wifi-offload
(read the last commit for additional info)
The one you posted is the latest work, but reading last commit is still WIP.
Thanks @Ansuel
They are both WIP so... 
1 Like
Stupid question.... I'm trying to flash my ax3600 (currently i always used ramfs)
Hit any key to stop autoboot: 0
trigger button release!
boot from rootfs 1
miwifi: check crash in rmem !
ubi0: attaching mtd1
ubi0: scanning is finished
UBI init error 28
Erasing NAND...
Erasing at 0x6e0000 -- 100% complete.
Writing to NAND... OK
resetting ...
What could be the reason? An image from robi repo works correctly tho...
this is both from a sysupgrade with an already installed image or a ramfs image using ubiformat...
I think I've read Robi saying we need ZSTD for ramfs:
Target_Images->ramdisk->Compression->ZSTD
problem is that a flashed image build by me doesn't load. custom ramfs image loads correctly.
Wonder if the problem is the size? Can't be since the buildroot should alert me of the problem...
1 Like
Yep think problem is me trying to use 30mb image... no idea why buildroot doesn't say image is too big?
(and now i understand robi with the problem of using smem... @robimarko any hint on a fixed partition solution to increase size?)
We don't have an image size defined in the generic.mk, I had this problem once with the AX9000 and an "oversized" image, but for me it failed already during the sysupgrade with an ubi error.
But 30MB doesn't sound to large...can you ubiattach that partition if booting from ramfs?
the flash is done from ramfs so nothing is mounted...
root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 6.8M 6.8M 0 100% /rom
tmpfs 203.8M 84.0K 203.7M 0% /tmp
/dev/ubi0_2 15.0M 48.0K 14.2M 0% /overlay
overlayfs:/overlay 15.0M 48.0K 14.2M 0% /
tmpfs 512.0K 0 512.0K 0% /dev
this is output with the ramfs image flashed
can you do an ubiattach for that partiton that is failing in u-boot to mount?