F10Alpha- Kernels deleted wrongly, left with just a dud.

John Summerfield debian at herakles.homelinux.org
Wed Sep 17 13:20:24 UTC 2008


Todd Denniston wrote:
> John Summerfield wrote, On 09/16/2008 11:03 AM:
>> John Summerfield wrote:
>>>
>>
>>> System hardware: HP DC7700 Intel vPro E6300 CPU etc etc.
>>>
>>> I'm not in a position to give much info on this atm as it doesn't boot.
> 
> <someone else may be able to comment on the snipped console log>
> 
> Way out suggestion:
> if one of the working kernel rpms are still in your yum cache,
> then boot the install image into rescue mode,
>  chroot to the system, rpm -ivh kernel-workingrev.rpm
>  sync;sync;exit
>  sync;reboot
> 
> and while you are at it you may want to fix /etc/yum.conf to keep many 
> kernels again.
> 
> 
> I've not had a machine following F10, so salt to taste.
> 

Unfortunately I lack space and had been forced to clean up stale 
packages, including good versions of those I now system.

The only rescue image I could find to hand is a i386 job, it cannot run 
my system in chroot, and "rpm --root" didn't work because the rescue 
system is too old.

I couldn't find an f9 rescue system: after some extensive googling I 
found there is none, the netinst image I already had:-) is what I need.

I can report tho that my yum configuration looks okay to me, yum 
apparently is ignoring it again??[1]

[1] Chess notation for blunder.

As I mentioned in another post, I've tried several kernels including one 
I'm sure worked before, so I'm beginning to think mkinitrd is broken again.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)




More information about the test mailing list