From: Fabio <fab...@du...> - 2005-10-20 08:56:52
|
Hi! I installed a kernel um (2.4.26) from deb packages. In /var/log/syslog of um machine I read this error: "modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.26-3um/modules.dep (No such file or directory)" Because of /lib/modules/2.4.18-37um/ exists, I move it: mv /lib/modules/2.4.18-37um/ /lib/modules/2.4.26-3um but depmod give me some errors (unresolved symbol). How can I solve it? Is there a way to solve it without recompile kernel? Note: I need not to load modules in um but I don't want to see this error. Thanks, Fabio -- Dott. Fabio Marcone 2T srl Telefono +39 - 0871- 540154 Fax +39 - 0871- 571594 Email fab...@du... Indirizzo Viale B. Croce 573, 66013 Chieti Scalo (CH) |
From: Antoine M. <an...@na...> - 2005-10-21 18:02:38
|
> Hi! > I installed a kernel um (2.4.26) from deb packages. In /var/log/syslog > of um > machine I read this error: > "modprobe: modprobe: Can't open > dependencies > file /lib/modules/2.4.26-3um/modules.dep (No such file > or directory)" > Because of /lib/modules/2.4.18-37um/ exists, I move it: > mv /lib/modules/2.4.18-37um/ /lib/modules/2.4.26-3um Don't do that! > > but depmod give me some errors (unresolved symbol). > > How can I solve it? > > Is there a way to solve it without recompile kernel? > > Note: I need not to load modules in um but I don't want to see this > error. Then in this case, simply create an empty directory: mkdir /lib/modules/2.4.26-3um depmod -a And that should be enough. You'll have a modules.dep, just no modules in it, so modprobe won't complain. Antoine |
From: Blaisorblade <bla...@ya...> - 2005-10-20 10:53:52
|
On Thursday 20 October 2005 10:56, Fabio wrote: > Hi! > I installed a kernel um (2.4.26) from deb packages. In /var/log/syslog of > um machine I read this error: > "modprobe: modprobe: Can't open dependencies > file /lib/modules/2.4.26-3um/modules.dep (No such file > or directory)" Which is harmless. Really. You didn't install modules, there's no need for modprobe to work well. If you install modules, that goes away. > Because of /lib/modules/2.4.18-37um/ exists, I move it: > mv /lib/modules/2.4.18-37um/ /lib/modules/2.4.26-3um It's a totally wrong thing to do. Try it on your host, and see things burn out if you want. Modules are almost _never_ compatible between two different kernel releases, especially so much different. > Note: I need not to load modules in um but I don't want to see this error. Hmm, that error is harmless. Really. However: Or otherwise create an empty /lib/modules/2.4.26-3um/ (and possibly even the kernel/ subdirectory), and try running depmod -a again - it should probably create an empty dependency listing and fix the warning. Or simply remove the "depmod -a" or "modprobe whatever" lines in the init scripts (not a great idea, though). -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Messenger: chiamate gratuite in tutto il mondo http://it.messenger.yahoo.com |