Bug 746435 - kernel 3.1.0-0.rc9.git0.0.fc16.x86_64 does not boot
Summary: kernel 3.1.0-0.rc9.git0.0.fc16.x86_64 does not boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-15 18:48 UTC by Jason Montleon
Modified: 2011-10-17 00:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-17 00:34:42 UTC
Type: ---


Attachments (Terms of Use)

Description Jason Montleon 2011-10-15 18:48:30 UTC
Description of problem:
kernel 3.1.0-0.rc9.git0.1.fc16.x86_64 does not boot on an original MacBook Air.

I removed rhgb and quiet from the boot options and still all I get are the echo lines from the grub.cfg:
Loading Fedora (kernel 3.1.0-0.rc9.git0.0.fc16.x86_64)
Loading initial ramdisk ...

Usually the system proceeds very quickly past this, but with rc9.git0.0 it seems to just hang forever.

I tried acpi=off and noacpi and no change.

I also tried creating a new intramfs with dracut to no effect.

Version-Release number of selected component (if applicable):
kernel 3.1.0-0.rc9.git0.0.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora on a Macbook Air (Original)
2. Update to kernel 3.1.0-0.rc9.git0.0.fc16.x86_64
3. Reboot
  
Actual results:
System does not boot

Expected results:
System boots

Additional info:
kernel 3.1.0-0.rc8.git0.1.fc16.x86_64 and prior boot just fine

Comment 1 Jason Montleon 2011-10-17 00:33:01 UTC
Closing this. It looks like the initrd line was left off when the kernel was adding to the grub2 config. I ran grub2-efi-mkconfig manually and the configuration was generated properly, and the system now boots properly with this kernel.

Thank you.


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