Date: Mon, 9 Aug 1999 18:08:34 -0700 (PDT) From: jzwiebel@cisco.com To: freebsd-gnats-submit@freebsd.org Subject: i386/13051: after installation on system using COM1, kernel won't allow login Message-ID: <19990810010834.8CD5D15383@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 13051 >Category: i386 >Synopsis: after installation on system using COM1, kernel won't allow login >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Aug 9 18:10:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: John Zwiebel >Release: 3.2 RELEASE >Organization: Cisco >Environment: ip1-pc# uname -a FreeBSD ip1-pc.cisco.com 3.2-RELEASE FreeBSD 3.2-RELEASE #1: Mon Aug 9 22:10:30 PDT 1999 root@ip1-pc2.cisco.com:/usr/src/sys/compile/HEADLESS i386 >Description: On a PC with no keyboard or mouse or video, After installing a kernel from ftp.freebsd.org using boot floppies, when the system reboots, it will not allow login on the COM1 port. I was able to use a Cntl-C during the boot process to come up single user and modify the /etc/ttys file. >How-To-Repeat: Need a PC with no keyboard or video or mouse, only a com1 port. Then install FreeBSD. There wasn't anything obvious that I could configure in /stand/sysinstall to get around this. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990810010834.8CD5D15383>