From owner-freebsd-current Mon Feb 21 22:20:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id AE8FE37B513 for ; Mon, 21 Feb 2000 22:20:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00686; Mon, 21 Feb 2000 22:32:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220632.WAA00686@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Donn Miller Cc: Vladimir Kushnir , freebsd-current@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Sun, 20 Feb 2000 19:59:15 EST." <38B08DE3.7080906@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Feb 2000 22:32:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Vladimir Kushnir wrote: > > = > > Hello, > > I dont't know if this is some HW problem, but after the last update s= ystem > > became unbootable if I load modules by /boot/loader rather them kldlo= ad. = > That seems to be a bug -- I'd just load the modules via /etc/rc.conf fo= r = > now.=A0 Other people have reported problems when loading modules via th= e = > boot loader.=A0 My advice would be to just load them via /etc/rc.conf This is entirely incorrect, and if you're having trouble loading modules = with the loader there's something wrong that needs to be fixed. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message