Posted: Fri May 04, 2007 9:00 Post subject: cannot send ctrl-c at redboot
I have a fon that seems to not respond at the ctrl-c sent wile booting.
I am using putty in ethernet mode but i cannot stop it and the fon get hung afeter the boot.
I have read of some people having the same problem but the only solution proposed where to use putty, that i'm already using. Others time i have sent ctrl-c without problems, so i do not understad what happenig.
I have to build a serial cable or there is some other way to get it stop and do a new flash?
If i have to buil the cable, could you provide a link to the schema?
thanks!
Redsector> the ctrl c thing only works with a serial cable.. not an ethernet cable... _________________ WRT54G,GS v1.1, V2, V3 V4, V5
WR850G V2, V3
Fonera 2100
Ctrl C works fine with Ethernet for me also. I did have a problem while using a Slax based disto and ctrl c. But there is a fix for that on the openwrt install guide.
I'm having the same problem with 2 Foneras. One was bricked by a bad firmware upload, and I have no idea how the other got bricked (changing too many settings? using old firmware- happened in Feb)? I only have access to my MacBook and it's not working with the Terminal. I don't have a serial port on my laptop so RedBoot may be my only option. Is there any workaround for this?
This is a really great site http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot . I had the same problems as you guys and this site had a bunch of commands/scripts that fixed it. (Though I'm using Linux so I'm not sure about Windows but I'm sure the site has something.)
This is what I used to make it work:
Thank you Mobad, finally some light
I have had some problems choosing a linux that works, but i find that the only commands that are really needed are
echo -e "\0377\0364\0377\0375\0006" >break.bin
to create the righgt ctrl-c sequence
and
nc 192.168.1.254 9000 <break.bin
to send the command
I have previosly opened anoter terminal windows in wich i asked a ping from 192.168.1.254 and when i saw the reply i sent the second command.
Now I have "fis init" the device, but now i'ms stuck again cause it seems that it does not want to create the "root.fs".
In any case i hope that this thread could finally put some light to the crtl-c and redboot problems
Well it could be that root.fs was not loaded properly. What is the error you are getting and are you sure you loaded root.fs properly through tftp or whatever you used.
Thanks for the tip! Worked for me! On my MacBook (so this should work for anyone on OS X, at least Tiger), netcat was already installed (from the BSD tools I suppose) so I didn't have to use DarwinPorts or Fink or build it from source. I tried just the nc command but nothing would happen once I saw the RedBoot prompt. A little modification of mobad's command got me into RedBoot, and I successfully loaded DD-WRT again!
Below is my output...
Code:
macbook:~/Desktop leaded$ nc 192.168.1.254 9000 <break.bin; telnet 192.168.1.254 9000== Executing boot script in 8.640 seconds - enter ^C to abort
??^C
RedBoot> ??h
^C punt! <-- I couldn't send anything to RedBoot, so exiting netcat started the telnet command
Trying 192.168.1.254...
Connected to 192.168.1.254.
Escape character is '^]'.
help <-- I typed help so I could get the RedBoot> but you don't HAVE to: you start at a RedBoot> prompt but you can't see it