From owner-freebsd-current  Fri Apr 30  4:26:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 023FE14FB0
	for <current@FreeBSD.ORG>; Fri, 30 Apr 1999 04:26:41 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.1/8.9.1) id NAA08416;
	Fri, 30 Apr 1999 13:26:35 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199904301126.NAA08416@freebsd.dk>
Subject: Re: New ATA drivers problem? (Was: New kernels won't boot)
In-Reply-To: <199904301104.NAA08369@freebsd.dk> from Soren Schmidt at "Apr 30, 1999  1: 4:52 pm"
To: sos@freebsd.dk (Soren Schmidt)
Date: Fri, 30 Apr 1999 13:26:35 +0200 (CEST)
Cc: abial@webgiro.com, green@unixhelp.org, tseidmann@SIMULTAN.CH,
	current@FreeBSD.ORG, shocking@prth.pgs.com
X-Mailer: ELM [version 2.4ME+ PL43 (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 Soren Schmidt wrote:
> > 
> > As I said before, I can make some tests, but unfortunately my machine
> > doesn't want to mount disks at all with the new ATA code... Please take a
> > look at the message I sent about a week ago.
> 
> Unfortunately they dont tell me much :(
> 
> I'll have to rearrange some disks here and try to make some new installs
> see if I can get the problem to appear then..

Meanwhile, could you try this patch to boot2.c and ata-disk.c and
install the new bootblocks created by this and see if it works with 
a genuine "ad" device set. You should then use ad?? in fstab of cause.
Boot directly ie like 0:ad(0,a)/kernel from the boot promt, as the
/boot/loader doesn't know about "ad" devices...

Another thing to try is to dump down ata-disk.c so it doesn't use 
either multi-sector mode or DMA, as that might confuse some disks,
notably WD but also Quantum has had some marginal disks...

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message