From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 4 23:57:36 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 029CC16A403 for ; Wed, 4 Apr 2007 23:57:36 +0000 (UTC) (envelope-from telmnstr@757.org) Received: from users.757.org (users.757.org [70.169.147.20]) by mx1.freebsd.org (Postfix) with ESMTP id CB00D13C448 for ; Wed, 4 Apr 2007 23:57:35 +0000 (UTC) (envelope-from telmnstr@757.org) Received: by users.757.org (Postfix, from userid 1123) id A604BA552; Wed, 4 Apr 2007 19:37:45 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by users.757.org (Postfix) with ESMTP id A504EA54F for ; Wed, 4 Apr 2007 19:37:45 -0400 (EDT) Date: Wed, 4 Apr 2007 19:37:45 -0400 (EDT) From: telmnstr@757.org cc: freebsd-hardware@freebsd.org In-Reply-To: Message-ID: References: <041C14B4-EEAB-44CF-A3BA-A8EB3D3BA504@altesco.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Can't boot after adding tx2plus card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2007 23:57:36 -0000 > Any ideas what else I can try? I hit something similiar... basically, your card comes up first, so you would need to customize your fstab and perhaps kernel regarding the change in boot devices. My hack was nassssty. Basically, we changed the first few bytes in the firmware image for the promise ultra-ATA card, so that the system bios wouldn't recognize it... reflashed the firmware (basically killing it). Then NetBSD saw the card once it was booting, but the onboard card was picked up first. We had 3 x ultraATA cards on top of whatever was in the system, and the # of drives was to change all the time... See if you can disable the onboard Promise BIOS.... probably not. Promise was of no help, and their flash utility checksummed the firmware so it had to be hacked. I no longer have access to any of that, and a co-worker helped with it as he had experience with the promise cards and knew that the first few bytes of the firmware are what the system bios sees when it scans for other bioses to execute.