From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 12:26:29 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0714116A4CF for ; Tue, 16 Dec 2003 12:26:29 -0800 (PST) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.131.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8854743D2D for ; Tue, 16 Dec 2003 12:26:27 -0800 (PST) (envelope-from jlfenton@citlink.net) Received: (qmail 22659 invoked from network); 16 Dec 2003 20:26:26 -0000 Received: from unknown (HELO citlink.net) ([67.136.217.1]) (envelope-sender ) by relay02.roc.ny.frontiernet.net (FrontierMTA 2.3.6) with SMTP for ; 16 Dec 2003 20:26:26 -0000 Message-ID: <3FDF6A79.8050609@citlink.net> Date: Tue, 16 Dec 2003 13:26:33 -0700 From: Joe Fenton User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20031216200054.1086816A564@hub.freebsd.org> In-Reply-To: <20031216200054.1086816A564@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.2 and amd64 - good enough for a production server? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 20:26:29 -0000 > From: Nakata Maho > Subject: Re: 5.2 and amd64 - good enough for a production server? > > 4) and 4.9-RELEASE (i386) doesn't work, hangs while looking for ad0 Is this when trying to boot? I ran into something that sounds similar on my MSI Master2-FAR Opteron system - when booting, it would start to list the devices, but only show the floppy. It was like it was hanging while looking for the harddrive. Actually, it was hanging while looking for drive B. I had a USB floppy plugged into the system which the BIOS mapped as B. The FreeBSD booter can't handle a USB floppy mapped as B. Unplugging the USB floppy allowed the booter to run properly. I imagine that disabling the BIOS support of the USB floppy would also work. I've debated whether or not to fill out a FreeBSD bug report on this. I haven't seen a report of this in the list, but a few were similar.