Asus RT-N66U

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... 74, 75, 76 ... 167, 168, 169  Next
Author Message
billias
DD-WRT Novice


Joined: 22 Jun 2012
Posts: 20

PostPosted: Tue Nov 27, 2012 23:43    Post subject: Reply with quote
Any suggestions?
Sponsor
BasCom
DD-WRT Guru


Joined: 29 Jul 2009
Posts: 1378
Location: Germany

PostPosted: Tue Nov 27, 2012 23:47    Post subject: Reply with quote
that happend to me:


==========================================================

____ ___ __ ______ _____ ____ _ _
| _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || |
|| | || ||____\ \ /\ / /| |_) || | \ \ / / __) | || |_
||_| ||_||_____\ V V / | _ < | | \ V / / __/|__ _|
|___/|___/ \_/\_/ |_| \_\|_| \_/ |_____| |_|

DD-WRT v24-sp2
http://www.dd-wrt.com

==========================================================


BusyBox v1.20.2 (2012-10-31 23:16:38 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@gateway:~#
root@gateway:~# vconfig add eth0 6
root@gateway:~# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
vlan1 | 1 | eth0
eth0.0007 | 7 | eth0
eth0.6 | 6 | eth0
root@gateway:~# ifconfig
br0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
inet addr:192.168.0.250 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11964319 errors:0 dropped:0 overruns:0 frame:0
TX packets:6718410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1472093731 (1.3 GiB) TX bytes:829021154 (790.6 MiB)

br0:0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18338567 errors:0 dropped:0 overruns:0 frame:0
TX packets:11109079 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2611658643 (2.4 GiB) TX bytes:1179123744 (1.0 GiB)
Interrupt:4 Base address:0x2000

eth0.0007 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6472147 errors:0 dropped:0 overruns:0 frame:0
TX packets:4495089 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:734860631 (700.8 MiB) TX bytes:483736205 (461.3 MiB)

eth1 Link encap:Ethernet HWaddr 50:46:5D:6E:32:12
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19197 errors:0 dropped:0 overruns:0 frame:1092756
TX packets:499979 errors:6803499 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26660420 (25.4 MiB) TX bytes:427139492 (407.3 MiB)
Interrupt:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 50:46:5D:6E:32:14
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:155262 errors:0 dropped:0 overruns:0 frame:35399
TX packets:1873839 errors:5406956 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43849787 (41.8 MiB) TX bytes:2306490985 (2.1 GiB)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2367 (2.3 KiB) TX bytes:2367 (2.3 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:87.147.25.21 P-t-P:87.186.224.142 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1476 Metric:1
RX packets:813829 errors:0 dropped:0 overruns:0 frame:0
TX packets:652192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:348366381 (332.2 MiB) TX bytes:62730878 (59.8 MiB)

tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.254.3 P-t-P:192.168.254.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:15848 errors:0 dropped:0 overruns:0 frame:0
TX packets:11122 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:16625238 (15.8 MiB) TX bytes:1558232 (1.4 MiB)

vlan1 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11865038 errors:0 dropped:0 overruns:0 frame:0
TX packets:6613990 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1545610418 (1.4 GiB) TX bytes:695387539 (663.1 MiB)

root@gateway:~# ifconfig eth0.6 up
root@gateway:~# ifconfig

br0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
inet addr:192.168.0.250 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11964565 errors:0 dropped:0 overruns:0 frame:0
TX packets:6718645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1472109910 (1.3 GiB) TX bytes:829042665 (790.6 MiB)

br0:0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18338994 errors:0 dropped:0 overruns:0 frame:0
TX packets:11109503 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2611695564 (2.4 GiB) TX bytes:1179162839 (1.0 GiB)
Interrupt:4 Base address:0x2000

eth0.0007 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6472328 errors:0 dropped:0 overruns:0 frame:0
TX packets:4495278 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:734872703 (700.8 MiB) TX bytes:483752849 (461.3 MiB)

eth0.6 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth1 Link encap:Ethernet HWaddr 50:46:5D:6E:32:12
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19197 errors:0 dropped:0 overruns:0 frame:1092756
TX packets:499982 errors:6803499 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26660420 (25.4 MiB) TX bytes:427139698 (407.3 MiB)
Interrupt:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 50:46:5D:6E:32:14
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:155262 errors:0 dropped:0 overruns:0 frame:35399
TX packets:1873842 errors:5406956 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43849787 (41.8 MiB) TX bytes:2306491191 (2.1 GiB)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2367 (2.3 KiB) TX bytes:2367 (2.3 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:87.147.25.21 P-t-P:87.186.224.142 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1476 Metric:1
RX packets:814005 errors:0 dropped:0 overruns:0 frame:0
TX packets:652376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:348376097 (332.2 MiB) TX bytes:62742568 (59.8 MiB)

tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.254.3 P-t-P:192.168.254.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:15848 errors:0 dropped:0 overruns:0 frame:0
TX packets:11122 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:16625238 (15.8 MiB) TX bytes:1558232 (1.4 MiB)

vlan1 Link encap:Ethernet HWaddr 50:46:5D:6E:32:10
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11865284 errors:0 dropped:0 overruns:0 frame:0
TX packets:6614225 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1545627581 (1.4 GiB) TX bytes:695409990 (663.1 MiB)

root@gateway:~#


have no, since upgrading on 64k. you may allow me access to your device to have a look around with a dumb password.

_________________
RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
billias
DD-WRT Novice


Joined: 22 Jun 2012
Posts: 20

PostPosted: Tue Nov 27, 2012 23:49    Post subject: Reply with quote
Tommorrow upgrade on 64 then. And we talk again.
BasCom
DD-WRT Guru


Joined: 29 Jul 2009
Posts: 1378
Location: Germany

PostPosted: Tue Nov 27, 2012 23:52    Post subject: Reply with quote
but be warned: flash back to ASUS STOCK first.
Dont upgrade to 64k CFE until DD-WRT 32k is installed: BRICKED UNIT. Also do not flash 64k DD-WRT onto 32k CFE: BRICKED UNIT.

Go back to Asus Stock first, then upgrade your CFE to 64K.
Reboot and reset to defaults. Then flash 64k FRACTAL Build. Be warned. Do it on your own risk !!


read here in CFE Thread
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=163479&highlight=

_________________
RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )


Last edited by BasCom on Wed Nov 28, 2012 2:37; edited 2 times in total
MoreHP
DD-WRT Novice


Joined: 17 Nov 2012
Posts: 8

PostPosted: Wed Nov 28, 2012 2:57    Post subject: Reply with quote
barryware wrote:
using your serial console.. stop the boot via ctrl-c at power up.

then just flash newest STOCK firmware (or a new merlin build) initiating the flash via serial console and use tftp via lan cable to send the firmware.

I have posted the procedure many times.


@barryware - I have tried this procedure many times and also have recently resorted to trying to get the lan ports working using nvram set lan1_ipaddr="192.168.1.1" as well as other nvram values and then commit.

The first reboot of the CFE goes like this: (note the et0 line)

Code:
CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五  9月 14 17:47:35 CST 2012 (boyau@localhost)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.127
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem:    0x80700000 - 0x80839350 (1282896)
Data:       0x80733120 - 0x807363E0 (12992)
BSS:        0x807363E0 - 0x80737350 (3952)
Heap:       0x80737350 - 0x80837350 (1048576)
Stack:      0x80837350 - 0x80839350 (8192)
Text:       0x80700000 - 0x80733118 (209176)

Device eth0:  hwaddr 50-46-5D-6C-2C-98, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Null Rescue Flag.
Loader:raw Filesys:tftp Dev:eth0 File:: Options:(null)
Loading: TFTP Server.
Failed.
Could not load :: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3916 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Linux version 2.6.24.111 (compiler@chaos) (gcc version 4.1.2) #10 Wed Oct 31 21:49:26 PDT 2012
CPU revision is: 00019749
Determined physical RAM map:
 memory: 07fff000 @ 00000000 (usable)
 memory: 08000000 @ 87fff000 (usable)
Zone PFN ranges:
  Normal          0 ->   131072
  HighMem    131072 ->   589823
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0:        0 ->    32767
    0:   557055 ->   589823
Built 1 zonelists in Zone order.  Total pages: 65535
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: 512 (order: 9, 2048 bytes)
CPU: BCM5300 rev 1 at 600 MHz
Using 300.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 252940k/131068k available (3490k kernel code, 8904k reserved, 1369k data, 188k init, 131072k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
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: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
highmem bounce pool size: 64 pages
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 = 8) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 8) 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 <maxk@qualcomm.com>
et_module_init: passivemode set to 0x0
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002201
Amd/Fujitsu Extended Query Table at 0x0040
Physically mapped flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x2000000 at 0x1c000000
bootloader size: 262144
nvram size: 32768
Physically mapped flash: Filesystem type: squashfs, size=0x617ca0
partition size = 6431744
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x01fe0000 : "linux"
0x0019dc00-0x007c0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x01fe0000-0x02000000 : "nvram"
0x007c0000-0x01fe0000 : "ddwrt"
Found a 0MB  serial flash
sflash: found no supported devices
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 (4096 buckets, 16384 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 <deri@ntop.org>
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 <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 188k freed
start service
starting Architecture code for broadcom
done
Booting device: Linksys WRT54G/GL/GS
loading switch-core
loading switch-robo
roboswitch: Probing device eth0: found a 53125!
boardflags are 0x0000
[USB] checking...
Some error found, we want to reboot!.....................
/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
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
nbw = 20
eth1: Argument list too long
eth1: Invalid argument
eth1: Invalid argument
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth2: Operation not supported
wl1.1: No such device
wl1.2: No such device
wl1.3: No such device
eth2: Operation not permitted
eth2: Invalid argument
eth2: Invalid argument
eth2: Argument list too long
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Operation not supported
eth2: Operation not supported
eth2: Operation not supported
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
BCMDOG: WDT device closed unexpectedly.  WDT will not stop!
Restarting system.
Please stand by while rebooting the system...
Decompressing...done
tmp_ret= 0


The next boot goes like this: (note: no et0 line)

Code:
CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五  9月 14 17:47:35 CST 2012 (boyau@localhost)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem:    0x80700000 - 0x80839350 (1282896)
Data:       0x80733120 - 0x807363E0 (12992)
BSS:        0x807363E0 - 0x80737350 (3952)
Heap:       0x80737350 - 0x80837350 (1048576)
Stack:      0x80837350 - 0x80839350 (8192)
Text:       0x80700000 - 0x80733118 (209176)

Committing NVRAM...done
Null Rescue Flag.
Loader:raw Filesys:tftp Dev:(null) File:: Options:(null)
Loading: TFTP Server.
Failed.
Could not load :: Error
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3916 bytes read
Entry at 0x80001000
Starting program at 0x80001000


I have had tfpt ready to go on WinXP command line, with my ip set static to 192.168.1.10

Code:
tftp -i 192.168.1.1 put RT-N66U_3.0.0.4_260.trx


It just times-out. I have faith in the tftp procedure, so I have tried many, many times. To no avail.
Nebudchanezzer
DD-WRT User


Joined: 09 Apr 2012
Posts: 60

PostPosted: Wed Nov 28, 2012 5:46    Post subject: Reply with quote
@ MoreHP:

CFE wrote:

CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五 9月 14 17:47:35 CST 2012 (boyau@localhost)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.127
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem: 0x80700000 - 0x80839350 (1282896)
Data: 0x80733120 - 0x807363E0 (12992)
BSS: 0x807363E0 - 0x80737350 (3952)
Heap: 0x80737350 - 0x80837350 (1048576)
Stack: 0x80837350 - 0x80839350 (8192)
Text: 0x80700000 - 0x80733118 (209176)

Device eth0: hwaddr 50-46-5D-6C-2C-98, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
Loader:raw Filesys:tftp Dev:eth0 File:: Options:(null)
Loading: TFTP Server.
Failed.


You should use ctrl^c to stop the boot somewhere around here.

EDIT: To me that looked liked you tried to do a regular boot, try just booting into recovery-mode.
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 13049
Location: Behind The Reset Button

PostPosted: Wed Nov 28, 2012 14:23    Post subject: Reply with quote
I heve posted this many times.. Stop the boot using ctrl-c.. You will be at the cfe prompt, then force the flash via tftp.. Toy can see below, the lan ports are initialized.. If not, you can bring them up using ifconfig.

barryware wrote:

Committing NVRAM...done
Waiting for reset button release...donDecompressing...done
tmp_ret= 0


CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五 9月 14 17:47:35 CST 2012 (boyau@localhost)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.127
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem: 0x80700000 - 0x80839350 (1282896)
Data: 0x80733120 - 0x807363E0 (12992)
BSS: 0x807363E0 - 0x80737350 (3952)
Heap: 0x80737350 - 0x80837350 (1048576)
Stack: 0x80837350 - 0x80839350 (8192)
Text: 0x80700000 - 0x80733118 (209176)

Device eth0: hwaddr C8-00-00-00-00-00, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set

Startup canceled
CFE> ^C
CFE> ^C
CFE>


now you have stopped the boot. Now start the routers tftp client and send the firmware.

cfe> flash -ctheader : flash1.trx [enter]

now launch tftp

when you are back at the cfe prompt, erase nvram, then power cycle the router. It will take some time for the router to flash.

cfe> nvram erase [enter]

now power cycle the router.

it will boot at least three times.

_________________
[Moderator Deleted] Shocked
MoreHP
DD-WRT Novice


Joined: 17 Nov 2012
Posts: 8

PostPosted: Wed Nov 28, 2012 16:25    Post subject: Reply with quote
@ barryware
I have followed your instructions exactly (-noheader rather than -ctheader)... many times over now just to be sure. Also tried tearing everything down, rebooting and reconnecting everything.
My serial console output looks exactly as your example does, aside from the hwaddr values. I stop the boot with ctrl-c at the same place.
At the prompt CFE> flash -noheader : flash1.trx
Within one second of pressing enter, I press enter on the WinXP command line tftp utility.
Looks like this: tftp -i 192.168.1.1 put RT-N66U_3.0.0.4_260.trx

After ~5seconds, the CFE reports...
Reading :: TFTP Server
Failed.: Timeout occured
*** command status = -21

After ~30 seconds the WinXP tftp reports...
Timeout occurred

@ Nebudchanezzer

I've tried the recovery-mode procedure as well...
The CFE just continually reports (as viewed in the serial console)...

Hello!! Enter Rescue Mode: (by Force)

Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured

All the while I'm initiating tftp transfer by WinXP tftp command line. Same result as with boot-halting procedure.

I'm not experienced enough to draw conclusions from this, however, I suspect that reason the tftp transfer is not successful, may be related to the router's lan ports not being available... even pinging 192.168.1.1 fails at all times. Also, pinging from the router to the PC (192.168.1.10) fails. Yes, I've checked my cable and also switched it for others, all of which are known to be working.
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 13049
Location: Behind The Reset Button

PostPosted: Wed Nov 28, 2012 16:27    Post subject: Reply with quote
MoreHP wrote:
@ barryware
I have followed your instructions exactly (-noheader rather than -ctheader)... many times over now just to be sure. Also tried tearing everything down, rebooting and reconnecting everything.
My serial console output looks exactly as your example does, aside from the hwaddr values. I stop the boot with ctrl-c at the same place.
At the prompt CFE> flash -noheader : flash1.trx
Within one second of pressing enter, I press enter on the WinXP command line tftp utility.
Looks like this: tftp -i 192.168.1.1 put RT-N66U_3.0.0.4_260.trx

After ~5seconds, the CFE reports...
Reading :: TFTP Server
Failed.: Timeout occured
*** command status = -21

After ~30 seconds the WinXP tftp reports...
Timeout occurred

@ Nebudchanezzer

I've tried the recovery-mode procedure as well...
The CFE just continually reports (as viewed in the serial console)...

Hello!! Enter Rescue Mode: (by Force)

Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured

All the while I'm initiating tftp transfer by WinXP tftp command line. Same result as with boot-halting procedure.

I'm not experienced enough to draw conclusions from this, however, I suspect that reason the tftp transfer is not successful, may be related to the router's lan ports not being available... even pinging 192.168.1.1 fails at all times. Also, pinging from the router to the PC (192.168.1.10) fails. Yes, I've checked my cable and also switched it for others, all of which are known to be working.

use the tftp utility found on the forum (tftp2.exe). do not use the windows command line.

_________________
[Moderator Deleted] Shocked
MoreHP
DD-WRT Novice


Joined: 17 Nov 2012
Posts: 8

PostPosted: Wed Nov 28, 2012 17:16    Post subject: Reply with quote
barryware wrote:
MoreHP wrote:
@ barryware
I have followed your instructions exactly (-noheader rather than -ctheader)... many times over now just to be sure. Also tried tearing everything down, rebooting and reconnecting everything.
My serial console output looks exactly as your example does, aside from the hwaddr values. I stop the boot with ctrl-c at the same place.
At the prompt CFE> flash -noheader : flash1.trx
Within one second of pressing enter, I press enter on the WinXP command line tftp utility.
Looks like this: tftp -i 192.168.1.1 put RT-N66U_3.0.0.4_260.trx

After ~5seconds, the CFE reports...
Reading :: TFTP Server
Failed.: Timeout occured
*** command status = -21

After ~30 seconds the WinXP tftp reports...
Timeout occurred

@ Nebudchanezzer

I've tried the recovery-mode procedure as well...
The CFE just continually reports (as viewed in the serial console)...

Hello!! Enter Rescue Mode: (by Force)

Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured
Reading :: TFPT Server.
Failed.: Timeout occured

All the while I'm initiating tftp transfer by WinXP tftp command line. Same result as with boot-halting procedure.

I'm not experienced enough to draw conclusions from this, however, I suspect that reason the tftp transfer is not successful, may be related to the router's lan ports not being available... even pinging 192.168.1.1 fails at all times. Also, pinging from the router to the PC (192.168.1.10) fails. Yes, I've checked my cable and also switched it for others, all of which are known to be working.

use the tftp utility found on the forum (tftp2.exe). do not use the windows command line.


Ok. I've tried the tftp2 utility with both the recovery mode and serial boot-halt procedures...
It reports...
Unable to get responses from the server.
Retry (3/3) ...

Server is set to: 192.168.1.1
Password is left blank
File is set to the location of the latest ASUS firmware file on my harddrive.
3 retry
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 13049
Location: Behind The Reset Button

PostPosted: Wed Nov 28, 2012 17:31    Post subject: Reply with quote
MoreHP wrote:
Ok. I've tried the tftp2 utility with both the recovery mode and serial boot-halt procedures...
It reports...
Unable to get responses from the server.
Retry (3/3) ...

Server is set to: 192.168.1.1
Password is left blank
File is set to the location of the latest ASUS firmware file on my harddrive.
3 retry

I don't know what to tell you. I have bricked mine many, many times and never had a problem recovering it.

try:

stop the boot
erase nvram
power cycle and stop the boot again (don't let it boot or write default nvram)
now try to tftp.

if that won't work, I have no further advice. The problem may be with your pc (firewall, av software, etc) and not the router.

_________________
[Moderator Deleted] Shocked
AlexHighTower
DD-WRT User


Joined: 16 Aug 2011
Posts: 69

PostPosted: Fri Nov 30, 2012 7:52    Post subject: Reply with quote
Hello,

I flashed DD-WRT (32k) as wiki says but I have two problems...
Can some one help me with?

1. I can't install opt on microsd card inserted into embedded socket inside box or using usb converter... I've tried 4 different cards with same symptoms:
- tried to format to ext2 and ext3
- start prep_optware, it starts to download files and expand them, I see bin/etc/usr... folder inside /opt dir
- in 99% of cases it gets stacked on installing opt-libc, simply nothing happens...
- if to reboot router there is only one empty dir /opt/etc/init.d

2. I can't get wi-fi AP 5MHZ working...
- tried to set "network mode" to each of types separately - router is not visible
- if I try to select channel manually - I can select it from drop down list, but when I press "apply" button it auto changed to "Auto" and nothing happens...

so, what to do?

thnx.

_________________
TP-Link TL-WR1043ND: DD-WRT v24-sp2 (08/07/10) std - build 14896
Asus RT-N16: DD-WRT build 19545 (kingmod)
BasCom
DD-WRT Guru


Joined: 29 Jul 2009
Posts: 1378
Location: Germany

PostPosted: Fri Nov 30, 2012 10:09    Post subject: Reply with quote
@alex: ext2 / ext3 broken. see trac ticket #2580

set network to NA mixed, save, apply. channel list will appear.

_________________
RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
AlexHighTower
DD-WRT User


Joined: 16 Aug 2011
Posts: 69

PostPosted: Fri Nov 30, 2012 12:33    Post subject: Reply with quote
BasCom wrote:
@alex: ext2 / ext3 broken. see trac ticket #2580

wow Sad

BasCom wrote:
@alex:set network to NA mixed, save, apply. channel list will appear.

I did it, also reboot to be on safe side
List of channels is visible and available, I can select channel, but after pressing "save" button it automatically changed to "auto"...
In "auto" mode my mac book pro doesn't see my 5ghz network (

_________________
TP-Link TL-WR1043ND: DD-WRT v24-sp2 (08/07/10) std - build 14896
Asus RT-N16: DD-WRT build 19545 (kingmod)
BasCom
DD-WRT Guru


Joined: 29 Jul 2009
Posts: 1378
Location: Germany

PostPosted: Fri Nov 30, 2012 12:54    Post subject: Reply with quote
@alex? what is configured? maybe you ran out of nvram ?
check !

_________________
RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
Goto page Previous  1, 2, 3 ... 74, 75, 76 ... 167, 168, 169  Next Display posts from previous:    Page 75 of 169
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT 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