I installed wrtsl54gs-2.6-squashfs on my WRTSL54GS, via the factory firmware upgrade page, but now for some reason it seems bricked.

It starts up and appears to be booting up, the power light blinks for a while and then eventually goes solid. If I plug in an Ethernet device, the Ethernet port lights will light up and will blink when traffic is transmitted to them.

However:

There is no DHCP.
I am unable to ping the router via any IP address configuration.
If I sniff the line with wireshark, I see no traffic from the router, only traffic from my NIC card trying to contact DHCP.

I _should_ be able to ping the router, right?

Does anyone have any ideas or any suggestions as to what I might do to resurrect this thing?

Hello,

The same for me with "openwrt-wrt54g-2.6-squashfs.bin" on a WRT54G r2. I made the upgrade, using the GUI from WhiteRussian RC6.
Now it seems bricked "It starts up and appears to be booting up, the power light blinks for a while and then eventually goes solid. If I plug in an Ethernet device, the Ethernet port lights will light up and will blink when traffic is transmitted to them." as well...

I'm able to connect it with a Putty using SSH connection ? Is there any way to put back another firmware on it using this way ?

Does anyone has anything to suggest ?

Thanks in advance

(Last edited by LoloMc on 22 Jul 2007, 20:49)

LoloMc,

This section is for the discussion of Kamikaze - not WhiteRussian. And no - your router is _not bricked_. Follow the installation instructions. Hint: Telnet.

Christopher,

I have put a kamikaze firmware on it actually
It is true that BEFORE putting this firmware, there was a White Russian on it. But this is a Kamikaze problem

I can not connect using Telnet. I'll try again

Thank you

Ah - I see. Sorry I misunderstood you.

Well, you see - Kamikaze has no GUI, so all the setting must be made to it via SSH, editing configs, etc.

As far as getting a new firmware on it now, I think you're going to want to do some research on TFTP upgrades with Kamikaze. I believe that is the only way to upgrade it at this point.

Sorry for being dense there. My bad.

I installed all of the firmware versions of Kamikaze that I could find last week (including the July 20th snapshot) on my wrtsl54gs and I could not get any of them to initialize the WAN port.  I think that it has to do with the following two threads (http://forum.openwrt.org/viewtopic.php?id=8435 and http://forum.openwrt.org/viewtopic.php?id=10528 ).  I added both serial and JTAG to the box last week and both work great (serial for seeing what is going on and JTAG for a new CFE as discussed here: http://forum.openwrt.org/viewtopic.php?id=9101 .  Although you probably do not need to go to the extent of adding JTAG in your case.  For the mean time until Kamikaze gets fixed for the wrtsl54gs I have switched back to White Russian.

Your router is most likely NOT bricked, and I think you may be able to get to it at 192.168.1.1 on the LAN side using telnet.  If you cannot telnet you should still be able to recover by tftp'ing White Russian to it.

Hi,

Unfortunately, I'm not able to recover anything... And I think I do not have the skills to try JTAG or SERIAL...

One thing I would like to be sure is that I have choose the correct firmware when I flashed it. I choosed the "'openwrt-brcm47xx-2.6-squashfs.trx" because on this page I saw that my AP has Broadcom 4712 @ 200MHz inside.
I realize that I should have choosed the "openwrt-wrt54g-2.4-squashfs.bin" or the "openwrt-wrt54g-2.4-squashfs.bin".
So, maybe I made a big mistake... Can somebody confirm ?

Thank you in advance

Hi Robert,

I'm not sure I'm really good with telnet... On Windos2k, after entering "telnet 192.168.1.1 22", I see SS-2.0-dropbear_0.49 in the command line terminal and the underscore blinking. But I can't write anything more...

Any help would be really appreciated

++

Hi Christopher,

No problem at all
I made some research and find a way to upgrade using tftp. Unfortunately, I tried with a linux box, with a MS WXP box and a MacOSX box. And each time, the same thing... "Timeout"

I tried this :
"tftp 192.168.1.1
binary
rexmt 1
timeout 60
trace
Packet tracing on.
tftp> put openwrt-wrt54g-2.6-squashfs.bin"

It is true that I didn't tried the following way
"Or, for a single command, so you don't have to retype each time:

echo -e "binary\nrexmt 1\ntimeout 60\ntrace\nput openwrt-xxx-x.x-xxx.bin\n" | tftp 192.168.1.1

Setting "rexmt 1" will cause the tftp client to constantly retry to send the file to the given address. As advised above, plug in your box after typing the commands, and as soon as the bootloader starts to listen, your client will successfully connect and send the firmware. You can try to run "ping -f 192.168.1.1" (as root) in a separate window and enter the line "put openwrt-xxx-x.x-xxx.bin" as the colons stop running over your terminal when you power-recycle your router."

I'll try this evening

++

Hi LoloMc,

"SS-2.0-dropbear_0.49 in the command line terminal and the underscore blinking" this is SSH and clearly indicates that your router is not seriously bricked.  Try using putty (http://www.chiark.greenend.org.uk/~sgta … nload.html) from your XP box to connect to 192.168.1.1 (22=ssh 23=telnet).

As for tftp'ing a new firmware you should read: http://wiki.openwrt.org/OpenWrtDocs/Ins … WrtViaTftp (specifically section 1.3).  The key is that there is basically a very small window of time that tftp will succeed without a timeout (what I did was to plug in the power supply of the router and then I immediately hit enter on the keyboard to start the tftp, if the tftp does not complete within 5 seconds of hitting enter then you were not quick enough, unplug and try again).  If you watch for a successful ping then you will likely be to slow.  I had a switch between my pc and my wrtsl54gs.  I also set my pc to static 192.168.1.10 and default route to 192.168.1.1

ssh (port 22) isn't activated until you telnet in and set the root password.  Until you set the root password you must use telnet. You are trying to use telnet on the wrong port. Try connecting with telnet  on the telnet port (23).   

"telnet 192.168.1.1 23" or just "telnet 192.168.1.1"

After you telnet in and set the root password telnet is disabled and you must use ssh with putty.

You can not use tftp unless you previously set the boot_wait nvram variable.