Community
cancel
Showing results for 
Search instead for 
Did you mean: 
DMalk2
Beginner
1,210 Views

dq87pg: ignore UEFI BootXXXX variables

Hello,

Intel motherboard dq87pg ignore/corrupt all UEFI BootXXXX/BootOrder variables except last one set.

So if you install Windows then Linux you've got in boot menu (F10) only Linux (grub) and if you installed Linux then Windows you've got only Windows Boot Manager by F10.

It appears to be worked well only in origin firmware ver. 0030, but in 0035,036 it was broken by ignoring UEFI variables. Also if you reflash the same motherboard (0035/0036) with both installed Win/Linux with origin 0030 firmware you've got all announced OSes in boot menu (F10) back(!). So it's just ignoring then and seen then only in ver. 0030

Version 014x corrupts previous set BootXXXX variables when you set new one. When you set new BootXXXX var via efibootmgr it's ok, but when you reboot and check it again with efibootmgr -v, you will see corrupted device path in all variables. So you've got again only one OS in boot menu (F10)

Also it's reproduces for all four motherboards in my hands

0 Kudos
18 Replies
Allan_J_Intel1
Employee
155 Views

I understand you have set some variables to boot with different operating systems and updated BIOS versions do not keep same configuration.

I see you are reporting same issue happens with BIOS 014, please make sure to test this configuration with latest version 0144

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3605&DwnldID=23560&keyword=dq87pg&lan... https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3605&DwnldID=23560&keyword=dq87pg&lan...

Allan.

DMalk2
Beginner
155 Views

I can confirm the bug is still here for version 0144.

Here is example

[root@haswell01 virt]# dmesg | grep "DQ87PG, BIOS"

[ 0.000000] DMI: /DQ87PG, BIOS PGQ8710H.86A.0144.2014.0113.1604 01/13/2014

[root@haswell01 virt]# efibootmgr -v

BootCurrent: 0004

Timeout: 1 seconds

BootOrder: 0008,0004,000A,0003

Boot0003* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...3.............&# 127;...

Boot0004* ubuntu HD(1,800,200000,ad1637e3-c160-4c1b-a030-3d702fcd8895)File(\EFI\ubuntu\grubx64.efi)

Boot0008* UEFI : LAN : IP4 Intel(R) Ethernet Network Connection i217-LM ACPI(a0341d0,0)PCI(19,0)MAC(7c05070d37c9,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0..BO

Boot000A* UEFI : LAN : IP6 Intel(R) Ethernet Network Connection i217-LM ACPI(a0341d0,0)PCI(19,0)MAC(7c05070d37c9,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO

[root@haswell01 virt]# efibootmgr -V

version 0.5.4

You can see I install Win then ubuntu. Windows var (Boot0003) looks invalid

DMalk2
Beginner
155 Views

DMalk2
Beginner
155 Views

0145 is stil NOT working

here example of corrupted efi vars:

BootCurrent: 0001

Timeout: 1 seconds

BootOrder: 0006,0001,0007,0000,0005

Boot0000* Fedora Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)

Boot0001* ubuntu HD(1,800,200000,ad1637e3-c160-4c1b-a030-3d702fcd8895)File(\EFI\ubuntu\shimx64.efi)

Boot0005* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...3.............&# 127;...

Boot0006* UEFI : LAN : IP4 Intel(R) Ethernet Network Connection i217-LM ACPI(a0341d0,0)PCI(19,0)MAC(7c05070d37c9,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0..BO

Boot0007* UEFI : LAN : IP6 Intel(R) Ethernet Network Connection i217-LM ACPI(a0341d0,0)PCI(19,0)MAC(7c05070d37c9,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO

Windows and Fedora won't boot and is not seen from F10 boot menu

DMalk2
Beginner
155 Views

Hello, intel

Today I have tested firmware 0146: the problem still exits.

What information I can provide for you to debug this problem?

Allan_J_Intel1
Employee
155 Views

Thanks for testing and posting the results.

I am currently researching on this issue. As soon as I can, I will send you a message with my findings. Thank you for your patience and understanding.

Allan.

Allan_J_Intel1
Employee
155 Views

Thank you for your patience. This is the response from engineering:

Intel recommends installing Linux last and then reconfigure boot manager file to start windows first. Please check the URL below for information about how to change boot manager file:

The content on these sites are not controlled by Intel. This information is offered for your convenience and should not be viewed as an endorsement by Intel for the merchants or services offered here

 

http://www.cnet.com/how-to/how-to-change-the-boot-order-of-a-dual-boot-linux-pc/ http://www.cnet.com/how-to/how-to-change-the-boot-order-of-a-dual-boot-linux-pc/

 

Allan.

 

 

 

 

DMalk2
Beginner
155 Views

Hello,

the article you provided above is for bios/mbr system and for grub,

in my case it is efi/gpt system and no grub (for example linux is booted via direct loading kernel with efi stub)

Also if I will use secure boot or bit locker grub will unable to load windows

Please ask your engineers for more information about this issue.

P.S.: tested on 0147 : but is still here

Allan_J_Intel1
Employee
155 Views

Thanks for the information, I am going to pass this information to our engineering department.

Allan.

DMalk2
Beginner
155 Views

hello,

any news for this subject?

MLimo
Beginner
155 Views

Dmitry,

I'm finding something similar in my environment. I find that as a workaround I can touch /efi/boot/bootx64.efi on the ESP and the entries are no longer corrupted after rebooting when viewing from efibootmgr. Can you see if maybe that helps to workaround it for you too?

Also, by chance do you have an /efi/boot/bootx64.efi on some other partition on the disk too? I'm wondering if that might be causing the BIOS to flag a different partition as the ESP.

DMalk2
Beginner
155 Views

seems not working for me.

Install Win8.1 then Fedora20. Got only one variable with fedora (press F10 during post or see via efibootmgr)

Variable Win8.1 was fine before F20 announced itself. After F20 I've got corrupted variable with 8.1 loader

Grub perfect load both oses.

Boot into F20 and touch /boot/efi/EFI/Boot/bootx64.efi

delete old variable with Windows and add new

Reboot. Now I've see windows variable alive and fedora variable corrupted

DMalk2
Beginner
155 Views

Intel, all version except 0030 during iteration Boot variables somehow corrupt Efi Device Path node. Please check and fix it.

Allan_J_Intel1
Employee
155 Views

Thanks for the update.

Intel engineering is still looking into the issue. Updates will be posted here.

Allan.

Allan_J_Intel1
Employee
155 Views

I am still trying to get an update on this matter. This thread would be updated as soon as I get any feedback from engineering team.

Allan.

DMalk2
Beginner
155 Views

these BootXXXX (corrupted) variables patched with AMI_MASKED_DEVICE_PATH_GUID = { 0x99e275e7, 0x75a0, 0x4b37, { 0xa2, 0xe6, 0xc5, 0x38, 0x5e, 0x6c, 0x00, 0xcb } };

if you skip it and next end path you will get previous valid path

Allan_J_Intel1
Employee
155 Views

After several tests we made in our labs, please try the following steps:

At BIOS, go to Boot configuration and configure the following options:

1-Enable "UEFI Boot" option

2- Disable "Legacy Boot" option (if Windows* 8 or 8.1)

3- Disable "Secure Boot" option

4- Disable "Fast Boot" option

Once have configured the Boot option above can proceed with the Installation of Windows* OS through UEFI.

5- Install Windows*

After finishing Windows* installation can proceed with Linux OS (our test was with Ubuntu* 14.04 LTS)

6- Install UBUNTU* through UEFI by pressing F10 in order to access the storage device where UBUNTU is stored

  1. 6.1 Select "something else" in the partition field
  2. 6.2 Reduce the size of Windows* OS (Free space must be enough to install UBUNTU*)
  3. 6.3 Create a partition of 1MB with the format "RESERVED BIOS BOOT AREA"
  4. 6.4 Create with the rest of the free space the partitions necessary for LINUX (/, /boot, /home,…)
  5. Restart the system and then it will starts with Linux Grub showing the OS options to boot. If the system does not show directly the

options or pressing F10 the options to boot, go and access the link below and install the "BOOT-REPAIR" Utility in Linux.

https://help.ubuntu.com/community/Boot-Repair https://help.ubuntu.com/community/Boot-Repair

  1. Once the Boot Repair Utility is installed you will have to see the Operating System options to boot.

Important Note: Operating Systems must be of 64 bits

Partitions Recommended for UBUNTU partitions (based on the components that we used)

Root ("/"): 20000MB

SWAP Partition: 4000MB (select this partition through "Used as" field)

/home Partition: Use the rest of the free space.

Let us know your findings.

Allan.

DMalk2
Beginner
155 Views

After I installed ubuntu, windows boot variable dissappeared from F10 menu (I check via ubuntu efibootmgr: it was patched with AMI_MASKED_DEVICE_PATH_GUID)

Reply