Displaying 6 results from an estimated 6 matches for "wdsmgfw".
2014 Dec 26
3
Chain-loading from WDS to PXELinux on a different tftp server
...).
Except that wouldn't work for your known servers.
About proxyDHCP. I'm loading wdsmfg.efi as the network boot program (NBP).
So some of my tested configurations do the std D-O-R-A to the DHCP server
and
then immediately do a TFTP read request from my TFTP server. Loading the
boot\x64\wdsmgfw.efi.
However, then it does RA - RA - RA to the WDS server (proxyDHCP port 4011).
I'm convinced it's the wdsmgfw.efi that's doing this.
Here's the best config I found:
TFTP Server Name (option 66) -- set to WDS server's IP address
Domain Name (option 15) -- set to DNS dom...
2014 Dec 29
0
Chain-loading from WDS to PXELinux on a different tftp server
...).
Except that wouldn't work for your known servers.
About proxyDHCP. I'm loading wdsmfg.efi as the network boot program (NBP).
So some of my tested configurations do the std D-O-R-A to the DHCP server and then immediately do a TFTP read request from my TFTP server. Loading the boot\x64\wdsmgfw.efi.
However, then it does RA - RA - RA to the WDS server (proxyDHCP port 4011).
I'm convinced it's the wdsmgfw.efi that's doing this.
Here's the best config I found:
TFTP Server Name (option 66) -- set to WDS server's IP address
Domain Name (option 15) -- set to DNS dom...
2014 Dec 29
2
Chain-loading from WDS to PXELinux on a different tftp server
...9;t work for your known servers.
>
> About proxyDHCP. I'm loading wdsmfg.efi as the network boot program
> (NBP). So some of my tested configurations do the std D-O-R-A to
> the DHCP server and then immediately do a TFTP read request from my
> TFTP server. Loading the boot\x64\wdsmgfw.efi.
>
> However, then it does RA - RA - RA to the WDS server (proxyDHCP
> port 4011). I'm convinced it's the wdsmgfw.efi that's doing this.
>
> Here's the best config I found:
> TFTP Server Name (option 66) -- set to WDS server's IP address
> Domai...
2015 Sep 02
1
HP EFI binaries
...property of the underlying handle.
If it helps,
http://git.ipxe.org/ipxe.git/blob/HEAD:/src/interface/efi/efi_debug.c
shows the code that iPXE uses to dump out meaningful labels for
arbitrary handles. This generates names such as:
PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)
ConIn
wdsmgfw
and when no descriptive naming scheme can be found, falls back to
dumping the raw handle and a list of installed protocols, such as
UNKNOWN<0x3f0df318,SimpleTextIn,SimpleTextInEx>
Michael
2015 Aug 28
6
HP EFI binaries
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
2016 Mar 16
5
Updated status on UEFI compliant version of the pxechn-module
Hi,
________________________________________
From: Gene Cumm <gene.cumm at gmail.com>
Sent: Wednesday, March 16, 2016 00:56
To: Jan Frode J?ger
Cc: syslinux at zytor.com
Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module
On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger
<jan.frode.jaeger at ntnu.no> wrote:
Without trying to figure out where data is