I try to install two loadable modules in Redhat7.2
(kernel: 2.4.7-10smp)
After the installation, they works fine.
But each time when I run the command depmod -a
I will got below error information:
*
depmod: *** Unresolved symbols in
/lib
can't get on internet now as getting unresolved symbols from tulip.o..I went
into xconfig when at book it said delaying connection...thought possibly
something became corrupted whatever...saw nothing odd then again as complex as
these things can be just one thing out of order and ..anyway
After successful recompile, I made modules and installed
them. Upon rebooting I have 25 unresolved symbols reported
in dmesg. How do I start tracking these down. This is
driving me up the proverbial wall and RH is of NO HELP!
Bob
--
Bob Hartung
www.radiologygrouppc.com
www.qchealthwatch.com
Date: Thu, 14 Dec 2000 12:32:27 -0600
From: Bob Hartung [EMAIL PROTECTED]
After successful recompile, I made modules and installed
them. Upon rebooting I have 25 unresolved symbols reported
in dmesg. How do I start tracking these down. This is
driving me up the proverbial wall and RH
successful recompile, I made modules and installed
them. Upon rebooting I have 25 unresolved symbols reported
in dmesg. How do I start tracking these down. This is
driving me up the proverbial wall and RH is of NO HELP!
Bob
--
Bob Hartung
www.radiologygrouppc.com
On Thu, 14 Dec 2000, Bob Hartung wrote:
Dave,
That was it! Now I wonder why in the past, since RH 5.2 I
have never had to rename the original modules directory
under /lib and I have recompiled every kernel since 5.2 when
installed? Oh well, another lession learned.
I did go through
/modules/`uname -r`.last
make modules
make modules_install
/sbin/depmod -a
shutdown -r now
I just added a scsi board, so I had to recompile to add scsi support which
I had previously taken out. Now I have a slew of the infamous ``Unresolved
symbols'' error messages
it in linux.redhat. In my
case, I
found that copying /usr/src/linux/arch/i386/lib/best_function.o to
/lib/modules/uname -r/misc/ got me past the unresolved symbols in
other modules. But, best_function.o will not load. It gives me a
"couldn't find the kernel version the module was compiled for"
e
On Sat, 26 Aug 2000, John Summerfield wrote:
Date: Sat, 26 Aug 2000 08:43:33 +0800
From: John Summerfield [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Subject: Re: Unresolved symbols on kernel rebuild
Another piece of advice, in general to anyone building
On Sat, 26 Aug 2000, John Summerfield wrote:
Date: Sat, 26 Aug 2000 08:43:33 +0800
From: John Summerfield [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Subject: Re: Unresolved symbols on kernel rebuild
Another piece of advice, in general to anyone
I am a newbie too. But, since no one asnwered this question, I would give
it a try. Hope this can induce some more helpful replies. :)
This happened to me couple times. It is usually because you didn't load
some necessary modules or didn't configure your kernel to support those
modules.
Do the
Since nobody answered, I am trying the last time. Please.. any help will
be very appreciated. Thanks. ---sram
-
Hi,
I tried to compile the kernel on a Intel PII using Red Hat 6.2. I did a
make xconfig
make dep
make zImage
make modules
make
On Fri, 25 Aug 2000 [EMAIL PROTECTED] wrote:
Date: Fri, 25 Aug 2000 10:09:11 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain
Subject: RE: Unresolved symbols on kernel rebuild
Nope, it's left-over stuff in linux/include/linux/modules.
Do this:
cd linux/include/linux
Hi,
I tried to compile the kernel on a Intel PII using Red Hat 6.2. I did a
make xconfig
make dep
make zImage
make modules
make modules_install
Stop here, it's all done. Especially if you're using a RHI kernel rpm.
The rpm includes a nisce script that puts the kernel in the right RHL
of this painfull procedure is to get many messages about
unresolved symbols for some modules (about 15 of them).
Is the above procedure the right one?
Am I forgetting something?
Thanks in advance.
George Kalovyrnas
Greece
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
make modules_install
make install
The result of this painfull procedure is to get many messages about
unresolved symbols for some modules (about 15 of them).
Is the above procedure the right one?
Am I forgetting something?
You're not forgetting anything, but the undefined symbols
make modules_install
make install
The result of this painfull procedure is to get many messages about
unresolved symbols for some modules (about 15 of them).
Is the above procedure the right one?
Am I forgetting something?
Thanks in advance.
George Kalovyrnas
Greece
You need to do this; (Note
Cute :-)
R2VvcmdlIEthbG92eXJuYXMgd3JvdGU6DQoNCj4gSXQgaXMgdGhlIDV0aC
B0aW1lIHRoYXQg
SSBoYXZlIHByb2JsZW1zIHdpdGggdGhlIGNvbXBpbGF0aW9uIG9mIHRoZS
BrZXJuZWwuDQo+
IEknbSB0cnlpbmcgdG8gY29tcGlsZSB0aGUga2VybmVsIDIuMi4xNS0yLj
UuMCAoIEkgdGhp
I have built a lot of uni-processor kernels and modules and have
never had this problem.
When I build them with SMP on in a SMP machine, I keep getting
these unresolved symbols.
Make sure you make mrproper and clean up everything in your build tree
when you change the SMP configuration
Alan Cox wrote:
I have built a lot of uni-processor kernels and modules and have
never had this problem.
When I build them with SMP on in a SMP machine, I keep getting
these unresolved symbols.
Make sure you make mrproper and clean up everything in your build tree
when you change
I'm getting lots of these with depmod -a.
I have built a lot of uni-processor kernels and modules and have
never had this problem.
When I build them with SMP on in a SMP machine, I keep getting
these unresolved symbols.
Kernel is 2.2.15 w/RedHat 6.2beta
Any suggestions?
--
Ray Atnip
%- Right... downloaded the RPM for 2.2.14 kernel source from
%- Rawhide, and reverted back to egcs-1.1.2-24 in order to compile
%- a kernel. When I tried gcc-2.95.2 with 2.2.13, the kernel
%- compiled fine, but I got "unresolved symbols" for the modules
%- during boot-up.
%-
%- To m
Right... downloaded the RPM for 2.2.14 kernel source from Rawhide, and
reverted back to egcs-1.1.2-24 in order to compile a kernel. When I tried
gcc-2.95.2 with 2.2.13, the kernel compiled fine, but I got "unresolved
symbols" for the modules during boot-up.
To my surprise, the
My metroX server works smooth, yet the /var/log/Xerrors complains about some
unresolved symbols.
Is this a real error ?
On the other hand, on another computer with a Genius (model 3) serial mouse
metroX seems to conflict with gpm. Though it used to work (at least for one
X session).
The error
Maybe you are not using the first kernel you got when you installed
Linux. Have you re-compiled it? Because the modules are different from a
kernel version to another. When building a new kernel, you have to do
make config
make dep
make clean
make zImage (or zlilo)
make modules
make
Joseph Cheek wrote:
looks like linux is having problems with your token ring adapter. is it
working? have you compiled your own kernel recently? which distro are
you using?
joe
Not using token ring. Using Red Hat 4.2 kernel 2.0.33 with all the updates
exceot for utils-linux or whatever
Anyone know why I get a message at boot stating unresolved symbols
in /lib/modules/2.0.33/net/ibmtr.o ?
And lastly what can I do to correct this? Do I need to recompile or
something? I have never gotten this error before, just the net-pf-4(5)
thing which I know how to take care of. Only thing
Hello list,
I built a kernel modules normally(using RedHat 5.0), but depmod -ae now produces
the following error:
/lib/modules/2.0.31/misc/iBCS: unresolved symbol(s)
kill_fasync_R1ace6ddf
Any use of iBCS reports the following error in the system logfiles:
28 matches
Mail list logo
