Bug 896190 - Kernel 3.7.2-201.fc18.x86_64 cannot boot
Summary: Kernel 3.7.2-201.fc18.x86_64 cannot boot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-16 20:04 UTC by pjhavariotis
Modified: 2013-03-25 17:06 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-25 17:06:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
upgrade.log (478.21 KB, text/plain)
2013-01-18 17:01 UTC, pjhavariotis
no flags Details

Description pjhavariotis 2013-01-16 20:04:56 UTC
Description of problem:

I have just finished the upgrade with the fedup utility from F17 64-bit version to F18 64-bit. After the laptop was rebooted, I selected the first entry from the GRUB menu which was: 3.7.2-201.fc18.x86_64

After selecting the aforementioned kernel there was an error/warning about dracut-cmdline[65] and some deprecated commands (KEYTABLE, SYSFONT).

Unfortunately the laptop could not boot and the capslk indicator was blinking !!!! In order to boot the machine I had no other option but to select the second entry from the GRUB menu which is : 3.6.11-1.fc17.x86_64. 


Version-Release number of selected component (if applicable):
3.7.2-201.fc18.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 pjhavariotis 2013-01-18 17:01:15 UTC
Created attachment 682557 [details]
upgrade.log

I am attaching the upgrade.log in order to show you what happened during the upgrade process.

Comment 2 pjhavariotis 2013-01-18 17:05:11 UTC
I have just come up with the bug 896579. Is it related to mine?

Comment 3 pjhavariotis 2013-01-19 19:57:58 UTC
Shall I install the NVIDIA drivers (yum install akmod-nvidia xorg-x11-drv-nvidia-libs) ? As far as I can see the command rpm -qa \*nvidia\* returns NOTHING.

Comment 4 pjhavariotis 2013-01-20 07:24:19 UTC
I have just updated the 3.7 kernel by installing the 204 version (kernel-3.7.2-204.fc18.x86_64) using yum. Again I am facing the same problem. When I tried to boot with it, the following dracut messages appear and the machine cannot boot (Kernel Panic with Flashing Caps Lock Light). On the contrary, the 3.6 kernel (3.6.11-1.fc17.x86_64) works as expected.

dracut-cmdline[65]: Warning: Kernel command line option 'KEYTABLE' is deprecated, use 'vconsole.keymap' instead.
dracut-cmdline[65]: Warning: Kernel command line option 'SYSFONT' is deprecated, use 'vconsole.font' instead.

Comment 5 pjhavariotis 2013-01-20 15:07:38 UTC
I have just tried the nomodeset kernel boot option and the machine finally managed to BOOT !!!!

Comment 6 Jorge Martínez López 2013-01-24 08:26:58 UTC
The dracut warnings are a red herring. To remove them, please edit /etc/default/grub and change in the line GRUB_CMDLINE_LINUX:

SYSFONT=... for vconsole.font=latarcyrheb-sun16
KEYTABLE=... for vconsole.keymap=...

Then update the Grub config by running 

# grub2-mkconfig -o /boot/grub2/grub.cfg

That will remove the warnings but non booting is caused by something else.

Comment 7 Mildred 2013-02-08 10:55:55 UTC
I have a similar problem with 3.7.5-201 on F18 as well. Cannot boot unless I use nomodeset. But then, I don't get Xorg running. I could also boot by connecting an external monitor. The LVDS screen then seems to work.

In fact, with the 3.7 kernel, it seem to boot find but the screen is black, except for 20px or so at the top of the screen, that randomly change. Until it doesn't change anymore.

This was a fresh install from the live desktop usb key, and the installed kernel was 3.6, but I did an update, ran grub2-mkconfig (because grubby couldn't update the config file). Now, the 3.7 kernel won't boot.

I have seemingly identical machines (just purchased a few months later), and on them, the 3.7 kernel works fine. The other difference is that on the newer machines, I just have F18, and on the older machines affected with this bug, I had installed F17, and run the F18 installer to overwrite the F17 system. I didn't use FedUp.

Comment 8 Mildred 2013-02-11 08:38:45 UTC
On the problem described above: the problem disappeared after a week end of not using the computers. Might have been a problem in the graphical BIOS.

Comment 9 Justin M. Forbes 2013-03-13 16:57:25 UTC
Is the 3.8.2 kernel working for you?

Comment 10 pjhavariotis 2013-03-14 06:57:02 UTC
Yes, it works!
(In reply to comment #9)
> Is the 3.8.2 kernel working for you?


Note You need to log in before you can comment on or make changes to this bug.