Posted: Sat Dec 12, 2009 17:54 Post subject: K2.6 support for WRT54Gv4/GSv3/GL/TM coming soon
I'm building now K2.6 test builds for above mentioned routers.
I have positive results (thx DHC_DarkShadow) running it on TM, so I guess it should run on Gv4, GSv3, GL and TM, as they have basically the same hardware.
Stay tuned...
EDIT: As it seems, only TM will run it. Please don't try it on any other router!
Last edited by Eko on Sat Dec 12, 2009 21:01; edited 1 time in total
Great news! Do you think it will work on other chips or should those of us with jtag/serial not even bother trying? _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
After flashing, the power light blinks, no response to pings.
Continous ping and a power cycle it just goes from hardware error to request time out. No response at all in regards to ttl.
I didn't have serial connected.. If it will help, I can recover and upgrade again with serial.
So.. GL users, do not flash atm.
Eko.. lemme know if you want a serial output during the flash..
Don't know if it is relevant, I guess it is, the 54GL could not run NEWD-2 build under K24 and these K26 builds are also NEWD-2. _________________ Kernel panic: Aiee, killing interrupt handler!
do not try this build on WRT54GS v4
result in a brick (I will JTAG tomorrow...)
also will try if I can get some info about what went wrong using serial console.
nvram_commit(): end
uploading [4096]
function stop_snmpd not found
function stop_pppoeserver not found
function stop_olsrd not found
function stop_openvpn not found
function stop_openvpnserver not found
function stop_freeradius not found
freeram=[3796992] bufferram=[1380352]
The free memory is enough, writing image once.
uploading [8192] ~ Edit (snip)
~[3390780]
uploading [3394876]
write=[3395584]
uploading [3395632]
linux: CRC OK
Writing image to flash, waiting a moment...
write block [0] at [0x00000000]
write block [65536] at [0x00010000] ~
~write block [3342336] at [0x00330000]
uploading [3395632]
erase[0]
erase[65536]
Restarting system.
Please stand by while rebooting the system...
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Tue Jun 20 16:22:41 CST 2006 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
No DPN
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
CPU type 0x29008: 200MHz
Total memory: 16384 KBytes
Total memory used by CFE: 0x80300000 - 0x803A39C0 (670144)
Initialized Data: 0x803398D0 - 0x8033BFE0 (10000)
BSS Area: 0x8033BFE0 - 0x8033D9C0 (6624)
Local Heap: 0x8033D9C0 - 0x803A19C0 (409600)
Stack Area: 0x803A19C0 - 0x803A39C0 (8192)
Text (code) segment: 0x80300000 - 0x803398D0 (235728)
Boot area (physical): 0x003A4000 - 0x003E4000
Relocation Factor: I:00000000 - D:00000000
Boot version: ==> v3.7
The boot is CFE
mac_init(): Find mac [00:21:29:C3:34:B9] in location 0
Nothing...
eou_key_init(): Find key pair in location 4
Update eou device id from [] to [VDOWT7NJ]
Update eou public key from
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Tue Jun 20 16:22:41 CST 2006 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
No DPN
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
CPU type 0x29008: 200MHz
Total memory: 16384 KBytes
Total memory used by CFE: 0x80300000 - 0x803A39C0 (670144)
Initialized Data: 0x803398D0 - 0x8033BFE0 (10000)
BSS Area: 0x8033BFE0 - 0x8033D9C0 (6624)
Local Heap: 0x8033D9C0 - 0x803A19C0 (409600)
Stack Area: 0x803A19C0 - 0x803A39C0 (8192)
Text (code) segment: 0x80300000 - 0x803398D0 (235728)
Boot area (physical): 0x003A4000 - 0x003E4000
Relocation Factor: I:00000000 - D:00000000
Boot version: v3.7
The boot is CFE
mac_init(): Find mac [00:21:29:C3:34:B9] in location 0
Nothing...
eou_key_init(): Find key pair in location 4
The eou device id is same
The eou public key is same
The eou private key is same
Device eth0: hwaddr 00-21-29-C3-34-B9, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3856 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Tue Jun 20 16:22:41 CST 2006 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
No DPN
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
CPU type 0x29008: 200MHz
Total memory: 16384 KBytes
Total memory used by CFE: 0x80300000 - 0x803A39C0 (670144)
Initialized Data: 0x803398D0 - 0x8033BFE0 (10000)
BSS Area: 0x8033BFE0 - 0x8033D9C0 (6624)
Local Heap: 0x8033D9C0 - 0x803A19C0 (409600)
Stack Area: 0x803A19C0 - 0x803A39C0 (8192)
Text (code) segment: 0x80300000 - 0x803398D0 (235728)
Boot area (physical): 0x003A4000 - 0x003E4000
Relocation Factor: I:00000000 - D:00000000
Boot version: v3.7
The boot is CFE
mac_init(): Find mac [00:21:29:C3:34:B9] in location 0
Nothing...
eou_key_init(): Find key pair in location 4
The eou device id is same
The eou public key is same
The eou private key is same
Device eth0: hwaddr 00-21-29-C3-34-B9, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3856 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
********************Sticks again here*****************************
I have a V3 but that is not supported by newd-2 either ..
Eko.. My router is bricked.. What am I going to do? _________________ [Moderator Deleted]
Is NEWD k2.6 compatible? _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I don't know if this is the right topic to post this, but since it's about older WRT54G models, will there be a micro k2.6 build at all ever? Or is k2.6 too big.
Joined: 21 Jul 2006 Posts: 1898 Location: Fortaleza Ce Brazil
Posted: Sat Dec 12, 2009 20:37 Post subject:
barryware wrote:
A GL does not like this build much (mini) ....
After flashing, the power light blinks, no response to pings.
Continous ping and a power cycle it just goes from hardware error to request time out. No response at all in regards to ttl.
I didn't have serial connected.. If it will help, I can recover and upgrade again with serial.
So.. GL users, do not flash atm.
Eko.. lemme know if you want a serial output during the flash..
GL like to be reborn using factory firmware ... go to linksys site ..download the properly firmware and try to TFTP it .. i have fixed many times one WRT54GL using this methods
Play with power plug and reset while TFTP it ..works in this way to me
_________________ DDwrt ...it rocks ....
1 R7800 54420 AP Wireguard webserver JFFS SAMBA FTP usb HD Mesh
1 R7800 54420 Cli Mesh
1 WZR1750 54389 AP Webserver Samba Wireguard
1 TP link Archer C7v5 54420 Cli Mesh
1 DD x86_64 48296 Gateway Samba Ftp Webserver
Last edited by stalonge on Sat Dec 12, 2009 20:40; edited 1 time in total
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Sat Dec 12, 2009 20:38 Post subject:
4512jth wrote:
I don't know if this is the right topic to post this, but since it's about older WRT54G models, will there be a micro k2.6 build at all ever? Or is k2.6 too big.
Dude.... that is what this thread is about. We are just starting testing.. I believe LOM is correct in regards to newd-2 bricking the router(s). It is possible that the K26 has nothing to do with it.
I have other routers that will run newd-2 but this build was for the "G" series routers. _________________ [Moderator Deleted]
....
