Posted: Sat Sep 28, 2013 3:01 Post subject: New K3.X builds
I've got the RT-N66U B1 router and I'm about to flash it with dd-wrt.
then new K3.X Mega build on the wiki says it bypasses the 32k/64k cfe issue, so I want to use that of course!
I'm concerned though that every description of dd-wrt says install a "mini" build first then a "big" or "mega" build, yet the k3.x build just points to mega and the webgui instructions say clear ram and install it! basically.
Joined: 01 Nov 2013 Posts: 10 Location: China/Shanghai/上海
Posted: Fri Nov 01, 2013 4:33 Post subject: Re: Asus RT-N66U flashing - works - success!
C_T wrote:
I got my Asus RT-N66U to work recently (late August-September). Mine is a B1 hardware version.
I followed the instructions and flashed it dozens of times and waited and waited. I also tried many differnt build versions. The 192.168.1.1 interface would never come back up after a flash (can't do http://192.168.1.1/do.htm?cmd=nvram+commit ). I've flashed other routers before and this was never a problem.
I opened the router and attached a serial level shifter. It was hanging on
Booting device: Linksys WRT54G/GL/GS
roboswitch: Probing device eth0: No such device
roboswitch: Probing device eth1: No such device
roboswitch: Probing device eth2: No such device
roboswitch: Probing device eth3: No such device
Segmentation fault
/etc/preinit: line 66: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory
/etc/preinit: line 66: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory
get_wl_instance doesnt return the right value 0
get_wl_instance doesnt return the right value 0
wl:-i down ->wl driver adapter not found
Write wireless mac fail : : No such device
wl:-i up ->wl driver adapter not found
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
get_wl_instance doesnt return the right value 0
wl:-i vlan_mode 0 ->wl driver adapter not found
get_wl_instance doesnt return the right value 0
wl:-i radio on ->wl driver adapter not found
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
get_wl_instance doesnt return the right value 0
wl:-i radio on ->wl driver adapter not found
get_wl_instance doesnt return the right value 0
No such device
Bad argument `DNAT'
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
I reason the nvram build was incomplete the first time, possibly due to script segfaulting, evidenced by the fact that erasing the nvram and rebuilding doesn't segfault the second time around and puts nvram in a working state. My serial output looked like Fractal's Sat Apr 07, 2012 10:24 pm post ( http://www.dd-wrt.com/phpBB2/viewtopic.php?p=680125 ) Simply rebooting did not help.
So I ran CFE> nvram erase and CFE> nvram commit and CFE> go and it finally booted and I could ping it.
I couldn't have done it without Fractal's post and a serial adapter.
It seems C_T was the only one who successfully could revive the RT-n66U with that "not coming back"-problem. I don't want my router to end aws an expensive brick, so I Opend the router and found the pins for the serial level shifter.
Can anyone recommend a serial level shifter? can it be done with this one: https://www.sparkfun.com/products/449 ?Do I only have to establish a serial connection with ssh or putty? or on the command line? how does it work in detail. A simple explaination will work for me. Please help!
Posted: Fri Nov 01, 2013 18:44 Post subject: Flashing My New RT-N66U with dd-wrt
Hello All.
This is my first post. Several years ago I had Linksys WRT54GL router and flashed it with dd-wrt. It was always rock solid! About a year and a half ago, I moved to a Linksys EA-3500, which I hate. I received my brand new in-the-box Asus RT-N66U router a few minutes ago and would like to flash it with dd-wrt.
I have read threads on this topic (Flashing DD-WRT onto an Asus RT-N66U), the wiki page, Wilkinson’s article, etc. to the point of exhaustion. I do have several questions that I hope many of you can help answer. I am confused with regard to the exact steps I need to perform. Here is what I understand to be applicable to my situation.
From the wiki – “New K3.X Builds”
25-May-2013: Since the experimental K3.X Broadcom Builds are out, you do not need to care what CFE you have. DD-WRT detects it automatically and extends 32KB NVRAM Version to 64KB. Which Image you have to flash, depends on your previous Image (Stock, Merlin, K2.6 DD-WRT ). If you have Stock Firmware / Merlin’s Firmware: Flash dd-wrt.v24-21676_NEWD-2_K3.x_mega_RT-N66U.trx
1. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
2. Install the INITIAL ASUS RT-N66U version of DD-WRT (file name ends in .trx) using either the Web GUI method or the Recover Utility method. Both methods are described below (What is the complete name of the file I need and where do I get it?)
3. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
4. "Upgrade" to your final version of DD-WRT (filename ends in .bin) using Web GUI or Recovery Utility (What is the complete name of the file I need and where do I get it?)
5. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
6. Note: is IMPORTANT to clear NVRAM (to select Factory Default settings) BEFORE and AFTER upload of any new firmware.
7. Upload Firmware via Web GUI
8. Clear settings (Clear NVRAM) select Factory Default settings. (How do I select “Factory default Setting” while doing a 30/30/30?)
9. Upload the .trx file using the stock web GUI. (What is the complete name of the file I need and where do I get it?)
10. Wait for the router to re-boot on its own. This may easily take 10-15 minutes to happen, so just be patient. You want both ping response and web-gui response to know that the router is fully re-booted.
11. Clear settings (Clear NVRAM) select Factory Default settings. Wait for the router to re-boot on its own!!! May take 10 minutes or more
Will these steps provide me with the latest dd-wrt and EVERY FUNCTION working correctly?
Or should I follow these steps?
- Set your NIC card to static > IP 192.168.1.12, Subnet 255.255.255.0, Default gateway192.168.1.1
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Access the router’s built in recovery mode by issuing 192.168.1.1 in browser field.
- Flash DD-WRT build (e.g.) Asus-RT-N66U_18777_mini build (should I use this very build or is there a later one???) and upload. When completed wait at least 10 minutes.
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Flash DD-WRT build (e.g.) Asus-RT-N66U_18777_big build (should I use this very build or is there a later one???) and upload. When completed wait at least 10 minutes
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Select Reset NVRAM defaults when it completes (should be quick), in the browser field, type in http://192.168.1.1/do.htm?cmd=nvram+commit. When done press enter. When complete select reboot and wait 5-10 minutes for the router to reboot and start building its layers.
All help appreciated and thanks in advance! I can't afford to brick this piece.
Joined: 01 Nov 2013 Posts: 10 Location: China/Shanghai/上海
Posted: Fri Nov 29, 2013 3:56 Post subject: still hanging after rebooting
Code:
reboot [len=6]
<20131129114756.442 RX>
reboot [len=6]
<20131129114756.442 RX>
<LF>root@DD-WRT:/tmpBCMDOG: WDT device closed unexpectedly. WDT will not stop! [len=76]
<20131129114756.464 RX>
<LF># Restarting system. [len=21]
<20131129114804.512 RX>
<LF>Please stand by while rebooting the system... [len=46]
<20131129114804.515 RX>
<LF>Decompressing...done [len=21]
<20131129114804.601 RX>
<LF>tmp_ret= 0 [len=11]
<20131129114804.674 RX>
<LF> [len=1]
<20131129114804.674 RX>
<LF> [len=1]
<20131129114804.674 RX>
<LF>CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE) [len=69]
<20131129114804.681 RX>
<LF>Build Date: 五 9月 14 17:47:35 CST 2012 (boyau@localhost) [len=61]
<20131129114804.687 RX>
<LF>Copyright (C) 2000-2008 Broadcom Corporation. [len=46]
<20131129114804.691 RX>
<LF> [len=1]
<20131129114804.692 RX>
<LF>Init Arena [len=11]
<20131129114804.692 RX>
<LF>Init Devs. [len=11]
<20131129114804.692 RX>
<LF>Boot partition size = 262144(0x40000) [len=38]
<20131129114804.696 RX>
<LF>CPU type 0x19749: 600MHz [len=25]
<20131129114804.705 RX>
<LF>Tot mem: 131072 KBytes [len=23]
<20131129114804.705 RX>
<LF> [len=1]
<20131129114804.705 RX>
<LF>CFE mem: 0x80700000 - 0x80839350 (1282896) [len=46]
<20131129114804.710 RX>
<LF>Data: 0x80733120 - 0x807363E0 (12992) [len=44]
<20131129114804.713 RX>
<LF>BSS: 0x807363E0 - 0x80737350 (3952) [len=43]
<20131129114804.719 RX>
<LF>Heap: 0x80737350 - 0x80837350 (1048576) [len=46]
<20131129114804.722 RX>
<LF>Stack: 0x80837350 - 0x80839350 (8192) [len=43]
<20131129114804.725 RX>
<LF>Text: 0x80700000 - 0x80733118 (209176) [len=45]
<20131129114804.732 RX>
<LF> [len=1]
<20131129114804.732 RX>
<LF>Committing NVRAM...done [len=24]
<20131129114806.028 RX>
<LF>Null Rescue Flag. [len=18]
<20131129114806.035 RX>
<LF>Loader:raw Filesys:tftp Dev:(null) File:: Options:(null) [len=57]
<20131129114806.726 RX>
<LF>Loading: TFTP Server. [len=22]
<20131129114806.728 RX>
<LF>Failed. [len=8]
<20131129114806.729 RX>
<LF>Could not load :: Error [len=24]
<20131129114806.733 RX>
<LF>Loader:raw Filesys:raw Dev:flash0.os File: Options:(null) [len=58]
<20131129114806.753 RX>
<LF>Loading: .. 3916 bytes read [len=28]
<20131129114806.768 RX>
<LF>Entry at 0x80001000 [len=20]
<20131129114806.772 RX>
<LF>Starting program at 0x80001000 [len=31]
<20131129114806.774 RX>
<LF>Linux version 2.6.24.111 (eko@dd-wrt) (gcc version 4.1.2) #3255 Sat Apr 7 13:35:16 CEST 2012 [len=93]
<20131129114809.956 RX>
<LF>CPU revision is: 00019749 [len=26]
<20131129114809.958 RX>
<LF>Determined physical RAM map: [len=29]
<20131129114809.961 RX>
<LF> memory: 07fff000 @ 00000000 (usable) [len=38]
<20131129114809.964 RX>
<LF> memory: 08000000 @ 87fff000 (usable) [len=38]
<20131129114809.968 RX>
<LF>Zone PFN ranges: [len=17]
<20131129114809.969 RX>
<LF> Normal 0 -> 131072 [len=32]
<20131129114809.972 RX>
<LF> HighMem 131072 -> 589823 [len=32]
<20131129114809.975 RX>
<LF>Movable zone start PFN for each node [len=37]
<20131129114809.978 RX>
<LF>early_node_map[2] active PFN ranges [len=36]
<20131129114809.981 RX>
<LF> 0: 0 -> 32767 [len=28]
<20131129114809.984 RX>
<LF> 0: 557055 -> 589823 [len=28]
<20131129114809.986 RX>
<LF>Built 1 zonelists in Zone order. Total pages: 65535 [len=53]
<20131129114809.992 RX>
<LF>Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd [len=81]
<20131129114810.000 RX>
<LF>Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes. [len=77]
<20131129114810.006 RX>
<LF>Primary data cache 32kB, 4-way, linesize 32 bytes. [len=51]
<20131129114810.011 RX>
<LF>Synthesized TLB refill handler (20 instructions). [len=50]
<20131129114810.015 RX>
<LF>Synthesized TLB load handler fastpath (32 instructions). [len=57]
<20131129114810.019 RX>
<LF>Synthesized TLB store handler fastpath (32 instructions). [len=58]
<20131129114810.024 RX>
<LF>Synthesized TLB modify handler fastpath (31 instructions). [len=59]
<20131129114810.029 RX>
<LF>PID hash table entries: 512 (order: 9, 2048 bytes) [len=51]
<20131129114810.034 RX>
<LF>CPU: BCM5300 rev 1 at 600 MHz [len=30]
<20131129114810.037 RX>
<LF>Using 300.000 MHz high precision timer. [len=40]
<20131129114810.040 RX>
<LF>console [ttyS0] enabled [len=24]
<20131129114810.044 RX>
<LF>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [len=63]
<20131129114810.052 RX>
<LF>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [len=61]
<20131129114810.055 RX>
<LF>Memory: 252912k/131068k available (3522k kernel code, 8936k reserved, 1373k data, 188k init, 131072k highmem) [len=110]
<20131129114810.151 RX>
<LF>Mount-cache hash table entries: 512 [len=36]
<20131129114810.359 RX>
<LF>NET: Registered protocol family 16 [len=35]
<20131129114810.363 RX>
<LF>Generic PHY: Registered new driver [len=35]
<20131129114810.374 RX>
<LF>PCI: Initializing host [len=23]
<20131129114810.376 RX>
<LF>PCI: Reset RC [len=14]
<20131129114810.377 RX>
<LF>PCI: Initializing host [len=23]
<20131129114810.484 RX>
<LF>PCI: Reset RC [len=14]
<20131129114810.487 RX>
<LF>PCI: Fixing up bus 0 [len=21]
<20131129114810.600 RX>
<LF>PCI/PCIe coreunit 0 is set to bus 1. [len=37]
<20131129114810.601 RX>
<LF>PCI: Fixing up bridge [len=22]
<20131129114810.601 RX>
<LF>PCI: Fixing up bridge [len=22]
<20131129114810.603 RX>
<LF>PCI: Enabling device 0000:01:00.1 (0004 -> 0006) [len=49]
<20131129114810.606 RX>
<LF>PCI: Fixing up bus 1 [len=21]
<20131129114810.609 RX>
<LF>PCI/PCIe coreunit 1 is set to bus 2. [len=37]
<20131129114810.612 RX>
<LF>PCI: Fixing up bridge [len=22]
<20131129114810.615 RX>
<LF>PCI: Fixing up bridge [len=22]
<20131129114810.616 RX>
<LF>PCI: Enabling device 0000:02:00.1 (0004 -> 0006) [len=49]
<20131129114810.619 RX>
<LF>PCI: Fixing up bus 2 [len=21]
<20131129114810.623 RX>
<LF>NET: Registered protocol family 2 [len=34]
<20131129114810.664 RX>
<LF>Time: MIPS clocksource has been installed. [len=43]
<20131129114810.673 RX>
<LF>IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [len=63]
<20131129114810.756 RX>
<LF>TCP established hash table entries: 4096 (order: 3, 32768 bytes) [len=65]
<20131129114810.764 RX>
<LF>TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [len=58]
<20131129114810.768 RX>
<LF>TCP: Hash tables configured (established 4096 bind 4096) [len=57]
<20131129114810.773 RX>
<LF>TCP reno registered [len=20]
<20131129114810.775 RX>
<LF>highmem bounce pool size: 64 pages [len=35]
<20131129114810.811 RX>
<LF>devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au) [len=55]
<20131129114810.816 RX>
<LF>devfs: boot_options: 0x1 [len=25]
<20131129114810.818 RX>
<LF>squashfs: version 3.0 (2006/03/15) Phillip Lougher [len=51]
<20131129114810.823 RX>
<LF>io scheduler noop registered [len=29]
<20131129114810.827 RX>
<LF>io scheduler deadline registered (default) [len=43]
<20131129114810.830 RX>
<LF>HDLC line discipline: version $Revision: 4.8 $, maxframe=4096 [len=62]
<20131129114811.052 RX>
<LF>N_HDLC line discipline registered. [len=35]
<20131129114811.056 RX>
<LF>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled [len=74]
<20131129114811.062 RX>
<LF>serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A [len=52]
<20131129114811.068 RX>
<LF>serial8250: ttyS1 at MMIO 0x0 (irq = 8) is a 16550A [len=52]
<20131129114811.070 RX>
<LF>PPP generic driver version 2.4.2 [len=33]
<20131129114811.075 RX>
<LF>PPP Deflate Compression module registered [len=42]
<20131129114811.080 RX>
<LF>PPP BSD Compression module registered [len=38]
<20131129114811.084 RX>
<LF>MPPE/MPPC encryption/compression module registered [len=51]
<20131129114811.088 RX>
<LF>NET: Registered protocol family 24 [len=35]
<20131129114811.092 RX>
<LF>PPPoL2TP kernel driver, V1.0 [len=29]
<20131129114811.095 RX>
<LF>tun: Universal TUN/TAP device driver, 1.6 [len=42]
<20131129114811.099 RX>
<LF>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [len=55]
<20131129114811.103 RX>
<LF>et_module_init: passivemode set to 0x0 [len=39]
<20131129114811.107 RX>
<LF>PCI: Enabling device 0000:01:01.0 (0000 -> 0002) [len=49]
<20131129114811.131 RX>
<LF>PCI: Enabling device 0000:02:01.0 (0000 -> 0002) [len=49]
<20131129114811.227 RX>
<LF>Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x00227e [len=110]
<20131129114811.331 RX>
<LF>Amd/Fujitsu Extended Query Table at 0x0040 [len=43]
<20131129114811.336 RX>
<LF>Physically mapped flash: CFI does not contain boot bank location. Assuming top. [len=80]
<20131129114811.343 RX>
<LF>number of CFI chips: 1 [len=23]
<20131129114811.345 RX>
<LF>cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. [len=73]
<20131129114811.351 RX>
<LF>Flash device: 0x2000000 at 0x1c000000 [len=38]
<20131129114811.355 RX>
<LF>bootloader size: 262144 [len=24]
<20131129114811.358 RX>
<LF>nvram size: 32768 [len=18]
<20131129114811.360 RX>
<LF>Physically mapped flash: Filesystem type: squashfs, size=0x1f7fbe [len=66]
<20131129114811.366 RX>
<LF>partition size = 2103268 [len=25]
<20131129114811.368 RX>
<LF>Creating 5 MTD partitions on "Physically mapped flash": [len=56]
<20131129114811.373 RX>
<LF>0x00000000-0x00040000 : "cfe" [len=30]
<20131129114811.376 RX>
<LF>0x00040000-0x01fe0000 : "linux" [len=32]
<20131129114811.380 RX>
<LF>0x0019e81c-0x003a0000 : "rootfs" [len=33]
<20131129114811.384 RX>
<LF>mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only [len=84]
<20131129114811.390 RX>
<LF>0x01fe0000-0x02000000 : "nvram" [len=32]
<20131129114811.397 RX>
<LF>0x003a0000-0x01fe0000 : "ddwrt" [len=32]
<20131129114811.398 RX>
<LF>Found a 0MB serial flash [len=26]
<20131129114811.399 RX>
<LF>sflash: found no supported devices [len=35]
<20131129114811.408 RX>
<LF>Broadcom Watchdog Timer: 0.07 initialized. [len=43]
<20131129114811.408 RX>
<LF>u32 classifier [len=15]
<20131129114811.409 RX>
<LF> Actions configured [len=24]
<20131129114811.412 RX>
<LF>Netfilter messages via NETLINK v0.30. [len=38]
<20131129114811.415 RX>
<LF>nf_conntrack version 0.5.0 (4096 buckets, 16384 max) [len=53]
<20131129114811.420 RX>
<LF>ctnetlink v0.93: registering with nfnetlink. [len=45]
<20131129114811.424 RX>
<LF>IPv4 over IPv4 tunneling driver [len=32]
<20131129114811.428 RX>
<LF>GRE over IPv4 tunneling driver [len=31]
<20131129114811.430 RX>
<LF>ip_tables: (C) 2000-2006 Netfilter Core Team [len=45]
<20131129114811.435 RX>
<LF>ClusterIP Version 0.8 loaded successfully [len=42]
<20131129114811.439 RX>
<LF>TCP bic registered [len=19]
<20131129114811.442 RX>
<LF>TCP cubic registered [len=21]
<20131129114811.443 RX>
<LF>TCP westwood registered [len=24]
<20131129114811.446 RX>
<LF>TCP highspeed registered [len=25]
<20131129114811.447 RX>
<LF>TCP hybla registered [len=21]
<20131129114811.450 RX>
<LF>TCP htcp registered [len=20]
<20131129114811.452 RX>
<LF>TCP vegas registered [len=21]
<20131129114811.455 RX>
<LF>TCP scalable registered [len=24]
<20131129114811.456 RX>
<LF>NET: Registered protocol family 1 [len=34]
<20131129114811.460 RX>
<LF>NET: Registered protocol family 17 [len=35]
<20131129114811.463 RX>
<LF>Welcome to PF_RING 3.2.1 [len=25]
<20131129114811.465 RX>
<LF>(C) 2004-06 L.Deri <deri@ntop.org> [len=35]
<20131129114811.468 RX>
<LF>NET: Registered protocol family 27 [len=35]
<20131129114811.471 RX>
<LF>PF_RING: bucket length 128 bytes [len=36]
<20131129114811.474 RX>
<LF>PF_RING: ring slots 4096 [len=31]
<20131129114811.478 RX>
<LF>PF_RING: sample rate 1 [1=no sampling] [len=44]
<20131129114811.482 RX>
<LF>PF_RING: capture TX No [RX only] [len=39]
<20131129114811.485 RX>
<LF>PF_RING: transparent mode Yes [len=30]
<20131129114811.489 RX>
<LF>PF_RING initialized correctly. [len=31]
<20131129114811.491 RX>
<LF>PF_RING: registered /proc/net/pf_ring/ [len=39]
<20131129114811.495 RX>
<LF>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> [len=62]
<20131129114811.503 RX>
<LF>All bugs added by David S. Miller <davem@redhat.com> [len=53]
<20131129114811.505 RX>
<LF>decode 1f02 [len=12]
<20131129114811.518 RX>
<LF>VFS: Mounted root (squashfs filesystem) readonly. [len=50]
<20131129114811.520 RX>
<LF>Mounted devfs on /dev [len=22]
<20131129114811.524 RX>
<LF>Freeing unused kernel memory: 188k freed [len=41]
<20131129114811.529 RX>
<LF>start service [len=14]
<20131129114811.836 RX>
<LF>starting Architecture code for broadcom [len=40]
<20131129114811.840 RX>
<LF>done [len=5]
<20131129114812.165 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114812.192 RX>
<LF>No such device [len=15]
<20131129114812.192 RX>
<LF>Booting device: Linksys WRT54G/GL/GS [len=37]
<20131129114812.198 RX>
<LF>roboswitch: Probing device eth0: No such device [len=48]
<20131129114812.284 RX>
<LF>roboswitch: Probing device eth1: No such device [len=48]
<20131129114812.289 RX>
<LF>roboswitch: Probing device eth2: No such device [len=48]
<20131129114812.293 RX>
<LF>roboswitch: Probing device eth3: No such device [len=48]
<20131129114812.297 RX>
<LF>Segmentation fault [len=19]
<20131129114812.348 RX>
<LF>/etc/preinit: line 66: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory [len=95]
<20131129114813.597 RX>
<LF>/etc/preinit: line 66: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory [len=95]
<20131129114813.793 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114813.865 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114813.904 RX>
<LF>wl:-i down ->wl driver adapter not found [len=42]
<20131129114814.619 RX>
<LF>Write wireless mac fail : : No such device [len=43]
<20131129114814.622 RX>
<LF>wl:-i up ->wl driver adapter not found [len=40]
<20131129114814.626 RX>
<LF>br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. [len=60]
<20131129114814.663 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114814.722 RX>
<LF>wl:-i vlan_mode 0 ->wl driver adapter not found [len=49]
<20131129114814.724 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114814.733 RX>
<LF>wl:-i radio on ->wl driver adapter not found [len=46]
<20131129114814.738 RX>
<LF>SIOCGIFFLAGS: No such device [len=29]
<20131129114815.277 RX>
<LF>SIOCGIFFLAGS: No such device [len=29]
<20131129114815.279 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114815.459 RX>
<LF>wl:-i radio on ->wl driver adapter not found [len=46]
<20131129114815.462 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114815.475 RX>
<LF>No such device [len=15]
<20131129114815.477 RX>
<LF>Bad argument `DNAT' [len=20]
<20131129114815.798 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114816.496 RX>
<LF>No such device [len=15]
<20131129114816.496 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114817.516 RX>
<LF>No such device [len=15]
<20131129114817.516 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114818.536 RX>
<LF>No such device [len=15]
<20131129114818.537 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114819.553 RX>
<LF>No such device [len=15]
<20131129114819.556 RX>
<LF>get_wl_instance doesnt return the right value 0 [len=48]
<20131129114822.206 RX>
<LF>No such device [len=15]
<20131129114822.208 RX>
<LF>
<20131129114832.221 RX>
get_wl_instance doesnt return the right value 0 [len=48]
<20131129114832.226 RX>
<LF>No such device [len=15]
<20131129114832.226 RX>
<LF>
<20131129114842.241 RX>
get_wl_instance doesnt return the right value 0 [len=48]
<20131129114842.246 RX>
<LF>No such device [len=15]
<20131129114842.247 RX>
<LF>
<20131129114852.261 RX>
get_wl_instance doesnt return the right value 0 [len=48]
<20131129114852.266 RX>
<LF>No such device [len=15]
<20131129114852.266 RX>
<LF>
<20131129114854.762 TX>
root [len=4]
<20131129114854.777 RX>
root [len=4]
<20131129114854.777 RX>
<LF>DD-WRT v24-sp2 mini (c) 2012 NewMedia-NET GmbH [len=47]
<20131129114854.821 RX>
<LF>Release: 04/07/12 (SVN revision: 18946) [len=40]
<20131129114854.824 RX>
<LF> [len=1]
<20131129114854.824 RX>
<LF>DD-WRT login:
<20131129114857.118 TX>
root [len=4]
<20131129114857.133 RX>
root [len=4]
<20131129114857.133 RX>
<LF>Password:
<20131129114900.530 TX>
admin [len=5]
<20131129114900.545 RX>
[len=0]
<20131129114900.545 RX>
<LF>========================================================== [len=59]
<20131129114900.552 RX>
<LF> [len=2]
<20131129114900.552 RX>
<LF> ____ ___ __ ______ _____ ____ _ _ [len=57]
<20131129114900.555 RX>
<LF> | _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || | [len=58]
<20131129114900.561 RX>
<LF> || | || ||____\ \ /\ / /| |_) || | \ \ / / __) | || |_ [len=59]
<20131129114900.565 RX>
<LF> ||_| ||_||_____\ V V / | _ < | | \ V / / __/|__ _| [len=60]
<20131129114900.571 RX>
<LF> |___/|___/ \_/\_/ |_| \_\|_| \_/ |_____| |_| [len=58]
<20131129114900.576 RX>
<LF> [len=2]
<20131129114900.577 RX>
<LF> DD-WRT v24-sp2 [len=38]
<20131129114900.581 RX>
<LF> http://www.dd-wrt.com [len=41]
<20131129114900.584 RX>
<LF> [len=2]
<20131129114900.584 RX>
<LF>========================================================== [len=59]
<20131129114900.590 RX>
<LF>Jan 1 00:00:50 login[1004]: root login on 'console' [len=53]
<20131129114900.594 RX>
[len=0]
<20131129114900.594 RX>
<LF> [len=1]
<20131129114900.594 RX>
<LF> [len=1]
<20131129114900.594 RX>
<LF>BusyBox v1.19.4 (2012-04-07 13:33:30 CEST) built-in shell (ash) [len=64]
<20131129114900.599 RX>
<LF>Enter 'help' for a list of built-in commands. [len=46]
<20131129114900.604 RX>
<LF> [len=1]
<20131129114900.604 RX>
<LF>root@DD-WRT:~# get_wl_instance doesnt return the right value 0 [len=63]
<20131129114902.287 RX>
<LF>No such device [len=15]
<20131129114902.289 RX>
<LF>get_wl_instance doesnt re
<20131129114912.304 RX>
turn the right value 0 [len=48]
<20131129114912.306 RX>
<LF>No such device [len=15]
<20131129114912.307 RX>
<LF>
Above you can see the log from a serial logger of my asus router.
As you can see it is already flashed, but I can not reach it at 192.168.1.1 and that sucks a lot. So with the serial logger I can login to dd-wrt with root/admin and reboot, but how can I send "nvram erase and nvram commit to the router and let dd-wrt restart?
Or what to do at all? I don't want my router to be an expensive brick...
I hope this is still an active subject. I have been a huge fan of the DD-WRT obv, now my Asus was losing WiFi radio for no reason...time to retire this soldier and upgrade.
Now I bought the N66U and it on specs seems to be a bad ass. However it sure looks like it comes with a ton of challenges on the setup. I have been reading and reading and looking and man it sure seems to be many opinions on this. So, I just downloaded the Mega and the Big, and then read I shouldn't read I could get away with the mega and I thought great. I uploaded it and then it looked like it went smooth. Then I realized it wouldn't save my changes...however on first boot up it saved the admin name and password. I tried some stuff and thought it was hung, so I gave up and booted in the recovery mode and uploaded Asus firmware and started over.
So, that is where I am now, I used the Big on this time and it is doing the exact same thing. I can initially make changes in the admin name and password, then same thing. I click apply to make the changes to things like WiFi name...nope it times out in the web browser (FireFox) and then I go back into the router and nothing is saved.
So, that is where I am now...flashed looks like it is working for all intents and purposes, but it will not save any changes.
Bah of all the things...Internet Explorer works but not Firefox. Oh I am sure there is a way to make it work, kill the cache or something but seriously? God I hate IE, but the router is now setup...sheesh.
Posted: Mon Dec 23, 2013 23:00 Post subject: Re: Flashing My New RT-N66U with dd-wrt
kailor wrote:
Hello All.
This is my first post. Several years ago I had Linksys WRT54GL router and flashed it with dd-wrt. It was always rock solid! About a year and a half ago, I moved to a Linksys EA-3500, which I hate. I received my brand new in-the-box Asus RT-N66U router a few minutes ago and would like to flash it with dd-wrt.
I have read threads on this topic (Flashing DD-WRT onto an Asus RT-N66U), the wiki page, Wilkinson’s article, etc. to the point of exhaustion. I do have several questions that I hope many of you can help answer. I am confused with regard to the exact steps I need to perform. Here is what I understand to be applicable to my situation.
From the wiki – “New K3.X Builds”
25-May-2013: Since the experimental K3.X Broadcom Builds are out, you do not need to care what CFE you have. DD-WRT detects it automatically and extends 32KB NVRAM Version to 64KB. Which Image you have to flash, depends on your previous Image (Stock, Merlin, K2.6 DD-WRT ). If you have Stock Firmware / Merlin’s Firmware: Flash dd-wrt.v24-21676_NEWD-2_K3.x_mega_RT-N66U.trx
1. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
2. Install the INITIAL ASUS RT-N66U version of DD-WRT (file name ends in .trx) using either the Web GUI method or the Recover Utility method. Both methods are described below (What is the complete name of the file I need and where do I get it?)
3. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
4. "Upgrade" to your final version of DD-WRT (filename ends in .bin) using Web GUI or Recovery Utility (What is the complete name of the file I need and where do I get it?)
5. Clear settings (Clear NVRAM) select Factory Default settings (How do I select “Factory default Setting” while doing a 30/30/30?)
6. Note: is IMPORTANT to clear NVRAM (to select Factory Default settings) BEFORE and AFTER upload of any new firmware.
7. Upload Firmware via Web GUI
8. Clear settings (Clear NVRAM) select Factory Default settings. (How do I select “Factory default Setting” while doing a 30/30/30?)
9. Upload the .trx file using the stock web GUI. (What is the complete name of the file I need and where do I get it?)
10. Wait for the router to re-boot on its own. This may easily take 10-15 minutes to happen, so just be patient. You want both ping response and web-gui response to know that the router is fully re-booted.
11. Clear settings (Clear NVRAM) select Factory Default settings. Wait for the router to re-boot on its own!!! May take 10 minutes or more
Will these steps provide me with the latest dd-wrt and EVERY FUNCTION working correctly?
Or should I follow these steps?
- Set your NIC card to static > IP 192.168.1.12, Subnet 255.255.255.0, Default gateway192.168.1.1
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Access the router’s built in recovery mode by issuing 192.168.1.1 in browser field.
- Flash DD-WRT build (e.g.) Asus-RT-N66U_18777_mini build (should I use this very build or is there a later one???) and upload. When completed wait at least 10 minutes.
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Flash DD-WRT build (e.g.) Asus-RT-N66U_18777_big build (should I use this very build or is there a later one???) and upload. When completed wait at least 10 minutes
- Put router into recovery mode by holding down the reset button while powering up the router, wait until the power led is blinking slowly, then release the reset button.
- Select Reset NVRAM defaults when it completes (should be quick), in the browser field, type in http://192.168.1.1/do.htm?cmd=nvram+commit. When done press enter. When complete select reboot and wait 5-10 minutes for the router to reboot and start building its layers.
All help appreciated and thanks in advance! I can't afford to brick this piece.
An answer to this question would be mighty helpful.
Posted: Mon Dec 23, 2013 23:03 Post subject: Re: still hanging after rebooting
jagottsicher wrote:
Above you can see the log from a serial logger of my asus router.
As you can see it is already flashed, but I can not reach it at 192.168.1.1 and that sucks a lot. So with the serial logger I can login to dd-wrt with root/admin and reboot, but how can I send "nvram erase and nvram commit to the router and let dd-wrt restart?
Or what to do at all? I don't want my router to be an expensive brick...
There's some info to get about unbricking a router if it comes to that, but wait for someone else to tell you what is what first.
Joined: 01 Nov 2013 Posts: 10 Location: China/Shanghai/上海
Posted: Thu Dec 26, 2013 20:03 Post subject:
@AtotehZ
Thx, but in this Thread the problem is already solved.
unbricking the Asus RT-N66U is easier than expected, but there is really some weird behaviour of the reset and the WPS-Button. Finally I worked the whole failed Flashing out and got dd-WRT running.
Posted: Thu Jan 02, 2014 6:19 Post subject: Truly Bricked RT-N66u... I think...
Hello everyone,
I believe I have truly bricked my RT-N66u after attempting to flash DD-WRT WITHOUT going into the unit's "safe mode" and clearing NVRAM out first. I did a 30/30/30, logged into the unit and dropped the DD-WRT file and everything seemed to be working fine, then it just went into limbo.
At this point the device turns on, HOWEVER:
-ON A NORMAL BOOTUP (not holding any buttons in) but the LEDs only light up for Power and the LAN port that a cable is plugged into. NO WIFI lights at all and unit is not reachable via web interface, will not respond to pings with a static set on PC in Win7 or Ubuntu.
-ON A RECOVERY BOOTUP (with WPS button held in) the device powers on and then once booted the following lights come on. Power, Lan1 (where cable is connected), and the two Wifi Band lights come on as well.
Ive tried:
-multiple pin-resets
-safe mode boot
-using the Asus firmware restoration tool
NONE of these methods have worked... Can anyone shed some light here on solving the problem?
I also followed THIS THREAD (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=159756&start=0) to the tee with NO LUCK.
Posted: Thu Jan 02, 2014 15:58 Post subject: Re: Truly Bricked RT-N66u... I think...
shanero1239 wrote:
Hello everyone,
I believe I have truly bricked my RT-N66u after attempting to flash DD-WRT WITHOUT going into the unit's "safe mode" and clearing NVRAM out first. I did a 30/30/30, logged into the unit and dropped the DD-WRT file and everything seemed to be working fine, then it just went into limbo.
At this point the device turns on, HOWEVER:
-ON A NORMAL BOOTUP (not holding any buttons in) but the LEDs only light up for Power and the LAN port that a cable is plugged into. NO WIFI lights at all and unit is not reachable via web interface, will not respond to pings with a static set on PC in Win7 or Ubuntu.
-ON A RECOVERY BOOTUP (with WPS button held in) the device powers on and then once booted the following lights come on. Power, Lan1 (where cable is connected), and the two Wifi Band lights come on as well.
Ive tried:
-multiple pin-resets
-safe mode boot
-using the Asus firmware restoration tool
NONE of these methods have worked... Can anyone shed some light here on solving the problem?
I also followed THIS THREAD (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=159756&start=0) to the tee with NO LUCK.
Thanks in advance!
Shane
which build did you flash? helps to include info like this..
Posted: Fri Jan 03, 2014 1:08 Post subject: Re: Truly Bricked RT-N66u... I think...
Voli wrote:
shanero1239 wrote:
Hello everyone,
I believe I have truly bricked my RT-N66u after attempting to flash DD-WRT WITHOUT going into the unit's "safe mode" and clearing NVRAM out first. I did a 30/30/30, logged into the unit and dropped the DD-WRT file and everything seemed to be working fine, then it just went into limbo.
At this point the device turns on, HOWEVER:
-ON A NORMAL BOOTUP (not holding any buttons in) but the LEDs only light up for Power and the LAN port that a cable is plugged into. NO WIFI lights at all and unit is not reachable via web interface, will not respond to pings with a static set on PC in Win7 or Ubuntu.
-ON A RECOVERY BOOTUP (with WPS button held in) the device powers on and then once booted the following lights come on. Power, Lan1 (where cable is connected), and the two Wifi Band lights come on as well.
Ive tried:
-multiple pin-resets
-safe mode boot
-using the Asus firmware restoration tool
NONE of these methods have worked... Can anyone shed some light here on solving the problem?
I also followed THIS THREAD (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=159756&start=0) to the tee with NO LUCK.
Thanks in advance!
Shane
which build did you flash? helps to include info like this..
---
Voli wrote:
shanero1239 wrote:
Hello everyone,
I believe I have truly bricked my RT-N66u after attempting to flash DD-WRT WITHOUT going into the unit's "safe mode" and clearing NVRAM out first. I did a 30/30/30, logged into the unit and dropped the DD-WRT file and everything seemed to be working fine, then it just went into limbo.
At this point the device turns on, HOWEVER:
-ON A NORMAL BOOTUP (not holding any buttons in) but the LEDs only light up for Power and the LAN port that a cable is plugged into. NO WIFI lights at all and unit is not reachable via web interface, will not respond to pings with a static set on PC in Win7 or Ubuntu.
-ON A RECOVERY BOOTUP (with WPS button held in) the device powers on and then once booted the following lights come on. Power, Lan1 (where cable is connected), and the two Wifi Band lights come on as well.
Ive tried:
-multiple pin-resets
-safe mode boot
-using the Asus firmware restoration tool
NONE of these methods have worked... Can anyone shed some light here on solving the problem?
I also followed THIS THREAD (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=159756&start=0) to the tee with NO LUCK.
Thanks in advance!
Shane
which build did you flash? helps to include info like this..
---
I SOLVED IT!!!
I hope this can help someone, and sorry for my incorrect context in the forum. I'm not very versed in how forums work yet, but I am a professional in the field and hope to utilze them more now aside from just using other people's solutions instead of contributing...
With that said, it ended up that the unit was simply not making it into the default recovery/rescue mode by using the normal method of holding the WPS button and powering up. This was due to an incomplete/incorrect flash of the mini DD-WRT release for this given router.
After 5 hours of research (and no sleep last night), it turns out that I had to do the following in the manner listed below to get into rescue mode:
-First and foremost, the PC NIC Card had to be connected to LAN port 1 of the Asus and the NIC IPv4 settings had to be set to 192.168.1.12 with a subnet mask of 255.255.255.0 and a gateway of 192.168.1.1 (standard stuff here).
-I held the WPS button while adding power, then after ALL the lights blinked once together, I released the WPS button and held in the RESET button for about 5 seconds, then released it.
THIS got the router into the slow blinking CFE rescue mode. once there, I set a constant ping to 192.168.1.1 on my laptop to make sure i was interfacing with the router.
I used the ASUS firmware restoration utility once after it had been sitting a few minutes and the stock (current) firmware upload failed. I then queued up the firmware file again in the ASUS tool but didn't hit upload yet.
I performed the reset again while watching my constant ping and it came back up. In the EXACT instant that i started getting ping replies off of 192.168.1.1, i clicked upload to send the file. The file uploaded and the unit flashed itself. Took about 30 minutes, then I power cycled it after completion with the standard power cable remove and reconnect method.
After that the router was fine and it is running my home network and handling traffic just fine.
Thanks for the insight and again, I hope this helps some other poor jerk that bricks their router like me )
Posted: Wed Mar 05, 2014 17:52 Post subject: Re: Truly Bricked RT-N66u... I think...
Quote:
-I held the WPS button while adding power, then after ALL the lights blinked once together, I released the WPS button and held in the RESET button for about 5 seconds, then released it.
You sir are my king! I honestly thought I'd bricked the router a month out of warranty. Attempting to load a mini build and it didnt reboot after flashing.
I couldn't get it to boot to recovery. I did these steps exactly and lo and behold the CFE Webserver appeared. I uploaded the current default Asus firmware.
As I speak the router has just rebooted and is back up and running.
What a load off my mind!
My router is an RT-N66U B1
(Admin - Can we append the recovery mode steps? This is the 2nd router that I could not get to boot to recovery and even Asus support didn't know these steps as I returned that router.)
)