system crashed during update

xchris · #1 26th December 2009, 05:53 PM

Hi,

I was updating my F12 and the system crashed .. no idea why..
anyway I cannot boot anymore using the kernel 2.6.31.9-174, but I can boot using the 2.6.31.6-166 ... now when I issue the yum update, the system says its up-to-date...
is there any way to 'force' the yum to update the system again ?

Regards

Chris

mouse_runner · #2 26th December 2009, 06:00 PM

Code:

yum clean all

followd by

Code:

yum update

xchris · #3 26th December 2009, 07:14 PM

thank you..
I did this but the system says 'No Packages marked for Update' i suppose it thinks the kernel is updated .. but i cannot boot with it... I only can boot with an older kernel from the grub menu..

chris

---------- Post added at 07:14 PM CST ---------- Previous post was at 06:08 PM CST ----------

I managed to 'force' the installation of the latest kernel.
I did 'yum erase kernel-2.6.31.9-174' the the update installed the 2.6.31.9-174 kernel again
but the system boots on 'black screen' as I see on the startup messages
it says :

Checking for module nvidia.ko [FAILED]
nvidia.ko for kernel 2.6.31.9-174.fc12.i686 was not found [ WARNING]
The nvidia driver will not be enabled until one is found [WARNING]

so as I see the nvidia driver is broken, or did not updated to 'match' the 2.6.31.9-174 kernel....

chris

marcrblevins · #4 26th December 2009, 07:36 PM

For Nvidia, you need akmods.

Code:

su -
yum install akmods

Corrections, make that:

Code:

yum install akmod-nvidia xorg-x11-drv-nvidia-libs.i686

xchris · #5 26th December 2009, 07:52 PM

thanx I will try your suggestion, but as I read this post http://forums.fedoraforum.org/showthread.php?t=237277 rpmfusion haven't build any kmods for the new kernel... - i though my problem was due to crashed system during the installation...

chris

PavanKY · #6 26th December 2009, 07:54 PM

I am facing a similar problem. My grub actually got screwed up. I had to re install it and the latest kernel x.174 would not work, had to boot back using x.166.

I only updated it because it was marked as a security update, didnt realize it was going to mess everything else up.

xchris · #7 26th December 2009, 08:37 PM

marcrblevins's solution (akmod-nvidia .....) works ... I boot the machine to an older kernel and installed the akmod...

thx

chris

marcrblevins · #8 26th December 2009, 08:46 PM

Yes, boot to 166, install akmod-nvidia, then reboot.

While you see the Fedora bar starting. Press Alt+D

You would see akmod-nvidia building kmod-nvidia for .174 on the fly! Is that sweet?
Try that the next time you know a new kernel is loaded.

Cheers

neo_in_matrix · #9 27th December 2009, 10:10 AM

Yeah. I had the same problem. What I got was only a black blank screen after the 3 colored bar completed. To be worse, I had deleted previous kernel and had no way to reboot. :-(

PavanKY · #10 27th December 2009, 10:33 AM

neo,
try to jump to console and install the files
you can use alt+ctrl+f3 to get a console screen, and use your id to login there.

Marc,
I am not getting the bar. I only get a blinking cursor even when I installed the akmod files. Any thing else I should look out for ? I am still using ~.166 kernel.

neo_in_matrix · #11 27th December 2009, 05:21 PM

Thanks for reply. I have another problem. My Fedora installation is a guest OS inside Sun Virtual Box. What files should I install?

marcrblevins · #12 27th December 2009, 05:27 PM

Quote:

Originally Posted by silentfreak

Marc,
I am not getting the bar. I only get a blinking cursor even when I installed the akmod files. Any thing else I should look out for ? I am still using ~.166 kernel.

Try:

Code:

cat /etc/grub.conf

You had a desktop environment running? Gnome or KDE?

PavanKY · #13 27th December 2009, 05:41 PM

I am using GNOME.

the grub.conf file has this output

Quote:

title Fedora (2.6.31.9-174.fc12.i686)
root (hd0,0)
kernel /vmlinuz-2.6.31.9-174.fc12.i686 ro root=/dev/mapper/vg_xempus-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet rdblacklist=nouveau snd_hda_intel.power_save=0
initrd /initramfs-2.6.31.9-174.fc12.i686.img
title Fedora (2.6.31.6-166.fc12.i686)
root (hd0,0)
kernel /vmlinuz-2.6.31.6-166.fc12.i686 ro root=/dev/mapper/vg_xempus-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet rdblacklist=nouveau snd_hda_intel.power_save=0
initrd /initramfs-2.6.31.6-166.fc12.i686.img
title Fedora (2.6.31.5-127.fc12.i686)
root (hd0,0)
kernel /vmlinuz-2.6.31.5-127.fc12.i686 ro root=/dev/mapper/vg_xempus-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.i686.img

---------- Post added at 09:41 AM CST ---------- Previous post was at 09:34 AM CST ----------

neo,

I am not sure if you just took out the kernel options from the boot menu or actually erased the kernels completely. If you just took out the kernel option from boot menu, editing the grub.conf file to include the earlier versions should be really simple.

marcrblevins · #14 27th December 2009, 11:32 PM

Silentfreak,
Add the 'nomodeset' option to your /etc/grub.conf file.

My version:

Code:

title Fedora (2.6.31.9-174.fc12.i686.PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.31.9-174.fc12.i686.PAE ro root=/dev/mapper/vg_kiriyamablevins-lv_root  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nomodeset rdblacklist=nouveau vmalloc=256m
        initrd /initramfs-2.6.31.9-174.fc12.i686.PAE.img
title Fedora (2.6.31.6-166.fc12.i686.PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.31.6-166.fc12.i686.PAE ro root=/dev/mapper/vg_kiriyamablevins-lv_root  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nomodeset rdblacklist=nouveau vmalloc=256m
        initrd /initramfs-2.6.31.6-166.fc12.i686.PAE.img
title Fedora (2.6.31.6-162.fc12.i686.PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.31.6-162.fc12.i686.PAE ro root=/dev/mapper/vg_kiriyamablevins-lv_root  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nomodeset rdblacklist=nouveau vmalloc=256m
        initrd /initramfs-2.6.31.6-162.fc12.i686.PAE.img

You said blank screen blanking cursor. It did not boot and no grub there?

PavanKY · #15 28th December 2009, 04:19 PM

marc,

I see the grub menu. I am able to log in to the ~.166 kernel. I just can not log in to the ~.174 kernel. When I choose the ~.174 kernel from the menu I see the blinking screen.

I did try using nomodeset. It does not help. So, I took out the quiet option and tried booting again. This is what I saw last before the blinking screen

Quote:

Trying to unpack rootfs image as initramfs

Any idea what that means ?