Possible Bug, or Possibly don't know what I'm doing.

[Andy Kennedy]

Probably the latter. . . but here goes:

I have a Syslinux boot disk that boots the Linux Kernel (with BusyBox as
the initrd) just fine.  I wanted a serial console, however, so I created
my syslinux.cfg file as this:
serial 0 115200 0xab3
default vmlinuz console=ttyS0,115200n8
My inittab for the initialization of the console terminal is
ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100
The really strange thing is that when I boot and I'm watching the
console (through minicom) I'll see the Syslinux verbiage, then I'll see
all the kernel stuff, then as soon as BusyBox running as init hits, the
console is hosed.  At reboot, after init is killed, the serial line goes
back to normal and I see the last line from the kernel.  Here is a snip
from that:
Using IPI Shortcut mode
Time: pit clocksource has been installed.
Freeing unused kernel memory: 540k freed
input: AT Translated Set 2 keyboard as /class/input/input0
z ne
     r.
       fg t fl
               !
                 .
                  i.
                    s.
                      Restarting system.
.

What it should say is:
input: AT Translated Set 2 keyboard as /class/input/input0


BusyBox v1.4.0 (2007-01-31) etc etc etc.
I'm thinking that I need to tell init to leave the serial port alone,
however, I don't know how.

Thanks in advance for any assistance you can give me in this.

Andy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: akennedy.vcf
Type: text/x-vcard
Size: 256 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20070131/3b088d76/attachment-0002.vcf