Menu
▾
▴
Re: Unresolved Symbols
|
From: Joshua B. <bj...@en...> - 2003-06-10 08:36:41
|
I don't get this line "you have modversions, but different." what does=20= that really mean? -Josh On Tuesday, June 10, 2003, at 02:11 AM, Leonid Froenchenko wrote: > This is example of module compiled WITH modversions (numbers at the=20 > end of symbol). If in your /proc/ksyms > you see register_chrdev instead of register_chrdev_Rsmp_63ef0035 - you=20= > have no modversions in kernel, but > if you see different number - you have modversions, but different. > > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > register_chrdev_Rsmp_63ef0035 > > Joshua Bernstein wrote: > > So whats up with these errors then? How can I check to see if the=20 > current running kernel was compilied with Modversions? What would I=20 > look for in /proc/ksyms? > > Thanks for all of your help... > > -Josh > > > On Tuesday, June 10, 2003, at 01:53=A0 AM, Leonid Froenchenko wrote: > > The concept is consistency. If you have kernel WITH modversions, you=20= > must compile modudles also WITH modversions. When you > changing some options in kernel config, you need to recomple kernel to=20= > reflect new configurations > > Joshua Bernstein wrote: > > I know about looking at /proc/ksyms, but it really doesn't tell me=20 > what options would provide the symbols I'm missing... It just tells me=20= > what I already have... I know the symbols are missing... Maybe I'm=20 > missing some concept here.. > > Alright, so I've disabled Module Versioning and I'm left with this=20 > during a make: > > mbox:~/lirc# make > cd . \ > =A0 && CONFIG_FILES=3D CONFIG_HEADERS=3Dconfig.h \ > =A0=A0=A0=A0 /bin/sh ./config.status > config.status: creating config.h > config.status: config.h is unchanged > config.status: executing default-1 commands > make=A0 all-recursive > make[1]: Entering directory `/root/lirc' > Making all in drivers > make[2]: Entering directory `/root/lirc/drivers' > Making all in lirc_dev > make[3]: Entering directory `/root/lirc/drivers/lirc_dev' > DIR=3D`pwd`; (cd /usr/src/linux/; make SUBDIRS=3D$DIR obj-m=3Dlirc_dev.o= =20 > modules) > /usr/src/kernel-source-2.4.20/scripts/pathdown.sh: line 4: TOPDIR:=20 > parameter null or not set > make[4]: Entering directory `/usr/src/kernel-source-2.4.20' > make[4]: *** No rule to make target `lirc_dev.o', needed by=20 > `modules'.=A0 Stop. > make[4]: Leaving directory `/usr/src/kernel-source-2.4.20' > make[3]: *** [lirc_dev.o] Error 2 > make[3]: Leaving directory `/root/lirc/drivers/lirc_dev' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/root/lirc/drivers' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/lirc' > > -Josh > > On Tuesday, June 10, 2003, at 12:54=A0 AM, Leonid Froenchenko wrote: > > Your lirc_serial has been compiled WITH modversions, but kernel you're=20= > running was =A0not, or with different ones. To > know the difference take a look to /proc/ksyms - this is what your=20 > kernel have, and compare output with list you put in mail. > > Joshua Bernstein wrote: > > I need module versioning in the kernel? I didn't think that was=20 > nesscary and was just an option to allow you load symbols that were=20 > compiled with a different version of the kernel... > > -Josh > > > > On Tuesday, June 10, 2003, at 12:37=A0 AM, Leonid Froenchenko wrote: > > yes ! you missing module versions > > Joshua Bernstein wrote: > > Hey Guys, > > =A0=A0=A0=A0Any idea what option I'm missing in my Kernel = Configuration?=20 > Regardless of what module I try to load I always get these symbols as=20= > errors: > > mbox:/lib/modules/linux/misc# modprobe lirc_serial > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > register_chrdev_Rsmp_63ef0035 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > add_wait_queue_Rsmp_8157eafc > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > exit_files_Rsmp_7306a8bc > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > __generic_copy_to_user_Rsmp_d523fdd3 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > _mmx_memcpy_Rsmp_15670e2d > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > wake_up_process_Rsmp_98f9d9dc > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > unregister_chrdev_Rsmp_c192d491 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > __pollwait_Rsmp_00b7d791 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > sprintf_Rsmp_1d26aa98 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > exit_fs_Rsmp_e9cd0de5 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > schedule_timeout_Rsmp_17d59d01 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > __wake_up_Rsmp_127fda83 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > kfree_Rsmp_037a0cba > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > printk_Rsmp_1b7d4074 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > remove_wait_queue_Rsmp_9cc53e22 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > kmalloc_Rsmp_93d4cfe6 > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > pidhash_Rsmp_c862817d > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > interruptible_sleep_on_Rsmp_8c23e4cb > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > schedule_Rsmp_4292364c > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > kernel_thread_Rsmp_7ca341af > /lib/modules/2.4.20-k7/misc/lirc_dev.o: unresolved symbol=20 > exit_mm_Rsmp_87622d3d > /lib/modules/2.4.20-k7/misc/lirc_dev.o: insmod=20 > /lib/modules/2.4.20-k7/misc/lirc_dev.o failed > /lib/modules/2.4.20-k7/misc/lirc_dev.o: insmod lirc_serial failed > mbox:/lib/modules/linux/misc# > > > > -Joshua Bernstein > Systems Analyst > University of Arizona > Tucson, Arizona, USA > > > > ------------------------------------------------------- > This SF.net email is sponsored by:=A0 Etnus, makers of TotalView, The=20= > best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > > > -- > > > > --------------------------------------------------------- > > <image.tiff> > > > > This message may contain confidential, proprietary or legally=20 > privileged information. The information is intended only for > the use of the individual or entity named above. If the reader of this=20= > message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this=20 > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by telephone, or=20= > by e-mail and delete the message from your computer. > > > > > <images.jpeg> > > -Joshua Bernstein > Systems Analyst > University of Arizona > Tucson, Arizona, USA > > > > > > > -- > > > > --------------------------------------------------------- > > <image.tiff> > > > > This message may contain confidential, proprietary or legally=20 > privileged information. The information is intended only for > the use of the individual or entity named above. If the reader of this=20= > message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this=20 > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by telephone, or=20= > by e-mail and delete the message from your computer. > > > > > <images.jpeg> > > -Joshua Bernstein > Systems Analyst > University of Arizona > Tucson, Arizona, USA > > > > > > > -- > > > > --------------------------------------------------------- > > <image.tiff> > > > > This message may contain confidential, proprietary or legally=20 > privileged information. The information is intended only for > the use of the individual or entity named above. If the reader of this=20= > message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this=20 > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by telephone, or=20= > by e-mail and delete the message from your computer. > > > > > <images.jpeg> > > -Joshua Bernstein > Systems Analyst > University of Arizona > Tucson, Arizona, USA > > > > > > > -- > > > > --------------------------------------------------------- <image.tiff> > > > This message may contain confidential, proprietary or legally=20 > privileged information. The information is intended only for > the use of the individual or entity named above. If the reader of this=20= > message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this=20 > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by telephone, or=20= > by e-mail and delete the message from your computer. > > > > > <images.jpeg> -Joshua Bernstein Systems Analyst University of Arizona Tucson, Arizona, USA |