Date: Tue, 20 Mar 2001 02:29:30 -0600 From: Andrew Hesford <ajh3@chmod.ath.cx> To: Sean Kelly <smkelly@zombie.org> Cc: Kris Kennaway <kris@obsecurity.org>, freebsd-stable@freebsd.org Subject: Re: Booting with modules Message-ID: <20010320022930.A1089@cec.wustl.edu> In-Reply-To: <20010320020229.A435@edgemaster.zombie.org>; from smkelly@zombie.org on Tue, Mar 20, 2001 at 02:02:29AM -0600 References: <20010319235314.A444@edgemaster.zombie.org> <20010319230008.B15322@xor.obsecurity.org> <20010320013443.A472@edgemaster.zombie.org> <20010319235300.A16082@xor.obsecurity.org> <20010320020229.A435@edgemaster.zombie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well... I know that xl and dc get along just fine, since the packets you have received that constitute this message passed through a firewally/router using xl0 and dc0 as the two network interfaces. Have you built a kernel with all these options built in? Is there still trouble? Why do you need /boot/loader to load them right away? Won't the kernel automatically load the modules the first time they are used? I've always believed in the one-giant-kernel point of view. Most things, definitely NIC drivers, should be built right into the kernel. Try this first. If recognition still fails, maybe you have broken or conflicting hardware. On Tue, Mar 20, 2001 at 02:02:29AM -0600, Sean Kelly wrote: > No matter whether I specify miibus or not in loader.conf, it still fails to > load if_xl.ko even though it is registered. If, however, I remove if_dc.ko > and miibus.ko from loader.conf, then if_xl.ko will load properly. It > seems to me that the two modules (xl and dc) don't get along, or that there > is some sort of limit to the number of modules it wants to load. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010320022930.A1089>