1

I am trying to insert a GOP driver for the SM750 embedded graphics chip into the platform firmware so that it can be used with secure boot. This is in the form of an .efi file that was given to me by the manufacturer so it their "official" GOP driver. Currently, I am using a .rom version of this driver by loading it into an EEPROM attached to the SM750 using an executable program in DOS that they also provided. I have been told this .rom file cannot be used with Secure Boot so I have been looking at ways to insert the .efi version of this driver into the firmware.

Reading section 32 of the [EDK2 Firmware guide] (https://edk2-docs.gitbooks.io/edk-ii-uefi-driver-writer-s-guide/32_distributing_uefi_drivers/) states there are 3 ways to insert into the platform.

  1. PCI option ROM

I believe this is how the .rom version of the driver is being loaded currently, since this is connected to the PCI bus and this would probably be the ideal way of doing this with the .efi driver, but I do not know a way that I can put the .efi file onto this EEPROM

  1. Through the platform flash

I would rather avoid this method if I can, I do not want to use a custom image from the manufacturer

  1. On an EFI partition in the hard drive

I thought this would be the way to do it, but after reading into it more it seems that this would only be viable for updates and not for loading the driver on boot. Correct me if I'm wrong with this, but this would also only execute when the OS is loaded from the EFI partition (in this case RHEL7).

The CPU is a Xeon D-1559 and the target OS is RHEL7.6

TL;DR what is the best way to insert an efi GOP driver into a system for use with secure boot.

New contributor
rt0218 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
  • Generally, .efi files are bootloaders for efi-based bootup (which includes secure boot). It wouldn't be loaded into the devices eeprom but rather stored on the EFI partition on the hard drive where the UEFI bios could find it and let you select it as a boot option. That said, it could just be a poorly chosen extension by the manufacturer. – Cliff Armstrong Mar 26 at 20:24
  • @CliffArmstrong Even if this file is a video driver? I would need video out somehow before getting to the EFI partition on a hard drive. Even if I don't "boot" from the this file in the traditional sense, would the system know to look for in the EFI partition for drivers to load? – rt0218 2 days ago
  • The SOP on PC (x86/_64 platforms in general) is for the video adapter to support certain highly standardized video modes specifically to allow video out during the POST and boot process. It's unclear to me if this is the case for the SM750... however, assuming the file really is an EFI bootloader, then it isn't a video driver... it's an image containing the machine code needed to bootstrap an OS... including any low-level drivers necessary for that task (specialty storage controllers and video hardware, for example). But that's a hypothetical. Like I said, the exention could be misleading. – Cliff Armstrong 2 days ago
  • The point I'm making is that there are some things in what you've said that make me wonder if perhaps you have some of the details incorrect. Might not. Just trying to give you a heads up that you might want to double check the facts so far and be sure you haven't gotten anything mixed up. – Cliff Armstrong 2 days ago

Your Answer

rt0218 is a new contributor. Be nice, and check out our Code of Conduct.

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.