Alternate link: DD-WRT website Note: for wget (or curl) with CLI flash (`write {f/w} linux`), change the https to http, use `curl -k {link} -o {file}`, or ftp
Important: if reporting any issues, provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.)
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build. _________________ "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
Last edited by kernel-panic69 on Sun Jan 05, 2020 21:21; edited 1 time in total
Do not upgrade to DD-WRT v3.0-r41892 std (01/05/20) on the Dlink DIR-882 A1 Router! you will brick it!!
Correct. it might work for other routers. not for the D-Link DIR882-A
This is what I wrote earlier:
In system information it shows: Dlink DIR860L B1
did something went wrong creating this build?
Although the file name is dlink-dir882-a1-webflash.bin it's 2 MB smaller then the previous one...
When trying to revert back to r41874 the unit got bricked.
flashing back completed but the unit didn't start again...
Finally I recovered the router back to r41874 using the D-Link Router Recovery mode...
Do not upgrade to DD-WRT v3.0-r41892 std (01/05/20) on the Dlink DIR-882 A1 Router! you will brick it!!
Correct. it might work for other routers. not for the D-Link DIR882-A
This is what I wrote earlier:
In system information it shows: Dlink DIR860L B1
did something went wrong creating this build?
Although the file name is dlink-dir882-a1-webflash.bin it's 2 MB smaller then the previous one...
When trying to revert back to r41874 the unit got bricked.
flashing back completed but the unit didn't start again...
Finally I recovered the router back to r41874 using the D-Link Router Recovery mode...
After pulling apart the r41892 images for the DIR-860L B1 and DIR-882, I have discovered there is definitely something weird going on.
r41892 for both DIR-860L B1 and DIR-882 contain the 3.10.108-d8 kernel, but r41874 for the DIR-882 is kernel 4.14.161, and 41954 is kernel 4.14.162.
The /lib/modules/ dir in r41892 for both DIR-882 and DIR-860L B1 seem very similar.
...The /lib/modules/ dir in r41892 for both DIR-882 and DIR-860L B1 seem very similar.
? Isn't that to be expected?
Both use the MediaTek MT7621AT
The WLAN should be different though,
DIR-878: MediaTek MT7615N
DIR-860L B1: MediaTek MT7612E, MediaTek MT7602E
Perhaps, but as you said, not in regards to WLAN. I would expect to see the MT7615E module at least. I have investigated the situation and it is far more bizarre -- and perhaps dangerous -- than I had thought.
I downloaded webflash.bin distributions for the DIR-882 A1 and the DIR-860L B1. The suspect revision is r41892. For reference I also downloaded revisions r41874 and r41954.
Code:
[xln@nacho Templates]$ ls -l *.bin
-rw-rw-r--. 1 xln xln 13938716 Jan 14 15:53 r41874--dlink-dir860lb1-webflash.bin
-rw-rw-r--. 1 xln xln 16146460 Jan 14 15:53 r41874--dlink-dir882-a1-webflash.bin
-rw-rw-r--. 1 xln xln 13701148 Jan 14 15:53 r41892--dlink-dir860lb1-webflash.bin
-rw-rw-r--. 1 xln xln 13729820 Jan 14 15:53 r41892--dlink-dir882-a1-webflash.bin
-rw-rw-r--. 1 xln xln 13721628 Jan 14 15:53 r41954--dlink-dir860lb1-webflash.bin
-rw-rw-r--. 1 xln xln 15933468 Jan 14 15:53 r41954--dlink-dir882-a1-webflash.bin
Code:
[xln@nacho Templates]$ echo; for bin in *.bin; do BWF="${bin}walk"; binwalk -Bv "$bin" > "$BWF"; cat $BWF | grep 'Target\|MD5\|LZMA\|Squashfs'; echo; done
In regards to the LZMA compressed sections (kernel), we can see that the r41892 webflash binaries for the DIR-882 A1 and DIR-860L B1 have kernels with the uncompressed size of 3819776 bytes. This is the 3.10.108-d8 kernel. The r41874 and r41954 binaries for the DIR-860L B1 also contain kernels of that size. On the other hand, we have r41874 and r41954 webflash binaries for the DIR-882 A1 that contain kernels with the uncompressed size of 6575504. These are the 4.14.161 and 4.14.162 kernels.
Now, if we turn our attention to the Squashfs sections (filesystem), we can see that the r41892 webflash binaries for both the DIR-860LB1 and DIR-882 A1 are IDENTICAL! Created at the same time, and having the exact same uncompressed sizes! The r41874 and r41954 webflash binaries are all totally different from one another.
All of this evidence strongly suggests that the r41892 build for the DIR-882 A1 is a dud. It may be safest to rebuild it, or at least pull it from the archive.
I don't know who to contact about this, but I feel like I need to tell someone about it. I hope one of you lads knows what to do in this situation!