From owner-freebsd-current Wed Feb 23 12:10:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (Postfix) with ESMTP id D024D37B9C7 for ; Wed, 23 Feb 2000 12:10:22 -0800 (PST) (envelope-from yds@dppl.com) Received: from dppl.com (avs.medianow.com [216.182.7.89]) by paris.dppl.com (Postfix) with ESMTP id 48648963B for ; Wed, 23 Feb 2000 15:10:21 -0500 (EST) Message-ID: <38B43EAC.75158BE0@dppl.com> Date: Wed, 23 Feb 2000 15:10:20 -0500 From: Yarema X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en, uk, ru, ja MIME-Version: 1.0 To: FreeBSD Current Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002220808.AAA59841@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa0400000) Mounting root from ufs:/dev/ad0s3a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 If at the boot prompt I: unload load kernel boot there's no problem. Also there's no problem if loading modules from /boot/loader.conf with a kernel suped and built on Feb. 17th with today's buildworld. Mike Smith wrote: > > > > it does : I've tried > > loading miibus alone : works fine > > loading miibus, then if_xl : loops in loading miibus > > Ok. We know that hurts, don't do that. 8) > From the above remark should I conclude that it's a known problem and we should refrain from loading modules from the boot loader until it works? Or would it help send boot_verbose output from my kernel as well? -- Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message