Dave Bresson wrote:
> 
> Hi,
> 
> Just a quick question that shouldn't be too hard to answer.  Since rolling
> my own 2.4.1 kernel, I'm getting this annoying message during bootup that
> i can't get to go away:
> 
> modprobe:  Note:  /etc/modules.conf is more recent than 
> /lib/modules/2.4.1/modules.dep
> 
> i tried doing a 'depmod -a' to redo the modules.dep file, and then reboot,
> however i still got this message.  Somewhere during the bootup process
> something must be doing a touch on modules.conf or something to cause
> this.  Perhaps it's the modprobe call in /etc/init.d/modutils ?  I looked
> at that script, but couldn't figure it out.  Could anyone tell me how to
> fix this?

  apparently no. this question keeps popping up, never answered. I had
the same problem and I wasn't even able to figure out what changes the
date on /etc/modules.conf

  the problem usually goes away after some time. have no idea why it
goes away.

  depmod -a does not help, even depmod -a in boot scripts does not help.
at some point during boot process the last modified data of
/etc/modules.conf changes to current date, but there's no reason for the
file to be modified... I went through start up scripts and wasn't able
to figure out why it's modified, there's no call to update-modules
there...

        erik

Reply via email to