@eduperez Thank you for these latest packages. So far I've got the latest "20180716" build of the driver, released today, running on the WRT3200ACM and it's working fantastic thus far.
hi, it is normal after install
I have these log
Sun Jul 22 20:43:57 2018 kern.info kernel: [ 277.808292] ieee80211 phy0: Data written to /tmp/BF_MIMO_Ctrl_Field_Output.txt
Sun Jul 22 20:43:58 2018 kern.info kernel: [ 277.889830] ieee80211 phy0: Data written to /tmp/BF_MIMO_Ctrl_Field_Output.txt
Sun Jul 22 20:43:58 2018 kern.info kernel: [ 277.979630] ieee80211 phy0: Data written to /tmp/BF_MIMO_Ctrl_Field_Output.txt
Sun Jul 22 20:43:58 2018 kern.info kernel: [ 278.049808] ieee80211 phy0: Data written to /tmp/BF_MIMO_Ctrl_Field_Output.txt
Thanks for the helps
I get the same unusual log entries as @fredlubrano when I connect with my SurfacePro 4 on the 5 GHz band. A large number of such entries are generated.
I am on Davidc502 latest build (20170714) for WRT3200ACM - Lede SNAPSHOT r7493-b123921a92 / LuCI Master (git-18.194.53747-b38306d).
BF_MIMO_Ctrl_Field_Output.txt" file creation was added at commit d9daa1d (added code to support BF for MU-MIMO), and seems to be normal, or perhaps just some debugging file.
The excessive "
Data written to /tmp/BF_MIMO_Ctrl_Field_Output.txt" message has been fixed on commit "
d9c8c59". Files available at 10.3.8.0-20180716-d9c8c59.
Not sure if this has been asked but how do I add the latest mwlwifi drivers to the OpenWRT builder if I'm compiling my own firmware?
Just update the "
PKG_SOURCE_VERSION" variable at "
package/kernel/mwlwifi/Makefile" to the commit that you want to include.
I've find the file and found the line that you suggested. Mind me asking a silly question but where do I find the latest package version number to paste in place of the one that's there already?
The commit hash from the upstream repo.
Thank you. I'll make that ammend in the makefile and compile it and let you know how it goes.
I have seen some posts on this topic but just to make sure there is no way to update the mwlwifi software , I have the following question:
I am on Davidc502 latest build "Lede SNAPSHOT r7493-b123921a92 / LuCI Master (git-18.194.53747-b38306d)" and get the following dependency error when I try to update to the latest kmod-mwlwifi_4.4.140+10.3.8.0-20180716-d9c8c59-9326.
Is there any way to ignore the dependencies and install or should I not do that?
root@ROUTER:~# opkg install --force-downgrade /tmp/kmod-mwlwifi_4.4.140+10.3.8.0-20180716-d9c8c59-9326_arm_cortex-a9_vfpv3.ipk Downgrading kmod-mwlwifi on root from 4.14.54+10.3.8.0-20180615-1 to 4.4.140+10.3.8.0-20180716-d9c8c59-9326... Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-mwlwifi: * kernel (= 4.4.140-1-78acdb0e5133ba67c91f7694e305d1e7) * * opkg_install_cmd: Cannot install package kmod-mwlwifi.
No, do not force the installation. These packages contain kernel modules, that must be used exclusively for a specific kernel version and configuration. You might end bricking your device if you do that.
You can either update to a newer davidc502's build (I think the keeps his builds updated regularly), or install an official release and then update the drivers using my packages.
Thanks for the confirmation.
I confirme the version 10.3.8.0-20180716 resolv "BF_MIMO_Ctrl_Field_Output.txt".
Thanks you for the helps.
I have just built the latest version for 18.06.0; files are available at https://github.com/eduperez/mwlwifi_LEDE/releases/tag/d9c8c59.
@eduperez Thank you. I had already installed your previous build of (d9c8c59) since it was built with the same kernel and everything is working great. In my case, would there be any benefit in installing build -2 on my system?
Source code for mwlwifi on builds 1 and 2 is exactly the same, I just rebuilt them over an updated version of OpenWrt (and had to use a different suffix precisely because kernel version was the same). However, if you could install build 1 over 18.06.0, then the packages are perfectly compatible, and you do not need to install build 2 at all.
Thanks for reporting!
You're welcome. Thank you for confirming.
Excellent thanks. Couple comments:
Is it safe to say the WRT32X uses the same driver as the WRT3200ACM? Could you please update your page with the description to show that router name too?
Also with 18.06 we call it OpenWrt again, not LEDE!
Yes, now that 18.06 has official support for the WRT32X, the device can also use my packages.
I have just updated the release page, thanks!