[ipxe.efi] No menu with Optiplex 3010

[aruhuno]

Server

• FOG Version: 1.5.4
• OS: Debian 9.5
• Kernel: 4.18.3 TomElliott 64

Description

Hello,

I recently created a new Windows 10 image in UEFI. The capture was done from VMware vSphere without too much trouble. I wanted to test the deployment of the image on one of our stations and here is what I have as a message:

I have of course followed the following documentation: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Thank you for your help.

[aruhuno]

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

The issues with the Dell x90s and x010s are know, but thank you for confirming on 390 and 3010 variants.

Yes, but it’s for wiki =]

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

As for the 3020s, I know that uefi device initialization does take time. Its almost at the point where you think its locked up, it will finish initializing the device.

Exactly and it’s aggaining!

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

FWIW, refind is used on the other end. When leaving the FOG iPXE menu to attempting to boot from the local uefi hard drive. So refind will not help you get iPXE to run.

Yes I know, but SANBOOT does not work.

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

You can use the FOS usb boot stick if you need to image these systems to bypass pxe booting if you need.

It’s true, but UEFI is only for test at the moment. I’ve made an image for notebook now.

[george1421]

@aruhuno said in [ipxe.efi] No menu with Optiplex 3010:

Optiplex 3020 (BIOS A03): works, but devices initialization is very slow (REFIND_EFI recommended?)
Optiplex 3020 (BIOS A18): same as above

The issues with the Dell x90s and x010s are know, but thank you for confirming on 390 and 3010 variants. You can use the FOS usb boot stick if you need to image these systems to bypass pxe booting if you need.

As for the 3020s, I know that uefi device initialization does take time. Its almost at the point where you think its locked up, it will finish initializing the device. FWIW, refind is used on the other end. When leaving the FOG iPXE menu to attempting to boot from the local uefi hard drive. So refind will not help you get iPXE to run.

[aruhuno]

@george1421
For my part, I tested on several models with BIOS update:

• Optiplex 390 (BIOS A05): not capable
• Optiplex 390 (BIOS A14): same as above
• Optiplex 3010 (BIOS A17): does not work, devices initialization never ends
• Optiplex 3010 (BIOS A21): same as above
• Optiplex 3020 (BIOS A03): works, but devices initialization is very slow (REFIND_EFI recommended?)
• Optiplex 3020 (BIOS A18): same as above

I did not test 7xx/7xxx series because they have the same behavior than 3xx/3xxxx series.

[Wayne Workman]

@george1421 Will do. I have a mess of things to do in the wiki and I finally have some time this weekend for it.
#wiki

[george1421]

@aruhuno If I remember correctly the x90 series was the first to support uefi booting, but they do not support network uefi booting. The x010 series was the first to support network booting (but not very well in uefi mode).

@Wayne-Workman Can we update the referenced wiki page to say that uefi booting is not working with the Dell OpliPlex 3010/7010 systems with FOG?

[aruhuno]

@george1421
Thanks for your guick answer.
So, can I update this page ?
I will test on a 390 and a 790 also shot. I have Lenovo E73 too.

[george1421]

Yes this is a known issue specifically with the 7010s, uefi booting, and the iPXE kernel. At this time the only solution is to either switch over to usb booting these devices or switch the 7010s back to bios (legacy) mode.