Re: compiling kernel and modules issues
> make xconfig > make dep > make clean [make bzImage] you need the kernel image here > make modules > make modules_install > edit /etc/lilo.conf and add lilo header. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: compiling kernel and modules issues
make xconfig make dep make clean [make bzImage] you need the kernel image here make modules make modules_install edit /etc/lilo.conf and add lilo header. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: compiling kernel and modules issues
On Tue, 3 Oct 2000, Tom Cheung wrote: > Would anyone tell me how can I update the kernel and modules > simultaneously without losing previous installed modules.Thanks a lot !! Hi. Let me first say that although I'm subscribed to lkml, I'm really only an aspiring kernel hacker, not in any way a guru at this point in time. However, I have found a solution to your last question that Works For Me(tm). The kernel modules are stored in /lib/modules//. The version number that the kernel will report (to 'uname -r', for example) is set in the top-level makefile, in three variables. What I do is I just append a string, usually -b#, which indicates which build this is from the source tree. For example, the first time I compiled a kernel from my 2.4.0-test9-pre7 tree, I appended '-b0' to the $EXTRAVERSION variable in the makefile, and the modules I compiled for that kernel were placed in /lib/modules/2.4.0-test9-pre7/. When that didn't work for me quite right, I edited the makefile again, changing '-b0' to '-b1', changed my configuration a little, and re-compiled. This time, make modules_install put the new modules in /lib/modules/2.4.0-test9-pre7-b1/. When I booted with the new kernel, it looked there for its modules. As I said, I'm really no guru, and as a result there may be some reason why this solution won't work for other people, and I just don't know about that reason yet. I do hope it helps you, though. The issue of overwriting all my modules when I re-compiled a kernel used to be a real annoyance to me, too, when I had one that pretty much worked but I just wanted to try another configuration. -Andrew C. Dingman [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: compiling kernel and modules issues
On Tue, 03 Oct 2000 16:17:54 +0800, Tom Cheung <[EMAIL PROTECTED]> wrote: >make mrproper >make xconfig >make dep >make clean >make modules >make modules_install >edit /etc/lilo.conf and add lilo header. > >Then after reboot I only see net directory under new modules directory >/lib/modules/2.2-17.Although I have selected sound and other device >drivers as modules.But they haven't build into modules.So is there any >thing I should pay attention to when update kernel and modules or I can >keep old modules and update modules during xconfig ? make modules_install only installs the modules that you compiled. Are you sure that you selected sound as modules? If you think that sound modules should have been built, make your .config available, together with the output from "ls -lR /lib/modules/2.2.17". >Would anyone tell me how can I update the kernel and modules >simultaneously without losing previous installed modules.Thanks a lot !! You should not mix modules from different kernels unless you know exactly what you are doing. It is not a recommended procedure. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
compiling kernel and modules issues
Hello Everyone: The kernel(2.2.14) seems to be no problem when newly installing RedHat 6.2 Then I download new kernel(2.2.17) for updating kernel. Before update I see the modules are OK in directory /lib/modules/kernel-version. Then I extract the 2.2.17 kernel source code in the /usr/src and rename linux to linux-2.2.17 and make symbolic link and delete previous modules version with command (rm -rf /lib/modules/2.2.14-xxx).After that I process the following in /usr/src/linux directory. make mrproper make xconfig make dep make clean make modules make modules_install edit /etc/lilo.conf and add lilo header. Then after reboot I only see net directory under new modules directory /lib/modules/2.2-17.Although I have selected sound and other device drivers as modules.But they haven't build into modules.So is there any thing I should pay attention to when update kernel and modules or I can keep old modules and update modules during xconfig ? Would anyone tell me how can I update the kernel and modules simultaneously without losing previous installed modules.Thanks a lot !! Tom Cheung - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
compiling kernel and modules issues
Hello Everyone: The kernel(2.2.14) seems to be no problem when newly installing RedHat 6.2 Then I download new kernel(2.2.17) for updating kernel. Before update I see the modules are OK in directory /lib/modules/kernel-version. Then I extract the 2.2.17 kernel source code in the /usr/src and rename linux to linux-2.2.17 and make symbolic link and delete previous modules version with command (rm -rf /lib/modules/2.2.14-xxx).After that I process the following in /usr/src/linux directory. make mrproper make xconfig make dep make clean make modules make modules_install edit /etc/lilo.conf and add lilo header. Then after reboot I only see net directory under new modules directory /lib/modules/2.2-17.Although I have selected sound and other device drivers as modules.But they haven't build into modules.So is there any thing I should pay attention to when update kernel and modules or I can keep old modules and update modules during xconfig ? Would anyone tell me how can I update the kernel and modules simultaneously without losing previous installed modules.Thanks a lot !! Tom Cheung - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: compiling kernel and modules issues
On Tue, 3 Oct 2000, Tom Cheung wrote: Would anyone tell me how can I update the kernel and modules simultaneously without losing previous installed modules.Thanks a lot !! Hi. Let me first say that although I'm subscribed to lkml, I'm really only an aspiring kernel hacker, not in any way a guru at this point in time. However, I have found a solution to your last question that Works For Me(tm). The kernel modules are stored in /lib/modules/kernel-version/. The version number that the kernel will report (to 'uname -r', for example) is set in the top-level makefile, in three variables. What I do is I just append a string, usually -b#, which indicates which build this is from the source tree. For example, the first time I compiled a kernel from my 2.4.0-test9-pre7 tree, I appended '-b0' to the $EXTRAVERSION variable in the makefile, and the modules I compiled for that kernel were placed in /lib/modules/2.4.0-test9-pre7/. When that didn't work for me quite right, I edited the makefile again, changing '-b0' to '-b1', changed my configuration a little, and re-compiled. This time, make modules_install put the new modules in /lib/modules/2.4.0-test9-pre7-b1/. When I booted with the new kernel, it looked there for its modules. As I said, I'm really no guru, and as a result there may be some reason why this solution won't work for other people, and I just don't know about that reason yet. I do hope it helps you, though. The issue of overwriting all my modules when I re-compiled a kernel used to be a real annoyance to me, too, when I had one that pretty much worked but I just wanted to try another configuration. -Andrew C. Dingman [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
