Unable to load opensuse 12.3 in UEFI mode

English Install/Boot/Login
1

hey guys,
I don’t know what is the bug in my computer or whatsoever but I am not able to load openSUSE 12.3 KDE in my windows 8 UEFI mode nor legacy mode.
Can you guys please help me out.

Here is the message it displays and doesn’t move on


ACPI error: Method parse/execution failed \SB.PCI0.PEG0.PEGP.DD07._BQC](Node FFFF880243cd6218), AE_NOT_FOUND(20120913/ps parse_536)
ACPI error: Evaluating  BCM failed (20120913/video364)

     3.984336][Firmware Bug]: Duplicate ACPI video bus devices for the same VGA Controller, Please try module parameter "Video.allow_duplicates=1" if the current driver doesn't work.
     3.982086] MXM: GUID detected in BIOS.

Bunch of same lines and and then at last “MXM: GUID detected in BIOS” and then it stopped right there.

I really want to install openSUSE. Please help me out guys

Your help is highly appreciated.

2

What is your hardware? What is your vidio?

At what point do you get this error?

Do you get the install menu?

Did you try pressing F3 and selecting NoKMS?

We can’t see over you shoulder and our crystal balls are out for repair

3

Hardware


intel i7 processor
Nvidia 650m 2GB Graphics card

I don’t know much about video
I am not even able to load to a live desktop as soon as I select go to live opensuse it shows me the above error
But I get a menu where I have to select whether Go to Live cd or fail safe mode or boot from hard disk

4

Did you try NOKMS graphic options is either F3 or F4 they should be listed at the bottom of the screen.

Once installed you can install the NVIDIA driver which should clear up things

5

Yes, I think I got it I had to change boot mode to Legacy first and boot priority to UEFI first. Anyways thanks a lot for your help.

6

I do not know how much will be relevant, but I think it is important to read the openSUSE-12.3 release notes, as those release notes have a number of relevant sections to UEFI, which I quote:

3.2. UEFI—Unified Extensible Firmware Interface

Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI.

Background: Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much “too much” is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (pstore) have been disabled by default. Nevertheless it is recommended to install any firmware updates the hardware vendor recommends.

3.3. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode

This only affects machines in UEFI mode with secure boot enabled.
YaST does not automatically detect if the machine has secure boot enabled and will therefore install an unsigned bootloader by default. But the unsigned bootloader will not be accepted by the firmware. To have a signed bootloader installed the option “Enable Secure Boot” has to be manually enabled.

3.4. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment

This only affects machines in UEFI mode.
When using the installer on the live medium, YaST does not detect UEFI mode and therefore installs the legacy bootloader. This results in a not bootable system. The bootloader has to be switched from grub2 to grub2-efi manually.

3.5. openSUSE 12.3 Medium May Not Boot on Future Secure Boot Enabled Hardware

This only affects machines in UEFI mode.
Our double signed shim on openSUSE 12.3 medium may be rejected by future firmwares.
If the openSUSE 12.3 medium does not boot on future secure boot enabled hardware, temporarily disable secure boot, install openSUSE and apply all online updates to get an updated shim.
After installing all updates secure boot can be turned on again.

3.6. Crypted LVM in UEFI Mode Needs /boot Partition

This only affects installations in UEFI mode.
In the partitioning proposal when checking the option to use LVM (which is required for full disk encryption) YaST does not create a separate /boot partition. That means kernel and initrd end up in the (potentially encrypted) LVM container, inaccessible to the boot loader. To get full disk encryption when using UEFI, partitioning has to be done manually.