Success, well 98% success anyway. New kernel boots just fine if you leave it alone during the boot but I have run into one small problem that I home someone may have seen before. During the boot Kudzu starts up. If you leave it alone and let it timeout the boot completes. If you enter the Kudzu then the boot will hang. If you CTRL-ALT-DEL the system will do a clean reboot. If you enter Kudzu it wants to remove the Generic modem driver. System config for serial ports: One Mainpine OCT+ ports ttyS05 thru ttyS12, plus it sees ttyS20 the control port for the Mainpine, plus two modems on ttys00 and 01. If you boot from the default kernel you will only see ports part of the Mainpines ports plus the two modems on ttys00 and 01 but Kudzu never starts. I suspect Kudzu is seeing the additional ports now that the kernel is build to use them but I don't understand why it causes a problem with booting. Anyone ever seen this? Thanks to all that have help me get this far. You guys have been great. > -----Original Message----- > From: centos-bounces at centos.org > [mailto:centos-bounces at centos.org] On Behalf Of Jim Perrin > Sent: Friday, July 21, 2006 5:08 PM > To: CentOS mailing list > Subject: Re: [CentOS] Building a new 2.6 kernel > > > > rpm -ivh --force kernel-smp-2.6.9-34.0.2.EL.PRX.01.i686.rpm > > The --force is a bad idea. The rest of the command is fine. Also, > since you're doing it this way, the kernel itself should tweak > grub.conf for you as part of the post install script in the rpm. > > -- > During times of universal deceit, telling the truth becomes a > revolutionary act. > George Orwell > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >