Re: modprobe errors return
On 18-Oct-99 Martin Fluch wrote: By the way, at every boottime a depmod is executet (perhaps you have seen the 'Updating modules...' message at boottime. If you get ever again such an message (and want to get rid of it) just run a depmod -a I had done that, to no avail. I have not seen the error since recompiling the kernel. modules.deb? or is it modules.dep ? thanks -- Andrew
Re: modprobe errors return
On 18 Oct, Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:44:40 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Could it be a problem with a package? -- Andrew - GnuPG Public KeyID: 0x48109681 *we all live downstream* -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I still get this when I do depmod -a. I have recompiled my kernel depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/comm.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/dstr.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/epat.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/epia.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/fit2.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/fit3.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/friq.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/frpw.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/kbic.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/ktti.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/on20.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/on26.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pcd.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pd.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pf.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pg.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pt.o This also shows up when I boot. Weird. I am still hoping it will go away by itself just like it started by itself :) -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux Clones are people two
Re: modprobe errors return
On 19-Oct-99 Christian Dysthe wrote: - GnuPG Public KeyID: 0x48109681 *we all live downstream* -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I still get this when I do depmod -a. I have recompiled my kernel depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o Mine are gone after recompiling, but before I recompiled, I got rid of everything under /lib/modules/2.2.12/ Oh yes, I have rebooted :) -- Andrew
RE: modprobe errors return
On 18-Oct-99 Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:44:40 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Could it be a problem with a package? I recompiled my kernel after removing /lib/modules/2.12/* and I don't see the errors yet. I already rebooted. *crosses fingers* -- Andrew
Re: modprobe errors return
On Mon, 18 Oct 1999, Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:44:40 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Could it be a problem with a package? modprobe relies on the info stored in /etc/modules.conf and /lib/modules/(kernelversion)/modules.deb, the later is generated by depmod out of the infos found in /etc/modules.conf and the modules itself. /etc/modules.conf is itself generated by the files stored in /etc/modutils/ with update-modules command (this is debian specific - AFAIK) What happened was (as I gues) the folowing: apt-get upgraded an package, which it self added some information to the directory /etc/modutils and ran an update-modules but forgot (perhaps becaus it is not important ... not all of the information stored in /etc/modules.conf is used to generate /lib/modules/2.2.12/modules.deb) to run a debmod ... modprobe only notes this fact. By the way, at every boottime a depmod is executet (perhaps you have seen the 'Updating modules...' message at boottime. If you get ever again such an message (and want to get rid of it) just run a depmod -a as root. Hop that clears the things a bit. Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
