Messages in this thread |  | | Date | Wed, 20 Sep 2000 16:43:28 +0200 | From | Graham Leggett <> | Subject | missing symbols with depmod - how to solve this? |
| |
Hi all,
I have recently been plagued with the problem of depmod complaining of missing symbols after a kernel compile - and I am completely stumped as to what is causing this.
- I confirm that no pre-existing /usr/src/linux or /lib/modules/2.2.17 directories exist. - I download and unpack a virgin v2.2.17 kernel into an empty /usr/src/linux directory. - I compile the kernel with the following commands:
make menuconfig ; make dep ; make clean ; make bzImage ; make modules ; make modules_install
- The compile ends successfully without any errors. - I copy the resulting bzImage and System.map files to the /boot directory, renaming them System.map-2.2.17 and vmlinubz-2.2.17 respectively. - I run
depmod -m /boot/System.map-2.2.17 -a 2.2.17
And I get this:
[root@jolanda /root]# depmod -m /boot/System.map-2.2.17 -a 2.2.17 /lib/modules/2.2.17/fs/nls_koi8-r.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-15.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-14.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-9.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-8.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-7.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-6.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-5.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-4.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-3.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-2.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_iso8859-1.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_cp950.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_cp949.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_cp936.o: unresolved symbol(s) /lib/modules/2.2.17/fs/nls_cp932.o: unresolved symbol(s) [hundreds of lines snipped]
If I ignore the above, configure LILO with the new kernel and reboot, the same problem happens when depmod -a runs during startup. The system is a Redhat Linux v6.1 system.
Has anyone any idea what on earth is causing this? I have been trawling the internet for a solution to this problem, but in all the documentation depmod is supposed to "just work" and in my case it "just doesn't".
Anyone encountered this before?
Regards, Graham -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |