Hey there,

I'm currently working on a security module. For this reason, I signed all the binaries on my PC with a digital signature.
When I (re)boot the pc I get the following message:

FATAL: modprobe: Could not load /lib/modules/2.6.38/modules.dep - no such file or directory

NOTE: I think this error only occures during the initrd loading phase. Once init was called, this error is gone.

The weird thing is: Even though it says this error is fatal, there seems to be no effects. My Linux (ArchLinux, own 2.6.38 vanilla-kernel) still boots and I did not see anything wrong.
Also note, that the file is NOT missing, its in his place. As I told, once the initrd phase is over, there seem to be no more problems with modprobe.

Any ideas whats wrong here?

In /lib/modules, is the directory correct? In most distros I have used, the directories within always contained more to the directory name, as so: 2.6.34.8-68.fc13.x86_64

The full path is correct as given in the error message. I do not have any additional stuff on my kernel version, because it is a self compiled vanilla kernel

Oh ok. So loading it manually works you say? Is the module the last one being loaded, or do you have it being loaded right away?

I think you are messing something up here. The file itself is no module. It is afaik the dependency file which is used by modprobe to check that all dependent modules are loaded.

Again I want to stress that this error only occurs during the part of booting, where data is loaded from initrd, once init is called, the error message doesn't occur anymore. So loading modules later one is no problem