Erik Mouw writes:
> On Fri, 28 Apr 2000 23:56:54 +0100 (BST), Russell King - ARM Linux Admin wrote:
> > Zach Welch writes:
> >> to my kernel parameter line (in fixup_sa1100), thinking that the output may
> >> be redirected at that point. No change was detected in the systems
> >> behaviour. Any thoughts as to what might be happening?
> >
> > Yep. The serial driver is probably getting confused with the debugging
> > messages.
> > If it boots that far, you should probably disable the debugging stuff and move
> > back to the more conventional kernel messages on console approach.
>
> I think the SA1100 serial driver doesn't correctly behave like a real
> console. If I compile with "Console on SA1100 serial port" and without the
> frame buffer device, I always get the message "Can't open initial
> console". I've put some printk("Now here") messages in the kernel to find
> out where the messages remain, but they aren't printed on the serial
> port, although they are available with the "dmesg" command. OTOH, kernel
> oopses generated on ttyS1 are verbosely reported on ttyS0.
Oh, something I missed - loose the /dev/ part. The correct line should be:
console=ttyS1,38400
However, without that line, it will default to the first console it can
find.
Another problem will be that although you can specify this argument, it
is totally ignored by the SA1100 serial driver. The port and data format
that is used for the console is hard coded into the driver for each port.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/ / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
