Messages in this thread |  | | From | "Marijn Kruisselbrink" <> | Subject | RE: (2.5.65) Unresolved symbols in modules? | Date | Tue, 18 Mar 2003 02:11:54 +0100 |
| |
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.65; fi > depmod: *** Unresolved symbols in > /lib/modules/2.5.65/kernel/drivers/char/lp.ko > depmod: parport_read > depmod: parport_set_timeout > depmod: parport_unregister_device > ... > [lots and lots of unresolved symbols in lots of modules] > > What am I doing wrong? What web page or kernel documentation should I > be reading? I experienced exactly the same problems when I was running 2.5 kernels for the first time. I think the problem is that the module-init-tools are installed in /usr/local/sbin instead of /sbin. In /sbin are still the ol dmodutils. When you simply run depmod, you will run the module-init-tools, but in the linux-makefile /sbin/depmod is called. You could simply copy the modutils to *.old (depmod -> depmod.old), and make symlinks/copys of the module-init-tools in /sbin (or just make sure make isntall installs them there).
Marijn Kruisselbrink
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |