I have just upgraded my RedHat Linux 7.2 system to 7.3; via the standard upgrade option on the 7.3 CD. All appeared to go well and the install appeared to complete without issue, however when I now bootup my machines I get the error message numerous times. "modprobe: Can't open dependencies file /lib/modules/2.4.7-10/modules.dep (No such file or directory). Once the system finally gets booted and you get the login prompt it fails to let you authenticate in. I have booted the system upon to rescue mode and indeed there is no 2.4.7-10 directory as its now been upgraded to 2.4.18-3. I have tried out of desperation copying the 2.4.18-3 directory to 2.4.7-10, reselecting the upgrade option and also selectively installing additional applications all to no avail. Can anybody point me in the right direction to fix my system? Many thanks in advance, Ian

Just make the file folder 2.4.7-10 a symbolic link to the new folder (2.4.18-3.)

Or if that don't work. recompile your kernel. this should definitely fix it. as dependencies and modules will be redefined to your kernel version.

Mark - the modules all have different symbols for which kernel they are compilied with, so modules from any other kernel won't work with any other kernel version. A kernel recompile will work, but that's more painful than need be. Ian - run: rpm -qa | grep kernel You should see several packages printed out with version numbers. I believe you're missing a rpm for 2.4.18 that you have installed from 2.4.17. (I haven't got my hands on 7.3 for my servers just yet, but I believe RedHat started packaging the modules in a separate rpm from the normal kernel.) You should be able to find this on the first RedHat install disk. Install it with `rpm -i /mnt/cdrom/2.4.18-x-modules.rpm`. The other option is to continue using your older kernel. You would need to modify your grub setup -- ask for more help if you want to do this.

Hello there, I like RH but I have to tell you I got the same error message on a debian (potato 2.2-r6): modprobe: Can't open dependencies file /lib/modules/2.4.19/modules.dep (No such file or directory). The previous messages might be right but here is my opinion (I’m kind of new to linux). What made me get this message was the installation of a newer kernel with parts of it as modules. What I did not see was that in the README file of the 2.4.19 kernel source it was written that in such configuration (module parts), after the kernel compilation we have to run more compilation commands: +++++++++++++++++++++++++++ +make modules +make install_modules +++++++++++++++++++++++++++ After this I got message telling that /etc/modules.conf was newer than /lib/modules/2.4.19/modules.dep or the contrary, I don’t really remember. What was to be done: ++++++++++ +depmod ++++++++++ And then no more problems ... except that modconf still can’t see any module (if anyone has a solution for this marginal problem it would be very nice) All the commands are done in the main directory of the kernel sources. More briefly, what you should do is, as it is said above by mike, reinstall the kernel (from the sources), and then maybe run the + make modules ++ make install_modules ++ depmod + . I’m not sure that helps but please be indulgent. Bye.