Re: still-extant potato boot problems (kmod/runany modprobe loop)
> Earlier I reported a problem with installing potato (from scratch)
> and getting errors at boot time like:
> kmod: runaway modprobe loop assumed and stopped
> and many occurrences of:
> modprobe: modprobe: Can't open dependencies files /lib/modules/2.2.17/modules.dep (No such file or directory)
If you are only seeing this on startup and it doesn't affect the rest of
ths instal then please ignore the message. This is an unfortunate result
of unix.o not being compiled into the default kernel, and unless Herbert
somehow manages to get unix.o to fit we can't do much about it.
> I thought I'd try getting to potato by upgrading (a clone of) my
> slink system. The upgrade went pretty well (well, I accidentally
> upgraded the original instead of the clone, but the clone seems
> to be working fine) until I installed the 2.2.17 kernel and rebooted.
> Those boot-time errors returned.
hm... you might get the modprobe runaway message but you really
shouldn't see the "Can't open dependencies file" message -- do you
really not have that file on your system?
> I also started getting a bunch of other errors, such as:
> - "modprobe: Can't locate module xxx"
> (at bootup; for roughly half of the modules)
Please show us the output of "uname -a" and "ls -R /lib/modules/$(uname -r)"
> - "start ppp0: SIOCSIFMETRIC: Operation not supported"
> (asynchonously, after something had triggered diald)
might want to file a but against ppp about this.
> - "Use of setserial/setrocket to set SPD_* flags is deprecated"
> - something like "xmit when interface down"
dunno about that one :(
> - (I can't even ping the other end of my diald's PPP connection
> (I used the numeric IP address logged by pppd when it
dunno about this one either. Hm... looks like it may be caused by
certain modules not being loaded or something?
Debian Developer <email@example.com>