> I am currently using 9600 for everything, including the BIOS. > The garbled output consists of a bunch of garbled-looking output that > scrolls by on the bottom line of the console very rapidly and then > stops with the terminal's cursor indented 5 spaces on the bottom > line.
This sounds a lot like a parity issue. In particular, CR and LF have different parity (in binary, CR=0001101 and LF=0001010), so a line where the sender thinks parity is in use but the receiver thinks otherwise will corrupt one but not the other. If the parity setting is odd, CR will work and LF will turn into something else, which can lead - and in my experience sometimes has led - to very much what you describe: about half the characters are corrupted (they get their high bit set, leading the receiver to ignore them or interpret them as other characters), with the CR after each line working but the LF not. What are you using to display the serial-console output? I don't see any mention of that. Whatever it is, you might try configuring it to strip-and-ignore parity bits; if my guess is right, that'll fix it. If you can get a capture of the serial output into a file, it might be worth postprocessing it to strip parity bits, to see if you get reasonable-looking text. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML [EMAIL PROTECTED] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
