top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Centos Kernel boot fail

0 votes
409 views

I installed 2.6.32-358.14.1.el6.centos.plus.x86_64 today and had some boot issues.

After rebooting, the system locked immediately after the Asus motherboard logo. I thought at first that it was a hardware issue because it didn't appear that grub even loaded. I wasn't even able to get into the BIOS to change the boot order so it appeared that it was a hardware issue. I reset the MB BIOS and rebooted, which allowed me to get into the BIOS. Everything looked normal. I then tried to boot and the same issue. I repeated the BIOS clear and this time got to grub and let it load the latest kernel (2.6.32-358.14.1.el6). It hung again. I repeated the BIOS clear, go to the grub screen, selected the previous kernel and everything was fine.

Once I got to the OS, I removed the "rhgb quiet" from grub.conf from the newest kernel. Rebooted. Hung again immediately after loading. The weird thing is that I couldn't just power down and get back to grub; I
had to clear the BIOS again before I could even load grub to select the previous kernel.

Anyone else experiencing issues with the latest kernel? Any idea why it seems to even corrupt the BIOS?

posted Jul 26, 2013 by Sonu Jindal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

+1 vote

I have a two ASUS "M5A99X EVO R2.0" motherboard based machines that I use for testing CentOS and I have booted the 2.6.32-358.14.1.el6.x86_64 and the 2.6.32-358.14.1.el6.centos.plus.x86_64 kernels on both machines without any issues.

answer Jul 27, 2013 by Jagan Mishra
0 votes

non-CentOS drivers? Are these from the OEM? Theyprobably need to be rebuilt to the new kernel.
Have you tried booting into "safe" mode or with video drivers disabled?
Just how you do that with CentOS I don't know but there should be instructions somewhere on the WEB.

answer Jul 28, 2013 by anonymous
Similar Questions
+2 votes

I am used to traditional update-rc.d et all.

Now I wonder how to add a a script that used to called by init.d (with start/sop ..) to the new "service start xx" regime.

All the tutorials I found talk about how to use update-rc.d..

+1 vote

I want to install ubuntu 17.2.
But after inserting my bootable pendrive I get this message on my screen.
Setup Error: end kernel panic - not syncing: vfs: unable to mount root fs on unknown block(2,0).
Please anyone problem?

+3 votes

As far as I know boot loader is the one who loads OS from ROM to RAM, then why Boot Loader is different as per OS.
And what is boot manager? Is Boot Manager is different as per OS?

+4 votes

Long ago I knew a way to get the boot process to require a keystroke at each step. This was important when you were trying to read the screen to figure out what is happening, typically wrong.

Can someone point me to how to do this on fedora?

...