if holding down reset for 30 not work,
try a 30-30-30
if that does not work, and you can still get into the machine - telnet to it and type in "ps" and see if the command is running _________________ 2x WRT54G v5, 2x WRT54G v2
2x BUFFALO WHR-G54S
1x La Fonera
FON Client Bridge tutorial
I've installed the 11296 build on my WAP54G ver 3.1, and after the upgrade, it's detected as WRT54Gx router. I've followed the procedure to change the nvram values (nvram set WAPver=3 and nvram commit) using the web interface, and it didn't return any errors. Then, I've saved that as a startup script ("save startup" button), pushed the reboot button on the web interface, and the router didn't come back....
Of course, it was using default config (30/30/30 rule). So then, I've reset the config again, and using telnet I did the changes to the nvram, and then reboot.
The router come back identified as a Linksys WAP54G v3.x, without any problems. I've tried also to unplug the router (just to see if the config was stored), and it come back alive and kicking..!
So, if anyone have the same problem, just don't push the "save startup" button.... it still works saving the config to the nvram. Maybe this isn't necessary anymore, and the wiki info should be fixed?
The only difference that I can see, is that the box of my router has a "WAP54G-LA" legend... (i'm from Chile, so I suppose that the LA is for LatinAmerica).
The manufacture date is 05/2008, and the FCC ID is Q87-WAP54GV31.