From owner-freebsd-hardware Wed Aug 16 1:13:49 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by hub.freebsd.org (Postfix) with ESMTP id B3E1037BDDC for ; Wed, 16 Aug 2000 01:13:44 -0700 (PDT) (envelope-from xopl@execpc.com) Received: from execpc.com (d185.as5.appl.wi.voyager.net [169.207.125.123]) by mailgw02.execpc.com (8.9.1) id DAA17594 for ; Wed, 16 Aug 2000 03:13:40 -0500 Message-ID: <399A4CF0.226E3E01@execpc.com> Date: Wed, 16 Aug 2000 03:12:32 -0500 From: Zach Johnson X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Can't load root fs with onboard ATA100 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm using FreeBSD 4.1-Release on an ABIT KA7-100 system that has primary and secondary ATA66 interfaces along with a Highpoint Technologies HPT370 ATA100 interface. I've got a Maxtor Diamond Plus ATA100 drive. First things first, I couldn't install on this drive while plugged into the ATA100, so I installed plugged into the primary ATA66. After plugging the drive back into the ATA100, it booted just fine. At the boot prompt, lsdev shows me my drive and it's slices/partitions/files. Then I 'boot'. The screen scrolls while displaying the hardware it is finding. First it finds atapci0 (my ATA66 interface), and depending on what I have plugged in there, it may find ata0 and ata1. Then, it finds atapci1 and lists ata2 (my harddrive). FreeBSD calls atapci1 a HighPoint Tech HPT366 ATA66 controller. This is the ATA100... same IRQ, same I/O ports. I'm guessing it calls it the HPT366 because ATA100 drivers aren't at a release stage for FreeBSD. After inspecting 'ata0-slave' and 'ata1-slave', FreeBSD displays: 'ata2-master: ata_command: timeout waiting for intr ata2-master: identify failed' Unfortunately, after this, 'ad2' is not listed. Even with a CDROM plugged into the ATA100, no 'acd#' is created. I get the same identify failure errors. Since there is no ad2, I get 'can't find root filesystem' errors, and FreeBSD dumps me to a mount root> prompt. I can't type ufs:/dev/ad* there because I just get a no such device 'ad' error. Is there anything at all that can be done about this? Or is the problem in the lack of ATA100 support and I should give up... (?!) I would really appreciate any help! Zach Johnson =) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message