Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.

If you want to support my work, please consider a small donation:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

wiki:talk:linux:kernelbuilding [2008/06/09 08:38]
alien
wiki:talk:linux:kernelbuilding [2014/02/08 20:37] (current)
87.189.120.44 added remark about cleaning the source tree before compiling
Line 42: Line 42:
 Thanks for spotting this mjc, I fixed it. The kernel sources location is a hot topic on [[http://www.linuxquestions.org/questions/forumdisplay.php?f=14|LQ nowadays]].\\  Thanks for spotting this mjc, I fixed it. The kernel sources location is a hot topic on [[http://www.linuxquestions.org/questions/forumdisplay.php?f=14|LQ nowadays]].\\ 
  --- Eric  --- Eric
- 
 --------------------------------------------------- ---------------------------------------------------
 +---------------------------------------------------
 +Hello Eric/Alien;
 +
 +Thanks to this guide, I 'slacked my box from 2.6.27.7 to 2.6.29.1 this morning. You can't refrain from holding your breath while booting but it went fine. Almost:
 +
 + The nvidia self-compiled kernel wasn't gathered from the 'check your other compiled modules' command;
 + 
 +It's obviously arch-stupid of me to have forgotten about this one, what with the nvidia logo popping up in my face every morning, but a warning to keep some sources at hand in some particular cases may come handy. 
 +
 +As examples that come to mind, there is the Proprietary graphic drivers like ATI or NVIDIA and the VirtualBox module.
 +
 +I am suggesting, if my system wasn't wrong and if it is normal for the new kernel to struggle to get to X with an Xorg.conf claiming for a proprietary module from an older kernel, that you edit the relevant part more or less like this:
 +
 +----
 +
 + **Other packages that contain kernel modules**
 +
 + Most certainly you will have packages installed that contain kernel modules that are not part of the default
 + kernel. Slackware has “alsa-driver” for instance, and if you installed a proprietary graphic driver or any
 + wireless driver, these are basically kernel modules too.
 + Now, with the installation of your new kernel, you will lose these modules, and you have to recompile the
 + sources so that the binary modules match the new kernel.
 +
 + You can get an overview of some packages that have installed a kernel module for your current kernel by running
 + this command (i.e. you must run this command while still running your old kernel):
 +
 +    > cd /var/log/packages
 +    > grep -l "lib/modules/$(uname -r)" *
 +
 + //Warning: not all of them will appear here; typically, for instance, Nvidia or VirtualBox won't!//
 +
 + The mentioned packages will need a recompile, which isn't a chore unless for your graphic driver since you
 + will end up in a terminal, with X respawning in a loop,  upon your first reboot. Be sure to have your driver's 
 + source at hand (a good opportunity to download the latest version), with the necessary documentation at the 
 + ready, to recompile and be able to start your graphic environment again.
 +
 + For ALSA you have a choice: either enable the ALSA driver that is part of the kernel you've just downloaded, 
 + or leave the kernel configuration like Slackware's: disable all ALSA support in the kernel and instead 
 + re-build the alsa-driver package. The 2.6 kernels of Slackware 12.2 have all the ALSA drivers built-in because
 + they will not work with the ALSA driver releases you can install separately.
 +
 +----
 +
 +That's it, thank you & sorry for the bother/clutter if it's irrelevant: I run Enlightenment DR16 from SLiM so it may be slightly a-typical. Cheers. Jean-Philippe 2009/04/07 07:18
 +
 +----
 +Hi Jean-Philippe. \\ Good idea there, I've added a clear warning sign in that section. Thanks, \\
 + --- Eric
 +
 +
 +----
 +
 +Hi Eric,
 +
 +Text under the "Building your kernel" heading says ''make all'' builds "vmlinuz (the uncompressed kernel)".  This should read "vmlinux (the uncompressed kernel)", no?
 +
 +Thanks for the article.  
 +
 + --- Dan 2011-08-05
 +
 +--------------------
 +**Kernel key ID ended**
 +
 +Hi Eric,
 +
 +the kernel key ID is changed. In the square, you write 0x517D0F0E, but it's ended. Now it's 6092693E.
 +
 +Regards
 +
 +Davide
 +--------------------
 +Hi Eric,
 +
 +it's always a good idea to do a "make mrproper" or at least "make clean" before building the kernel. Never expect a source tree to be clean. This applies actually to any software you build from source. Thanks for this article.
 +
 +Regards,
  
 +Heiko

Personal Tools
sponsoring