Re: Debian Upgrade Woes
If you can get into upgrade mode (alternating red/green led), then it is *extremely* unlikely that your slug is bricked.
Once it's in upgrade mode, the redboot telnet interface cli command parser is not operable - that is normal.
Note that the SerComm upgrade protocol which upslug2 implements uses a non-standard ethernet packet type (i.e. lower level than IP packets), so is *highly* susceptible to filtering by network devices. Don't assume upslug2 is not working until you have tried a direct cross-over cable connection between the slug and a Linux host that is not running a firewall.
Even being able to ping a device (which is one level above IP) is not a guarantee that something in your network is filtering upgrade ethernet packets (which are one level below IP).
From: Richard <email@example.com>
Date: Wednesday, Apr 23, 2008 3:49 am
Subject: Debian Upgrade Woes
>As I can telnet to the, beast in upgrade mode, but it unresponsive,
>is there anything I can type while the telnet connection is active
>to allow upslug2 to see the slug ?.
>Else it looks like I've got a brick
>Sorry Tobias , this mail was suppose to go to the list.
>Registered Linux User 365161
>OS Mandriva x86_64 2008.0 Kernel 184.108.40.206-1mdv
>HAM Callsign G8JVM : Locator IO82SP
>QRV all bands 80mtrs to 3 cms ,( non WARC )
>A computer is like a Native American Indian teepee, it has no gates, no windows and has an apache inside.
>To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org