modules.dep No such file or directory
 

I just upgraded my Kernel version from 2.6.17 to 2.6.18. Although I didn't installed the default kernel from debian repo (2.6.18-4-686). I re-compiled the kernel taking the existing .config file from 2.6.17 and then made few changes. I compiled the kernel debian way.

Now, during the boot with this new kernel I get these messages 7-8 times right in the beginning of the boot process:
Did I disabled something during the kernel configuration?

Thanks

Try running "depmod -a" as root to create one. Does the error go away?

I ran that command and it gave no errors but unfortunately the error messages still appears.

Let's see, next question: Are you using an "initrd" as part of the GRUB entry that boots you into the new kernel?

Yes, I am using it.

Also I just found out (while doing some researching) that when I give the command:

depmod.modutils, I get the follow error message:
I have installed the package module-init-tools.

THanks for your effort...

Cool, was about to see if this thread helped.

What I meant that nothing helped to get rid of that message. I still get that message.

I tried:

mkinitramfs -o /boot/initrd.img-<kerne-version> <kernel-version>


but it didn't help.

You should compile the filesystem drivers into the kernel, not as modules.

Or do:
"apt-get install initramfs-tools"
"cd /usr/src/linux" (ot where ever your source is)
"update-initramfs -c -k 2.6.18"
add "initrd /boot/initrd.img-2.6.18" to the kernel stanza in /boot/grub/menu.lst

ok, I will try that. But I simply took the config file of my old kernel 2.6.17 and made some changes, but I did not play with the filesystem drivers...

Also when I had compiled the kernel, I gave the following command:

Do you think that "--initrd" can be the culprit?

Thanks

You already made an initrd with that.
Can you see it under /boot/ ?
Did you add it to menu.lst?

N.B. I don't use an initrd for anything else than bootsplash. I always compile filesystem drivers in the kernel, not as modules.

Oh yeah the initrd has always been there in my grub menu. I also tried to re create it. Also one thing I would like to mentioned is that I compiled the kernel (.deb) on a different machine and then transferred the package to my machine and just installed it.

Also, can you post your config file which does not require initrd image. I have been trying to do that since a long time but I have never ever figured out a configuration which will make my kernel independent of initrd.

Your help is much appreciated.

Thanks

It doesn't matter if you compile on a different box.

Here's the nearest I found for your kernel. You naturally have to adjust for your hardware, and might want to clean it up some (been too lazy).
http://personal.inet.fi/surf/makuyl/....6.19.2-070111

Ran into a similar problem recently in another thread. It seems that make-kpkg links back to the original source directory. If the source dir is removed/moved after compilation then all those links in /lib/modules go bye bye. I don't know if there is a workaround or if there is a correct way to do it, but for now it is advisable to keep the the linux source directory exactly where it was at compile time.

Thanks Daws, you are exactly right. When I transfer the kernel package to my machine, it does not have the source directory(after all it takes so much of space) and I am in a situation where I cannot afford to keep the source directory. I never had any problems with Sarge.

Can anyone suggest some fix for it? Also although the system boots perfectly after those messages, but I would still like to get rid of those messages. Looks ugly, kind of.

Thanks

Anyone????:scratch: