From owner-freebsd-current Mon Nov 6 7:23:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 106BF37B4C5 for ; Mon, 6 Nov 2000 07:23:35 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id QAA11114; Mon, 6 Nov 2000 16:20:31 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13so7N-0004q1-00; Mon, 06 Nov 2000 16:23:29 +0100 Date: Mon, 6 Nov 2000 16:23:29 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Cc: sos@freebsd.dk Subject: ad1 is not detected. Message-ID: <20001106162328.A18026@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@freebsd.org, sos@freebsd.dk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message