search for: 065f36e00ee

...ug 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 DevicePath(0000:0000:0000:0000:0000:0000)) > 291: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EF,0x1)/IPv4(0.0.0.0)) > 2A6: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 2BB: Simpl...

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

...gt; > >> 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 making a mistake when implementing > >> > the Device Path protocol. > >> > > >> > >>> > >&...

>>> 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 a visual bug but it DOES give a hint that there may be an issue in the MAC addresses. <<< It has to...

...t;masottaus at yahoo.com> >> 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 making a mistake when implementing >> > the Device Path protocol. >> > >> > >>> >> > It is possible that this is a...

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 =

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 DevicePath(0000:0000:0000:0000:0000:0000)) 291: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EF,0x1)/IPv4(0.0.0.0)) 2A6: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) 2BB: SimpleNetwork PXEBaseCode...

...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 making a mistake when implementing > the Device Path protocol. > > > It is possible that this is a visual bug but it DOES give a hint that > > there may be an issue in the MAC addresses. > > It...

...; 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 making a mistake when implementing >> >> > the Device Path protocol. >> >> > >> >> &...

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

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.

...; specify a valid MAC in its entirety and leaves off the >> >> >> >> >> >> > leading >> >> >> >> >> >> > nibble >> >> >> >> >> >> > (11 characters, not 12). Handle 267 shows "065F36E00EE" >> >> >> >> >> >> > not >> >> >> >> >> >> > "0065F36E00EE". >> >> >> >> >> >> > <<< >> >> >> >> >> >> > >> >...