search for: edkshellbinpkg

Displaying 4 results from an estimated 4 matches for "edkshellbinpkg".

2016 Jun 14
2
Getting HTTP path-prefix to work with syslinux.efi
.... Do you have a shell option > in your boot selections? None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 (firmware A16) seem have a built-in EFI shell option, but in all three cases I had success running the external EFI shell from github.com/tianocore/edk2/tree/master/EdkShellBinPkg (naming it /efi/boot/bootx64.efi on a FAT USB stick). > I'm guessing a lack of TCPv4Sb (an alias for the > EFI_TCP4_SERVICE_BINDING_PROTOCOL ). You're onto something. All three systems do report TCPv4Sb identically in their "guid" output, TCPv4Sb : 00720665-67EB-4A99-B...
2016 Jun 15
0
Getting HTTP path-prefix to work with syslinux.efi
...gt;> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 > (firmware A16) seem have a built-in EFI shell option, but in all three cases > I had success running the external EFI shell from > github.com/tianocore/edk2/tree/master/EdkShellBinPkg (naming it > /efi/boot/bootx64.efi on a FAT USB stick). Examining a 9020 I have access to, I'm guessing that depends on what's on the HDD. >> I'm guessing a lack of TCPv4Sb (an alias for the >> EFI_TCP4_SERVICE_BINDING_PROTOCOL ). > > > You're onto somethin...
2016 Jun 13
2
Getting HTTP path-prefix to work with syslinux.efi
> > Is syslinux.efi supposed to be able to handle HTTP URLs? > > If the underlying firmware can. Try just specifying an HTTP URL in the > config or on the command line instead of the path-prefix option. Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. Somehow I was under the impression improvements from pxelinux variants like lpxelinux were
2011 Jul 28
3
efilinux release 0.8
Hi, I'm pleased to announce release 0.8 of efilinux, a reference implementation of a minimal UEFI bootloader. This bootloader has no bells or whistles, it is simply a prototype with the minimum amount of smarts required to load a linux kernel (though loaders for other formats could be added). Currently it only supports booting x86-64 bzImages but i386 support is planned for release 0.9, with