New EKO Builds 4/7/12 18946 - Supports the new Cisco's

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2, 3, 4, 5, 6, 7, 8, 9  Next
Author Message
Fractal
DD-WRT Guru


Joined: 19 Apr 2010
Posts: 1191

PostPosted: Sat Apr 07, 2012 15:41    Post subject: New EKO Builds 4/7/12 18946 - Supports the new Cisco's Reply with quote
http://www.dd-wrt.com/site/support/other-downloads?path=others%2Feko%2FV24-K26%2Fsvn18946%2F

Please post your results..

I want to mention that in my testing in some cases going from factory to dd-wrt flashed fine, and the only thing that was needed was after at least 5 minutes or so, (you MUST give the router enough time to both complete the flash AND rebuild the variables = 5 to 10 minutes or you will brick it!) a simple power cycle is needed then the router is fully dd-wrt operational..

I wanted to point this out, just incase someone flashed a new build and thought it bricked there router.. AGAIN a simple power cycle about 5 minutes after initial flash has completed and you are golden.

Enjoy,

-Fractal

Edit: Thanks Murrkf

PS.... A special thanks to EKO for the super fast commits to svn to make these available.


Last edited by Fractal on Sat Apr 07, 2012 16:32; edited 1 time in total
Sponsor
GH0
DD-WRT User


Joined: 05 Dec 2008
Posts: 249

PostPosted: Sat Apr 07, 2012 15:56    Post subject: Reply with quote
Is the RT-N66U commits a part of this release, or is this at least supporting the N66U?

Last edited by GH0 on Sat Apr 07, 2012 15:59; edited 1 time in total
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7110

PostPosted: Sat Apr 07, 2012 16:09    Post subject: Reply with quote
GH0 wrote:
Is the RT-N66U commits a part of this release, or is this at least supporting the N66U?


Can you see it in the directory linked to in the first post?

_________________
I'm on a whiskey diet, lost 3 days already
Murrkf
DD-WRT Guru


Joined: 22 Sep 2008
Posts: 11371

PostPosted: Sat Apr 07, 2012 16:21    Post subject: Reply with quote
Please be cautious on uploading these builds. Failing to wait is the principle cause people brick their routers. There needs to be either a visual indicator of completed flashing such as access to the webgui, front lights or pinging, that indicates complete nvram rebuild and safe to reboot, or increase the wait time to ten minutes.

My standard comments:

This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build. (eg: 18946_NEWD-2_K2.6_mega-nv64k.bin).Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build.

_________________
SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor. So See this:
http://i31.tinypic.com/24mz3ms.png

LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."


Last edited by Murrkf on Sat Apr 07, 2012 16:59; edited 1 time in total
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7110

PostPosted: Sat Apr 07, 2012 16:40    Post subject: Reply with quote
RT-N66U 32KB nvram
E900 64KB nvram
E1200v1 64KB nvram
E1200v2 64KB nvram
E1500 64KB nvram
E1550 60KB nvram
E2500 60KB nvram
E3200 60KB nvram
E4200 60KB nvram

Eko can maybe do a clarification about the protection mechanism against flashing wrong type of build.

I take it that routers with 32KB nvram do not understand nv60k or nv64k and will reject upgrade attempts of those.
I assume that an nv60k router does not accet a 32KB nvram build nor does it accept an 64KB nvram build , and that an nv64k router has the same protection against 32KB and 60KB nvram builds.

If my assumption is right then there is no way to brick these routers with the wrong nvram type build as long as you use the web gui for updates.

Eko?

_________________
I'm on a whiskey diet, lost 3 days already
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5772

PostPosted: Sat Apr 07, 2012 17:51    Post subject: Reply with quote
yes, LOM, the GUI upgrade procedure now checks for right build.
_________________
Professional debrick service for EU countries for small fee.
Send inquiries to: debrick at dd-wrt dot si

Have a brick you don't need?

Paypal & Amazon.com gift cards are welcome. Every $ or € counts. Email: donate at dd-wrt dot si
stalonge
DD-WRT Guru


Joined: 21 Jul 2006
Posts: 1288
Location: Fortaleza Ce Brazil

PostPosted: Sat Apr 07, 2012 18:55    Post subject: Reply with quote
working here

I am using 2 E3000 in 5 GHz mode AP + Client bridge ..

18946 M Big

No problem so far



Very Happy Very Happy

_________________
DDwrt ...it rocks ....

1 WZR1750 25179 BS
1 DDx86 VMware 23919
1 E3000 22000+ Kong 4G Squid
1 E3200 24118 4G
1 WRT610Nv2 22000+ Kong
1 WHR G125 Voip 15962
1 WRT150N 23838
1 WHR HP 54 like Repeater Bridge 15962
GH0
DD-WRT User


Joined: 05 Dec 2008
Posts: 249

PostPosted: Sat Apr 07, 2012 21:30    Post subject: Reply with quote
Well, after testing for about three hours I haven't been able to get the build to load successfully on an RT-N66U.

What I initially tried:
Using Internet Explorer, I reset the router to as close as stock as possible, running AP Mode. Downloaded the .trx build for initial flashing. Went to the firmware page and flashed the .trx (dd-wrt.v24-18946_NEWD-2_K2.6_mini_RT-N66U.trx) build. After waiting 15 minutes, I saw that the LED Lights for Power, my LAN port, and Wireless 2.4GHz radio was on. Waited 15 minutes, held the reset button for 20 seconds and then it initiated the router recovery mode on it's own. Turned the router off, waited thirty seconds, and then plugged it back in.

Setup a static IP of 192.168.1.2, and was unable to ping 192.168.1.1 (what I assume should still be the default IP Address after reboot). This would either respond back with one of two (or both messages) Request Timed Out & Destination Host Unreachable. I wasn't able to reach the WebGUI either. Nor did I see any wireless signal broadcasting with the default dd-wrt as I have for my other builds.

Then I tried flashing the .trx build using ASUS's firmware restoration utility, this proceeded to the same issue.

I was able to restore the ASUS firmware after testing this so I still have a functional router, just not using dd-wrt.

I didn't see any point in attempting to flash the .bin image via the firmware restoration utility. I can try TFTP'ing however, it seems to me that it wouldn't work. If I am doing something wrong for this build/router, let me know please and will re-work my test.

I was running the stock ASUS 3.0.0.3.108 firmware when I was attempting to flash the new DD-WRT build.
Fractal
DD-WRT Guru


Joined: 19 Apr 2010
Posts: 1191

PostPosted: Sat Apr 07, 2012 22:24    Post subject: RT-N66U Reply with quote
Ok, I went and took my N66U to factory firmware
3.0.0.3.108 - ASUS Firmware

after that I did the firmware upgrade, did the whole 3 minute wait, everything... the router will reboot and boot up as expected... HOWEVER! even doing hard reset and WPS selection does not allow dd-wrt to load successful. I am able to load dd-wrt and get everything working only if I break into the CFE and issue a nvram erase, then nvram commit.

I have attached serial boot log, and it shows everything I did and how it got to work.. I will go over this with Eko and see if there is something that needs looked at.

Serial log starting at when dd-wrt.v24-18946_NEWD-2_K2.6_mini_RT-N66U.trx successfully loaded:

__________________________
Code:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.04.07
Decompressing...done
tmp_ret= 0


CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五 12月  9 10:10:49 CST 2011 (boyau@localhost.localdomain)
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 - 0x8079D320 (643872)
Data:       0x807330F0 - 0x807363B0 (12992)
BSS:        0x807363B0 - 0x80737320 (3952)
Heap:       0x80737320 - 0x8079B320 (409600)
Stack:      0x8079B320 - 0x8079D320 (8192)
Text:       0x80700000 - 0x807330E8 (209128)

Device eth0:  hwaddr 20-CF-30-B7-57-40, 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 (eko@dd-wrt) (gcc version 4.1.2) #3255 Sat Apr 7 13:35:16 CEST 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: 252912k/131068k available (3522k kernel code, 8936k reserved, 1373k 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
PPPoL2TP kernel driver, V1.0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
et_module_init: passivemode set to 0x0
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=0x1f7fbe
partition size = 2103268
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x01fe0000 : "linux"
0x0019e81c-0x003a0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x01fe0000-0x02000000 : "nvram"
0x003a0000-0x01fe0000 : "ddwrt"
Found a 0MB  serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
    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
get_wl_instance doesnt return the right value 0
No such device
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

DD-WRT v24-sp2 mini (c) 2012 NewMedia-NET GmbH
Release: 04/07/12 (SVN revision: 18946)

DD-WRT login: root
Password:
==========================================================
 
 ____  ___    __        ______ _____         ____  _  _
 | _ \| _ \   \ \      / /  _ \_   _| __   _|___ \| || |
 || | || ||____\ \ /\ / /| |_) || |   \ \ / / __) | || |_
 ||_| ||_||_____\ V  V / |  _ < | |    \ V / / __/|__   _|
 |___/|___/      \_/\_/  |_| \_\|_|     \_/ |_____|  |_|
 
                       DD-WRT v24-sp2
                   http://www.dd-wrt.com
 
==========================================================
Jan  1 00:00:19 login[1002]: root login on 'console'



BusyBox v1.19.4 (2012-04-07 13:33:30 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@DD-WRT:~# reboot
BCMDOG: WDT device closed unexpectedly.  WDT will not stop!
Terminated
root@DD-WRT:~# Restarting system.
Please stand by while rebooting the system...
Decompressing...done
tmp_ret= 0


CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五 12月  9 10:10:49 CST 2011 (boyau@localhost.localdomain)
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 - 0x8079D320 (643872)
Data:       0x807330F0 - 0x807363B0 (12992)
BSS:        0x807363B0 - 0x80737320 (3952)
Heap:       0x80737320 - 0x8079B320 (409600)
Stack:      0x8079B320 - 0x8079D320 (8192)
Text:       0x80700000 - 0x807330E8 (209128)

Device eth0:  hwaddr 20-CF-30-B7-57-40, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Startup canceled
CFE> ^C
CFE> ^C
CFE> ^C
CFE> nvram erase
*** command status = 0
CFE> nvram commit
*** command status = 0
CFE> go
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 (eko@dd-wrt) (gcc version 4.1.2) #3255 Sat Apr 7 13:35:16 CEST 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: 252912k/131068k available (3522k kernel code, 8936k reserved, 1373k 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
PPPoL2TP kernel driver, V1.0
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=0x1f7fbe
partition size = 2103268
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x01fe0000 : "linux"
0x0019e81c-0x003a0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x01fe0000-0x02000000 : "nvram"
0x003a0000-0x01fe0000 : "ddwrt"
Found a 0MB  serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
    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: Asus RT-N66U
loading bcm57xx
loading switch-core
loading switch-robo
roboswitch: Probing device eth0: found a 53125!
/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
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
br0: No such file or directory
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: No such file or directory
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
eth1: Invalid argument
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
device eth1 entered promiscuous mode
br0: 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
BCMDOG: WDT device closed unexpectedly.  WDT will not stop!
Restarting system.
Please stand by while rebooting the system...
Decompressing...done
tmp_ret= 0


CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五 12月  9 10:10:49 CST 2011 (boyau@localhost.localdomain)
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 - 0x8079D320 (643872)
Data:       0x807330F0 - 0x807363B0 (12992)
BSS:        0x807363B0 - 0x80737320 (3952)
Heap:       0x80737320 - 0x8079B320 (409600)
Stack:      0x8079B320 - 0x8079D320 (8192)
Text:       0x80700000 - 0x807330E8 (209128)

Device eth0:  hwaddr 20-CF-30-B7-57-40, 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 (eko@dd-wrt) (gcc version 4.1.2) #3255 Sat Apr 7 13:35:16 CEST 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: 252912k/131068k available (3522k kernel code, 8936k reserved, 1373k 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
PPPoL2TP kernel driver, V1.0
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=0x1f7fbe
partition size = 2103268
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x01fe0000 : "linux"
0x0019e81c-0x003a0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x01fe0000-0x02000000 : "nvram"
0x003a0000-0x01fe0000 : "ddwrt"
Found a 0MB  serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
    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: Asus RT-N66U
loading bcm57xx
loading switch-core
loading switch-robo
roboswitch: Probing device eth0: found a 53125!
/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
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
br0: No such file or directory
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: No such file or directory
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
eth1: Invalid argument
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
device eth1 entered promiscuous mode
br0: 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
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Operation not supported
eth2: Operation not supported
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device vlan2 entered promiscuous mode
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
device vlan2 left promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
submit_button=[index] submit_type=[changepass]
name=[index] type=[changepass] service=[] sleep=[1] action=[5]
Apply:submit_button=[index] service=[index] sleep_time=[0] action=[3]
ApplyTake:submit_button=[index] service=[index] sleep_time=[0] action=[3]
vlan2: No such process
vlan2: No such process
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
bridge br0 is still up; can't delete it
vlan2: No such process
vlan2: No such process
device br0 already exists; can't create bridge with the same name
br0: No such file or directory
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
br0: No such file or directory
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
eth1: Invalid argument
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
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: 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: 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
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Operation not supported
eth2: Operation not supported
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
lo: File exists
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
function stop_splashd not found
function start_splashd not found
vlan2: No such process
gethostbyname: Success
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
jass0
DD-WRT Novice


Joined: 01 Jul 2009
Posts: 3

PostPosted: Sun Apr 08, 2012 0:46    Post subject: Reply with quote
I am unable to connect to SSH (connection refused) while on Brainslayer 18777 it worked fine. I'm running Netgear WNR3500v2/U/L.

Anyone else with this problem?
Gi
DD-WRT Novice


Joined: 08 Apr 2012
Posts: 9

PostPosted: Sun Apr 08, 2012 1:51    Post subject: Reply with quote
Just flashed from stock firmware. No major problems so far.

I had connection refused after enabling SSHd also. I changed to another port and applied the setting.
It responded on that port, I switched back to 22 and applied, it works on 22 now.

Linksys E2500
dd-wrt.v24-18946_NEWD-2_K2.6_mini-e2500.bin
secotton
DD-WRT Novice


Joined: 08 Apr 2012
Posts: 1

PostPosted: Sun Apr 08, 2012 2:07    Post subject: Reply with quote
I was able to flash the firmware no problem, but the 5Ghz radio doesn't show up - should it show up in this build. I've tried a few resets - still doesn't show up.

Linksys E2500
dd-wrt.v24-18946_NEWD-2_K2.6_mini-e2500.bin
wrt310nv2 user
DD-WRT Novice


Joined: 26 Nov 2011
Posts: 12

PostPosted: Sun Apr 08, 2012 3:34    Post subject: Reply with quote
Everything is running fine here flashed dd-wrt.v24-18946_NEWD-2_K2.6_mini.bin and its been running for Time: 02:54:40 up 2:54, load average: 0.03, 0.01, 0.00 without any issues.
yylyyl
DD-WRT Novice


Joined: 06 Mar 2012
Posts: 7

PostPosted: Sun Apr 08, 2012 4:25    Post subject: Reply with quote
Works perfectly on my E1550, thank you
Very Happy
Gi
DD-WRT Novice


Joined: 08 Apr 2012
Posts: 9

PostPosted: Sun Apr 08, 2012 8:59    Post subject: Reply with quote
secotton wrote:
I was able to flash the firmware no problem, but the 5Ghz radio doesn't show up - should it show up in this build. I've tried a few resets - still doesn't show up.

Linksys E2500
dd-wrt.v24-18946_NEWD-2_K2.6_mini-e2500.bin


I had been following Fractal's other E2500 test build thread and didn't see where he had reported 5ghz working in the built firmware, so I wasn't expecting it to. Confirming that it does not work on my E2500 either.

Linksys E2500
dd-wrt.v24-18946_NEWD-2_K2.6_mini-e2500.bin
Goto page 1, 2, 3, 4, 5, 6, 7, 8, 9  Next Display posts from previous:    Page 1 of 9
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

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