Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=755093 --- Comment #25 from Chris Murphy <bugzilla@xxxxxxxxxxxxxxxxx> 2011-12-07 17:49:53 EST --- Interesting. I'm not sure if this file is significant for EFI boot or CSM-BIOS or both or neither. Just today for the first time I am (was) able to get an EFI boot with X starting up (anaconda from F16 DVD, and gnome from the resulting installation). On a MBP 4,1, previous attempts resulted in display hang as described in bug 751147. It's been a while, but in previous attempts I'm pretty sure they were bare disks and the Firmware.scap file could not have been present if true. Today's attempt is on a MBP4,1 with this Firmware.scap file on its EFI System partition. However, the problem I'm now having after one successful boot and startup to Gnome's login window (and logging in then rebooting) is that without any changes I can't get a successful boot+startup to a gnome login. I get a different boot experience each time, usually a hang in GRUB Legacy which I can ESC from to reload GRUB but subsequent boots fail the same way. The second most frequent boot experience is failure to unpack initramfs followed by a kernel panic. And the one after that, completely black screen but apparently a successful boot as I was able to blindly switch to F2 tty shell, login as root, save dmesg to file and reboot. Getting such wildly different boot results while not seemingly changing any parameters, is making testing very difficult. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review