I am trying to configure and install kernel-2.6.2 onto my system (dual-boot, RH9 and WinXP). These are the steps I have successfully managed: extracting tarball, make config (I chose the option for PII computers), make dep ,and make clean . All ran without error. I then ran make bzImage , and make modules without difficulty. However, when I ran make modules_install the following error was generated:

[root@localhost linux-2.6.2]# make modules
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
Building modules, stage 2.
MODPOST
[root@localhost linux-2.6.2]# make modules_install
depmod: *** Unresolved symbols in /lib/modules/2.4.24/kernel/crypto/autoload.o
depmod: *** Unresolved symbols in /lib/modules/2.4.24/kernel/crypto/proc.o
Warning: you may need to install module-init-tools
See (there is an URL here, but the forum will not let me post it)
INSTALL drivers/net/dummy.ko
INSTALL fs/smbfs/smbfs.ko
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.2; fi


I went to the suggested link (which the forum will not allow me to post) and saw that this was a "known gotcha"

Known gotchas.
~~~~~~~~~~~~~~
Certain known bugs are being reported over and over. Here are the
workarounds.
... snip ...
- depmod reports Unresolved symbols? depmod from modutils instead of
depmod from module-init-tools is first in $PATH (might be different
$PATHs as $USER and $ROOT)

My problem, is I do not know what I am supposed to do at this point, or how to do it. It appears that I have to re-order the commands in my $PATH, though I am not sure where that is, or how to do it.

Can anyone provide some help?

I'm don't think this would effect anything, but instead of running make dep/bzimage/modules, you can just run 'make'. If you type 'make help' it puts a * by each thing that is done when you run 'make'.

If you have installed the correct version of module-init-tools, try appending .OLD to the end of the old binaries (move the old depmod to depmod.OLD, etc.).
That worked fine for me back under 2.6.0-test1, and should still work with 2.6.2.
You can always move the old binaries back to their original file names if you end up needing to.

[QUOTE]Originally posted by pilot1
[B]I'm don't think this would effect anything, but instead of running make dep/bzimage/modules, you can just run 'make'.

I receive the same error messages.

If you have installed the correct version of module-init-tools, try appending .OLD to the end of the old binaries (move the old depmod to depmod.OLD, etc.).

Now for the newbie question. How do I find out if I have installed teh correct version of module-init-tools?

I appreciate the help you are giving me.

What does 'modprobe -V' return?

For me it returns 'module-init-tools version 0.9.14' and I'm running 2.6.1 without any problems.

Something weird is going on there though cuz it is complaining about unresolved symbols in the 2.4.24 module dir. Did you edit the makefile at all?

You also might wanna try to do 'make menuconfig' instead of 'make config'. This will give you a nice ncurses window where you can easily configure your kernel.

HC

'modprobe -V' returned the following:

[root@localhost linux-2.6.2]# /sbin/modprobe -V
modprobe version 2.4.22
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*

perhaps I am not compiling the kernel properly?

If I need to install the 'module-init-tools' module, would this be found if I run 'make menuconfig'?

Thanks again.

you need to install the module-init-tools. It's a requirement since kernel 2.5.something. Download the sources and then make sure you follow the instructions in the README file (if you don't, bad things might happen) and also look at the FAQ if errors occur.

Whether or not you need this won't be found with menuconfig. But your output of modprobe -V shows that you don't have the module-init-tools installed. I would use make xconfig, though, since it's much easier to deal with.

Thanks for the help! I'll try what you suggested and will post the result here.

On second glance, the Unresolved Symbols error messages don't appear to be anything that matters. Once you install module-init-tools, 2.6 should run fine.

I have downloaded and installed module-init-tools following the instructions that come with the download.

However, when I use the modprobe command, I still do not see the module:

[root@localhost linux-2.6.2]# /sbin/modprobe module-init-tools
modprobe: Can't locate module module-init-tools

Do I need to rebuild the 2.6.2 kernel againl at this point? Or is there something else that I am not doing correctly?

Thanks for your help!

module-init-tools is not a module. It replaces the old versions of modprobe, insmod and the like with new versions. Try
/sbin/modprobe -V
If everything installed correctly, you should get something like

module-init-tools version 3.0-pre9

as output. Do
make modules_install
again. And then do whatever you still need to do to get things going (like moving the right files to /boot and making changes to lilo.conf or grub).

Something is not working right. I have just run modprobe -V again and got the following output:

[root@localhost michael]# /sbin/modprobe -V
modprobe version 2.4.22
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*

Any ideas? I am about ready to give up on upgrading the kernel.

when you installed module-init-tools, where did you install it? If you did just
./configure
then it got installed in /usr/local/sbin and not /sbin. You can check with
whereis modprobe

btw, I think it's better to install it in /sbin.

Type "whereis modprobe"
If you see it's installed to multiple sbin directories, that's your problem. Find out which one is the old one, and move it.

Here is the output from whereis modprobe .

[root@localhost michael]# whereis modprobe
modprobe: /sbin/modprobe /sbin/modprobe.old /etc/modprobe.conf /usr/share/man/man8/modprobe.8

It looks like I have modprobe in /sbin. What else should I be checking? Thanks again!

hmm..
Do "/sbin/modprobe -V"
and then "/sbin/modprobe.old -V" just to see what it says