similar to: HP EFI binaries

Without the GUID-Aliases list can debugging not continue? I don't see anything similar in the Gen9 UEFI command list http://h17007.www1.hp.com/docs/iss/proliant_uefi/v32403933.html#topictoc On Mon, Aug 17, 2015 at 4:33 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene >

Gene, after modifying some of Patrick's code I have been able to get the EFI_GUID - 83F01464-99BD-45E5-B383AF6305D8E9E6 Does this give you the info you need? On Mon, Aug 17, 2015 at 4:33 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene > > > > Thanks for the reply.

On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene > > Thanks for the reply. I didn't have a guid command, and couldn't find the > equivalent. dh > fs0:\efi-dh.txt worked, but dh -p Net did not so I ran dh Nothing of the sort listed with the help command to list the full GUIDs and their aliases? > -d -v -p SimpleNetwork >

On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: > > Gene thanks, here is the output > > My IP is 10.2.49.10 > Img @ 71d89718 = 8cdcd40ca5f0 > Udp @ 71d89718 = 8cdcd40ca5f0 > Udp @ 71d89718 = 8cdcd40ca5f0 > Udp @ 71d89718 = 8cdcd40ca5f0 > > From that point it is hung I find it hard to believe that it'd print that. I think you

On Mon, Aug 31, 2015 at 6:42 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Thanks Gene! > > this one is much better EXCELLENT! That's what I wanted to see. It iterates through 3 handles, printing the entire MAC buffer and the handle's memory address. Looks like it's merely a visual display bug. > On Mon, Aug 31, 2015 at 3:11 PM, Gene Cumm <gene.cumm

On Tue, Sep 1, 2015 at 11:36 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene > > I have tried to sleep 75 seconds right before the spawn_load() call just to > wait if it wasn't ready yet to send. Also according to tcpdump there are no > RRQ packets to the tftp server from syslinux. (only the initial > syslinux.efi) Where are you doing the capture? I find

>>> > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL).? Does the handle for Pxebc contain a Net?? >>> It does contain a Net but there are 2 issues with SNP: 1) The interface is different than

Gene thanks, here is the output My IP is 10.2.49.10 Img @ 71d89718 = 8cdcd40ca5f0 Udp @ 71d89718 = 8cdcd40ca5f0 Udp @ 71d89718 = 8cdcd40ca5f0 Udp @ 71d89718 = 8cdcd40ca5f0 >From that point it is hung On Sun, Aug 30, 2015 at 4:10 AM, Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > On Fri, Aug 28, 2015 at 3:13 PM, Derrick M <derrick.martinez at gmail.com> > wrote:

On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On

>>> I'm just debating what's the best algorithm here.? It would seem if the LoadeImage's DeviceHandle provides UDPv4Sb, use it as it's guaranteed to be the same interface.? Otherwise, we need a MNPSb (EFI_MANAGED_NETWORK_SERVICE_BINDING) that provides UDPv4Sb across the same interface.? Presumably it should also provide TCPv4Sb (rather than being on a separate

On Thu, Jul 2, 2015 at 9:58 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > OK there are problems. > > From > https://sourceforge.net/p/edk2/mailman/message/31604654/ > ""In current EDKII implementation, all the network servicebinding protocols for a > NIC device are installed together on the NIC's device handle, so you can get all > of them when you

On Mon, Aug 31, 2015 at 06:08:19AM -0400, Gene Cumm via Syslinux wrote: > On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: > > > > Gene thanks, here is the output > > > > My IP is 10.2.49.10 > > Img @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 =

OK there are problems. From https://sourceforge.net/p/edk2/mailman/message/31604654/ ""In current EDKII implementation, all the network servicebinding protocols for a NIC device are installed together on the NIC's device handle, so you can get all of them when you have chosen a special NIC handle."" Unfortunately there are PCs with UEFI implementations not following the

On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm

>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. > > There's a lot of variation. 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

On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. >> >> >> There's a lot of variation. Do you have a shell option >> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 >

On Fri, Aug 28, 2015 at 3:13 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene, > > Your binaries didn't work for me, however I put some code in to print the > byes of mac1 and mac2. In efi_create_binding() it does go through all of the > macs looking for the correct one and then finds a 100% match. In this case > the mac is 8c-dc-d4-0d-a5-f0 so &&

On Thu, Jul 9, 2015 at 5:30 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) > > The only solution for these is to use our own stack (likely full > TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). > Does the handle for Pxebc contain a Net?

On Mon, Jul 6, 2015 at 6:04 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > > What I've found: > (from older to newer hardware) > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). Does the

On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: > On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm wrote: >> On Mon, Nov 27, 2017 at 2:14 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund >> > <Joakim.Tjernlund at infinera.com> wrote: >> > > On Mon,