My sparc is doing pretty well (connect to ebertland.net :), but I am having problems with the serial console using kernel version 2.2.1. I get these messages in all my logfiles:
Mar 2 00:42:48 ebert-dsl5 kernel: zs_open ttyS0, tty overwrite. Mar 2 00:42:58 ebert-dsl5 kernel: zs_open cua0, tty overwrite. Mar 2 00:42:58 ebert-dsl5 last message repeated 19 times Mar 2 00:42:58 ebert-dsl5 kernel: zs_open ttyS0, tty overwrite. Worse yet, when I open the serial console through a null-modem cable on my x86 machine, all I have to do is hit <return> to cause a kernel Oops. That's not very nice. Fortunately, I can ssh to the machine without any trouble. This is coming from the getty, AFAIK. My inittab is unchanged from the debian install. Here is the relevant info: ------------------ # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> #1:2345:respawn:/sbin/getty 38400 tty1 #2:23:respawn:/sbin/getty 38400 tty2 #3:23:respawn:/sbin/getty 38400 tty3 #4:23:respawn:/sbin/getty 38400 tty4 #5:23:respawn:/sbin/getty 38400 tty5 #6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 ---------------------- As you can see, only T0 has an active getty. For the record, I have a sparcstation2 with 32MB and a .4GB disk. There is no video or keyboard, and the kernel detects and uses the serial console for boot messages properly. I did not have these problems (I think) with the 2.0.x kernel that was on the boot floppies. Thanks for any insight you can give me! -- ================================================================= Jeffrey Ebert [EMAIL PROTECTED] Sonics, Inc. (650)938-2500, x108 =================================================================
