unresolved symbols in modules after kernel recompile
doug reeder
I'm recompiling the 2.2.12 kernel to enable support for a
parallel port printer. Unfortunately, this breaks everything
that's compiled as a modules.
My sequence of commands is
cd /usr/src/linux
make xconfig
make dep
make clean
make modules
make modules_install
make bzdisk
depmod -a
This is where dozens of .o files are reported as having unresolved symbol(s).
I can boot from the new kernel on disk, but nothing that was compiled as
a module works.
I tried doing
make modules
make modules_install
after the make bzdisk, but that didn't change anything.
Neither the Kernal HOWTO, the Modules mini-HOWTO, the O'Reilly
_Linux Network Administartors Guide_ address this problem.
I'm using the Red Hat 6.1 distribution on an HP Visualize Workstation.
--
P. Douglas Reeder Lecturer, Computer. Science. Dept., Ohio State Univ..
ree...@cis.ohio-state.edu http://www.cis.ohio-state.edu/~reeder/reeder.html
GE/S d+ s+:- a C+@$ UH+ P+ L E W++ N+ o? K? w !O M+ V PS+() PE Y+ PGP- t 5+ !X
R>+ tv+ b+++>$ DI+ D- G e+++ h r+>+++ y+>++
Bill Unruh
>I'm recompiling the 2.2.12 kernel to enable support for a
>parallel port printer. Unfortunately, this breaks everything
>that's compiled as a modules.
ALL distributions that I have every heard of support parallel port
printers out of the box. What made you think you should recompile?
Despite what some of the ancient and outdated howtos say, you almost
never should recompile your kernel. You will almost always make things
worse, rather than better.
(Yes, it is possible to recompile one's kernel and have it work.
)
Bill Delphenich
I seem to remember hearing that parallel port support only works when installed as a module.
All distributions I have run into include the module for parallel port support out of the
box.
I have always recompiled my kernel, being pretty much old-school. However, I have been
wrestling with RH7 lately, and I have never run into so many problems. This is not a happy
situation for the Linux community if we lose the ability to do our own kernels.
Rob Funk
doug reeder <ree...@cis.ohio-state.edu> wrote:
>I'm recompiling the 2.2.12 kernel to enable support for a
>parallel port printer. Unfortunately, this breaks everything
>that's compiled as a modules.
>
>My sequence of commands is
>
>cd /usr/src/linux
>make xconfig
>make dep
>make clean
>make modules
>make modules_install
>make bzdisk
>depmod -a
>
>This is where dozens of .o files are reported as having unresolved symbol(s).
>I can boot from the new kernel on disk, but nothing that was compiled as
>a module works.
>
>I tried doing
>
>make modules
>make modules_install
>
>after the make bzdisk, but that didn't change anything.
The second way is the correct order -- make and install modules after
making everything else.
When recompiling the same version of the kernel that you are already
using, it often helps to rename the module directory that you're
using, so that the new compile uses its own module directory. Try "mv
/lib/modules/2.2.12 /lib/modules/2.2.12.old", then "make
modules_install" again. Otherwise you get depmod confusion because of
old modules that weren't replaced.
But if you're recompiling the kernel anyway, I'd recommend just
downloading 2.2.17 or (if it's released yet) 2.2.18, since a lot has
been fixed since 2.2.12. See ftp.kernel.org.
--
==============================| "A slice of life isn't the whole cake
Rob Funk <rf...@funknet.net> | One tooth will never make a full grin"
http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"