On Thu, 21 Aug 2003 17:06:25 +0100
Mark Watts <[EMAIL PROTECTED]> wrote:
> > Code: f7 74 7c 6b ff ff ff 7a 3f f0 7b b1 fe 00 00 f6 80 80 00 00
> > /etc/rc0.d/K00linuxconf: line 31: 4772 Segmentation fault rm -f
> > /var/lock/subsys/linuxconf
I have had these errors ever since the new bootscreen arrived. Don't
know if it is related. However, what I do know is what fixes these
errors on my box.
Don't laugh, I know it sounds strange, but this is what I did (copied
from an earlier message of mine, which sparked an avalanche
of exactly zero replies):
*****
rc.modules has this:
if modprobe -V 2> /dev/null | head -n 1 | grep -q module-init-tools;
then
MODULES=/etc/modprobe.preload
else
MODULES=/etc/modules
fi
now, I was desperately looking for a cause of the failed shutdown.
Forcing modules by comments and shutdown went through:
#if modprobe -V 2> /dev/null | head -n 1 | grep -q module-init-tools;
#then
# MODULES=/etc/modprobe.preload
#else
MODULES=/etc/modules
#fi
this is weird. The line exits 1 as it should. Head and grep shouldn't
break anything. So what about the modprobe? Testing this:
modprobe -V
#if modprobe -V 2> /dev/null | head -n 1 | grep -q module-init-tools;
# then
# MODULES=/etc/modprobe.preload
#else
MODULES=/etc/modules
#fi
sends the kernel to nirvana at shutdown. Don't ask me how this can be...
*****
I still have no idea what this is. I only know that I did some 20
reboots to test this. I then thought that maybe I had a strange setup,
even more so as no one else here seemed to have this problem.
if you use the 2.4 kernel, then try commenting out the lines except the
/etc/modules line. If it works, be glad, and puzzled like me. If it
doesn't work, forget it ;)
Mark
