Goto page Previous1, 2, 3 ... 11, 12, 13, 14, 15Next |
| Author | Message |
|---|
mrjcd
DD-WRT Guru
Joined: 31 Jan 2015
Posts: 5370
Location: Texas
| | Posted: Thu Feb 08, 2018 2:37 Post subject: | | jwh7 wrote: | @mrjcd
I've compiled your magical procedure into the wiki, take a look:
https://dd-wrt.com/wiki/index.php/Asus_RT-N12#RT-N12D1_Installation |
Looks good to me.
Glad you specified the builds to use for the D1. So many people will grab the C1 or B1 firmware cause it seems a close fit --- that is not the way.
In all the different builds I have used on the RT-N12D1 I have never used a build made for C1 or B1.
When time permits I'll drag mine out and try some newer builds ... see what happens.
As for my opinion with newest builds as of this time on the Rt-N12D1, I'd say 50/50 chance you may lose your router or put it in a bricklike-doorstop-state. |
|
Sponsor
<=' td='> |
mrjcd
DD-WRT Guru
Joined: 31 Jan 2015
Posts: 5370
Location: Texas
| | Posted: Thu Feb 08, 2018 15:16 Post subject: Re: thanks | | chemestri wrote: | | thanks for help and instructions. just to confirm all went well when following the instructions. working fine |
Great
thanks for letting us know |
|
angler
DD-WRT User
Joined: 10 Feb 2012
Posts: 56
| | Posted: Wed Feb 14, 2018 6:28 Post subject: | | FWIW, the 33215 mega wouldn't play for my D1 (using 'updated' D1 install instructions) - but v30-29409 mini did, just my $0.02. |
|
jwh7
DD-WRT Guru
Joined: 25 Oct 2013
Posts: 2613
Location: Indy
| | Posted: Wed Feb 14, 2018 14:21 Post subject: | | angler wrote: | | FWIW, the 33215 mega wouldn't play for my D1 (using 'updated' D1 install instructions) - but v30-29409 mini did, just my $0.02. |
Interesting; you went from stock to dd-wrt.v24-25974_NEWD-2_K2.6_mini.bin to dd-wrt.v24-33215_NEWD-2_K3.x_mega.bin but the latter failed? And you followed the wiki's (meaning mrjcd's...) exact steps (such as, no resets except in OEM f/w, and flashing 25974 twice)?
_________________
#NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
x64 OPNsense 20.7.6|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.5: RT-ACRH13, R6220, WNDR3700v4 |
|
angler
DD-WRT User
Joined: 10 Feb 2012
Posts: 56
| | Posted: Sat Feb 17, 2018 23:04 Post subject: | yes, I suspect it's because some D1's may only have 4MB of NVRAM like the C1 so the megas will fail
| jwh7 wrote: | | angler wrote: | | FWIW, the 33215 mega wouldn't play for my D1 (using 'updated' D1 install instructions) - but v30-29409 mini did, just my $0.02. |
Interesting; you went from stock to dd-wrt.v24-25974_NEWD-2_K2.6_mini.bin to dd-wrt.v24-33215_NEWD-2_K3.x_mega.bin but the latter failed? And you followed the wiki's (meaning mrjcd's...) exact steps (such as, no resets except in OEM f/w, and flashing 25974 twice)? |
|
|
jwh7
DD-WRT Guru
Joined: 25 Oct 2013
Posts: 2613
Location: Indy
| | Posted: Sat Feb 17, 2018 23:48 Post subject: | | angler wrote: | | yes, I suspect it's because some D1's may only have 4MB of NVRAM like the C1 so the megas will fail |
You mean flash (ROM); the C1 has 8MB. OEM firmware is bigger than 4MB:Version 3.0.0.4.376.3754
2015/01/12
5.76 MB OEM D1 firmware is even bigger:Version 3.0.0.4.380.8120
2017/11/01
6.91 MBytes What does dmesg show for flash size?
_________________
#NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
x64 OPNsense 20.7.6|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.5: RT-ACRH13, R6220, WNDR3700v4 |
|
angler
DD-WRT User
Joined: 10 Feb 2012
Posts: 56
| | Posted: Sun Feb 18, 2018 22:06 Post subject: | yeah, curious neither 7.2MB nor 7.3MB mega builds seem to play although they go through the cycle
FWIW:
Linux version 2.6.24.111 (root@nmndev) (gcc version 4.1.2) #29172 Tue Apr 5 00:38:08 CEST 2016
CPU revision is: 00019749
Found a 8MB ST compatible serial flash
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
Entering add_active_range(0, 0, 8192) 0 entries of 256 used
Zone PFN ranges:
Normal 0 -> 8192
HighMem 8192 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
On node 0 totalpages: 8192
Normal zone: 0 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 8192 pages, LIFO batch:1
HighMem zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 8192
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 256 (order: 8, 1024 bytes)
CPU: BCMd144 rev 1 at 300 MHz
Using 150.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 25996k/32768k available (3482k kernel code, 6756k reserved, 1369k data, 188k init, 0k highmem)
Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: no core
PCI: no core
PCI: Fixing up bus 0
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky
et_module_init: passivemode set to 0x0
PCI: Setting latency timer of device 0000:00:02.0 to 64
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
PCI: Setting latency timer of device 0000:00:01.0 to 64
pflash: found no supported devices
bootloader size: 131072
nvram size: 32768
sflash: Filesystem type: squashfs, size=0x2046e4
partition size = 2174976
Creating 5 MTD partitions on shfs, sflashx2046e:
0x00000000-0x00020000 : s on scfeot;fla
0x00020000-0x007f0000 : s on slinux;fla
0x0017d000-0x00390000 : s on srootfsfla
mtd: partition 390000rootfsn sroo doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : tfsn snvram;esn't
0x00390000-0x007f0000 : tfsn sddwrt;esn't
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Performance counters on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri
NET: Registered protocol family 27
PF_RING: bucket length 128 bytes
PF_RING: ring slots 4096
PF_RING: sample rate 1 [1=no sampling]
PF_RING: capture TX No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear
All bugs added by David S. Miller
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 188k freed
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device br0 entered promiscuous mode
device vlan0 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: port 1(vlan0) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan1 entered promiscuous mode
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan0) entering forwarding state
device vlan1 left promiscuous mode
| jwh7 wrote: | You mean flash (ROM); the C1 has 8MB. OEM firmware is bigger than 4MB:Version 3.0.0.4.376.3754
2015/01/12
5.76 MB OEM D1 firmware is even bigger:Version 3.0.0.4.380.8120
2017/11/01
6.91 MBytes What does dmesg show for flash size? |
|
|
angler
DD-WRT User
Joined: 10 Feb 2012
Posts: 56
| | Posted: Wed Mar 07, 2018 6:31 Post subject: | | update: it looks like the K26 builds work fine, K3x builds load but ports are unresponsive and wireless security doesn't clear |
|
Skram0
DD-WRT Novice
Joined: 03 Nov 2012
Posts: 6
| | Posted: Wed Mar 14, 2018 5:47 Post subject: | | angler wrote: | | update: it looks like the K26 builds work fine, K3x builds load but ports are unresponsive and wireless security doesn't clear |
I also tried the upgrade in the wiki to the 'dd-wrt.v24-33215_NEWD-2_K3.x_mega.bin' build. But after flash the wireless light wasn't lit. Then after a while refreshing pages started missing packets. Then eventually the whole GUI was unresponsive even though pings went through.
I downgraded back to 'dd-wrt.v24-25974_NEWD-2_K2.6_mini.bin' and it seems to be okay.
UPDATE: Maybe some of the packet loss was due to my browser/ad blockers. I've upgraded to 'dd-wrt.v24-35244_NEWD-2_K2.6_mega.bin' and was still getting a bit of packet loss (pages don't display properly) sometimes even though I'm hard wired. But I've successfully setup my wireless Client Bridge and I'm getting about 88Mbps from the living room. |
|
beren
DD-WRT Novice
Joined: 24 Mar 2012
Posts: 26
| | Posted: Thu Mar 22, 2018 22:58 Post subject: | I'm not really sure why the instructions are so convoluted. I started following them, I installed the .trx linked, but after it went to the endless reboot cycle I just went into rescue mode. You turn the router off, hold the reset button and keep it held down until your ping to 192.168.1.1 works. You'll notice the ttl=100. That means it's in rescue mode. I went to the web CFE page at http://192.168.1.1, picked the mini.bin in the zip file. After that uploaded and rebooted, I grabbed a firmware from the ftp site. I picked dd-wrt.v24-34311_NEWD-2_K3.x_mega.bin at random, uploaded it and picked the option to reset nvram as well. Booted and seems to work just fine.
I'm going to bet going into rescue mode and uploading the mini firmware would work just fine, then upgrade to a newer mega one. Just make sure to reset nvram. This build has 256k of nvram it seems. |
|
beren
DD-WRT Novice
Joined: 24 Mar 2012
Posts: 26
| | Posted: Thu Mar 22, 2018 23:00 Post subject: | | angler wrote: | | update: it looks like the K26 builds work fine, K3x builds load but ports are unresponsive and wireless security doesn't clear |
What do you mean ports are unresponsive and wireless security doesn't clear? Make sure you clear nvram when you update… |
|
zelbinion
DD-WRT Novice
Joined: 17 Jul 2009
Posts: 9
| | Posted: Wed Apr 11, 2018 7:06 Post subject: | So, I think the Wiki (this page: https://www.dd-wrt.com/wiki/index.php/Asus_RT-N12) needs to be updated.
I had two RT-N12 ver D1's and I successfully updated them to dd-wrt using the 'old' instructions (prior to the update that I think occurred around March 22 2018.)
The 'old' instructions mentioned using ports 2 or 3 only, and using tftp to do the upload, and did not reference the ASUS recovery utility at all. Like I said, I had no trouble with these instructions.
Recently, I purchased a third RT-N12D1, and discovered the instructions had changed. I tried following the instructions as they appeared on April 11, 2018, and found they did not work.
When I attempted to upload the .trx file (step 4) I got an error saying that the firmware was not certified or something (sorry, I didn't capture the full error message.) The progress bar went to 100%, but at the end, nothing happened. The router did not reboot, and even when I rebooted it manually, it came back up on the original firmware. I also tried finding the original firmware version mentioned in the instructions (3.0.0.4.374.813) and tried uploading that through the web UI, but I got the same error message, and the firmware did not update.
I can't remember the exact firmware version the router came with, but I think it started with 3.0.0.4.380.xxx
What I wound up doing is putting the router into recovery mode (holding the reset button for 15-20 seconds while powering on the router) and then using the ASUS recovery program to downgrade the firmware to version 3.0.0.4.374.813. Once this was complete and the router rebooted, I was able to follow the instructions in the wiki and everything worked.
So, it seems ASUS has added some sort of firmware signing feature to newer firmware versions that will not let you either downgrade the firmware past a certain version, or load 3rd party firmware via the web UI.
Downgrading the firmware using the recovery utility seems to work around the issue.
Hope this helps. |
|
jwh7
DD-WRT Guru
Joined: 25 Oct 2013
Posts: 2613
Location: Indy
| | Posted: Wed Apr 11, 2018 13:25 Post subject: | | zelbinion wrote: | So, it seems ASUS has added some sort of firmware signing feature to newer firmware versions that will not let you either downgrade the firmware past a certain version, or load 3rd party firmware via the web UI.
Downgrading the firmware using the recovery utility seems to work around the issue. |
This is the case with many (most? all?) manufacturers for (at least) US models, due to FCC mandates.
Did you try the 'old' method when it still had the original (newer) OEM f/w?
_________________
#NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
x64 OPNsense 20.7.6|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.5: RT-ACRH13, R6220, WNDR3700v4 |
|
zelbinion
DD-WRT Novice
Joined: 17 Jul 2009
Posts: 9
| | Posted: Wed Apr 11, 2018 18:57 Post subject: | | jwh7 wrote: |
Did you try the 'old' method when it still had the original (newer) OEM f/w? |
Not on the latest router, because those instructions are no longer on wiki, and I could not remember the sequence in sufficient detail to want to risk it. I suspect it would have worked fine, since the initial load of dd-wrt was uploaded via tftp, likely by-passing any sort of firmware signature check. I didn't bother to check what version of the firmware was running on the first two routers I updated with the tftp method, though it wasn't that long ago -- maybe February 2018?
If anyone has an older copy of the update instructions for the RT-12ND1, or if the wiki saves revisions and that's something that could be retrieved, it might be a good idea to list the previous method as an alternate way to install dd-wrt on these routers with the newest firmware. |
|
