EDITED: Yes, I agree that this thread is cumbersome. I will see what I can do to compile the information in the thread to pass on to the other moderator(s) who have wiki access to populate this page: https://wiki.dd-wrt.com/wiki/index.php/Linksys_EA6350
I don't think new devices pages are really necessary, since the procedures for all these are basically the same, right? Other than the 6350v2 that is, which is not in the supported list but can be flashed via serial?
Is all that is needed to properly support it is for BS to add the board id? Looks like lots of these models all use the EA6350 build already.
I will update the EA6400 wiki to mention which files to use for the appropriate model.
I have already updated the Supported Devices wiki to point the EA6xxx devices to the appropriate threads, afaik:
EA6300, EA6350v1, and EA6400 point to EA6400 wiki
EA6500 and EA6700 point to EA6700
EA6900 points to EA6900 (unchanged)
Should I update Supported Devices to add the 6350v2, and point to the serial flash thread, or just mention it in the wiki (at least until and if BS adds the support, if its easy). _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
As far as new device pages, I dunno. People want Gerber in a spoon. I personally think that would be a little more logical and organized than the train wrecks I've seen on the forum and in the wiki, but I digress _________________ "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
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Apr 12, 2020 19:57 Post subject:
And who's names are in the comments?
@imWACCo: If you could use the serial method of flashing and give us a dump of the CFE boot log before you flash one of each in text files and attach them to the ticket, that would be awesome! Just a small request...
EDIT: I edited my previous post about procedure to reflect LOM's post about the CFE for v1 and technoside's post about the CFE for v2. I'm not going to entertain deslatha's broken English interjections. Sh*t this thread is a train wreck. _________________ "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
If you could use the serial method of flashing and give us a dump of the CFE boot log before you flash one of each in text files and attach them to the ticket, that would be awesome! Just a small request...
Well, no and yes. I've not seen my TTL cable in... 8?... years. Just ordered one from Am Prime, should be here in two days.
I got a bunch of different N/AC routers for free. It seems like every one of the %&#@ things need TTL
kernel-panic69, what can I do to help? sorry for the mess on this thread. I have a spare EA6350 V2 not currently using it, and I can get whatever is needed for this. _________________ WRT54GL v1.1 - Flashed
Linksys WRT54G2 v1 - Flashed
EA6350 v2 - Flashed
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Apr 12, 2020 22:39 Post subject:
@technoside2, imWACCo: Pretty much an entire serial boot log from stock firmware, preferably. Attach to this ticket: https://svn.dd-wrt.com/ticket/6529
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Mon Apr 13, 2020 2:51 Post subject:
Yes, that is not new news (to me). I believe V3 is a Qualcomm IPQ 4xxx SoC: https://wikidevi.wi-cat.ru/index.php/Linksys_EA6350_v3 (not necessarily relevant here, but). No need to run through that, as the V1 is already supported, but a CFE boot log from stock to compare to a log from V2 from stock would be good to have. I would've responded already, but severe thunderstorm kicked off the power for a few hours. _________________ "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
Posted: Mon Apr 13, 2020 17:06 Post subject: EA6350 V2
kernel-panic69 wrote:
@technoside2, imWACCo: Pretty much an entire serial boot log from stock firmware, preferably. Attach to this ticket: https://svn.dd-wrt.com/ticket/6529
P.S. If you don't have access to the Trac system, you can also attach them here as text files and I can transfer them to the ticket.
Serial Boot log, Nvram show, and devinfo show, attached to this thread.
I had stock firmware. I decided to install dd-wrt. I flashed nflash0.trx with image linksys-ea6400-numinit-super-hacky-smaller-version.bin.
I enabled ssh and edited CFE from @deslatha https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1142886#1142886.
I posted there my router values and flashed mtd0. I think it went OK.
root@DD-WRT:~# ls -la
drwx------ 3 root root 0 Jan 1 01:00 .
drwxrwxrwx 11 root root 0 Jan 1 01:06 ..
drwx------ 2 root root 0 Jan 1 01:01 .ssh
root@DD-WRT:~# cd /tmp/
root@DD-WRT:/tmp# ls -la
drwxrwxrwx 11 root root 0 Jan 1 01:06 .
drwxr-xr-x 15 root root 162 Aug 20 2015 ..
-rw-r--r-- 1 root root 816 Jan 1 01:01 .ipt
-rw-r--r-- 1 root root 524288 Oct 14 2018 1.bin
-rw-r--r-- 1 root root 27 Jan 1 01:02 TZ
drwx------ 2 root root 0 Jan 1 01:00 cron.d
-rw-r--r-- 1 root root 268 Jan 1 01:01 dnsmasq.conf
-rw-r--r-- 1 root root 0 Jan 1 01:00 dnsmasq.leases
drwx------ 2 root root 0 Jan 1 01:00 etc
-rw-r--r-- 1 root root 39 Jan 1 01:01 hosts
-rw-r--r-- 1 root root 68 Jan 1 01:00 loginprompt
drwxr-xr-x 2 root root 0 Jan 1 01:00 mnt
drwx------ 2 root root 0 Jan 1 01:00 nvram
drwxr-xr-x 3 root root 0 Jan 1 01:00 oet
-rw-r--r-- 1 root root 23 Jan 1 01:01 resolv.conf
-rw-r--r-- 1 root root 0 Jan 1 01:01 resolv.dnsmasq
drwx------ 3 root root 0 Jan 1 01:00 root
drwxr-xr-x 2 root root 0 Jan 1 01:06 services
lrwxrwxrwx 1 root root 8 Jan 1 01:00 udhcpc -> /sbin/rc
-rw-r--r-- 1 root root 2 Jan 1 01:00 udhcpc.expires
drwxr-xr-x 10 root root 0 Jan 1 01:00 var
drwx------ 2 root root 0 Jan 1 01:00 www
root@DD-WRT:/tmp# mtd unlock /dev/mtd0
Unlocking /dev/mtd0 ...
root@DD-WRT:/tmp# mtd write -f /tmp/1.bin /dev/mtd0
Unlocking /dev/mtd0 ...
Writing from /tmp/1.bin to /dev/mtd0 ... [w]
root@DD-WRT:/tmp#
But after reboot my ea6350v2 doesn't communicate via RS, doesn't answer on ping.
I tried to hold rerset button for 20 secs and also wps button. No reaction.
Is there sth I can do to bring by router to live? _________________ RT-N18U - FreshTomato
EA6350v2 - bricked
EA6350v2 - Stock
WRT54GL - FreshTomato