fsvara
01-09-2001, 05:31 PM
I'm using SuSE 6.4 and I just compiled my 2.4.0 kernel. After booting it
I came through some very strange errors I couldn't explain. <br>
After some searching, I found that all of these errors were caused by modules
not being found. I also found that this was propably due to problems with
my modules.dep file.<br>
With all kernels I previously compiled myself, the file /lib/modules/[kernelversion]/modules.dep
was automatically generated, with all the available modules and their dependencies
listed.
The file /lib/modules/2.4.0/modules.dep existed also, but it was empty. I
am quite sure that this is why modprobe keeps answering 'Module bla not found'.
How can I have the correct content for my modules.dep for the kernel 2.4.0
generated?
I find this pretty strange as this file was always autogenerated with the
modules I had chosen in the kernelconfug when compileing 2.2.x kernels.<br>
Thanks In Advance,
fsvara
I came through some very strange errors I couldn't explain. <br>
After some searching, I found that all of these errors were caused by modules
not being found. I also found that this was propably due to problems with
my modules.dep file.<br>
With all kernels I previously compiled myself, the file /lib/modules/[kernelversion]/modules.dep
was automatically generated, with all the available modules and their dependencies
listed.
The file /lib/modules/2.4.0/modules.dep existed also, but it was empty. I
am quite sure that this is why modprobe keeps answering 'Module bla not found'.
How can I have the correct content for my modules.dep for the kernel 2.4.0
generated?
I find this pretty strange as this file was always autogenerated with the
modules I had chosen in the kernelconfug when compileing 2.2.x kernels.<br>
Thanks In Advance,
fsvara