Hi all. I have a WAP54G 3.1 and I'm trying to install the last 7.09 version, but it simple "doesn't work". It only reply to my "ping" but no other interaction (ssh, telnet, web, ...)
The whiterussian 0.9 work well, but Kamikaze no. The "act" led near the power one are power off (with the original firmware and with the whiterussian it switch on). The firmware, I think, it's the right one (brcm-2.4-squashfs).

How / what I have to do the for make it working?

Thanks

I too find my self in a similar place.
I have another wrt linksys V3 running DDWRT.
I was fiddling about with different versions of firmware, installed tomato and then after reading around I saw some features that may have suited a project I was working on in the openwrt firmware.

Perhaps a little about my computer knowledge, CPM with a Z80. (so long ago, forgotten it mostly by now.. Then Amiga then Dos and various Windows to XP

I have reasonable network configuration abilities, hard setting ip addresses, gateways, etc. Can handle doc command prompts OK.

Have had a little fiddle with Ubuntu but do not know too much about Linux architecture.

I installed Kamikaze 7.09 without fully understanding what I was doing.

Much reading, trial and error enabled a ping to 192.168.1.1 but no web page. telnet 192.168.1.1 produces
 
=== IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
------------------------------------------

BusyBox v1.4.2 (2007-09-29 09:36:14 CEST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
KAMIKAZE (7.09) -----------------------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
---------------------------------------------------
root@(none):/#

I did try passwd and then found I could no longer telnet.
Ping still worked OK.
Tried an SSH client and also TFTP

Manged to get it back to telnet state.
IPKG command

root@(none):/# ipkg update
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
An error ocurred, return value: 22.
Collected errors:
ipkg_update_cmd: ERROR: failed to make directory /usr/lib/ipkg/lists: Read-only
file system
root@(none):/#

and then

root@(none):/# ipkg list
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
base-files-brcm47xx-2.6 - 10-9078 -
bridge - 1.0.6-1 -
busybox - 1.4.2-2 -
dnsmasq - 2.39-1 -
dropbear - 0.50-2 -
hotplug2 - 0.9+r102-2 -
iptables - 1.3.7-1 -
kernel - 2.6.22-brcm47xx-1 -
kmod-diag - 2+2.6.22-brcm47xx-1 -
kmod-madwifi - 2.6.22+r2568-20070710-brcm47xx-2 -
kmod-ppp - 2.6.22-brcm47xx-1 -
kmod-pppoe - 2.6.22-brcm47xx-1 -
kmod-switch - 2.6.22-brcm47xx-1 -
libgcc - 4.1.2-10 -
mtd - 5 -
ppp - 2.4.3-8 -
ppp-mod-pppoe - 2.4.3-8 -
uclibc - 0.9.28-10 -
udevtrigger - 106-1 -
wireless-tools - 29-1 -
Done.

I have tried to TFTP origonal firmware.BIN but get timeouts.
I am now well sure I am in past my abilities and am unsure if I should try the passwwd and SSH options again as suggested by http://martybugs.net/wireless/openwrt/flash.cgi

Tried

mtd -r write openwrt-brcm-2.4-squashfs.trx linux

says it cant find the file
tried
mtd -r write c:/openwrt-brcm-2.4-squashfs.trx linux

As expected I need to get to the DOS files, not sure haow to address this.

Tried changing the password

root@(none):/# passwd
Changing password for root
New password:
Retype password:
passwd: cannot update password file /etc/passwd
root@(none):/# exit
Seems I am stuck

(Last edited by grunthos on 12 Mar 2008, 20:38)

grunthos:  The normal procedure for installing openwrt is as follows
1. Flash the appropriate firmware image to your router and wait for it to reboot.
2. Telnet into the router at 192.168.1.1 and use passwd to change password. This disables telnet access.
3. SSH into the router at 192.168.1.1 and configure it as required.

Use of telnet is disabled because it's an old, insecure protocol. You shouldn't need to re-enable it after flashing. If you're  using windows I recommend putty as an SSH client.
I'm really not sure why you're getting "Read-only file system" errors. Could you explain exactly how you "Manged to get it back to telnet state" are you running in failsafe mode or something?
The first thing I would try is power cycling the router and SSHing into it with putty.
If that doesn't work I would think the easiest thing would be to re-flash it with kamikaze either via command line or TFTP.
BTW: in order to flash a firmware image with "mtd -r write firmware.trx linux" you need to get the firmware onto the router first. You can do this using wget or scp, wget is probably easiest, e.g.

cd /tmp
wget http://downloads.openwrt.org/kamikaze/7.09/<whatever image you need> 
mtd -r write <your image's filename> linux

Wow what a pathway to functionality that was.. Thanks Turingtest... for the above. I did try that at least a dozen times but it simply did not work at the stage I was at. Until later. I got your message just as the router was booting into the GUI web page Webif
I will update this post later tonight as I am sure that a lot of what I did, although gleaned from pages like
-----------------------------------------------------------------------------------
"2.12. How do I reflash / How do I revert back to my previous firmware?

Make sure you have set boot_wait=on. To verify this do:

nvram get boot_wait

should return on. You can set boot_wait=on to on by doing:

nvram set boot_wait=on
nvram commit

When this is done you can follow the OpenWrtDocs/Deinstalling page.

boot_wait indicates whether or not the boot loader (CFE) should wait for a tftp transfered firmware before it loads the firmware present on the ROM. To adjust the length of time the CFE waits for this TFTP transfer, use the sparsely known wait_time variable. In example:

nvram set wait_time=30
nvram commit

This would cause the boot_wait period to be 30 seconds, allowing plenty of time for TFTP transfer. The default varies between models and versions and seems to range between 1 and 3 seconds."
--------------------------------------------------------
although useful was somewhat confusing. eg. NVram did not exist, seems it has been deleted in favor of config files.

I did find a command string, something like /sbin/??? It was the first step to getting things going, it at least rescued the partition, from there I could at least telnet in under the "safe/rescue mode and set the passwd. from there SSH with putty... Then came my long learning curve..

Will get to work now and update the rest later.....

A real fix for those dead brick routers.
Needless to say the pathway to getting things going was long and tedious.
I did reach the point where the router was performing well with kamakaze and webif web interface.
Thanks to the Xwrt guys.
The list of packages able to be easily installed was most impressive. I will be again installing Openwrt/webIF and exploring more.

Very impressive and powerfull stuff. Pick a feature/package that you need and add it!!!

--------------------------------------------------------------------------
Once I had fiddled with it for a few days I decided to get it back to the more familiar DDwrt firmware. (I needed to do some survey work with it. The last thing you need is a new operating system that may not quite do what is needed.)

By this stage I was fluent in safe mode, telnet, ping, SSH/Putty MTD commands etc.
------------------------------------------------
I followed the instructions at
http://wiki.openwrt.org/Faq#head-1953fb … 599d465569

boot_wait did not seem to be an option available to me
----------------------------------------------------------------
and then the instructions at
http://wiki.openwrt.org/OpenWrtDocs/Deinstalling
--------------------------------------------------
comments like...
"You need to convert the bin (eg. openwrt-wrt54g-squashfs.bin) file to a trx file before reflashing"

WRONG! The openwrt-brcm-squashfs.trx is a generic trx file that will work on any supported broadcom platform. The openwrt-wrt54g-squashfs.bin is just "bin header + openwrt-brcm-squashfs.trx', the bin header just contains the firmware version number and what models the firmware can be loaded on; the bin header is only used for verification before writing the trx data to the flash. The mtd utility writes the given file to flash without verifying it; use one of the openwrt-brcm-squashfs.trx when using mtd. Converting the openwrt-wrt54g-squashfs.bin file back to a trx is just plain ignorant. "

were far from helpful and just plain rude, demonstrating an arrogant attitude that seems to demonstrate a wish to not only look down on others less knowledgable but a wish, for whatever reason, to keep them in a lesser place.

Whilst some people may know lots about linux and its operations, I do not profess to do so.  I am more than happy to install it on a spare computer and learn. ( any one of three that sit under my desk ticking away at different projects.) I started out back in the early 1980's building my own z80 based computer, adding CPM operating system to it along with floppy disk drives, from there, many different computers and systems. I have now spent over 60 hours on a $70.00 router. For me it is the search for knowledge.. but so hard to extract here?
End of gripe.
------------------------------------------------------------
Refering to the Bin to TRx conversion, instructions stating that

1.2. Using the webif
Since White Russian RC4 you can use the webif to go back to the original firmware. The webif automatically recognizes a firmware image uploaded in BIN or TRX format and converts it accordingly.

Load the webif in your web browser and goto the System / Firmware upgrade page
make sure Erase the JFFS2 partition is checked
choose the BIN or TRX firmware file (downloaded before from the manufactures website onto your PC)
-----------------------------------------------------------------
This statement would seem to be inaccurate as the web based update with linksys.BIN stated errors in the trx file.

Back to the CLI/ Putty

Trimming the file with dd bs=32 skip=1 if=original.bin of=original.trx
and
mtd -e linux -r write original.trx linux resulted in a very unhappy router.

Over the weekend I wandered into the workshop and manufactured a Jtag buffer cable. This was soon ticking away under the desk, backing up all sections of the flash, but no amount of re writing, including a full dump from when the whole thing was working well. I extracted the data from another router, sadly different version, did not help....

Many hours searching the openwrt community resulted in little extra information.
---------------------------------------------

A few hours ago, wandering about the DDwrt community, with heaps of people responding to questions, I discovered the following.

http://www.wlan-skynet.de/download/skyn … _setup.exe

would seem to be the best thing since sliced bread....

Its all apps in one package. You need a Jtag cable, install the software, get the jtag talking, run the web update and key in your MAC address found on the sticker of the wrt router. Select the hardware version from the web updated code and it generates a new  CFE.BIN, once that is installed with the command
tjtag -flash:cfe
reboot and use the supplied TFTP software to but any standard XXXXX.bin file back on and reboot. The standard web page is available with normal passwords etc. to enable normal configuration
I did glean from Openwrt, that the CFE had to have the mac address hard/soft coded. Thus the repair kit works oh so well.

I look forward to more semi destructive explorations.
What I did find was many people who have routers stuck/bricked and finding no answers. With any luck my postings will lead them to successful rescues.