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]
On Mon, Mar 17, 2003 at 04:46:57PM -0800, Torrey Hoffman wrote:
> 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)
--
Vincent Hanquez [Tab]
> 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
On Mon, 2003-03-17 at 16:56, Vincent Hanquez wrote:
> On Mon, Mar 17, 2003 at 04:46:57PM -0800, Torrey Hoffman wrote:
> > 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]
> - 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...
> - The kernel makefile used the module tools under /usr/local/sbin if
> they exist.
I totally agree with this.
At 02:11 AM 3/18/2003 +0100, Marijn Kruisselbrink wrote:
> > 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).
./configure --prefix=/usr --bindir=/bin --sbindir=/sbin
----- Original Message -----
From: Torrey Hoffman <[email protected]>
Date: 17 Mar 2003 16:46:57 -0800
To: Linux Kernel <[email protected]>
Subject: (2.5.65) Unresolved symbols in modules?
> I'm trying 2.5 for the first time. I am getting hundreds of unresolved
> symbols in (all?) modules. Note that:
You'll need latest Rusty's modutils. You can download them
at ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules.
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
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 <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.