I've seen some vendor drivers using that kind of hack. returning an error from the entry point) if fast boot is enabled.
Subject: Re: Is it possible to manually (from code) load 'Realtek UEFI UNDI Driver' from firmware?įast boot in the first place.There is also the possibility that the "fast boot" option is implemented by having the Realtek UEFI UNDI Driver itself check for the "fast boot" setting, and refusing to be loaded (i.e. We have been trying to move partners away from hacky solutions and to this method. The uefi spec defined method to request the bds connect something is using
Your application qualifies as "fast boot" either. Then the system seems to work as intended - I'm doubtful that running TBH I'm doubtful a UEFI application is supposed to load option ROMĭrivers. downloaded from network Realtek UNDI driver (RtkUndiDxe.efi) copied it to efi boot folder ( EFI\Boot\ ) booted into shell by system default boot and loaded Realter UNDI driver manually by command load 'RtkUndiDxe.efi As result, network interfaces appeared. (The PCI busĭriver installs EFI_LOAD_FILE2_PROTOCOL on the handle that carriesĮFI_PCI_IO_PROTOCOL too, for exposing the UEFI driver.) See also Will not load drivers from the disk (which could otherwise be loaded viaĭriver# options), or from the ROM BARs of PCI cards. I'v tried to load it using EFI_FIRMWARE_VOLUME2_PROTOCOL, enumerating files of type EFI_FV_FILETYPE_DRIVER and loading them, in such wayThat will only load drivers that are part of the platform firmware. Maybe somebody knows from where I can load this UNDI driver? Some drivers were loaded, but there was not 'Realtek UEFI UNDI Driver' among them. It does have a different file size though. Driver says updated, but version number is still 0.47. By using UEFI, certain on-board hardware would get ignored (in my case my on-board audio) and thus the problems I faced. Status = gBS->StartImage(ImageHandle, NULL, NULL) Realtek PCIe FE / GBE / 2.5G / Gaming Ethernet Family Controller Software - REALTEK. Thank you bochane and kemical for your inputs, but I solved it now I was booting Windows 10 using UEFI firmware which is a new and better way of BIOS for devices such as tablets and phones. Print(L"%d) Load image success '%s'\n", Index3, UiSection) Status = gBS->LoadImage(FALSE, gImageHandle, DevicePath, NULL, 0, &ImageHandle) Print(L"%d) Found driver image '%s'\n", Index3, UiSection) ĭevicePath = FvFileDevicePath(Buffer, &NameGuid) If (EFI_SUCCESS = NextStatus/* & Index3 ReadSection( NextStatus = Fv->GetNextFile(Fv, Key, &FileType, &NameGuid, &Attributes, &Size) Description: UEFI UNDI Driver for RealTek RTL8168B Download RealTek RTL8168B UEFI UNDI Driver v.2.040. Status = gBS->LocateHandleBuffer(ByProtocol, &gEfiFirmwareVolumeProtocolGuid, NULL, &NoHandles, &Buffer) įor (Index = 0 Index HandleProtocol(Buffer, &gEfiFirmwareVolumeProtocolGuid, (VOID **)&Fv) I'v tried to load it using EFI_FIRMWARE_VOLUME2_PROTOCOL, enumerating files of type EFI_FV_FILETYPE_DRIVER and loading them, in such way I found, that some drivers (including 'Realtek UEFI UNDI Driver') are not loaded, when BIOS option 'Fast boot' is on. I'll definitely keep the Intel NIC for future troubleshooting, but the Realtek seems to be the winner here.I am developing efi application that should work with network. In the meantime, I'll look forward to 10.048 to finish off this not-so-fun ride we've all been on, some of you more than others. But websites definitely appear to come up faster. Also the Intel NIC has to travel back and forth through the PCIe lanes while the Realtek chip is much closer to the CPU. I would venture to guess that the Intel NIC is a 1Gbe card and the Realtek is 2.5Gbe. Like, everything is a bit "snappier" when browsing.
Don't get me wrong, I was still getting my full internet speeds on the Intel NIC, but websites seem to come up faster being back on the Realtek NIC. I am enjoying the speed of this onboard NIC. I'm not sure if Intel updates any components on these cards over the years, but they definitely keep the drivers updated.Īnyway, after seeing the consensus that the latest Realtek drivers fix most of the issues (with disabling a few things), I gotta say.
While it is a new card, the tech itself is quite old, from around 2008. Download Description Version Update Time File Size UEFI UNDI Driver (32/64/ARM) 2.036 2 127 KB. As I had posted earlier in the thread, some of us went out and bought some separate PCIe NICs. I wanted to give an update here on the recent driver posted, 10.047.