The 885 and 890 are more related to each other, they use the BCM4709 CPU and BCM4366 WiFi chipset.
The 885 is related to the 895, not the 890.
The 890 has 43602, similar to the R8000 and Asus RT-AC3200.
Thanks for clarifying - I wonder what the difference between the BCM43602 WiFi Chipset (DIR-890L) and the BCM4360 WiFi Chipset (DIR-880L) is that causes the DD-WRT to brick the 880L. They are both Wireless AC 3x3 chipsets. I know the routers have different CPUs too, so that may make a difference.
Finally had some time and I installed the factory to DD-WRT(the latest) and then attempted to install Quarks ddwrt-webflash-dir868-880-r33345b-patched. After finishing the counter was done but I was still seeing the warning so I gave it another good 15 minutes but never came back. I just went in and put again the factory to dd-wrt and I stopped there.
Quark can touch on this more once he sees what went on here, but I believe his builds are meant to work on a fully upgraded DD-WRT build. In other words, after upgrading with factory-to-ddwrt and then webflash, you can then go right to his. However, you only put the factory-to-ddwrt on, and well, going to Quarks right after that could cause a problem. Those who have his working (at least that I know of) never did it that way. I was on a full version of the 30432 for my 880, put Quarks on (ddwrt-webflash-dir868-880-r33345a-patched.bin) and it works great. He has some newer builds too, it's up to "C" now.
However, if you have 33257 working just fine, well then you're good to go. That build virtually has all the much needed updates and toys that have been added recently. Just curious, are you using SSH on that? Because that had seemed to be the major culprit with the bricking problem. If it's off, turn it on and see what happens (if you want to, not sure if SSH is something you use much if at all).
shayne85 wrote:
I wonder what the difference between the BCM43602 WiFi Chipset (DIR-890L) and the BCM4360 WiFi Chipset (DIR-880L) is that causes the DD-WRT to brick the 880L.
Yeah, well, that's like, been fixed 2 weeks ago. Heck, even 33215 (8/25/17 one of the best stable builds recently) works perfectly fine for some 880 users that I am aware of. Then there is the fix by Quark (which I am using right this second on my 880). Several 868 users confirmed 33215 and also Quark's build works for them. Homie above said 33257 works fine for him. There are options available now (confirmed working ones). It's not a dire situation anymore.
My builds can be used once your router is running dd-wrt. Doesn't matter whether it's the webflash variant or the factory-to-ddwrt variant. The build image I've uploaded is mainly targeted toward the 868 and 880 models. If the 885/890 works with the latest builds you should go for it as mine is using older Broadcom wireless drivers. Newer drivers crashed the 868 and 880.
Do use the web GUI to reset settings to default and reconfigure the router again. Don't restore from previous saved config files, especially if you made a big jump in versions.
However, if you have 33257 working just fine, well then you're good to go. That build virtually has all the much needed updates and toys that have been added recently. Just curious, are you using SSH on that? Because that had seemed to be the major culprit with the bricking problem. If it's off, turn it on and see what happens (if you want to, not sure if SSH is something you use much if at all).
All I need is a stable system and so far I am happy with it. Samba works fine with my USB3 drive, add blocker works, perhaps if there were more choices of host files.
Thank you for all the info and support.
dg.
Edit: I did turn on SSHd and it works fine without any issues.
Edit: I did turn on SSHd and it works fine without any issues.
Yep, not that surprising It never seemed to be much an issue on 885s and higher. It's more obvious than ever now that the real problem which had been taking place with the 868/880 was the newer Broadcom drivers which Quark mentioned. SSH, Sputnik and a few other things being used/enabled apparently had some conflict with those models when using later builds with the newer drivers.
I noticed that memory utilization fluctuates between 84% and 90%. I assume that it is due to the samba service. Does DD-WRT have a nfs module/service? There are some old articles but nothing current or in the Wiki.
Posted: Thu May 31, 2018 3:16 Post subject: Re: Your DIR885L is it a rev A1 or Rev A2
Iccntsafe wrote:
Your DIR-885L is it a Rev A1 or A2.
I have the A2 and am unable to get any factory to DD-WRT to load it just reports an error and backs out.
OP's first post already mentioned he's using rev. A2.
Are you using the cfe miniweb recovery to flash the factory to ddwrt initial build? Which build did you use? _________________
Netgear R7800 kongpro 19.07 20190919 || Netgear R7000 36070M kongac (Client Bridge=5GHz, AP=2.4GHz with bridged VAP)
Linksys WRT32X davidc502 OpenWrt || Linksys WRT1200ACv1 Gargoyle 1.11.x
Linksys WRT1900ACSv2 dd-wrt 39956
Posted: Thu May 31, 2018 15:52 Post subject: Re: Your DIR885L is it a rev A1 or Rev A2
Ah-Pin-Kor wrote:
Iccntsafe wrote:
Your DIR-885L is it a Rev A1 or A2.
I have the A2 and am unable to get any factory to DD-WRT to load it just reports an error and backs out.
OP's first post already mentioned he's using rev. A2.
Are you using the cfe miniweb recovery to flash the factory to ddwrt initial build? Which build did you use?
I use the web interface in the Router menu, I tried the Kong bin first as I have had good results with other routers in the past using this.
Posted: Thu May 31, 2018 17:37 Post subject: Re: Your DIR885L is it a rev A1 or Rev A2
Iccntsafe wrote:
Ah-Pin-Kor wrote:
Iccntsafe wrote:
Your DIR-885L is it a Rev A1 or A2.
I have the A2 and am unable to get any factory to DD-WRT to load it just reports an error and backs out.
OP's first post already mentioned he's using rev. A2.
Are you using the cfe miniweb recovery to flash the factory to ddwrt initial build? Which build did you use?
I use the web interface in the Router menu, I tried the Kong bin first as I have had good results with other routers in the past using this.
Posted: Wed May 08, 2019 22:50 Post subject: I have D-Link 885L - HW version A2
When I review the router database on dd-wrt.com, it shows A1 as being supported, but not A2.
I purchased this router on eBay and they didn't specify the HW version (I assumed there was only one, A1.)
However, what I received in the mail was DIR-885L A2.
Does anyone know if I can use a current version of dd-wrt meant for HW version A1 on my A2 version router? I'd prefer not to brick it after just receiving it in the mail.
If it works, I'm planning on flashing from OEM firmware V. 1.20 to DD-WRT V3.0 [Beta] Build 37305 which was released on 10-10-2018 and will use the factory-to-ddwrt.bin file.
Posted: Thu May 09, 2019 3:29 Post subject: Re: I have D-Link 885L - HW version A2
lindercannon wrote:
Does anyone know if I can use a current version of dd-wrt meant for HW version A1 on my A2 version router? I'd prefer not to brick it after just receiving it in the mail.
If it works, I'm planning on flashing from OEM firmware V. 1.20 to DD-WRT V3.0 [Beta] Build 37305 which was released on 10-10-2018 and will use the factory-to-ddwrt.bin file.
1. The OP of this thread has a hw A2 and he had it running dd-wrt. I flashed my A1 to dd-wrt using the cfe recovery webpage and not through the stock firmware webui itself.
2. Once you have flashed the factory-to-ddwrt, flash Kong's R8000 build. It supports DIR-885L. _________________
Netgear R7800 kongpro 19.07 20190919 || Netgear R7000 36070M kongac (Client Bridge=5GHz, AP=2.4GHz with bridged VAP)
Linksys WRT32X davidc502 OpenWrt || Linksys WRT1200ACv1 Gargoyle 1.11.x
Linksys WRT1900ACSv2 dd-wrt 39956
As for the h/w differences, I suspect there is a stepping change to the wifi chip 4366. From the dlink forums, there is a post for the 895L (the bigger brother of the 885L, same chips, just extra 5GHz band):
http://forums.dlink.com/index.php?topic=74718.0
===info below for 895L===
Hardware change from A2 to A3:
1. Real panel wording changed from “Router/Extender" to “Router/AP", due to no full extender mode support from Broadcom.
2. Firmware is compatible with A1/A2, starting from v1.11.
Hardware change from A1 to A2:
1. BRCM internal silence drop in 4366 RF chipset from B1 to C0
2. Firmware backward compatible, starting from v1.11
3. FCC/CE Certification ID remain unchanged.
4. Complies with ErP Lot26: 2017
Rev A1 - A4 all use 1.4GHz CPU.
===end info for 895L====
EDIT1: see post below from openwrt forum:
https://forum.openwrt.org/t/d-link-885l-r-a2/6177/19 _________________
Netgear R7800 kongpro 19.07 20190919 || Netgear R7000 36070M kongac (Client Bridge=5GHz, AP=2.4GHz with bridged VAP)
Linksys WRT32X davidc502 OpenWrt || Linksys WRT1200ACv1 Gargoyle 1.11.x
Linksys WRT1900ACSv2 dd-wrt 39956
Last edited by Ah-Pin-Kor on Sat May 11, 2019 0:19; edited 1 time in total
It never seemed to be much an issue on 885s and higher. It's more obvious than ever now that the real problem which had been taking place with the 868/880 was the newer Broadcom drivers which Quark mentioned. SSH, Sputnik and a few other things being used/enabled apparently had some conflict with those models when using later builds with the newer drivers.
