kmod-mwlwifi 5.15.98+2020-02-06-a2fd00bb-3 » 5.15.102+2020-02-06-a2fd00bb-3
Seems the oldest... this is my poor opinion, only kernel version is changed... driver is the same
2020-02-06-a2fd00bb-3
1 Like
Sorry typo as my other ap's are running 22.03.3
So to go from openwrt 22.03.2 to divested build I would need to reboot the router into the stock linksys firmware on partition 0. Then flash the divested sysupgrade image over the installed openwrt 22.03.2 on partition 1?
The router will then reboot into partition 1 which should be the divested build.
Have I understood the process correctly?
And in future, I would always flash from the stock linksys page to maintain the stock firmware on partition 0.
Cheers
Spart
Do you really need the stock OEM firmware anymore. Why not sysupgrade from current 22.03.2 to divested build on the alternate partition
Yes.
Yes, I like to have the stock firmware so that at any time I can simply reboot to stock and reflash whatever build I want to try out from within the gui's without having to resort to CLI ssh return to stock.
It looks like the divested build is still a work in progress and the wifi driver issues are in a bit of flux. The latest fixes are not in the openwrt 22.03.x builds and there are various posts above that suggest that all is still not well.
In the divested world with the WRT3200ACm is the 3rd radio working and the wifi dropout issues now resolved?
Cheers
It looks like the divested build is still a work in progress and the wifi driver issues are in a bit of flux
In the divested world with the WRT3200ACm is the 3rd radio working and the wifi dropout issues now resolved?
There is no development here, these are just tweaked configs with a few small patches on top.
These devices are dead, broken, end of life, and insecure.
No one is likely to change that.
1 Like
But you still make build for those devices, so I guess it is what you are using?
WRT32X works great here. 
3 Likes
Are you back on Divested now? I just jumped from 22.03.2 to SNAPSHOT (r22400), and built the image with the list of packages you provided in your earlier post. Lack of USB-storage support being the reason I moved away from Divested in the first place..
However in the latest Master there does not seem to be a package for "kmod-ata-marvell-sata". Is this not supported anymore? Not a big issue, as my HDD is connected by USB, but would be good to understand if it's removed, unnecessary or replaced by some other package.
Good to be on 5.15 anyway - seems to be working fine so far..
Thanks!
1 Like
You're right I removed the marvell-sata from the package list after I posted that, it's not needed on our targets. Using USB3.0 and Samba is a big reason I build from master snapshots, but I've looked at Divested patches and sorta do a hybrid of some of his interesting changes.
1 Like
What are the divested patches that intrigue you? 
Also, are the latest changes to the mwlwifi driver (from Kalos) now included in master, or divested, or would one somehow have to implement these oneself?
1 Like
I use patches 0002, 0003, 0004, 0006, 0009, 0010 running WRT1900ACS as applicable. These speak to the thread title.
I also peruse the CHANGELOG.txt to keep an eye on what’s going on.
It’s broken, abandoned, and will never be fixed. Add a decent wifi AP and you add more life to your box, and a happier experience.
2 Likes
@ghoffman this pr looks to address the wrt32x sysupgrade settings issue.
Hopefully we will get a fix soon enough in the master 
1 Like
I'd second @RuralRoots advice and get an external AP but I guess it depends on your use case.
As for the builds I'd also recommend following the videos on the divested wiki and having a go at building your own firmware. It's not that hard and you can adapt it to your needs.
3 Likes
Thanks for the replies. I've actually been a pretty happy user of the built in wi-fi since the times of david's builds, with some ups and downs, but overall stability had been enough.
Of course times have changed, and now quite a few devices on my network already support wifi6. So maybe it's time to get a dedicated AP sooner than later too. Still happy to see that our devices are definitely not abandoned by the community, as they are quite capable on most fronts.
1 Like
@mrtomtom -
great pickup - i hope this is the fix!!!
thanks
1 Like
Absolutely. Unless you need gb internet with QoS these units are fine.
I recently got a Zyxel NWA50AX. There is an openwrt package for it. Been quite happy with it so far.
Today's build: https://divested.dev/unofficial-openwrt-builds/mvebu-linksys/20230330-00/
Has fixes for the recent Wi-Fi security issue:
- https://github.com/vanhoefm/macstealer
- https://github.com/openwrt/openwrt/commit/d54c91bd9ab3c54ee06923eafbd67047816a37e4
And a fix for the WRT32X sysupgrade issue: https://github.com/openwrt/openwrt/pull/11692
It also drops the OpenSSL related reverts (and thereby updates to 3.0.x) that I did due to compile failure, the solution was to install on host: perl-IPC-Cmd
6 Likes
I still have an ACS with 19.07 lying around which I want to start using again. From reading up on things it would seem I should probably upgrade to 21.02 first, without keeping my config, then rebuild from scratch. Which shouldn't be too hard as I think I still have the UCI commands for said config somewhere.
Having done that I should be using DSA.
At this point it gets a bit strange. Apparently I cannot upgrade to 22.03 because it has that broken switch issue. In that thread somebody pointed to these builds as a way to stay current. But from the changelogs I can not make out if these builds don't have said issue.
So, am I correct in going from vanilla 19.07 to vanilla 21.02 and then from vanilla 21.02 to your build, if I want an up to date system without that issue? Anything I should know?
I apologize if this has been asked and answered, I read all the changelogs, but 1057 posts in this thread was a bit much.
Hi,
Yes with regards the upgrade to 21 first. Then onto a divested build.
The switch issue has mostly been fixed as of kernel 5.15 (it no longer acts as a hub but a proper switch). There is still some issue with vlans over the wifi not being tagged correctly. So you may want to look into that depending on your use case.
Can't think of anything else you should know. Just have fun playing
3 Likes
VLANs and creating a separate subnet for my WiFi clients are things I have only imagined so far. I can do it on a Cisco, but OpenWRT has eluded me thus far.
The only complex configuration I have on the router would be an OpenVPN tunnel with the VPNBypass package. If I can make that all work again then I'm happy.
Testing it on an even older WNDR3800 now. Then on to the ACS. Good thing it has dual-boot, I can switch back to the other partition when needed.
Thank you for the reply!
1 Like