From owner-freebsd-questions Wed Sep 20 18:33:16 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA29195 for questions-outgoing; Wed, 20 Sep 1995 18:33:16 -0700 Received: from MediaCity.com ([205.216.172.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA29184 for ; Wed, 20 Sep 1995 18:33:14 -0700 Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id SAA20726 for freebsd-questions@freebsd.org; Wed, 20 Sep 1995 18:33:50 -0700 From: Brian Litzinger Message-Id: <199509210133.SAA20726@MediaCity.com> Subject: Non existent keyboard found during serial console boot To: freebsd-questions@freebsd.org Date: Wed, 20 Sep 1995 18:33:50 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24 ME7a] Content-Type: text Content-Length: 828 Sender: owner-questions@freebsd.org Precedence: bulk in sys/i386/boot/biosboot/README.serial it says: - BOOT THE MACHINE. The boot block will probe for a keyboard on your system. If it fails to find one, you'll see a prompt appear on the terminal that looks something like this: No keyboard found. >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. My system does not have a keyboard attached and at this point 'No keyboard found.' fails appear. The system boots up on the VGA display as it usually does. Using boot: /kernel -h it boots correctly via the serial console. I'm about to use the FORCE_COMCONSOLE option, but I like the idea of having a choice at boot time. What have I done wrong? I'm running a -current as of just before the sig 11 nightmare. Thanks, Brian Litzinger brian@easynet.com