Very Computer

Hi,

I upgraded kernel on one of my Linux boxes and
I don't quite understand why it doesn't want to
upgrade my modules too. Basically I did typical
steps:
make config
make dep
make clean
make zdisk
make modules
and here I'm getting the abovementioned "nothing to do",
however after following booting I'm getting lots of loud
complains that "modules do not match". Does any one
have any idea why it can be ?

Thanks for any help,
Rgds,

Andrei

On Tue, 13 Jul 1999 20:58:10 GMT, Andrei A. Dergatchev
 [snip]

What happened to:

make modules_install

?
That's what copies your updated modules from the /usr/src/linux/...
directories into the /lib/modules/<release>/ subdirectories.

Hope this helps,
John

Hi,

Thanks for your reply,

Yeah, I was a bit too short. Yes of course I did

Quote:>make modules_install

after "make modules"

Quote:

>?
>That's what copies your updated modules from the /usr/src/linux/...
>directories into the /lib/modules/<release>/ subdirectories.

However somehow in my case it only copies to /lib/modules/2.0.36/net
saying for all other subdirs that there's nothing to do :-( I guess as
"make modules" hadn't produced modules, "make modules_install"
can't do anything useful?

Quote:

>Hope this helps,
>John

Andrei

I am having similar problems with my new RH 6.0 installation.  I can
make the kernel image, fix up lilo and everything and be able to boot my
old kernel, but as soon as I hit that 'make_install' I am screwed.  My
old kernel complains that it can't find the modules dependancies, and
the new image gets all upset about
not finding 'inet-pf-1'.  Does anyone have any solutions here?

Also, I am confused as to how two different kernel images can now
peacefully co-exist when using modules?  Don't they try and use the same
modules directory so that only one of them can have the
correct dependancies???  Can anyone offer some explanation?

Thanks so much for your help.

Steve

[snip]

Quote:>Also, I am confused as to how two different kernel images can now
>peacefully co-exist when using modules?  Don't they try and use the same
>modules directory so that only one of them can have the
>correct dependancies???  Can anyone offer some explanation?

Modules should go into directories under /lib/modules. The
directory name is the kernel version, e.g. /lib/modules/2.2.9

You could try running depmod before rebooting in order to
create the module dependencies file; "depmod -a 2.2.9" for
kernel version 2.2.9.

Norman

Quote:> I am having similar problems with my new RH 6.0 installation.  I can
> make the kernel image, fix up lilo and everything and be able to boot my
> old kernel, but as soon as I hit that 'make_install' I am screwed.  My
> old kernel complains that it can't find the modules dependancies, and
> the new image gets all upset about
> not finding 'inet-pf-1'.  Does anyone have any solutions here?

after booting a new kernel, you need to run 'depmod -a' to remake the
dep file (it's usually in /lib/modules/{version}/modules.dep).  The warning
about 'net-pf-1' is b/c you have compiled support for Unix domain sockets
as a module and not included a line like 'alias net-pf-1 unix' to your
/etc/conf.modules.

Quote:> Also, I am confused as to how two different kernel images can now
> peacefully co-exist when using modules?  Don't they try and use the same
> modules directory so that only one of them can have the
> correct dependancies???  Can anyone offer some explanation?

look at /lib/modules, the directory where the modules are installed.  Mine
looks like:
        ./      ../     2.0.36/     2.2.0-pre7/     2.2.5/
which is one directory for each version I currently have installed.  Each one
contains its own modules.dep file, so the kernel doesn't get confused.  A very
elegant design on the kernel people's part IMO.
-ckm