On 07/26/2012 01:59 PM, Pasi Kärkkäinen wrote:
"noefi" kernel cmdline option didn't help
When booting Fedora 17 x64 there's the GRUB bootloader with graphical
background image, I let it boot the default entry "Fedora 17", I see it the
allocating memory pages, loading VMLINUZ etc, and then the display mode /
resolution changes, and then there's just blank screen and a cursor blinking..
Does that ring any bells?
Not really, no. The fact that you're seeing a mode switch proceeding a
blinking cursor makes me think the kernel is probably starting, but you may
be seeing a series of failures after that point.
I'm pretty sure this is a Intel firmware bug, but it'd be
nice to be able to
confirm that somehow..
Well, either the bootloader or the kernel (or something after that) is not
succeeding If Windows works in UEFI mode on the machine, then we would still
consider it to be a bug we should fix, even if the firmware fails to comply to
precisely to our previous interpretation of the spec.
That being said, I doubt if we're going to have a high degree of success
debugging this over email.