Skip to contentSkip to conversation

(2.5.65) Unresolved symbols in modules?

DISCUSSION Torrey Hoffman 4 participants 5 messages Mar 18, 2003 – Mar 19, 2003

lore
Share & tools
lore
#0 lore raw

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?

Thanks

Torrey Hoffman
[email protected]

#1 lore raw
Quoted 2 lines · Torrey Hoffman

and then:
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.65; fi

                             ^^^^^^^^^^^^

you seem to use old depmod (not /usr/local/sbin/depmod)

Signature · 1 line
Vincent Hanquez [Tab]
#2 lore raw
Quoted 5 lines · Vincent Hanquez
Quoted 2 lines · Torrey Hoffman

and then:
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.65; fi

                             ^^^^^^^^^^^^

you seem to use old depmod (not /usr/local/sbin/depmod)

Ah, of course. I followed the instructions that came with the module-init-tools, and then just used "make modules_install". So much for following instructions.

I can only make the general observation that it would be helpful if:
- module-init-tools documentation pointed out this drawback of installing to /usr/local/sbin
- module-init-tools documentation stated if it is or is not backward compatible for the 2.4 kernels (is it?)
- The kernel makefile used the module tools under /usr/local/sbin if they exist.

(sigh)

Anyway, thanks again for the advice.

Torrey Hoffman
[email protected]

#3 lore raw
Quoted 2 lines

- module-init-tools documentation stated if it is or is not backward compatible for the 2.4 kernels (is it?)

If you have a new enough version of modutils, and you rename these to depmod.old modprobe.old etcetera, they are backwards-compatible...

Quoted 2 lines

- The kernel makefile used the module tools under /usr/local/sbin if they exist.

I totally agree with this.

#4 lore raw
In reply to Torrey Hoffman
Quoted 15 lines · Torrey Hoffman

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

Quoted 8 lines
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.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.