similar to: HP EFI binaries

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 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 &&

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 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

>>> Gene, Your binaries didn't work for me, <<< I had problems with them too (I didn't see anything) >>> 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?&& memcmp(mac_1,

On Fri, Aug 28, 2015 at 03:34:12AM -0700, Patrick Masotta via Syslinux wrote: Derrick wrote: > > More importantly: look at the actual captured text.? It does NOT > > specify a valid MAC in its entirety and leaves off the leading nibble > > (11 characters, not 12).? Handle 267 shows "065F36E00EE" not "0065F36E00EE". > > I saw that, they might even be

Patrick Yes it looks like EFI_SUCCESS is true. There is a line if status == EFI_SUCCESS and status is 0 so it continues On Aug 29, 2015, at 01:00, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > Gene, > Your binaries didn't work for me, > <<< > I had problems with them too (I didn't see anything) > > however I put some code in to print

On Fri, Aug 28, 2015 at 4:22 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > Thanks Derrik; I got your efi-dh.txt > > I've found this: > > 252: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 267: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EE,0x1)/IPv4(0.0.0.0)) > 27C: SimpleNetwork PXEBaseCode LoadFile

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 =

>>> More importantly: look at the actual captured text.? It does NOT specify a valid MAC in its entirety and leaves off the leading nibble (11 characters, not 12).? Handle 267 shows "065F36E00EE" not "0065F36E00EE". <<< I saw that, they might even be making a mistake when implementing the Device Path protocol. >>> It is possible that this is

On Mon, Aug 31, 2015 at 07:59:06PM -0400, Gene Cumm via Syslinux wrote: > 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.

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it

On Thu, Jun 25, 2015 at 4:55 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Looks like the patch mostly addresses the > initial search to find the right handle for > PXE. I think I found the remaining source of the > issue (the part that's generating the > handle->Configure() messages). > I'm trying to read through pieces of the EFI

On Sun, Sep 13, 2015 at 4:38 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > > Patrick, Oscar, what specific build tools are you two using? > > GNU ld (GNU Binutils for Debian) 2.22 > gcc version 4.7.2 (Debian 4.7.2-5) > NASM version 2.10.01 > > Trying to recall if there's other utility packages. > > -- > -Gene >

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

Sorry guys; I got a bit lost about Gene's request on this thread; usually a handle dump like # dh > handles.txt it's all we need to see the relationship between the NBP's device handle and the Service Binding handles. Did you get handles.txt? is it available for download somewhere? >>> Gene, after modifying some of Patrick's code I have been able to get the

On Fri, Jul 3, 2015 at 11:05 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Lovely, the ServiceBindings are on a handle that resembles the NIC > while the Pxebc is IP-type specific. Looks like we should try to do a > ServiceBinding based on Pxebc but fall back to MAC-based searching, > saving all 3 handles, the image handle, Pxebc handle, and

On Fri, Jun 26, 2015 at 10:49 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Commit 23b2707 should resolve this. Please > let me know if you need > test binaries > > -- > -Gene > <<< > > > 1) About the Service Binding protocols, PXE protocol, etc having the same handle# is clear if we > see that the number is in fact

>>> Looks like the patch mostly addresses the initial search to find the right handle for PXE.? I think I found the remaining source of the issue (the part that's generating the handle->Configure() messages). I'm trying to read through pieces of the EFI spec, gnu-efi API, and a few other sources.? I'm pretty certain you'll see that the previous patch/binaries