Well, i did recompile the kernel on both of them. there are 2 machines, and 8500 and an 8100. i made an installed the modules for the 8500...after a recent hard drive crash on the 8500, i am no longer have them. however, in the past when i had upgraded the kernel, but not the modules (i usually build everything into the kernel) -- it would only give me this error at boot time.
likewise on the 8100, which is using a Mach Kernel - has everything built into it... and only gives me the error at boot time. is there some way to tell the kernel that there are *no* modules? som way to trick it into behaving? thanks! dylan on 03.5.15 5:36 AM, Pisupati, Ajay at [EMAIL PROTECTED] wrote: > hi, > I am no expert, but did you compile the kernel recently and forget > to do make modules_install? > make sure that the file _is_ missing. if the whole directory "2.4.21-rc1" > is missing in /lib/modules then you definately forgot that step. > hth, > ajay > > -----Original Message----- > From: dylan [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 15, 2003 3:01 AM > To: debian ppc > Subject: strange modprobe messages > > > Hi- > > on my 2 ppc machines i have noticed something strange over the past few > days: > > in /var/log/{daemon.log, syslog} > > i am getting the following messages from modprobe in irregular intervals: > > May 14 23:19:09 cmn modprobe: modprobe: Can't open dependencies file > /lib/modules/2.4.21-rc1/modules.dep (No such file or directory) > > May 14 23:24:32 cmn modprobe: modprobe: Can't open dependencies file > /lib/modules/2.4.21-rc1/modules.dep (No such file or directory) > > May 14 23:27:05 cmn modprobe: modprobe: Can't open dependencies file > /lib/modules/2.4.21-rc1/modules.dep (No such file or directory) > > > anyone know what might be causing this... i am pretty sure that it hasn't > been happening that long... > > > thanks in advance, > > dylan -- "The world is a dangerous place to live; not because of the people who are evil, but because of the people who don't do anything about it." -Albert Einstein
