Fixing a kernel link problem
I'm not really sure what problem I have but....
hopehope123 I am not sure it is impossible. I have four 10,000rpm Ultra-320 SCSI hard drives (and two 7,200 rpm EIDE hard drives on the same...
I am trying to compile a kernel for arm architecture. I need to use the uinput modules, including keybdev.
When I try to modprobe keybdev I get:
lib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: unresolved symbol handlescancodelib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: unresolved symbol keyboardtaskletlib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: unresolved symbol kbdledfunclib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: unresolved symbol kbdrefreshledslib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: insmod lib-modules-2.4.26-ys-kernel-drived-lib-modules-2.4.26-ys-kernel-drivers-input-keybdev.o: insmod keybdev failed
The bit of code that exports those symbols is in drivers-char-keyboard.c and even exports those symbols:
EXPORTSYMBOL(handlescancode); EXPORTSYMBOL(kbdledfunc); EXPORTSYMBOL(kbdrefreshleds);
So the only thing I can think of is that something (the linker???) is not hooking up keybdev to the symbols exported by keyboard....
Hi Jean , Thanks for your reply. -I am not sure it is impossible. I have four 10,000rpm Ultra-320 SCSI hard -drives (and two 7,200 rpm EIDE hard...
I know next to nothing about how the various dependencies and symbols are resolved during a kernel build and module inserts.... But clearly the code is there, the symbols should be there, but the module is not seeing them.
Are there any commands that would let me see the kernel symbols that are exported?
Or perhaps can I modify the Makefile(s) to tell the kernel it needs to make that connection?
(And no I cannot change to a newer kernel.... It's a highly modified kernel for a particular piece of hardware I am working with....)
Linux groups from Newsgroups