Re: 1.3.57 module loading problems
I think that if you answer 'Yes' to "Set version information for all
symbols for modules" this may fix your problem. However, you don't need
modules. Everything can be compiled statically in the kernel (including
PPP). There is a glitch, if your answer 'Yes' to setting version
information above, then you currently must compile PPP support as a
module. So, if you don't want to use modules, do not answer yes to the
above question.
Also, it seems as if they're changing some of the directories where
various modules will reside. Thus, modprobe has trouble finding some of
them.
The only reason I can see for using modules is that if you only very
rarely need some feature provided by a module and you want to save a
little memory by not loading it all the time. If this is not your case,
then I would recommend not using modules.
Gerry
gerry@blue.intele.net
On Wed, 31 Jan 1996, Dale Scheetz wrote:
> I've really done it now. (Thank goodness I have an alternate kernel to
> boot from)
> Due to information I recieved (I think from linux-kernel) on how to get
> the "unsatisfied symbols" messages from dependancy checking to go away, I
> rebuilt the kernel with the following process:
>
> make config
> make depend
> make clean
> make zImage
> make modules
> make modules_install
>
> In the past I was not doing the make modules_install, however all it
> seems to do is to put bsd_comp.o into /lib/modules/1.3.57/net, but when I
> reboot this new kernel it can't load any modules!
> When I tried to insmod the modules manually, I get:
> can't open /lib/modules/misc/ppp.o
> So, I found the proper .o files and moved them to /lib/modules/misc (BTW,
> the misc part of the path did not exist). Now insmod says:
> kernel-version needed but can't be found
>
> I am getting really tired of the way modules don't work, and the
> statement "Linus doesn't use modules" is a very poor excuse for these
> features not working.
>
> I would like to improve my understanding of how modules work (and fail
> to) to the point that I can at least use them. I suspect that this
> problem is fixable in the config phase, if I only knew which option I was
> choosing wrong. I have checked yes to all the module support/symbol
> checking options and this leads me to my primary question.
>
> If I say no to external module support, to the modules I declare needed
> (like ppp) automaticaly get compiled into the kernel? In other words, how
> does Linus "not use modules" and get ppp to work?
>
> BTW, the isofs module fails to initialize (even on my fallback kernel,
> 1.3.43). I assume that this is because I have SCSI support compiled in
> and this includes isofs, so the module is superfluous (the iso file
> systems work just fine)
>
> The loadable modules concept has so much promise that I would prefer to
> come to terms with it, rather than ignore it an hope it will go away.
>
> One of the greatest possible uses for loadable modules would be during
> installation. If the modules could be configured during installation (on
> the installation disk) then small machines (<8meg) with specialty
> hardware would not be such a pain to install on.
>
> Can anyone point me to documentation that provides a functional
> description of how modules are supposed to work?
>
> TIA,
>
> Dwarf
>
> ------------ --------------
>
> aka Dale Scheetz Phone: 1 (904) 877-0257
> Flexible Software Fax: NONE
> Black Creek Critters e-mail: dwarf@polaris.net
>
> ------------ If you don't see what you want, just ask --------------
>
>
Reply to: