From owner-freebsd-hardware@FreeBSD.ORG  Fri Feb 11 20:46:49 2005
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E790F16A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri, 11 Feb 2005 20:46:49 +0000 (GMT)
Received: from webcrossing.com (mailhost.webcrossing.com [208.185.149.90])
	by mx1.FreeBSD.org (Postfix) with SMTP id B78C243D41
	for <freebsd-hardware@freebsd.org>;
	Fri, 11 Feb 2005 20:46:49 +0000 (GMT)
	(envelope-from jsoule@webcrossing.com)
Received: from adsl-68-120-249-249.dsl.scrm01.pacbell.net [68.120.249.249] by
	webcrossing.com; Fri, 11 Feb 2005 12:46:48 -0800
In-Reply-To: <IBRG0O00.F7J@hadar.amcc.com>
References: <IBRG0O00.F7J@hadar.amcc.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <653e3f49df8b196a4653fd90454812ea@webcrossing.com>
Content-Transfer-Encoding: 7bit
From: Jeff Soule <jsoule@webcrossing.com>
Date: Fri, 11 Feb 2005 12:46:48 -0800
To: "Vinod Kashyap" <vkashyap@amcc.com>
X-Mailer: Apple Mail (2.619.2)
cc: freebsd-hardware@freebsd.org
Subject: Re: Problems with 4.10 Release and "supported" hardware
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2005 20:46:50 -0000

That used to work, but not anymore.  I have four other servers with the 
same configuration that I successfully installed 4.10 on by waiting 
before hitting enter at the kernel configuration screen. :-(


On Feb 11, 2005, at 10:43 AM, Vinod Kashyap wrote:

>
> I have seen this problem when trying to install 4.10 on a SuperMicro
> motherboard.  It was not just the 3ware controller that was not
> getting detected, no other PCI controller would get detected either.
> This was irrespective of whether the 3ware controller was plugged in
> or not.  Do you see other PCI controllers (pci0, pci1 etc.)in the boot
> messages?
>
> The work around I found for this was to not hit 'Enter' immediately
> after the 'Kernel Configuration Menu' shows up.  Wait on that menu
> for about 20 seconds, and then continue.  You should be able to see
> the controller and its attached devices.
>