Re: Modprobe errors after second kernel compile.
On Tue, 3 Jun 2003 09:57:39 +0100 Patrick Beard [EMAIL PROTECTED] wrote: Hi, I upgraded to kernel 2.4.19 to allow me to add the i810 framebuffer patch. everything went fine except I had missed the generic-scsi support and so my cdrw didn't work. I turned this option on and recompiled. This time when I went to install the resulting .deb I received a warning about installing the same revision of kernel (I did change the -rev on the kpkg command) and modules.dep could be wrong but this would be sorted on a reboot. However now when I boot up I get a handful of modprobe errors for things that are working just fine (sound, usb mass storage and the like). The system is working fine but I hate these errors. What did I do wrong, and how can I resolve it? See section 5 of the kernel-package newbiedoc: http://newbiedoc.sourceforge.net/system/kernel-pkg.html#BUILD-KERNEL-PKG Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modprobe errors I cannot fix
On Fri, Oct 06, 2000 at 02:04:17AM +, Pollywog wrote: I just upgraded to 2.4.0 test9 kernel and got this error: lilypad modprobe: modprobe: Can't locate module char-major-14 I then made sure that /etc/modutils/aliases contained this: alias char-major-14 off I ran update-modules, but still I get the modprobe error. Have I done something incorrect? I dunno, but I have: alias char-major-14 soundcore You got a sound card? If you don't have sound support, maybe just comment it out. -- /bin/sh ~/.signature: Command not found
Re: modprobe errors I cannot fix
On 06-Oct-2000 Eric G . Miller wrote: I ran update-modules, but still I get the modprobe error. Have I done something incorrect? I dunno, but I have: alias char-major-14 soundcore You got a sound card? If you don't have sound support, maybe just comment it out. I have a sound card, but I am not using kernel sound support; I am using the commercial OSS drivers. -- Andrew
RE: modprobe errors I cannot fix
On 06-Oct-2000 Pollywog wrote: I just upgraded to 2.4.0 test9 kernel and got this error: lilypad modprobe: modprobe: Can't locate module char-major-14 I then made sure that /etc/modutils/aliases contained this: alias char-major-14 off I ran update-modules, but still I get the modprobe error. I found a file /etc/modutils/alsa and I believe it was the cause of the problem. I have removed it and run 'update-modules' and I believe that should take care of it. thanks -- Andrew
Re: modprobe errors again
On Thu, 21 Oct 1999, Pollywog wrote: There has to be a bug in some package, because I upgraded my potato system and again I get the modprobe errors below: Oct 21 19:21:08 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep This is a know bug in the modutils package. See the bugs page on this. Solution is to add the file /etc/modutils/paths and add entries for each one of subdirectories under /lib/modules/2.2.12/. Then run update-modules. -- Jean Pierre
Re: modprobe errors again
On 21-Oct-99 Jean Pierre LeJacq wrote: On Thu, 21 Oct 1999, Pollywog wrote: There has to be a bug in some package, because I upgraded my potato system and again I get the modprobe errors below: Oct 21 19:21:08 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep This is a know bug in the modutils package. See the bugs page on this. Solution is to add the file /etc/modutils/paths and add entries for each one of subdirectories under /lib/modules/2.2.12/. Then run update-modules. Thanks, I will try that. -- Andrew
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]
Re: modprobe errors after apt-get upgrade
On 16 Oct, Martin Fluch wrote: Then recompile the kernel ... that should work. Nope, did that. Same errors. -- 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 after apt-get upgrade
On Fri, 15 Oct 1999, Christian Dysthe wrote: On 16 Oct, Martin Fluch wrote: Then recompile the kernel ... that should work. Nope, did that. Same errors. Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a look at their date) ... I guess you can savely remove them ... or move /lib/modules/2.2.12 to /lib/modules/2.2.12.old and install the modules again... Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors after apt-get upgrade
On 16 Oct, Martin Fluch wrote: Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a look at their date) ... I guess you can savely remove them ... or move /lib/modules/2.2.12 to /lib/modules/2.2.12.old and install the modules again... There are no old modules in there. Only the new ones created and installed by using make-kpkg and dpkg. These errors started a couple of days ago after a dselect upgrade. I have not touched the kernel and the modules since I kernel 2.2.9 came out a while back until I did the recompile today. I suppose I just have to wait and keep upgrading my potato box and hope these errors disappear just as mysteriously as they appeared? -- 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 after apt-get upgrade
On 16-Oct-99 Christian Dysthe wrote: On 16 Oct, Martin Fluch wrote: Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a look at their date) ... I guess you can savely remove them ... or move /lib/modules/2.2.12 to /lib/modules/2.2.12.old and install the modules again... There are no old modules in there. Only the new ones created and installed by using make-kpkg and dpkg. These errors started a couple of days ago after a dselect upgrade. I have not touched the kernel and the modules since I kernel 2.2.9 came out a while back until I did the recompile today. I suppose I just have to wait and keep upgrading my potato box and hope these errors disappear just as mysteriously as they appeared? That is what I am going to do :) -- Andrew
Re: modprobe errors after apt-get upgrade
You upgrade to a new version of modutils. Do an update-modules. Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Any ideas on how to fix this? -- Andrew - GnuPG Public KeyID: 0x48109681 *we all live downstream* -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- David Natkins Email to: [EMAIL PROTECTED] Fax to: (718) 488-1780 Phone: (718) 403-2474
Re: modprobe errors after apt-get upgrade
On Fri, 15 Oct 1999, Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Any ideas on how to fix this? depmod -a Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors after apt-get upgrade
On 15 Oct, Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Any ideas on how to fix this? -- Andrew - GnuPG Public KeyID: 0x48109681 *we all live downstream* -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I am gettting som /usr/lib/modules.something..errors when I boot after yesterdays upgrade. I am not able to read it, cause it races by so fast, and I can not see them it when I do a dmesg.It looks like it says something about /lib/modules/2.2.9/modules.dep and /etc/modules.conf. I have some messages like this in my daemon.log also now that are new. There's at least 10 of these module related messages during boot that I have never seen before. No idea what this is either. -- 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 after apt-get upgrade
On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: 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 looks like what I am getting while booting also. This started yesterday after an upgrade of my potato box. -- 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 after apt-get upgrade
On 15-Oct-99 Christian Dysthe wrote: On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: I got: depmod: *** Unresolved symbols in /lib/modules/2.2.12/misc/snd.o -- Andrew
Re: modprobe errors after apt-get upgrade
On 15-Oct-99 David Natkins wrote: You upgrade to a new version of modutils. Do an update-modules. That was the first thing I did. It did not stop the messages. thanks -- Andrew
Re: modprobe errors after apt-get upgrade
On Fri, 15 Oct 1999, Christian Dysthe wrote: On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: 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 ... Then recompile the kernel ... that should work. Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors
On Mon, Mar 08, 1999 at 07:39:12PM -, Pollywog wrote: Here are some errors I am getting. Below I include my /etc/modules. I compiled the modules into the kernel, so do I need /etc/modules at all? You have compiled the modules for _use_ with the kernel. If you wanted them to be build _into_ the kernel you should have compiled them not as modules, but as regular kernel options. Unusual System Events =-=-=-=-=-=-=-=-=-=-= Sorry, can't help you there. I've no ideia. # /etc/modules #auto Anyway, why don't you uncomment the auto entry? This way the kernel loads the modules as it needs them, and you don't have to mention all of them in /etc/modules. OTOH, why don't you try 2.2.x? It's great with the modules, installing and removing them from memory and you don't even notice. Cheers, -- Pedro Guerreiro (aka digito)([EMAIL PROTECTED]) Diplomacy: the art of letting someone have your own way.
Re: modprobe errors
On 09-Mar-99 Pedro Guerreiro wrote: OTOH, why don't you try 2.2.x? It's great with the modules, installing and removing them from memory and you don't even notice. I am staying away from the newer kernels because I don't know anything about them, and I don't know how to use ipchains. I fixed my problem. All I had to do was remove the entries I had in /etc/modules since all the modules are compiled into the kernel. I upgraded to kernel 2.0.36 without problems, so I must have goofed the first time I tried it. I probably left something out. thanks -- Andrew -- PGP Key ID 0x5EE61C37 PGP5.0 --
