Posted: Sun Jul 31, 2022 17:19 Post subject: Has wireless improved with the WRT3200ACM?
I've had problems with the wireless on this device for years, and it's always been attributed to some kind of hardware fault. I've run DD-WRT on it for years and also tried OpenWRT without any improvement. For some time, I hobbled along by plugging a second router into it to at least get some semblance of wireless.
I finally got fed up and replaced it entirely with a Netgear R7000 and all of my wireless problems went away. It's of a similar vintage and has less features on paper than the WRT3200ACM, but it "just works".
Now that I'm no longer using it for anything important on the network, does anyone know if there is any way to modify the device to fix the problem? Has this issue ever been addressed or is the consensus to junk it?
I see that there are a lot of "firmware" updates for this device:
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sun Jul 31, 2022 17:24 Post subject:
There have been driver updates and patches more recently for Marvell that have improved things. The key factor is using configurations that the driver supports vs. what the driver does not support. If you're that fed up with it, I am always open to donated hardware for testing or deployment. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I have a couple of questions. Are these updates for DD-WRT or the OEM firmware? Is the wireless more stable with the OEM firmware or the same?
I've read that the issue is with the hardware, something about Marvell, and can't be solved with software. But because the problem is intermittent and the router needs to be left on for symptoms to develop, I've found that it's very hard to test for. It's also frustrating that this has been an ongoing problem, despite the WRT3200ACM being several years old now.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sun Jul 31, 2022 18:59 Post subject:
If you read that it was the hardware, then you misread. It has to do with driver support and the acquisition of Marvell by NXP. Despite this, BrainSlayer and nbd (OpenWRT, madwifi, mac80211, mt76) have made some progress in making things better. You must've stopped reading somewhere along the way in the past year or so. I believe that one of the firmware updates for the wifi hardware chipsets was recent, but don't quote me on status of which one is in use. There's only been one Marvell device get any love from Linksys proper with a stock firmware update that I know of.
I do recall when I first got the WRT1900acV1 routers, the wifis latency was not great.
But a few years later when I tested again with the newest dd-wrt build, WiFi Latency WAYYY better than it was before. Even better than stock OEM firwmare.
just make sure you get the LATEST build and not some firmware from the router database.
Time to live in the now and test to your heart's content and figure out your optimal wifi settings. OR, my offer still stands if you'd rather give someone else the burden _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Linksys firmware support mostly ended in 2018, but early 2020 a few surprising but final firmware updates.
Open source driver mwlwifi dev ended about the same time, or maybe better to say slowed down to trickle.
TLDR in early December 2020 a mac80211 patch by nbd fixed a major issue plaguing Marvell after r44048.
Eight months later, there are too many updates overall to mention so at this point try current build r49677.
During webUI Firmware Upgrade, or webflash, leave dropdown option alone, keep "Do not Reset" selected.
Remember to avoid old configuration on current builds, nvram erase && rebootafter a successful upgrade.
Or, use Factory Defaults from webUI Administration to avoid a command-line interface (CLI) Telnet or SSH.