From owner-freebsd-questions Sun Oct 8 6:18:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from n5ial.gnt.com (n5ial.gnt.com [204.49.69.6]) by hub.freebsd.org (Postfix) with ESMTP id 5E88137B66C for ; Sun, 8 Oct 2000 06:18:13 -0700 (PDT) Received: (from jim@localhost) by n5ial.gnt.com (8.7.5/8.7.3) id IAA11461 for freebsd-questions@FreeBSD.ORG; Sun, 8 Oct 2000 08:12:46 -0500 Date: Sun, 8 Oct 2000 08:12:46 -0500 From: Jim Graham To: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD 4.1.1 refuses to see 30GB hard drive as > 2GB Message-ID: <20001008081246.A10865@n5ial.gnt.net> Mail-Followup-To: freebsd-questions@FreeBSD.ORG References: <20001007213350.A2124@n5ial.gnt.net> <20001008004234.A4501@n5ial.gnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <20001008004234.A4501@n5ial.gnt.net>; from Jim Graham on Sun, Oct 08, 2000 at 12:42:34AM -0500 X-PGP: see http://www.gnt.net/~n5ial for PGP Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I may have found an answer.... On Sun, Oct 08, 2000 at 12:42:34AM -0500, Jim Graham wrote: > On Sat, Oct 07, 2000 at 08:50:27PM -0700, Heredity Choice wrote: > > Tell the CMOS there is no drive on the IDE channel to > > which the big Maxtor is connected. Then boot on a bootable drive, and > > while it is installing the OS may discover and mount the Maxtor, as long > > as the BIOS isn't interfering. This didn't work, btw. > According to the motherboard's docs, it supports UDMA 66. The plot thickens.... As I was looking at the boot messages this morning, I happened to notice something a couple of lines up from the ad1: ... line. Here are the three messages: ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 19547MB [39714/16/63] at ata0-master using UDMA33 ad1: 2014MB [4092/16/63] at ata0-slave using UDMA66 Note the first line. Could it be as simple as changing the IDE cable tomorrow, when the computer shop opens again? Or is that too easy? Or, if it's the controller itself, can I add another controller? If I do, can it work along with the one on the motherboard (as a third disk controller)? Or do I need to disable the one on the motherboard first? Anyone know if I just found the problem? Thanks, --jim -- 73 DE N5IAL (/4) | Another good rule to follow: jim@n5ial.gnt.net | Do not try to implement solutions that ICBM / Hurricane: | do not work. 30.39735N 86.60439W | -- Thomas Ptacek in comp.security.unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message