Re: can't get past BIOS...

^P is only useful at one particular stage of boot in the BIOS.  net6501 also accepts +++ followed by 1 second of nothing to display the uManager (micro manager) interface.  I’d use that as your test, so you don’t need to keep re-setting the unit to get interaction.  Just try a new terminal speed and hit + 3 times to see if you get a reaction.

This is the bane of serial connections.  Short of hooking up an oscilloscope, I think you just have to keep guessing and trying.  Possible values can be 2400, 4800, 9600, 19200, 38400, 57600.

	ED.


On 2014, Aug 10, at 5:22 AM, Marco A. Calamari <[email protected]> wrote:

> 
> On Sun, 2014-08-10 at 13:06 +0800, Eric Abrahamsen wrote:
>> I've inherited a 6501 from someone who doesn't remember what speed the
>> serial port was left at, and isn't even sure if there's an OS on the
>> drive.
> 
> Kernel normally reset the speed of tty, so it the bios tty and
> the kernel tty are not equal, you'll have gibberish.
> 
> Try to match kernel speed from the beginning using the same
> speed in bios
> 
> HTH
> 
>> 
>> I'm trying to get started with booting the machine, but can't even get
>> past step one: after trying two dud cables, I've got one that I'm pretty
>> sure is crossover, but no matter what the speed and settings, I get
>> gibberish on the console. I've spent several hours trying all reasonable
>> settings, starting with 19200/8N1/no flow, and going out from there.
>> 
>> But I only get one short-ish line of gibberish -- the higher the speed,
>> the longer the line. It sure doesn't look like a splash screen of any
>> sort, and the router does not go on to boot an OS. Just the one line,
>> then silence. Typing or hitting ^P has no effect at any stage.
>> 
>> So I'm assuming I'm hitting some early-stage error, and the line I'm
>> seeing is simply a note to that effect (though I don't know why I can't
>> get it to come through clearly).
>> 
>> Does this look like anything familiar to anyone? Any guesses as to what
>> the error might be -- if there's a reasonably small pool of possible
>> errors, I guess I could just try addressing them one by one to see if I
>> hit it by accident. I have already tried wiggling most of the plugs :)
> 
> 
> _______________________________________________
> Soekris-tech mailing list
> [email protected]
> http://lists.soekris.com/mailman/listinfo/soekris-tech