Pre-compiled updated mwlwifi drivers for stable releases

@eduperez Thank you for the updated driver/firmware package. However, unfortunately it is failing to install on the latest 17.01.4 release.

Installing kmod-mwlwifi (4.4.93+ to root...
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-mwlwifi:
 * 	kernel (= 4.4.93-1-9f18c9c8eae6a4bfe17f419b398e25cd) * 
 * opkg_install_cmd: Cannot install package kmod-mwlwifi.
1 Like

@WildByDesign Looks like I did not update my build environment properly after all... thanks for reporting, I will try to fix it tonight!

I have just taken down the package for 17.01.4, as it was compiled against the HEAD version instead. I have already fixed my build environment to point it to the 17.01.4, but now it is failing because of some files it cannot download from somewhere. Will have a look at it tomorrow.

Package for 17.01.4 is up again at:

I still have not upgrade my device, and I have not been able to test the package; but this time I am pretty confident it will at least install correctly.

Thanks for these, I've just upgraded from OpenWRT 15.05.1 to LEDE 17.01.4 and tried flashing your new release. opkg thinks its an older version...

# opkg install kmod-mwlwifi_4. 
Not downgrading package kmod-mwlwifi on root from 4.4.92+ to 4.4.92+

So the --force-reinstall option others indicate they've used is definitely required I think.

@slackline Yes, I am afraid that is expected behaviour: LEDE uses a naming scheme using "driver_version-commit_date" that I found confusing; my packages are named as "driver_version-driver_release-commit_id" instead, and sometimes opkg gets confused about which one is newer than the other. As these packages are considered "experimental" and are expected to be installed manually, I think this is a just little nuisance.

Wasn't a complaint at all, hopefully highlighting it as a requirement should others come looking for answers.

Drivers have installed fine and I've restarted the interfaces but not rebooted (unsure if the modules get unloaded), network is in use at present so can't reboot just yet.

Thanks for your effort building and maintaining these.

@eduperez Latest package release with latest driver and firmware working great on 17.01.4. Thank you, sir.

Thanks a lot @eduperez!

I installed LEDE 17.01.4 on my WRT1200ACv2 and 5GHz wifi did not work, but with your update it does now. Will need some days for stability testing.

For reference, I did this:

wget --no-check-certificate #uname -a said kernel is 4.4.92
opkg install --force-reinstall kmod-mwlwifi_4. 

I installed the latest snapshot and have this driver.
kmod-mwlwifi - 4.9.58+

Is it the latest one or should I install one of following two?



@yrh1 My builds can installed only on stable releases, you cannot install them on snapshot releases.

1 Like

Thanks for the info. I will go back to 17.01.4 and then install.

New release available at

  • Make sure bandwith is initialized.

Thank you for this update. Working great so far. I seem to find that the LEDE Stable branch 17.01.x builds have far less issues on the WRT3200ACM compared to many of the recent trunk builds. So I am thankful that you take the time to keep mwlwifi current on the stable branch for the community.

I'm glad to know people find these packages useful!

Just another little update at

  • Added debugfs file tx_amsdu to control tx amsdu

This was committed about an hour ago, so I have not had time to test it thoroughly; take it with care.

1 Like

This was fast...

  • Added MDE to beacon

These updates are targeted to fix specific bugs, that have been reported at the official repo, so I am releasing the packages as fast as they appear, instead of trying them myself first.

@eduperez Great stuff, thank you. You are keeping up just as fast, if not faster, in comparison to community trunk builds with regard to mwlwifi driver/firmware related package. This is very much appreciated.

I have been running your latest "760f7bf" for approx. 20 minutes thus far and so far it's working well without issue. It looks as though yuhhaurlin may be 'going on a bug fixing tear' right now which is great to see.

EDIT: Up just over 7 hours now and still zero issues with devices disassociating and such. Good stuff!

Hopefully that finally fixes the 802.11r functionality.

Another bug fixed:

1 Like