Any results what seems the most stable? I am getting messages that 8.9.0.0.83 breaks from time to time, just list 8.9.0.0.88 and 8.9.0.0.89. I am hesitant to use 8.9.1.0.0 exactly because of the TI warning.
1 Like
Dear all, i know this is very old issue, but i ended up on this thread when desperately trying to figure out why did not wlcore / wl18xx accesspoint work reliably. So to write to fellow googlers how this ended happily for me:
The issue with driver was reliably re-produced by this:
- start accesspoint - all is fine.
- drop wifi connection, by removing antenna of the router. After say 30s - replug the antenna
- observe the clients reconnect
Before – using 8.9.0.0.83 firmware – i could repeat the plug-unplug for few times, say 2.5 times on average before weird issues started popping up; ping did not go through on random host and so. Sometimes there was “unable to flush” messages and sometimes nothing. Sometimes the dump.
I was able to get this issue fixed, by patching my kernel driver from “wilink8-wlan/build-utilites - WiLink8 WLAN development project - WiLink8 build scripts.” - “patches/kernel_patches/4.19.38”. And upgrading the firmware then to the latest (8.9.1.0.2).
The new firmware (8.9.1.0.2) did not work with the unpatched kernel driver (got kernel message - too old firmware).
Thanks for the message. Can you describe exactly what you were doing?
Did you recompile the kernel from source?
How did you patch?
I have a project with kernel 4.19.94-ti-r73, but I can not seem to find any of the stuff that can be used for that kernel.
Kind regards,
Johan Henselmans
I now notice i did not open up too much the background; the system i was working with, was custom “host” board with some SMARC - computing unit. The linux in there was buildroot 2019.02.11 – due lack of maintanance on project.
The kernel was mainstream kernel downloaded linux.org - and then patched with the patches on the my previous post. The hostapd / wpa_supplicant were both unpatched (=they came as they came from the buildroot – buildroot does have patches though).
I also changed the kernel config according to the some “check kernel config” script from the WiLink8 build-utilities.
- So yes; i did recompile the kernel.
- I patched by unzipping the kernel source, then applying the patches one by one. Not sure were there any conflicts, but certainly not any “shit, how is this suppose to be done”.
- after patching, recompiling and redeploying kernel with new fw-blobs
Good luck,
Pauli
Robert, it seems that Pauli (supa5000 has found the answer. Would it be possible to incorporate the patches, so that we can all enjoy the latest version of the firmware and the driver?
Kind Regards,
Johan Henselmans.