Module loading question

Module loading question

Post by David Henderso » Tue, 24 Dec 1996 04:00:00



I recently upgraded my 2.0.0 kernel to 2.0.27 by downloading and
compiling the source code.  Tastes great, lasts long time.

Now, when I boot up, I get a message that it can't find the
modules.dep in the modules/2.0.27 directory.  Sure.  I ain't
got one.  So I made a soft link from modules/2.0.0 to 2.0.27.
Now I get lots more error messages.  Nothing is apparantly
amiss, I just get lots of messages.

What do I need to do?

Thanks!
David
--
*-------------------------------------------------------------------*

*-------------------------------------------------------------------*
Outside of a dog, a book is a man's best friend.  Inside of a dog,
it's too dark to read.       --  Mark Twain

 
 
 

Module loading question

Post by Russ Thai » Tue, 24 Dec 1996 04:00:00



> I recently upgraded my 2.0.0 kernel to 2.0.27 by downloading and
> compiling the source code.  Tastes great, lasts long time.

> Now, when I boot up, I get a message that it can't find the
> modules.dep in the modules/2.0.27 directory.  Sure.  I ain't
> got one.  So I made a soft link from modules/2.0.0 to 2.0.27.
> Now I get lots more error messages.  Nothing is apparantly
> amiss, I just get lots of messages.

> What do I need to do?

> Thanks!
> David
> --
> *-------------------------------------------------------------------*

> *-------------------------------------------------------------------*
> Outside of a dog, a book is a man's best friend.  Inside of a dog,
> it's too dark to read.       --  Mark Twain

Remove the soft link.

Go into the /usr/src/linux directory (I assume linux is linked to 2.0.27
source).

Do a

make modules
make modules_install

the next time you reboot all should be OK.

Russ

 
 
 

Module loading question

Post by John Goerz » Wed, 25 Dec 1996 04:00:00



>I recently upgraded my 2.0.0 kernel to 2.0.27 by downloading and
>compiling the source code.  Tastes great, lasts long time.

>Now, when I boot up, I get a message that it can't find the
>modules.dep in the modules/2.0.27 directory.  Sure.  I ain't
>got one.  So I made a soft link from modules/2.0.0 to 2.0.27.

Whoops!  BAD idea :-)

Delete that symlink immediately.

What you probably didn't do was:

make modules; make modules_install

from your Linux source directory.

Quote:>Now I get lots more error messages.  Nothing is apparantly
>amiss, I just get lots of messages.

>What do I need to do?

--
John Goerzen          | Running Debian GNU/Linux (www.debian.org)
Custom Programming    |

 
 
 

1. Networking module loading question

Hi,

When I load a networking module in the new kernels, open routine of the
driver automatically gets called.
Basically I do
#insmod ./3c59x.o

Open routine of the driver gets called even though I have not opened the
interface with
#ifconfig eth0 up

Is there a way to stop automatic opening of the interface? Is kernel doing
it or some user level configuration
controls it?.

- Pankaj

2. PCMCIA SCSI Question

3. editing modules.conf to load sound driver modules

4. Compaq Netelligent for Mandrake

5. IDE-SCSI module corrupts further module loading on 2.5.50

6. Q: what about CheapBytes RedHat 4 Linux distribution?

7. Sb16 and midi module(can't load module midi)~!

8. firewall problems

9. Failed to load module "ati" (module does not exist,0)

10. load module error--kernel-module version mismatch

11. Load three modules with /etc/modules.conf?

12. using rc.modules to load same module twice

13. load module error--kernel-module version mismatch