From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 15 07:32:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E93716A4CE for ; Mon, 15 Dec 2003 07:32:46 -0800 (PST) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 083A643D37 for ; Mon, 15 Dec 2003 07:32:45 -0800 (PST) (envelope-from drais@wow.atlasta.net) Received: (qmail 58399 invoked by uid 1068); 15 Dec 2003 15:32:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Dec 2003 15:32:44 -0000 Date: Mon, 15 Dec 2003 07:32:44 -0800 (PST) From: David Raistrick To: thundergod@bigfoot.com In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-hackers@freebsd.org Subject: Re: REPOST - Installation Bug - All available versions hang on install X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 15:32:46 -0000 > Pro 10/100 PCI network adaptor. What makes this system unusual is that i= t > is =93legacy free=94 which means it has none of the traditional I/O ports= (no > serial, parallel, PS/2 or even floppy interface). All I/O is via one of = the =2E...and thereby it doesn't have a keyboard controller at all. The system is hanging on boot looking for the keyboard controller itself and not finding one, since it doesn't exist. I've seen this on an embeded system as well. I don't recall the exact workaround, but without the ability to build your own release, you won't be able to make the change anyway. You might try installing on another machine (any machine) that can use the systems disk. But out of the box, I suspect there is no workaround for you. If you DO have the legacy-keyboard-enable type option, you should try that...but I suspect you would have if you had it. If someone else is familar enough with the workaround for this issue, and can post it, I could make the changes and build an ISO for you, probably, though my free time for such at the moment is limited. When my developers get in, I'll dig further regarding the workaround, as well. =2E..david (a lowly sysadmin. :) --- david raistrick drais@atlasta.net=09=09http://www.expita.com/nomime.html