Bug 683693

Can you get a screenshot with more details?

Created attachment 483530 [details]
screenshot of invalid opcode failure

(In reply to comment #2)
> Created attachment 483530 [details]
> screenshot of invalid opcode failure

Wow, all you get is that first line from the oops?

(In reply to comment #3)
> (In reply to comment #2)
> > Created attachment 483530 [details]
> > screenshot of invalid opcode failure
> 
> Wow, all you get is that first line from the oops?

Yes :(

If there's anything I can do to get more details about the error, let me know.

Are you using the EFI boot disk?

(In reply to comment #6)
> Are you using the EFI boot disk?

EFI boot disk? I'm not sure what you're referring to. Enlighten me?

I'm using the image located here: http://download.fedoraproject.org/pub/fedora/linux/releases/test/15-Alpha/Fedora/x86_64/iso/Fedora-15-Alpha-x86_64-DVD.iso

I'm creating a bootable usb drive using unetbootin.

Can you try blacklistsing the efivars module? (Just add "blacklist=efivars" to the kernel command line.)

(In reply to comment #8)
> Can you try blacklistsing the efivars module? (Just add "blacklist=efivars" to
> the kernel command line.)

Ok, I tried that, and I got identical results.

Did the line just before "invalid opcode" still say "EFI Variables Facility"?

(In reply to comment #10)
> Did the line just before "invalid opcode" still say "EFI Variables Facility"?

Yes it did.

Maybe we load that in the initrd? Try "rdblacklist=efivars blacklist=efivars" in the kernel options...

Oh, never mind, we build it in. The magic option is "noefi", try that...

(In reply to comment #13)
> Oh, never mind, we build it in. The magic option is "noefi", try that...

The 'noefi' did the trick; however, now my end result is a flickering screen which is gray most of the time, but occasionally flashes pink. Still no anaconda. Should I file a separate bug report for that?

(In reply to comment #14)
> > Oh, never mind, we build it in. The magic option is "noefi", try that...
> 
> The 'noefi' did the trick; however, now my end result is a flickering screen
> which is gray most of the time, but occasionally flashes pink. Still no
> anaconda. Should I file a separate bug report for that?

I really don't know where to go from here. We can't see where it's failing unless you can get kdump working somehow, and we can't disable just efivars. (I suspect you need EFI support to get working video.)

Can you try to disable EFI in the BIOS settings? It might be under "operating system type" - you should change it to Windows XP if that's possible.

(In reply to comment #16)
> Can you try to disable EFI in the BIOS settings? It might be under "operating
> system type" - you should change it to Windows XP if that's possible.

My options are UEFI or Legacy. Using the Legacy option, and picking the 'basic video driver' option from the grub menu allows me to get to the installer (the default option in the grub menu does not work).

You need to file another bug about the video failure then.

This bug will be left open until we get the UEFI problem fixed properly, but for now we at least have a workaround.

This should be fixed in 2.6.38-3

kernel-2.6.38.1-6.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.38.1-6.fc15

Can you confirm this was fixed?

Has the F15 alpha install image been updated with the new kernel?

kernel-2.6.38.2-8.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.38.2-8.fc15

(In reply to comment #21)
> Can you confirm this was fixed?

I can confirm that I have no EFI problems when booting a completed install (even without updating to the latest kernel); however this bug is specifically about booting the install image.

kernel-2.6.38.2-8.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Verified on an X120e.

I am having the same error while booting a self made kernel with UEFI fireware

if I leave the efivars module not compiled in, I can boot the kernel but if I modprobe efivars module, the system freezes immediately

could you enlighten me what's the relevant patch/config change in kernel-2.6.38.2-8.fc15 which fixes the "invalid opcode: 0000 [#1] SMP" in efivars module? thanks

(In reply to comment #27)
> I am having the same error while booting a self made kernel with UEFI fireware
> 
> if I leave the efivars module not compiled in, I can boot the kernel but if I
> modprobe efivars module, the system freezes immediately
> 
> could you enlighten me what's the relevant patch/config change in
> kernel-2.6.38.2-8.fc15 which fixes the "invalid opcode: 0000 [#1] SMP" in
> efivars module? thanks

We had an out-of-tree patch that tried to make EFI default to physical mode.

thanks for the info. I applied that EFI physical mode patch as well, without it, I can't even boot my thinkpad w520 (so bug 699313 is filed)