Re: insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/modules.dep
In-Reply-To: <20001025184953.A21593@radiks.net>; from gothyk@radiks.net on Wed, Oct 25, 2000 at 06:49:53PM -0500
Erik,
I found the thread on debian-user where you and others were discussing the
problem with timestamps on /etc/modules.conf and /lib/modules/`uname
-r`/modules.dep:
http://lists.debian.org/debian-user-0010/msg03774.html
I am having the same problem, so I was wondering if you ever found a
resolution to your problem? I modified /etc/init.d/modutils to read like
this:
(ls -la /etc/modules.conf /lib/modules/`uname -r`/modules.dep ; \
date ) > /root/modutils.debug
echo -n "Calculating module dependencies... "
depmod -a > /dev/null
echo "done."
(ls -la /etc/modules.conf /lib/modules/`uname -r`/modules.dep ; \
date ) >> /root/modutils.debug
I did that so that I could try to see when modules.conf was getting a
newer date between the depmod -a and the modprobe's lower in
/etc/init.d/modutils. When I boot, /root/modutils.debug contains:
-rw-r--r-- 1 root root 3486 Feb 11 2001 /etc/modules.conf
-rw-r--r-- 1 root root 38017 Feb 11 2001 /lib/modules/2.2.18pre21/modules.dep
Sun Feb 11 04:43:24 CST 2001
-rw-r--r-- 1 root root 3486 Feb 11 2001 /etc/modules.conf
-rw-r--r-- 1 root root 38017 Feb 11 04:43 /lib/modules/2.2.18pre21/modules.dep
Sun Feb 11 04:43:30 CST 2001
Then, after booting, if I run /etc/init.d/modutils manually,
/root/modutils.debug contains:
-rw-r--r-- 1 root root 3486 Feb 11 09:53 /etc/modules.conf
-rw-r--r-- 1 root root 38017 Feb 11 04:43 /lib/modules/2.2.18pre21/modules.dep
Sun Feb 11 10:47:08 CST 2001
-rw-r--r-- 1 root root 3486 Feb 11 09:53 /etc/modules.conf
-rw-r--r-- 1 root root 38017 Feb 11 10:47 /lib/modules/2.2.18pre21/modules.dep
Sun Feb 11 10:47:09 CST 2001
Some weird things are happening to the timestamps on these files!
1) When I first boot, before depmod -a, the modtime is not even displayed
by the "ls -la" I put in /etc/init.d/modutils.
2) When I first boot, after depmod -a, the modtime for modules.dep is set
to 4:43, the same as what "date" reports.
3) When I rerun /etc/init.d/modutils, before depmod -a, I can see why I
was getting the "modules.conf is newer than..." messages: because
modules.conf has modtime 9:53 (from before I rebooted.)
4) When I rerun /etc/init.d/modutils, after depmod -a, the modtime
relationship is correct, so I no longer get the "modules.conf is newer
than..." message.
Hypothesis:
- depmod -a is being run before hwclock sets the system clock to the
correct local time, probably because I chose "use UTC time for hardware
clock" when I installed Debian.
- This would also explain why "Robert A. Jacobs" <gothyk@radiks.net>
(http://lists.debian.org/debian-user-0010/msg03811.html) saw that the
problem went away after a while -- because evetually, the difference
between local time and UTC was positive...
So, I guess my next question may be how to set the hardware clock back to
local time? This might fix the problem, but doesn't let me keep the HW
clock at UTC. Perhaps /etc/rcS.d/S50hwclock.sh should be moved ahead in
the boot sequence?
Cheers,
Lyren
Reply to: