Date: Sun, 6 May 2001 18:14:06 -0400 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "David W. Chapman Jr." <dwcjr@inethouston.net>, <freebsd-stable@freebsd.org> Subject: Re: Broken module loading and kernel dependencies Message-ID: <001701c0d679$de3b77c0$1200a8c0@gsicomp.on.ca> References: <002101c0d667$b0a7b3d0$1200a8c0@gsicomp.on.ca> <003701c0d66e$32ee5280$931576d8@inethouston.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I did not have to statically compile pppoe support in the kernel. Here are > the modules I loaded > > ng_pppoe > ng_ppp > ng_socket > ng_ether > netgraph > > it all seemed to work good. Did you kldload all of these from the command prompt? The problem seems to crop up when one (or more) modules which are dependancies for others are loaded statically in the kernel, and the others are loaded dynamically. The dynamic loader doesn't see that the module is already present, and tries to load it again. (For PPPoE, the problem manifests when you only have 'options netgraph' in your kernel. This forces ppp to try and load the other ng_* modules dynamically and things fall apart.) > If I did kldload if_rl it would pick up the kingston but not the realtek, if > I loaded if_dc it would pick up the kingston and then I would try to load > if_rl and it would tell me its already loaded and wouldn't pick up the > realtek, but I could not get both nic's to work until I compiled them into > the kernel. I imagine this is because of 'device miibus', a dependency of both. -- Matt Emmerton 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?001701c0d679$de3b77c0$1200a8c0>