Someone tell me if I am wrong buy I think you have two steps in the incorrect order. I believe it should be: The normal steps according to most kernel compile howtos:make dep clean bzImage modules install modules_installAnd by 3rd party modules I didn't mean the ones which come with the ML 9.1, but ones like the nvnet, fglrx, pwcx and such which you have to install yourself separate from kernel, but which are installed by default in the /lib/modules section of the compiled kernel (along with the modules from the default flavour kernel).Best regards,Adrian----- Original Message -----From: Brant FitzsimmonsSent: Tuesday, June 17, 2003 3:04 AMSubject: Re: [expert] how not to lose the 3rd party modules when recompiling kernelAdrian Golumbovici wrote:
What are the steps you are taking to recompile the kernel?Hi all,I am having a bit of a problem. Most times you recompile kernels are to get support for hardware you have, but the default flavour kernel don't have it. at least 90% of the times when you recompile is just to enable a few things, disable some other or after a patch, but using same kernel version. But this should not influence IMHO the 3rd party modules (or at least 99.99% of the time). For some strange reason each time I recompile the kernel, the 3rd party modules just disappear from the /lib/modules/... and then have to reinstall them. With custom compiled modules am not sure if only to copy the previous compiled module in the /lib/modules/... would work (didn't try it/always recompiled), but with rpmed modules you definitely have to rpm -e and then rpm -ivh again. :/ It is a major PITA if you have more than a couple of such modules. Anyone any idea what am I doing wrong, or how to prevent the kernel recompile make my 3rd party modules disappear?Best regards,Adrian
-- Brant Fitzsimmons [EMAIL PROTECTED]"All truth passes through three stages. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." -Arthur Schopenhauer (1788-1860)
make dep clean bzImage modules modules_install install
The last two steps need to be in that order because "install" creates an initrd file based on the contents of your /lib/modules/new_kernel_name which is created by the "modules_install" command. If the "install" command comes first there are no modules present upon which to base the initrd file.
Switch the last two steps and see what happens. If it doesn't work let me know and I'll be sure to shut up. I'm kind of new to helping people. :-)
-- Brant Fitzsimmons [EMAIL PROTECTED] "All truth passes through three stages. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." -Arthur Schopenhauer (1788-1860)
