Booting stops with 2.6.5-Kernel

[Jeff Vian]

jludwig wrote:

>On Fri, 2004-04-23 at 19:03, Dan Weisenstein wrote:
>  
>
>>Thomas Bitschnau wrote:
>>
>>    
>>
>>>Hi!
>>>
>>>I installed a 2.6.5-Kernel via rpm. The entry in the grub.conf file was
>>>done by the system.
>>>If I try to start the system with the newly installed kernel, it just
>>>stops booting after the "Freeing unused kernel memory: 148k
>>>freed"-message.
>>>There are no errors like kernel-panic or something.
>>>
>>>What shall I do now?
>>>--
>>>Thomas B.
>>>
>>>GIVE: Support the helpless victims of computer error.
>>>
>>>
>>> 
>>>
>>>      
>>>
>>To at least get you back to a running condition, you could boot up with 
>>a rescue disk or self contained linux distro (like knoppix), mount your 
>>partition that has /boot on it, and change the vmlinuz link back to your 
>>old kernel. Don't know if you'll have to change your grub.conf file (in 
>>/boot/grub) or anything else. Maybe someone else can chime in.
>>
>>Dan
>>
>>-- 
>>Dan Weisenstein
>>General Manager
>>Tesoro Electronics
>>715 White Spar Road
>>Prescott, AZ 86303
>>928-771-2646
>>    
>>
>Typically rpm does not remove a working kernel, or at least not on my
>systems when just installing a kernel. 
>If this is so with you just reboot with the old kernel.
>2.6.5 is a development kernel anyways and will have bugs.
>
rpm -U kernel*   WILL replace the existing kernel.
rpm -i kernel* does NOT replace it but installs the new one alongside 
the original.

I believe yum and up2date are set up to default kernel updates to an 
install and not an update.

AFAICT, these boot problems are why up2date and yum were set up to 
install a new kernel version and not to replace the existing one.