From mboxrd@z Thu Jan 1 00:00:00 1970 From: neil.baylis@gmail.com (Neil Baylis) Date: Tue, 22 Nov 2011 10:52:31 -0800 Subject: Serial console temporarily garbled In-Reply-To: References: Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org My apologies for the confusion, I meant ttyS0. I mistyped when composing the email. Neil On Tue, Nov 22, 2011 at 10:43 AM, Dave Hylands wrote: > Hi Neil, > > On Tue, Nov 22, 2011 at 10:20 AM, Neil Baylis > wrote: > > I'm working on an embedded system running a 2.6.32 kernel originally > derived > > from RHEL6. > > > > The hardware architecture is similar to a PC. The device is a specialized > > server. It uses an 8250 compatible serial port for the console. > > > > When it's booting up, everything looks fine until it initializes the > serial > > driver. At that point the output to the console becomes garbled until (I > > think...) getty runs for the console port. Then it's readable again. > > > > It looks as though the initialization of the serial driver is setting the > > wrong baud rate, or perhaps some other configuration. During the boot > > process, this garbled output happens for about 1 second, during which > > probably a few thousand characters of garbage are output. > > > > The grub boot parameter specifies "console=ttys0,57600" > > Did you mean ttyS0? The capital S is significant. > > The serial ports default to 9600 baud, which is probably what the > garbage coming out is. > > > The getty line for the console specifies "T0:23:respawn:/sbin/getty -L > ttys0 > > 57600 vt100" > > This should probably also be ttyS0 > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.davehylands.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111122/11750012/attachment.html