From owner-freebsd-current Thu Sep 23 10: 9:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 5EB231507A for ; Thu, 23 Sep 1999 10:09:23 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA19247; Thu, 23 Sep 1999 12:07:59 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id MAA12386; Thu, 23 Sep 1999 12:07:58 -0500 (CDT) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id MAA21789; Thu, 23 Sep 1999 12:07:58 -0500 (CDT) Date: Thu, 23 Sep 1999 12:07:58 -0500 (CDT) From: Jonathan Lemon Message-Id: <199909231707.MAA21789@free.pcs> To: freebsd@osterskov.dk, current@freebsd.org Subject: Re: Problem with Compaq SMART-2SL array controller X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >After doing a cvsup yesterday evening i can't seem to boot on my >raid cotroller using the same kernel config. > >Is -current probing hardware i a different way now or ?? It appears so. The IDA driver needs to stomp on the WD driver's vectors in order to boot off of the RAID controller. It seems that something changed so that wd is getting probed after the ida driver now, and removing the vectors. For now, you could remove the IDE devices from the config file, until this gets fixed. Ideally, the boot blocks/loader should be taught to boot from something other than wd() or da(). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message