Joined: 25 Feb 2009 Posts: 104 Location: Peoria Illinois
Posted: Fri Mar 06, 2009 5:46 Post subject:
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3856 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
CPU revision is: 00029006
Linux version 2.4.36 (root@dd-wrt) (gcc version 3.4.6 (OpenWrt-2.0)) #340 Sun Jul 27 20:07:55 CEST 2008
Setting the PFC to its default value
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
CPU: BCM4704 rev 9 at 264 MHz
Using 132.000 MHz high precision timer.
Calibrating delay loop... 263.78 BogoMIPS
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-0 with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 3) is a 16550A
PCI: Setting latency timer of device 00:01.0 to 64
PCI: Setting latency timer of device 00:02.0 to 64
PCI: Setting latency timer of device 01:02.0 to 64
PCI: Enabling device 01:02.0 (0004 -> 0006)
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
Amd/Fujitsu Extended Query Table v1.3 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x5c7fa8
partition size = 6105260
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x0011d754-0x006f0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : "nvram"
0x006f0000-0x007f0000 : "ddwrt"
sflash not supported on this router
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Booting device: Asus WL-500W
nvram_commit(): end
sh: cannot create /proc/sys/net/ipv4/tcp_congestion_control: nonexistent directory
nvram_commit(): end
br0: Bad file descriptor
device eth0 entered promiscuous mode
br0: Bad file descriptor
eth2: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
channel 6, val 20
800, 300, 6
spec 2B06
eth2: Invalid argument
eth2: Invalid argument
eth2: Operation not supported
eth2: Operation not supported
device eth2 entered promiscuous mode
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
device eth1 entered promiscuous mode
device eth1 left promiscuous mode
sh: /tmp/.rc_startup: not found
The Milkfish Router Services
ERROR: Necessary service setting not found: milkfish_username - aborting.
The Milkfish Router Services
Restoring SIP ddsubscriber database from NVRAM...
Empty.
The Milkfish Router Services
Restoring SIP ddaliases database from NVRAM...
Empty. _________________ 2x WRT54G2 v1
1x Asus WL-500w
To think, after all this time, all our chats together you still don't trust me. There's hope for you yet, doctor.
Joined: 25 Feb 2009 Posts: 104 Location: Peoria Illinois
Posted: Fri Mar 06, 2009 5:49 Post subject:
its booted, I'm going to flash a new image.. I had to rig it.. with clips and this USB thing, that USB board is to small.. Thanks Donny, Red and Barryware.. Operation is a success!
Im going to flash the second to the newest MEGA build.. any objections? _________________ 2x WRT54G2 v1
1x Asus WL-500w
To think, after all this time, all our chats together you still don't trust me. There's hope for you yet, doctor.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Fri Mar 06, 2009 11:52 Post subject:
pock wrote:
its booted, I'm going to flash a new image.. I had to rig it.. with clips and this USB thing, that USB board is to small.. Thanks Donny, Red and Barryware.. Operation is a success!
Im going to flash the second to the newest MEGA build.. any objections?
Don't use the newest. Flash first using asus restoration utility with mini_trx.bin, do a 30/30/30....then flash with web gui using mega.bin
follow the wiki instructions(I edited them yesterday)
Congrats on getting this far....that was the hard part.
redhawk _________________ The only stupid question....is the unasked one.
Joined: 13 Nov 2008 Posts: 5266 Location: CENTRAL Midnowhere
Posted: Fri Mar 06, 2009 13:53 Post subject:
Use 11296 first. I think it is stable for that unit. 11650 also might be stable, but it is still, in my view, not as rock solid as 11296 has been. You could do both, and should at some point, but I would do 11296 first. This fellow reports using 11296 on a 500W without problems:
Joined: 13 Nov 2008 Posts: 5266 Location: CENTRAL Midnowhere
Posted: Fri Mar 06, 2009 15:00 Post subject:
Donny wrote:
What did we learn?
Uhm...Pock....I didn't actually include you in this "we"... (I actually only meant Redhawk! ) _________________ Warning: I'm "out of my element!"
http://www.youtube.com/watch?v=MjYJ7zZ9BRw&NR=1
Joined: 25 Feb 2009 Posts: 104 Location: Peoria Illinois
Posted: Fri Mar 06, 2009 15:28 Post subject:
Right, well in the interest of the public, and anyone who kept up with this thread, don't use the Micro USB board _________________ 2x WRT54G2 v1
1x Asus WL-500w
To think, after all this time, all our chats together you still don't trust me. There's hope for you yet, doctor.
Joined: 13 Nov 2008 Posts: 5266 Location: CENTRAL Midnowhere
Posted: Fri Mar 06, 2009 16:28 Post subject:
redhawk0 wrote:
Me?.....I didn't learn very much....it sounds like you guys did the majority of the learning
redhawk
Okay...Well...could you at least explain what WE learned?? (And now I mean all of us).
Pock...Are you up and running? What build? Have you rebooted? What is your boot wait set at? Have you replicated the problem? _________________ Warning: I'm "out of my element!"
http://www.youtube.com/watch?v=MjYJ7zZ9BRw&NR=1
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Fri Mar 06, 2009 16:44 Post subject:
Serial cable is required to possibly debrick units without JTAG port.
Serial cable can be either USB or DB9 connection type.
It must be capable of doing voltage level shift to +3.3V not just +5V.
There are 4 connections that are required for Serial to function properly. +3.3V, GND, Tx and Rx.
Some boards are NOT marked with pin designation. You must ohm out your power and GND in this case so things don't get connected backwards and blow out your cable chip. Then you can guess at the last 2 Rx and Tx lines.
The cable has Rx and Tx but these are relative to the cable...so Rx line needs to be connected to the routers Tx line....because the router's designator's are relative to the router.
So Tx and Rx get crossed for proper connection.
On routers that have 2 Serial ports (Tx0, Tx1 and Rx0, Rx1) you generally use the zero port for your connections (I've not seen a router yet that you connect up to the "one" side)
Once you make the connection setup your computer Serial terminal display for 115200 8-N-1. Plug in your router and you should see text on the screen. You can monitor the tty output of the CFE as it is booting...or break in using Cntl-C and enter low level commands to try to fix things.
The most useful for our purpose is the
"nvram show" and "nvram erase" commands.
Once the nvram is erased...type "reboot" or power cycle it....now tftp your firmware....or just let it boot up if firmware was previously loaded properly.
So...that's it in a nutshell....any questions/comments....just ask.
But before someone asks....NO you can NOT reload a CFE if it is damaged through the Serial port...a working CFE has to be running in order to get CFE commands....so loading a CFE without a CFE is impossible.
redhawk _________________ The only stupid question....is the unasked one.
Last edited by redhawk0 on Fri Mar 06, 2009 17:08; edited 1 time in total
Joined: 13 Nov 2008 Posts: 5266 Location: CENTRAL Midnowhere
Posted: Fri Mar 06, 2009 16:52 Post subject:
And, I take it that since the CFE was fine, and the router was stuck on 192.168.1.5 (shows in Pocks output) somehow the SP1 nvram has gotten "stuck" with that SP1 build.
There is contrary information of whether it gets stuck at any rebooting (which is what would have happened here when Pock changed the IP address...unit would have tried to reboot) or if it happens only when USB is enabled...(which might also be the same issue if that also causes a reboot.) _________________ Warning: I'm "out of my element!"
http://www.youtube.com/watch?v=MjYJ7zZ9BRw&NR=1
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Fri Mar 06, 2009 16:57 Post subject:
Donny wrote:
And, I take it that since the CFE was fine, and the router was stuck on 192.168.1.5 (shows in Pocks output) somehow the SP1 nvram has gotten "stuck" with that SP1 build.
There is contrary information of whether it gets stuck at any rebooting (which is what would have happened here when Pock changed the IP address...unit would have tried to reboot) or if it happens only when USB is enabled...(which might also be the same issue if that also causes a reboot.)
Yeah...something was probably wrong with how the unit sensed the Reset button (maybe the GPIO variable was bad)....so the NVRAM setting for the IP address was always used....clearing the nvram removed the bad parameters....then a reboot reset the correct parameters for the router.
Remember...with every build of dd-wrt some of these variables change (my suspicion is that the GPIO variable for the reset button was one of them...so a 30/30/30 won't work in this case)...that is why a hard reset is required when loading. It cleans out the "old" variable so the new ones take effect at boot up.
redhawk _________________ The only stupid question....is the unasked one.