Correct Build for WNDR4000?

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
strophy
DD-WRT Novice


Joined: 01 Sep 2014
Posts: 8

PostPosted: Thu Oct 19, 2017 8:31    Post subject: Reply with quote
Confirm 33215 does work, comes in at 7,805kb so just small enough to fit under the 7,808kb limit. I've also been running 30082 for almost a year with zero problems.

Unfortunately the latest K3.x mega version with the KRaCK fix is 33525 and is too large to flash at 7,813kb. Maybe later builds will be smaller.
Sponsor
vinnie97
DD-WRT User


Joined: 30 Jan 2009
Posts: 86

PostPosted: Sat Oct 21, 2017 4:16    Post subject: Reply with quote
dd-wrt.v24-33555_NEWD-2_K2.6_mega-nv64k (10/20/17) is working great for me, the first time I've upgraded in 4 years.
strophy
DD-WRT Novice


Joined: 01 Sep 2014
Posts: 8

PostPosted: Sat Oct 21, 2017 4:30    Post subject: Reply with quote
Kernel 3.x version of that build is also small enough, just updated to DD-WRT v3.0-r33555 mega (10/20/17) with no problems!

http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2017/10-20-2017-r33555/broadcom_K3X/dd-wrt.v24-33555_NEWD-2_K3.x_mega-nv64k.bin
vinnie97
DD-WRT User


Joined: 30 Jan 2009
Posts: 86

PostPosted: Sat Oct 21, 2017 5:56    Post subject: Reply with quote
Is it safe to use the DD-WRT web UI interface to upload to Kernel 3.x from 2.x?
strophy
DD-WRT Novice


Joined: 01 Sep 2014
Posts: 8

PostPosted: Sat Oct 21, 2017 6:28    Post subject: Reply with quote
Yes, I've done 2.6 -> 3.0 update before. Any problems, just do a 30/30/30 reset and try again. Uploading a too large firmware also caused no problems, it just rebooted the router without flashing anything. Pretty foolproof.
alcuin
DD-WRT Novice


Joined: 14 Feb 2007
Posts: 26

PostPosted: Fri May 11, 2018 21:30    Post subject: Reply with quote
k3.x build r35531 is the last version I am able to get wireless working. Later builds do not have a visible SSID, and builds 35874+ show radio is off in the status screen.

edit:nm, I see this is a known issue.
5. Wireless is broken for all modes on all k3.x and k2.x builds after 35531.
Fixed in r35910; wait for the next build! Tickets: 6258, 6259, 6260

edit2: can confirm that r35916 wifi works again. web page admin wouldnt come up after initial flash. had to telnet in and erase nvram, then everything worked after that.
o-l-a-v
DD-WRT Novice


Joined: 10 Aug 2011
Posts: 22
Location: Norway

PostPosted: Sun Jul 15, 2018 8:55    Post subject: Reply with quote
So the k3.x r35916 is still the recommended build? I'm updating from Kong 2014 build, time to patch the KRACK voulnerability.

Edit: I just flashed from Kong 22000++ to r35916 k3.x through web GUI, all went good. Did a normal reset before and after flash.
daydreams
DD-WRT Novice


Joined: 27 Aug 2018
Posts: 2

PostPosted: Mon Aug 27, 2018 20:41    Post subject: Reply with quote
I'm sorry for this is probably a dumb question, but is 5Ghz wireless working fine? Because on openwrt they claim there is "no driver"?
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Tue Aug 28, 2018 14:18    Post subject: Reply with quote
daydreams wrote:
I'm sorry for this is probably a dumb question, but is 5Ghz wireless working fine? Because on openwrt they claim there is "no driver"?
Yes it works fine; I'm on k3x 36698. OpenWRT is a big difference from DD; they use newer kernels that don't work w/ broadcom's binary (kernel-version-specific) drivers.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
daydreams
DD-WRT Novice


Joined: 27 Aug 2018
Posts: 2

PostPosted: Sun Sep 09, 2018 14:19    Post subject: Reply with quote
So i had an unlucky experience.. On top of stock i installed dd-wrt.v24-35916_NEWD-2_K2.6_mini-WNDR4000.chk and somehow it went wrong - my ethernet port wasn't working or only after a very long time (did many combinations of 30/30/30 and simple reset). None of newer k3.x or mega builds would install either (despite web admin of 35916-mini over the air working fine). As the last attempt, i tried to flash dd-wrt.v24-35916_NEWD-2_K3.x_mega-WNDR4000.chk (over same mini build) - and that give me a blinking green power led =(
At least tftp with stock worked

UPD when i started with dd-wrt.v24-36698_NEWD-2_K2.6_mini-WNDR4000.chk, then i was able to update to dd-wrt.v24-36698_NEWD-2_K3.x_mega-WNDR4000.chk later; i get mega pack.. however, i wonder if i can set up USB 3G modem with K2.6 mega or do i need the K3.0..?

UPD all these versions do not update firmware, as noted in the next post


Last edited by daydreams on Mon Sep 24, 2018 21:32; edited 2 times in total
cdoublejj
DD-WRT Novice


Joined: 08 Aug 2014
Posts: 9

PostPosted: Mon Sep 24, 2018 1:19    Post subject: Reply with quote
nice to see it's still alive, just noticed my firmware was from 2014!

about to try 35916, odd it's .chk file while the rest are .bin, i wonder why that is?

EDIT: that's a no go, it just displays a "This page can't be displayed" a second or 3 after hittings "flash" and starting the load bar/timer.

i guess i'll try build 215

daydreams wrote:
I'm sorry for this is probably a dumb question, but is 5Ghz wireless working fine? Because on openwrt they claim there is "no driver"?


mines been conking out form time to time, however after trying build dd-wrt.v24-33555_NEWD-2_K3.x_mega-nv64k earlier it hasn't come back up, even after reverting to dd-wrt.v24-33215_NEWD-2_K3.x_mega-nv64k

i don't mind as i'll be running REAL APs soon, this will just route after that.

someone in here also mentioned capacitor failure is common in home routers even with out bulging, at least for them.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Mon Sep 24, 2018 17:45    Post subject: Reply with quote
cdoublejj wrote:
about to try 35916, odd it's .chk file while the rest are .bin, i wonder why that is?
Read the Peacock and device wiki; .chk is for initial install. Smile Use the mega-nv64k.bin file to update; I installed 37012 k3x nv64k on my 4000 via GUI, and is running fine other with the VAP workaround.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
cdoublejj
DD-WRT Novice


Joined: 08 Aug 2014
Posts: 9

PostPosted: Tue Sep 25, 2018 0:40    Post subject: Reply with quote
i did read the wndr wiki, perhaps i'm failing to comprehend a single line in there. however i am uneducated on peacock.

Might guess it's this older thread, https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=51486

Looks like i need to stop being lazy with the 30-30-30 resets.

it' also sounds like i need to flash another image just to flash the CHKs. it would be interesting to know WHY they are release as CHK instead of Bin?

EDIT: wow there is some good info in there the only catch is it's from 2009 so some of it may require a grain of salt but, some of the basic stuff will merit more reading.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7221
Location: Columbus, Ohio

PostPosted: Tue Sep 25, 2018 1:19    Post subject: Reply with quote
Again, the .chk file is for going from Netgear to dd-wrt. The bin file is for when you are already on dd-wrt.
_________________
I am far from a guru, I'm barely a novice.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2613
Location: Indy

PostPosted: Tue Sep 25, 2018 13:37    Post subject: Reply with quote
cdoublejj wrote:
i did read the wndr wiki, perhaps i'm failing to comprehend a single line in there. however i am uneducated on peacock.

Might guess it's this older thread, https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=51486
? The WNDR4000 wiki has the Peacock Announcement link next to the file type description. Razz ...which states:
WNDR4000 wiki wrote:
-Flashing from OEM firmware requires the initial trailed build mini .chk file (with WNDR4000 in the name)
-Upgrades use the nv64k (or trailed) build and not the nv60k nor generic builds

cdoublejj wrote:
it' also sounds like i need to flash another image just to flash the CHKs. it would be interesting to know WHY they are release as CHK instead of Bin?
You're overthinking this; see 'Trailed builds' in section 4 of the Peacock. Smile You don't need the .chk file if you're already running DD. [However, it should work, but apparently it isn't for newer builds, based on recent posts.]

As for the 30-30-30, that usually isn't necessary unless you run into serious problems (and should never be done on ARM devices, btw).

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.4|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 44758: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum