root@leviathan:~# setserial -g /dev/ttyS
/dev/ttyS0, UART: 16550A, Port: 0xdc00, IRQ: 16
/dev/ttyS1, UART: 16550A, Port: 0xdc00, IRQ: 16
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
root@leviathan:~# grep -e tty -e serial /etc/default/grub
GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
#GRUB_SERIAL_COMMAND="serial --speed=38400 --unit=0 --word=8 --parity=no --stop=1"
root@leviathan:~# grep ttyS /etc/inittab
#T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 19200 vt100
T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100
#T0:2345:respawn:/sbin/getty -L ttyS1 38400 vt100
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
root@leviathan:~# grep ttyS /etc/securetty
Now, the one part that could be causing a problem on the server but I can't tell is setserial's output, which is noteworthy. The motherboards COM header is expressly disabled in the bios (as I don't have the header to physically put in this box), but I do have a Serial Card and many working null modem cables.
The serial card is: 01:09.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)
In windows, I've got a 2-port serial card, it is properly recognized as COM3 and COM4. When I try to open a connection to the Debian box via COM3/COM4, all I get is a black screen and I can't tell if I am actually connected to the serial console or not .... I am curious if I missed something here ... I tend to experiment a lot and serial access would just make things so much easier when I am forced to reboot this box and it doesn't come back up ... a lot easier then lugging a 60lb CRT onto my desk to plug into that computer ....
> A: Yes.
> >Q: Are you sure?
> >>A: Because it reverses the logical flow of conversation.
> >>>Q: Why is top posting frowned upon?