From owner-freebsd-current Thu Aug 3 10:46:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 072EB37B60E for ; Thu, 3 Aug 2000 10:46:19 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA73057; Thu, 3 Aug 2000 19:44:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008031744.TAA73057@freebsd.dk> Subject: Re: ATA66 support In-Reply-To: <20000803191538.A8387@titan.klemm.gtn.com> from Andreas Klemm at "Aug 3, 2000 07:15:38 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 3 Aug 2000 19:44:57 +0200 (CEST) Cc: jcm@FreeBSD-uk.eu.org (j mckitrick), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Andreas Klemm wrote: > > I bought a separate ATA PCI controller which is capable of ATA 66. > But using an ATA-66 capable cable causes the system to hang during > boot. Strange.. > atapci0: at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled Funny, what have you done to disable Busmastering ? > atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 > ata2: at 0xa400 on atapci1 > atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 That looks OK... > > The motherboard has to be severely broken if a PCI controller wont work... > > What HW are we talking about here ? > > Tyan Titan Pro, SMP board, 2 x 200 PPro Got one of those too, works like a charm with both Promise and HPT366 controllers and IBM's... > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 AHA! try swap that with a known good drive (ie non Maxtor/WD) if you can.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message