From owner-freebsd-stable Sun Sep 29 18:47:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 544E837B401 for ; Sun, 29 Sep 2002 18:47:21 -0700 (PDT) Received: from c18070.belrs1.nsw.optusnet.com.au (c18070.belrs1.nsw.optusnet.com.au [210.49.78.171]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E36043E42 for ; Sun, 29 Sep 2002 18:47:20 -0700 (PDT) (envelope-from ajmawer@optusnet.com.au) Received: (qmail 27938 invoked from network); 30 Sep 2002 01:43:36 -0000 Received: from unknown (HELO optusnet.com.au) (unknown) by unknown with SMTP; 30 Sep 2002 01:43:35 -0000 Message-ID: <3D97AD22.1040404@optusnet.com.au> Date: Mon, 30 Sep 2002 11:47:14 +1000 From: Antony Mawer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020926 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Hittinger Cc: stable@FreeBSD.ORG Subject: Re: PCI probing broken on DELLs again References: <200209292032.g8TKW1hX000822@ns1.pu.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Hittinger wrote: > It looks to me like the 4.6 pci probing is picking up his ata0 disk as ata2, > not quite linking to it properly, and then failing when it probes ata0 later. > > Does anyone know of an easy way to disable the ata2 probe? My thinking is > that if the ata2 probe is prevented then the ata0 probe will probably work > and then he can run 4.6/7. Now that caught my interest. A while ago I was trying to setup FreeBSD 4.6 on a machine with a Promise FastTrak100 TX2 "RAID" card. On the original box I was trying to do the setup on, sysinstall picked up ar0 _and_ ad4 (I think it was, from memory, anyway), so I got the selection box to choose what disk I wanted to fdisk and disklabel. I installed to ar0 and ignored ad4, but during trying to install files to it, sysinstall threw up gzip errors and the install bombed out. I gave up fiddling and moved the RAID card etc into another box. This time, sysinstall only picked up ar0, I installed to it, and everything went smoothly. Is there any likelihood this could somehow be related...? -Antony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message