From owner-freebsd-current  Mon Nov  6  7:27:38 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 814E937B4D7
	for <freebsd-current@FreeBSD.ORG>; Mon,  6 Nov 2000 07:27:33 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id QAA37316;
	Mon, 6 Nov 2000 16:27:33 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200011061527.QAA37316@freebsd.dk>
Subject: Re: ad1 is not detected.
In-Reply-To: <20001106162328.A18026@petra.hos.u-szeged.hu> from Szilveszter Adam at "Nov 6, 2000 04:23:29 pm"
To: sziszi@petra.hos.u-szeged.hu (Szilveszter Adam)
Date: Mon, 6 Nov 2000 16:27:32 +0100 (CET)
Cc: 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 Szilveszter Adam wrote:
> Hi!
> 
> I have just completed a new kernel build (to test the sound:-) but now I
> have a similar problem to that reported on -stable wrt 4.2-BETA. Upon boot,
> ad1 (sitting on ata0 as slave) is not recognized and therefore the boot
> cannot complete. I have even remade the devices because MAKEDEV was changed,
> but it was not the solution. I have completed a buildworld too so sources
> userland and kernel are definitely in sync.
> 
> Of course, I can reconfigure ad1 to become seconadry master (and probably
> that is what I will try next) but this problem seems to be serious and 
> related to
> the one on -STABLE so I thought I would report it. Of course, IDE slave
> disks always worked on this system before. In my kernel config I only have 
> 
> device ata
> device atadisk
> device atapicd
> 
> The disks are Quantum FireBall lct15 on ad0 and Q. Fireball SE 4.3A as
> ad1 but I do not think this should matter. FYI, the ATAPI CD-ROM sitting on
> ata1 master was detected without probs.
> 
> Any ideas?

Damn, why cant I reproduce this misbehavior, please feel free to investigate
why the probe code fails, and then please tell me...

-Søren


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