I get when I boot. So far, I've reinstalled the package, checked that I had module-init-tools, and did mkinitrd as directed in the README.initrd. I didn't have any problem with the previous 2.6.x kernel and it was working fine with 2.6.14.3.

It appears that the problem does lie with module-init-tools. I currently have 3.1; I tried 3.2.2 and made some progress. The problem I had was with 'make install' because it would produce an error saying 'too many symbolic links' or something like that. Does anyone else have that problem? So, I manually copied over lsmod to /sbin/ and it fixed the whole lsmod error. However when I moved the rest of the files to /sbin/, I would get a new error saying either insmod or modprobe does not recognize the -c variable or something like that. I decided to revert back to the old files created by module-init-tools so I can start over again without half broken files, and I just remembered I forgot to do ./generate-modprobe.conf so I hope that will fix it when I try again tomorrow.

Yep. ./generate-modprobe.conf and depmod 2.6.15.3 did the trick.

I'd just like to congratulate you for helping this man out!

lol I think that way this poster did his problem/resolution is the way it SHOULD be.

1: You have a question, and post a new thread

2: You update the original post as you find new things

3: You let everybody know how you resolved the problem.

I commend you for it.

Yup, he did it very well! And he didn't put us down for not knowing the answer. Fancy that!

Unfortunately I'm gonna sound like a jackass newbie... but how do you do a ./generate-modprobe.conf? I can't figure it out!

I think I've come to the conclusion that I must have done something wrong, I don't have seem to have the script. Is it generated while installing the modutils, or is it just automatically in the compressed file?

Please ignore me, I'm 99% retarded... I figured out my problem... I was using modutils... not module-init-tools