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 >

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

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, 2017-11-27 at 18:03 -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 2:14 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund > >

On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: > On Mon, 2017-11-27 at 08:42 -0500, Gene Cumm wrote: >> Bringing the discussion to the list. >> >> You stated you see the following on your Lenovo ThinkPad T470s with >> UEFI firmware N1WET41W (1.20 date: 10/17/2017): >> >> >> core_udp_sendto: stalling

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

Bringing the discussion to the list. You stated you see the following on your Lenovo ThinkPad T470s with UEFI firmware N1WET41W (1.20 date: 10/17/2017): core_udp_sendto: stalling on configure with no mapping OUI 54-E1-AD lspci -s 0:1f.6 -v 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21) Subsystem: Lenovo Ethernet Connection (4) I219-V

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.

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

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

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

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 =

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

Hi all, Here is the situation: I have 2 nodes MDS1 , MDS2 (10.0.0.22 , 10.0.0.23) I wish to use as failover MGS, active/active MDT with zfs. I have a jbod shelf with 12 disks, seen by both nodes as das (the shelf has 2 sas ports, connected to a sas hba on each node), and I am using lustre 2.4 on centos 6.4 x64 I have created 3 zfs pools: 1. mgs: # zpool

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

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

Hi, I am trying to create a boot cd for ia64 systems which will go into the efi shell, map to fs0 (cdrom) and give a help message on screen. I have tried creating a CD using isolinux but this boots as the Red Hat AW2.1 CD 1 and ignores the message file. After selecting the efi shell and mapping to fs0 then entering - elilo linux ks=nfs:<ip address>:<kickstart file> I get the message

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,