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 dhNothing of the sort listed with the help command to list the full GUIDs and their aliases?> -d -v -p SimpleNetwork > fs0:\efi-simplenetwork.txtExcellent job on finding the target alias.> Also attaching a screenshot from Oscar's debug code. > > Thank youAt least it makes it through a lot of the initial code. -- -Gene> On Sat, Aug 15, 2015 at 11:38 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Sat, Aug 15, 2015 at 12:13 PM, Derrick M <derrick.martinez at gmail.com> >> wrote: >> > Gene, >> > >> > >> > Thanks for sending the binary. Looks like my DL160 G9 still gets stuck >> > at >> > syslinux.efi according to the TFTP logs. On the PXE menu I have My IP is >> > 10.12.3.4 >> > >> > Does the binary include the fix for multiple NICs? I assume yes since I >> > have >> > an address >> >> Yes it does. >> >> Let's start with some basics: >> >> - What baseboard firmware version? Is there a newer one available? >> >> - Any chance of getting a dump of some EFI data, specifically the >> GUID-Aliases list (which should be almost universal but good to >> cross-reference) and a list of device handles? The following should >> work in your EFI shell, presuming you can extract data from fs0 (the >> first mounted FAT* file system). >> >> >> guid > fs0:\efi-guid.txt >> dh > fs0:\efi-dh.txt >> dh -p Net > fs0:\efi-dh-net.txt >> >> >> In particular, I'm looking for where the Pxebc lives relative to >> MNPSb/UDPv4Sb (Net is a common Simple Network Protocol alias). >> >> -- >> -Gene
>>> > 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 dhNothing of the sort listed with the help command to list the full GUIDs and their aliases?> -d -v -p SimpleNetwork > fs0:\efi-simplenetwork.txtExcellent job on finding the target alias.> Also attaching a screenshot from Oscar's debug code. > > Thank youAt least it makes it through a lot of the initial code. -- -Gene <<< Hi Gene, Please see my code here https://github.com/ppatpat/syslinux/edit/master/efi/main.c\efi_create_binding() At the end it includes simple code printing to console the corresponding SB GUID in case of error (i.e. missing SB); I think that code is 100% harmless and pretty handy in these situations. Best, Patrick
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 > > > > 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 > fs0:\efi-simplenetwork.txt > > Excellent job on finding the target alias. > > > Also attaching a screenshot from Oscar's debug code. > > > > Thank you > > At least it makes it through a lot of the initial code. > > -- > -Gene > > > On Sat, Aug 15, 2015 at 11:38 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> > >> On Sat, Aug 15, 2015 at 12:13 PM, Derrick M <derrick.martinez at gmail.com > > > >> wrote: > >> > Gene, > >> > > >> > > >> > Thanks for sending the binary. Looks like my DL160 G9 still gets stuck > >> > at > >> > syslinux.efi according to the TFTP logs. On the PXE menu I have My IP > is > >> > 10.12.3.4 > >> > > >> > Does the binary include the fix for multiple NICs? I assume yes since > I > >> > have > >> > an address > >> > >> Yes it does. > >> > >> Let's start with some basics: > >> > >> - What baseboard firmware version? Is there a newer one available? > >> > >> - Any chance of getting a dump of some EFI data, specifically the > >> GUID-Aliases list (which should be almost universal but good to > >> cross-reference) and a list of device handles? The following should > >> work in your EFI shell, presuming you can extract data from fs0 (the > >> first mounted FAT* file system). > >> > >> > >> guid > fs0:\efi-guid.txt > >> dh > fs0:\efi-dh.txt > >> dh -p Net > fs0:\efi-dh-net.txt > >> > >> > >> In particular, I'm looking for where the Pxebc lives relative to > >> MNPSb/UDPv4Sb (Net is a common Simple Network Protocol alias). > >> > >> -- > >> -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. 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 > fs0:\efi-simplenetwork.txt > > Excellent job on finding the target alias. > > > Also attaching a screenshot from Oscar's debug code. > > > > Thank you > > At least it makes it through a lot of the initial code. > > -- > -Gene > > > On Sat, Aug 15, 2015 at 11:38 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> > >> On Sat, Aug 15, 2015 at 12:13 PM, Derrick M <derrick.martinez at gmail.com > > > >> wrote: > >> > Gene, > >> > > >> > > >> > Thanks for sending the binary. Looks like my DL160 G9 still gets stuck > >> > at > >> > syslinux.efi according to the TFTP logs. On the PXE menu I have My IP > is > >> > 10.12.3.4 > >> > > >> > Does the binary include the fix for multiple NICs? I assume yes since > I > >> > have > >> > an address > >> > >> Yes it does. > >> > >> Let's start with some basics: > >> > >> - What baseboard firmware version? Is there a newer one available? > >> > >> - Any chance of getting a dump of some EFI data, specifically the > >> GUID-Aliases list (which should be almost universal but good to > >> cross-reference) and a list of device handles? The following should > >> work in your EFI shell, presuming you can extract data from fs0 (the > >> first mounted FAT* file system). > >> > >> > >> guid > fs0:\efi-guid.txt > >> dh > fs0:\efi-dh.txt > >> dh -p Net > fs0:\efi-dh-net.txt > >> > >> > >> In particular, I'm looking for where the Pxebc lives relative to > >> MNPSb/UDPv4Sb (Net is a common Simple Network Protocol alias). > >> > >> -- > >> -Gene >
On Tue, Aug 25, 2015 at 6:50 PM, Derrick M <derrick.martinez at gmail.com> wrote:> Without the GUID-Aliases list can debugging not continue?No, the GUID-Aliases list was just merely a double-check on how these systems create aliases. I'm just getting a little stumped as to what's going on.> I don't see anything similar in the Gen9 UEFI command list > > http://h17007.www1.hp.com/docs/iss/proliant_uefi/v32403933.html#topictocExcellent reference! Apparently your shell uses alias instead of guid. http://h17007.www1.hp.com/docs/iss/proliant_uefi/v28070872.html -- -Gene> 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. 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 > fs0:\efi-simplenetwork.txt >> >> Excellent job on finding the target alias. >> >> > Also attaching a screenshot from Oscar's debug code. >> > >> > Thank you >> >> At least it makes it through a lot of the initial code. >> >> -- >> -Gene >> >> > On Sat, Aug 15, 2015 at 11:38 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> On Sat, Aug 15, 2015 at 12:13 PM, Derrick M >> >> <derrick.martinez at gmail.com> >> >> wrote: >> >> > Gene, >> >> > >> >> > >> >> > Thanks for sending the binary. Looks like my DL160 G9 still gets >> >> > stuck >> >> > at >> >> > syslinux.efi according to the TFTP logs. On the PXE menu I have My IP >> >> > is >> >> > 10.12.3.4 >> >> > >> >> > Does the binary include the fix for multiple NICs? I assume yes since >> >> > I >> >> > have >> >> > an address >> >> >> >> Yes it does. >> >> >> >> Let's start with some basics: >> >> >> >> - What baseboard firmware version? Is there a newer one available? >> >> >> >> - Any chance of getting a dump of some EFI data, specifically the >> >> GUID-Aliases list (which should be almost universal but good to >> >> cross-reference) and a list of device handles? The following should >> >> work in your EFI shell, presuming you can extract data from fs0 (the >> >> first mounted FAT* file system). >> >> >> >> >> >> guid > fs0:\efi-guid.txt >> >> dh > fs0:\efi-dh.txt >> >> dh -p Net > fs0:\efi-dh-net.txt >> >> >> >> >> >> In particular, I'm looking for where the Pxebc lives relative to >> >> MNPSb/UDPv4Sb (Net is a common Simple Network Protocol alias). >> >> >> >> -- >> >> -Gene
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 EFI_GUID - 83F01464-99BD-45E5-B383AF6305D8E9E6 <<< OK that GUID is EFI_UDP4_SERVICE_BINDING_PROTOCOL_GUID then you bound the required Service Binding protocol. Could you please show us here the modified code?>>>Does this give you the info you need? <<< Depending on your code changes we could infer the handle structure but the dump I've mentioned before (if you didn't already uploaded somewhere) would be nice to see. Best, Patrick