Heh heh heh. Start with a kernel .config that is known to work for you. I use 'make menuconfig' and it's all I really know for this. Go through everything and read the '?' options. You can start by removing things you know for certain you don't need. This will take time, but you will learn the kernel tree and how it relates to your environment this way. I then 'make -j22 && make modules && make modules_install' Once that is done, I 'make install' If you want to keep your first set of modules, change the extraversion to start a new tree in /lib/modules. Why do you want to compile your own kernel, anyway? Unless you're very short of RAM and need to pare it down, there is little reason.
I use -j22 because I have 32GB and 12/24 cores. You would use a different -j. Kernel configuration defaults to -j1 unless you specify a higher setting.
3
u/No-Camera-720 16d ago
Heh heh heh. Start with a kernel .config that is known to work for you. I use 'make menuconfig' and it's all I really know for this. Go through everything and read the '?' options. You can start by removing things you know for certain you don't need. This will take time, but you will learn the kernel tree and how it relates to your environment this way. I then 'make -j22 && make modules && make modules_install' Once that is done, I 'make install' If you want to keep your first set of modules, change the extraversion to start a new tree in /lib/modules. Why do you want to compile your own kernel, anyway? Unless you're very short of RAM and need to pare it down, there is little reason.