[lkml]   [2003]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: (2.5.65) Unresolved symbols in modules?
> if [ -r ]; then /sbin/depmod -ae -F  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

Marijn Kruisselbrink

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:34    [W:0.025 / U:3.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site