search for: 8470p

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

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

...i/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 Gen9" h...

...0:\efi-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...

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

...I use 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 f...

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

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

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it

...r 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-compliant U...

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