Ah I uploaded my through the GUI. Are you using the WRT54Gv8.x compressor?
Code:
CFE version 1.0.37 for BCM947XX
I think your using the wrong CFE compressor
I used CFE_Updater-Gv8.X-comp.bin in GUI.
The CFE updated OK but it just won't automatically flash from tftp during the first boot. i can manually flash the micro plus kernel.
update:
just tried CFE-Updater-Gv8-GSv7-v3.bin through gui, also showing
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Wed Oct 28, 2009 22:08 Post subject:
beyondwind wrote:
I used CFE_Updater-Gv8.X-comp.bin in GUI.
The CFE updated OK but it just won't automatically flash from tftp during the first boot. i can manually flash the micro plus kernel.
update:
just tried CFE-Updater-Gv8-GSv7-v3.bin through gui, also showing
Code:
CFE version 1.0.37 for BCM947XX
I just redid mine again, Initial TFTP of the compressor.bin I cannot get to got(same as 7.2),but it does update through the GUI and after waiting 3 min.s and the power cycle TFTPing the firmware on goes without a hitch both GS 7.0 and 7.2
What is the first four digits of the serial number on your v7.0? _________________ The New Me
I used CFE_Updater-Gv8.X-comp.bin in GUI.
The CFE updated OK but it just won't automatically flash from tftp during the first boot. i can manually flash the micro plus kernel.
update:
just tried CFE-Updater-Gv8-GSv7-v3.bin through gui, also showing
Code:
CFE version 1.0.37 for BCM947XX
I just redid mine again, Initial TFTP of the compressor.bin I cannot get to got(same as 7.2),but it does update through the GUI and after waiting 3 min.s and the power cycle TFTPing the firmware on goes without a hitch both GS 7.0 and 7.2
What is the first four digits of the serial number on your v7.0?
serial number: CGNB1g39xxxx
which compressor.bin are you using? from my serial console I see:
Device eth0: hwaddr 00-1A-70-xx-xx-xx, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
***normally TFTP attempts here *****
Invalid boot block on disk
Reading :: Failed.: Timeout occured
there are no TFTP attempts made by the CFE. I am wondering whether it is related to the nvram setting.
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Wed Oct 28, 2009 22:33 Post subject:
Ah, dunno if it has anything to do with it, mine is CGNC the second gen v7.0.
I am using CFE_Updater-Gv8.X-comp.bin from the original post page 1. The firmware I am TFTPing on is not SSH, don't think that makes a difference. I use the web GUI to upload the compressor bin then use TFTP to upload the firmware. _________________ The New Me
Posted: Thu Oct 29, 2009 20:06 Post subject: Noob with a theory
Ok, so I compressed the CFE on a WRT54Gv8 and like 4 other posters to this thread and the "Going back from 128K" thread (3 of which who also had v8's) I had significant problems. The exact same problems they had: slowness, lockups, CPU load spiking eventually to 100% etc...
Due to my meticulous following of the procedures, 30/30/30 resets before and after, reading and re-reading of the peacock thread, and the fact that I'm not alone, I am convinced that there's another variable besides user error. But wait there's more - I've actually got a good noob WAG what that variable might be!!
During my due-diligence before touching this router (because it's my sister's) I ran across a thread that discussed hardware differences between WRT54Gv8.0's. I didn't bookmark the thread, but I remember the key fact. Most v8.0's have two Broadcomm chips, but some v8.0's have one Broadcomm and one EON chip. This router is one of the EON-having kind, I know because I cracked it open just to see.
So... That's my noob WAG - that the EON chip-bearing v8.0's have problems with this CFE compression in it's current form.
-Does anybody here who knows more than me (read: everyone) have any opinion on whether this WAG has any merit? Would having one Broadcomm and one EON chip in the router have anything to do with CFE compression complications?
-Do any of you other people who had problems with CFE-compression on a v8.0 have an EON chip? There's no screws, you just gotta pull the blue plastic away from the black plastic - it snaps apart and snaps right back together again.
-Has anyone with a v8.0 that has an EON chip successfully compressed the CFE without resulting complications?
Maybe we can save some others the aggravation if my WAG is true, and warn others burdened with EON chips away from doing the CFE-compression. I'm off to do a VXworksREVERT and be forever scarred with an incorrect MAC address, and cross my fingers that fixes it so I don't having any 'splaining to do to my sis.
Joined: 22 Jun 2008 Posts: 2440 Location: Am now Dark_Shadow
Posted: Fri Nov 06, 2009 3:43 Post subject:
barryware wrote:
I backed up the compressed cfe via http. The edited the sdram init, then plowed the compressed cfe back. Now it always has 16mb ram even after a hard reset.
I just Flashed my new GSv6 with that CFE, works great.
Red and T, PM me if you want me to do any testing for compressors for these units. I have in my possession a GSv5, GSv6, and a GSv7. _________________ The New Me
I backed up the compressed cfe via http. The edited the sdram init, then plowed the compressed cfe back. Now it always has 16mb ram even after a hard reset.
I just Flashed my new GSv6 with that CFE, works great.
Red and T, PM me if you want me to do any testing for compressors for these units. I have in my possession a GSv5, GSv6, and a GSv7.
Any easy way to compress it as of now? From what I can tell you took a CFE from another unit, edited it, and flashed it onto the GSv6. I know it's possible to change a cfe using telnet/ssh.
with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled