I remember I had a similar problem, but I don't think it was serious. I think it was caused by the system clock being converted from GMT to local time after modprobe checks the timestamps on those files. I fixed my problem by touching /etc/module.conf back a few hours. I think your problem will dissapear in a few hours.
Duncan Findlay ----- Original Message ----- From: "Joost Kooij" <[EMAIL PROTECTED]> To: "Balbir Thomas" <[EMAIL PROTECTED]> Cc: <debian-user@lists.debian.org> Sent: Sunday, June 24, 2001 9:31 AM Subject: Re: /etc/modules.conf is more recent than modules.dep ??? > On Sat, Jun 23, 2001 at 08:43:56PM -0500, Balbir Thomas wrote: > > hi, > > I keep getting the following error message at boot time: > > > > modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.4.5/modules.dep > > > > On other occasions it is insmod that issues the message. I have had this problem since kernel 2.2.17. I am presently running kernel 2.4.5 compiled by myself > > using the debian kernel package tools (make-kpkg). I have also tried things > > like depmod -A . > > Try it again, with "depmod -a" and see if that changes it for the better. > > Did you use update-modules to generate /etc/modules.conf from all the files > under /etc/modultils/ ? > > > Any ideas what may be going wrong. Note - if I touch modules.dep to make it more > > recent . On the next boot something reverses the situation again . > > That sounds weird. I don't understand it either, nor seen it before. > > Cheers, > > > Joost > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >