Stock 7.1 SuSE Kernel 2.4.0 compile/install failure
Trying to recompile the stock 2.4.0 kernel from SuSE 7.1. However cannot get the 'make modules_install' to complete successfully. This a fresh install of stock 7.1. Here are the kernel compile/install steps taken: # make menuconfig (Selected OK and saved .config) # make dep (Runs to completion OK) # make clean (Runs to completion OK) # make bzImage (Runs to completion OK) # make modules (Runs to completion OK) # make modules_install - *** FAILS - below is an excerpt of text surrounding failure ----------------------------------------------------------------- client:/usr/src/linux # make modules_install make -C kernel modules_install make[1]: Entering directory `/usr/src/linux-2.4.0.SuSE/kernel' make[1]: Nothing to be done for `modules_install'. . . . make[1]: Leaving directory `/usr/src/linux-2.4.0.SuSE/arch/i386/mm' make -C arch/i386/lib modules_install make[1]: Entering directory `/usr/src/linux-2.4.0.SuSE/arch/i386/lib' make[1]: Nothing to be done for `modules_install'. make[1]: Leaving directory `/usr/src/linux-2.4.0.SuSE/arch/i386/lib' cd /lib/modules/2.4.0; \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.0; fi depmod: *** Unresolved symbols in /lib/modules/2.4.0/thinkpad/thinkpad.o depmod: get_module_symbol client:/usr/src/linux # ----------------------------------------------------------------- I have turned off all pcmcia configurations in the .config file and still get this error. My questions are: 1. How do I correct this failure? 2. If this cannot be corrected can I stub out the pcmcia modules, since this is a desktop model with no pcmcia support? -jpg
Yup SUSe doesn't consider kernel upgrades as important. Modutils definelty fails.... and this probibly is due to a difference on how the kernel expects the kernel dameon to be used and how SUSE has it set up. Ruben On 2001.04.23 15:26:00 -0400 John Griffin wrote: Trying to recompile the stock 2.4.0 kernel from SuSE 7.1. However cannot get the 'make modules_install' to complete successfully. This a fresh install of stock 7.1. Here are the kernel compile/install steps taken: # make menuconfig (Selected OK and saved .config) # make dep (Runs to completion OK) # make clean (Runs to completion OK) # make bzImage (Runs to completion OK) # make modules (Runs to completion OK) # make modules_install - *** FAILS - below is an excerpt of text surrounding failure ----------------------------------------------------------------- client:/usr/src/linux # make modules_install make -C kernel modules_install make[1]: Entering directory `/usr/src/linux-2.4.0.SuSE/kernel' make[1]: Nothing to be done for `modules_install'. . . . make[1]: Leaving directory `/usr/src/linux-2.4.0.SuSE/arch/i386/mm' make -C arch/i386/lib modules_install make[1]: Entering directory `/usr/src/linux-2.4.0.SuSE/arch/i386/lib' make[1]: Nothing to be done for `modules_install'. make[1]: Leaving directory `/usr/src/linux-2.4.0.SuSE/arch/i386/lib' cd /lib/modules/2.4.0; \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.0; fi depmod: *** Unresolved symbols in /lib/modules/2.4.0/thinkpad/thinkpad.o depmod: get_module_symbol client:/usr/src/linux # ----------------------------------------------------------------- I have turned off all pcmcia configurations in the .config file and still get this error. My questions are: 1. How do I correct this failure? 2. If this cannot be corrected can I stub out the pcmcia modules, since this is a desktop model with no pcmcia support? -jpg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com -- Brooklyn Linux Solutions http://www.mrbrklyn.com http://www.brooklynonline.com 1-718-382-5752
* Brooklyn Linux Solutions CEO [Mon, 23 Apr 2001 10:45:59 -0400]:
Modutils definelty fails.... and this probibly is due to a difference on how the kernel expects the kernel dameon to be used and how SUSE has it set up.
Which kernel daemon? If you mean the module loader, you're way off. Unresolved symbols means that a module needs a function or variable that either isn't present in any other module or the kernel. Or the symbol is in the kernel but it fails to export it. Philipp -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
participants (3)
-
Brooklyn Linux Solutions CEO -
John Griffin -
Philipp Thomas