Re: (2.5.65) Unresolved symbols in modules?

Bill Davidsen (davidsen@tmr.com)
Wed, 19 Mar 2003 16:29:20 -0500 (EST)


On 17 Mar 2003, Torrey Hoffman wrote:

> I'm trying 2.5 for the first time. I am getting hundreds of unresolved
> symbols in (all?) modules. Note that:
> - I have installed the module-init-tools.
> - "which depmod" as root says /usr/local/sbin/depmod
> - depmod -V as root says "module-init-tools 0.9.10"
>
> But make modules_install as root produces:
>
> [lots of mkdir -p /lib/modules/2.5.65/kernel/...; cp drivers/... .ko
> /lib/modules/2.5.65/kernel/...]
>
> and then:
> 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?

Did you have init-tools installed in /sbin before? This looks like the
message I saw from an early version of the package rather than the 2.4
version. In any case I think you either have to change the path to run the
correct module tool, or remake and install the tool in the compatible mode
which works with 2.4 or 2.5.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

- 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/