From owner-freebsd-questions Mon Jun 28 5:59:43 1999 Delivered-To: freebsd-questions@freebsd.org Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E75714FD5 for ; Mon, 28 Jun 1999 05:59:29 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: (from richard@localhost) by stevenson.cogsci.ed.ac.uk (8.8.7/8.8.7) id NAA05371; Mon, 28 Jun 1999 13:59:26 +0100 (BST) Date: Mon, 28 Jun 1999 13:59:26 +0100 (BST) Message-Id: <199906281259.NAA05371@stevenson.cogsci.ed.ac.uk> From: Richard Tobin Subject: Serial console problem To: freebsd-questions@FreeBSD.org Organization: just say no Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a machine running 3.1-19990407-STABLE which I have configured to have the console on a serial port: Jun 28 13:42:40 pc-news /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x30 on isa Jun 28 13:42:40 pc-news /kernel: sio0: type 16550A, console I have this in ttys: ttyd0 "/usr/libexec/getty std.9600" dialup off secure cuaa0 "/usr/libexec/getty std.9600" vt100 on secure (using ttyd0 didn't work presumably because the cable doesn't have the neecessary handshaking lines). When I boot, the boot messages appear on the serial device, and I get a login prompt and can log in. But attempting to output to /dev/console hangs, and control-C produces: bash: /dev/console: Interrupted system call Syslog also gets stuck, which is bad (though it seems OK if I change syslog.conf to not use /dev/console at all). Where have I gone wrong? Do I need to get ttyd0 working instead of using cuaa0? -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message