search for: 2570p

...;handles) what gives me all the handles that include the Service Binding Protocol "bguid". For each of this handles I get the DevPath handle and I parse it looking for the matching MAC address. The bguid handle with the right MAC is used for binding. So far it works in the problematic HP 2570p but also in a Vmware 10 client with double NIC. I'll test a bit more and I'll upload the code. Best, Patrick

...l the network servicebinding protocols for a NIC device are installed together on the NIC's device handle, so you can get all of them when you have chosen a special NIC handle."" Unfortunately there are PCs with UEFI implementations not following the former rule. i.e. HP Elitebook 2570p (single NIC) shell> dh ... 172: DevPath (..9,0x0)/MAC(FC15B4E81CAC,0x0))Net MNPSb ARPSb DHCPv4Sb TCPv4Sb IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb ... 184: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc ... 19D: DevPath (..v4(0.0.0.0,UDP,DHCP,0.0.0.0))Load Net Pxebc ... shell> dh 172 Ha...

>>> > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue. > 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at >

...t Pxebc and the SBs where > attached to different handles?? mmhhh > > I have to admit; UEFI development is a bit messy... > > I'd suspect possibly. I also have yet to see evidence your HP > EliteBook 2560p is not UEFI-2.0 compliant. It's safe to assume the > 2560p and 2570p are not 2.1 compliant as the Pxebc appears backed by a > Net not an MNPSb. > > -- > -Gene > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listi...

...s me all the handles that include the Service Binding Protocol "bguid". > For each of this handles I get the DevPath handle and I parse it looking for the matching MAC address. > The bguid handle with the right MAC is used for binding. > > So far it works in the problematic HP 2570p but also in a Vmware 10 client with double NIC. > I'll test a bit more and I'll upload the code. 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. Other...

...; --- >? efi/x86_64/linux.S | 61 > ++++++++++++++++++++++++++++++++++++------------------ >? 1 file changed, 41 insertions(+), 20 deletions(-) > I can just confirm this patch: 1) it is needed. 2) it solves the problem. 3) so far not regression detected. Test: Client Hardware: HP 2570P Boot Mode: PXE EFI64 Target OS: ubuntu-15.04-desktop-i386.iso Trying to PXE boot "ubuntu-15.04-desktop-i386.iso" on an EFI64 platform quietly aborts after transferring initrd.lz. After applying the present patch "ubuntu-15.04-desktop-i386.iso" booted normally....

...< What I've found: (from older to newer hardware) 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). About MNPSb; even when it presents the same interface than all the Service Binding protocols remember we have to create a child of the particular matching protocol and those do not have the sam...

...ng protocols for a > NIC device are installed together on the NIC's device handle, so you can get all > of them when you have chosen a special NIC handle."" > > Unfortunately there are PCs with UEFI implementations not following the former rule. > > i.e. HP Elitebook 2570p (single NIC) > > shell> dh > ... > 172: DevPath (..9,0x0)/MAC(FC15B4E81CAC,0x0))Net MNPSb ARPSb DHCPv4Sb TCPv4Sb IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb > ... > 184: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc > ... > 19D: DevPath (..v4(0.0.0.0,UDP,DHCP,0.0.0.0))Lo...

> > Today there are certain PCs i.e Elitebook 2560p, Elitebook 8460p that with > updated FW ""to the last known version"" cannot PXE boot syslinux for the > above mentioned reasons. > > We have already talked about this with Gene an there's an strategy for making > syslinux able to deal with these "weirdo" FWs. > It's just a matter

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

....03/gnu-efi/gnu-efi-3.0/lib/hand.c\LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles); When LibLocateHandle() try to locate EFI_UDP4_SERVICE_BINDING_PROTOCOL it fails with EFI_NOT_FOUND (14) which looks like an HP firmware issue. Newer versions of the HP Elitebook family like 2570p and 8470p PXE boot syslinux.efi correctly. Unfortunately this error does not display any error message on 6.0.3. I wonder if this problem with HP EFI firmware affecting current but not the newest hardware it's not somehow related to the recent thread "Problem boot PXE UEFI on HP ML350 Ge...

...-guid.txt dh > fs0:\efi-dh.txt dh bd >> fs0:\efi-dh.txt fs0 being the EFI boot partition on the hard drive of the VM. > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) a) Hunt for a Sb. b) use Net > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). a) use Sb on Pxebc handle b) use Net > About MNPSb; even when it presents the same interface than all the Service Binding protocols > remember we have t...

...be the reason why in the past Pxebc and the SBs where attached to different handles?? mmhhh > I have to admit; UEFI development is a bit messy... I'd suspect possibly. I also have yet to see evidence your HP EliteBook 2560p is not UEFI-2.0 compliant. It's safe to assume the 2560p and 2570p are not 2.1 compliant as the Pxebc appears backed by a Net not an MNPSb. -- -Gene

...hould just check their firmware against the "UEFI standard". Plus FW new versions should fix more than just only critical and security issues. Today is like this: You say you want better firmware? OK, then buy our new line of PC. i.e. Elitebooks 2560p/8460p fail while the newer Elitebooks 2570p/8470p work like a charm :-/ Best Patrick

> Hi All, > > My PXE configurations works fine for a bios PXE (the server in legacy > mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi > but not the next one ldlinux.e64 > > > Any ideas? > > Thanks > Latest updates (including firmware) for the HP ML350 Gen9 were released on 2014DEC19 (v1.21); I would suggest double-checking

...empty virtual clients when testing Syslinux PXE then I prefer redirecting console commands to a USB pendrive >>> > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) a) Hunt for a Sb. b) use Net <<< I do a hunt for either UDPv4Sb or TCPv4Sb >>> > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). a) use Sb on Pxebc handle b) use Net <<< I reuse the "Hunt for a S...

...3.0/lib/hand.c\LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles); > > When LibLocateHandle() try to locate EFI_UDP4_SERVICE_BINDING_PROTOCOL it fails with > EFI_NOT_FOUND (14) which looks like an HP firmware issue. > Newer versions of the HP Elitebook family like 2570p and 8470p PXE boot syslinux.efi correctly. > Unfortunately this error does not display any error message on 6.0.3. > > I wonder if this problem with HP EFI firmware affecting current but not the newest hardware it's not > somehow related to the recent thread "Problem boot PXE...

...implement TCP or respond to TCP if it doesn't use TCP yet should respond to ARP requests). > >>> > > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) > > a) Hunt for a Sb. > b) use Net > <<< > > I do a hunt for either UDPv4Sb or TCPv4Sb Just summarizing choices. >>>> > > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). > > a) use Sb on...

...k their firmware against the "UEFI standard". > Plus FW new versions should fix more than just only critical and security issues. > Today is like this: You say you want better firmware? OK, then buy our new line of PC. > i.e. Elitebooks 2560p/8460p fail while the newer Elitebooks 2570p/8470p work > like a charm :-/ As stated before, it is my understanding that the Elitebook 2560p/8460p devices _are_compliant_ with UEFI-2.0 which stated to use an SNP directly under PXEBC while UEFI-2.1 stated to use a MNP directly under the PXEBC. Please don't call these devices non-compl...

Hi All, My PXE configurations works fine for a bios PXE (the server in legacy mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi but not the next one ldlinux.e64 Any ideas? Thanks Software> syslinux ver 6.3 atftp 7.1 Log server side >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over