My apologies for the confusion, I meant ttyS0. I mistyped when composing the email.<br><br>Neil<br><br><div class="gmail_quote">On Tue, Nov 22, 2011 at 10:43 AM, Dave Hylands <span dir="ltr"><<a href="mailto:dhylands@gmail.com">dhylands@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Neil,<br>
<div class="im"><br>
On Tue, Nov 22, 2011 at 10:20 AM, Neil Baylis <<a href="mailto:neil.baylis@gmail.com">neil.baylis@gmail.com</a>> wrote:<br>
> I'm working on an embedded system running a 2.6.32 kernel originally derived<br>
> from RHEL6.<br>
><br>
> The hardware architecture is similar to a PC. The device is a specialized<br>
> server. It uses an 8250 compatible serial port for the console.<br>
><br>
> When it's booting up, everything looks fine until it initializes the serial<br>
> driver. At that point the output to the console becomes garbled until (I<br>
> think...) getty runs for the console port. Then it's readable again.<br>
><br>
> It looks as though the initialization of the serial driver is setting the<br>
> wrong baud rate, or perhaps some other configuration. During the boot<br>
> process, this garbled output happens for about 1 second, during which<br>
> probably a few thousand characters of garbage are output.<br>
><br>
> The grub boot parameter specifies "console=ttys0,57600"<br>
<br>
</div>Did you mean ttyS0? The capital S is significant.<br>
<br>
The serial ports default to 9600 baud, which is probably what the<br>
garbage coming out is.<br>
<div class="im"><br>
> The getty line for the console specifies "T0:23:respawn:/sbin/getty -L ttys0<br>
> 57600 vt100"<br>
<br>
</div>This should probably also be ttyS0<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dave Hylands<br>
Shuswap, BC, Canada<br>
<a href="http://www.davehylands.com" target="_blank">http://www.davehylands.com</a><br>
</font></span></blockquote></div><br>