On 1/25/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote: > I have a plain vanilla Centos source (not 100% sure where we got it > from), but I can't seem to get a build that installs correctly. Welcome to the joy of building custom kernels. > I tried the method described at > http://wiki.centos.org/HowTos/Custom_Kernel, but rpm doesn't like the > output file, and even if I install it with -F, nothing seems to happen - > no new kernel, now initrd, nothing. Something in your build process has likely failed. Also, -F is to 'freshen' an existing package. This is something you most definitely DO NOT want to do with a kernel. > When I tried following the directions in the README file that came with > the source, I built the kernel just fine, but the instructions then go > on to describe how to modify LILO to make the install work, and my boot > loader is GRUB - not sure how to reconcile those two. Look at your /etc/grub.conf and add a stanza like the others, but with your kernel info. It should be pretty straight forward. > > So, I built yet another kernel (rpm) following the guide at > http://www.howtoforge.com/kernel_compilation_centos, and the rpm built > just fine, but when I run mkinitrd, it complains that I don't have the > ahci module in my kernel. The only reference I have found to ahci is in > my boot setup, and it is already enabled, so, once again, I am stuck. > Anyone have any ideas here? Yes. Follow one guide at a time. This will keep you from dragging your problem around with you. Troubleshoot why your build failed the first time around. > > I'm running Centos 2.6.9-42.0.3ELsmp on a Dell Precision 390 (P4/HT > 3GHz, 2Gb mem, ATI FireGL 4700, 160Gb SATA, ... Seems fairly common hardware. Are you sure you need to rebuild? Perhaps the centos wiki was not stern enough in discouraging custom builds for a plethora of reasons. What feature is it that you wish to enable in your custom kernel? -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell