Re: /etc/modules.conf is more recent than modules.dep ???
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.
----- Original Message -----
From: "Joost Kooij" <firstname.lastname@example.org>
To: "Balbir Thomas" <email@example.com>
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
> > 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
> > using the debian kernel package tools (make-kpkg). I have also tried
> > 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
> under /etc/modultils/ ?
> > Any ideas what may be going wrong. Note - if I touch modules.dep to make
> > recent . On the next boot something reverses the situation again .
> That sounds weird. I don't understand it either, nor seen it before.
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact