Restore latest kernel

[Mike Adolf]

Karl Larsen wrote:
> Mike Adolf wrote:
>   
>> Mark Haney wrote:
>>   
>>     
>>> Mike Adolf wrote:
>>>   
>>>     
>>>       
>>>> This morning I ran the latest Ubuntu update.  It installed a new kernel 
>>>> 2.6.24.21.  I rebooted and all was well.  Then I installed my new pctv 
>>>> 800i tuner card. To do so, according mythtv wiki, I first extracted 
>>>> firmware from a windows file and placed it into 
>>>> /lib/firmware/2.4.24.21-generic, I downloaded the latest v4l driver 
>>>> tree, did a make and make install. This is supposed to overwrite kernel 
>>>> drivers. When I tried to reboot modprob failed.  It also failed in 
>>>> recovery mode.
>>>>
>>>> Can I some how remove the corrupt 2.4.24.21 kernel, so that auto update 
>>>> reinstalls it? I an new booted into 2.4.24.19.
>>>>
>>>> Thanks,
>>>> Mike
>>>>
>>>>     
>>>>       
>>>>         
>>> Okay, why do you think the kernel is corrupt?  Can you not boot into 
>>> that kernel at all? It sounds like you can.  Let's try to backtrack to 
>>> what the problem is before we go about re-installing a kernel.  If 
>>> there's a module that won't load (or is loading and bombing, we can 
>>> remove the module listing so it doesn't get autoloaded.  That's quicker 
>>> and easier.
>>>
>>> What are the errors you're seeing?
>>>
>>>
>>>   
>>>     
>>>       
>> I can not boot 2.4.24.21. If I boot it in recovery mode it gets to the 
>> point of running modprobe and gives the error "abnormal exit" and hangs. 
>> Recovery mode boot flies by so fast I can't really see what it is doing. 
>> I can still boot into a previous kernel (.19)
>>
>> Mike
>>
>>   
>>     
>     Hi Mike I am using Hardy and decided to see what kernel I am using. 
> I was surprised to see it was:
>
>
> title        Ubuntu 8.04.1, kernel 2.6.24-21-generic
> root        (hd0,5)
> kernel        /boot/vmlinuz-2.6.24-21-generic 
> root=UUID=8713c541-dffa-4fd2-b22
> b-e600afacbab2 ro quiet splash
> initrd        /boot/initrd.img-2.6.24-21-generic
> quiet
>
>     So I have had this kernel for some time and everything seems to be 
> working exactly like it did with the many earlier kernels. Your problem 
> must be with some other cause.
>
> Karl
>
>
>   
Thanks, but you need to read my original post.

Mike