From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 13:48:40 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 7BB6B37B401 for ; Sun, 18 May 2003 13:48:40 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4557E43F75 for ; Sun, 18 May 2003 13:48:35 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8p1/8.12.8) id h4IKmQGw022276; Sun, 18 May 2003 22:48:26 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200305182048.h4IKmQGw022276@spider.deepcore.dk> In-Reply-To: <200305181636.44142.cjp@sandstorm.net> To: Charles Peterman Date: Sun, 18 May 2003 22:48:26 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: hackers@FreeBSD.ORG Subject: Re: Maxtor Ultra ata/133 controller, FreeBSD 4.[5,8], and the boot process 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: Sun, 18 May 2003 20:48:40 -0000 It seems Charles Peterman wrote: > > As it turns out, the latest rev of the Intel SDS2 motherboard also rev's its > ICH4 ide controller, turning it into a useless piece of PIO crap and > destroying my systems' performance and sucking down my weekend. > > After contacting Soren Schmidt concerning the state of the ata driver and > whether a quick hack would be appropriate, I decided to venture into using > a PCI add-on card controller, in this case the Maxtor Ultra ata/133 > controller. There is only one disk aside from the 3ware raid, which does not > show up as an ata device. > > The install CD for 4.5 installs to this drive without a problem, but it tells > me that the loan disk is at ad4. Upon reboot, the boot loader fails, > horribly, no loader found. Rebooting with the install CD, and going into the > loader's command line, I find that my disk is listed as disk2s1, and not the > disk4 I thought it would be. That sounds very strange unless you move it physically to the other channel.. However 4.5 is way too old for this purpose, try 4.8 that has a much better chance of supporting that board (I'm not sure which Serverworks chip it has one there, the docs I found for the SDS2 didn't tell)... > Is there a variable I could set during boot to get the disk to show up as ad0? > SImilar to the way removing ATA_STATIC_ID from the kernel compile does. no. -Søren