Eric Kristopher Sandall wrote:
>
> On Tue, 4 Jun 2002, Michael Zhu wrote:
>
> > Hi, I built a kernel module. I can load it into the
> > kernle using insmod command. But each time when I
> > reboot my computer I couldn't find it any more. I mean
> > I need to use the insmod to load the module each time
> > I reboot the computer. How can I modify the
> > configuration so that the Linux OS can load my module
> > automatically during reboot? I need to copy my module
> > to the following directory?
> > /lib/modules/2.4.7-10/
>
> You don't need to do this, actually, you should _not_ do this.
Forgive me, but how else, without copying the module.o to
/lib/modules/<version>/... and doing "depmod module.o",
is the kernel able to find the module in order to load it?
Is not /lib/modules/<version> the standard place to install
module binaries?
> > I've done that. But it doesn't work.
> >
> > Any help will be appreciated.
>
> Just put the module name in /etc/modules
> example: I want my network card (3Com 3c905c - 3c59x module), vfat, and
> ide-scsi (for my IDE burner) to load at
> boot, so I have in my /etc/modules:
>
> 3c59x
> ide-scsi
> vfat
>
> The order does not matter.
But still, the kernel must be able to find the module
binary and identify its dependencies.
Cheers,
-- Joe
"Thanks to Microsoft, I am now blind in both eyes. They have
rolled back in my head so many times this week that they
are apparently stuck there now."
- Jonathan Rickman, regarding M$ anti-open-source PR.
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
