search for: liblocatehandle

Displaying 20 results from an estimated 24 matches for "liblocatehandle".

2015 Mar 12
2
Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
...fectly TFTP transferred, it nevers asks for ldlinux.e64, and immediately gives up. I have traced the problem to: /syslinux-6.03/efi/udp.c\core_udp_open() /syslinux-6.03/efi/main.c\efi_create_binding(&Udp4ServiceBindingProtocol, &Udp4Protocol); /syslinux-6.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. U...
2015 Jul 27
2
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
...> -EFI_SERVICE_BINDING *sbp; > +EFI_SERVICE_BINDING *sbp =NULL; > ... > > -? ? if (status != EFI_SUCCESS) > +? ? if (status != EFI_SUCCESS || sbp == NULL) >? ? ? ? goto free_binding; > ... The presumption was that we'd see an error rather than non-error from LibLocateHandle() when nr_handles is 0 and be guaranteed to find a matching handle.? Your additional measures seem the best choice. -- -Gene <<< OK I have adopted this code approach; testing it since last week, so far so good. Presumably there are other people testing this; feedback appreciated. Bes...
2015 Mar 12
0
Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
...vers asks for ldlinux.e64, and immediately gives up. > > I have traced the problem to: > > /syslinux-6.03/efi/udp.c\core_udp_open() > /syslinux-6.03/efi/main.c\efi_create_binding(&Udp4ServiceBindingProtocol, &Udp4Protocol); > /syslinux-6.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 sysli...
2015 Sep 12
3
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
..... >> > >> > - if (status != EFI_SUCCESS) >> > + if (status != EFI_SUCCESS || sbp == >> NULL) >> > goto free_binding; >> > ... >> >> The presumption was that we'd see an error rather than >> non-error from LibLocateHandle() when nr_handles is 0 and be guaranteed >> to find a >> matching handle. Your additional measures seem the best choice. >> -- >> -Gene >> <<< >> >> OK I have adopted this code approach; testing it since last >> week, so far so good. >...
2015 Mar 05
0
Problem boot PXE UEFI on HP ML350 Gen9
> 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
2015 Jul 22
3
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
>>> Jeff, Patrick: Could you try my code from my github repo branch efi-multinic?? It's derived from Patrick's code and I finally see good responses with a VMware VM's e1000e NIC (never saw ANYTHING good from it until now). git://github.com/geneC/syslinux.git https://github.com/geneC/syslinux.git -- -Gene <<< Hi there I think in the case of a particular
2015 Jul 03
2
EFI: PXE: "My IP is 0.0.0.0"
...Binding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it works. Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &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 b...
2015 Jun 22
1
EFI: PXE: "My IP is 0.0.0.0"
...ith the following: >> NBP file download successfully. >> Getting cached packet >> My IP is 0.0.0.0 >> >> After the patch it ended with the following (note that the IP is the same >> as the Station IP address): >> NBP file download successfully. >> LibLocateHandle returned nr 8 >> Handle [0] gave -3 00000000 >> Handle [1] gave -3 00000000 >> Handle [2] gave 0 0ad402a7 >> Getting cached packet >> My IP is 10.212.2.167 I'd guess that the ARP packets are being seen on NIC0 and not NIC1. I'm hoping to have another patch thi...
2015 Jun 25
2
EFI: PXE: "My IP is 0.0.0.0"
...m also trying to fix this bug but unfortunately I'm not having much time. This is the approach I'm going to try: 1) detecting the right NIC at pxe.c\net_parse_dhcp(void) (as you do) 2) saving its associated MAC address. 3) at main.c\efi_create_binding() (let's consider the UDP case) LibLocateHandle() returns the handles of the devices that publish a EFI UDPv4 Service Binding Protocol GUID. Each device with a published EFI UDPv4 Service Binding Protocol GUID supports the EFI UDPv4 Protocol and may be available for use. Considering a "Device Path Protocol" is attached to device handl...
2015 Jun 22
5
EFI: PXE: "My IP is 0.0.0.0"
...ave some more information. Before the patch, the boot sequence ended with the following: NBP file download successfully. Getting cached packet My IP is 0.0.0.0 After the patch it ended with the following (note that the IP is the same as the Station IP address): NBP file download successfully. LibLocateHandle returned nr 8 Handle [0] gave -3 00000000 Handle [1] gave -3 00000000 Handle [2] gave 0 0ad402a7 Getting cached packet My IP is 10.212.2.167 Greetings, Sebastian On Sun, Jun 21, 2015 at 8:48 PM, Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > On Sat, Jun 20, 2015 at 5:09 PM, G...
2015 Aug 13
3
[syslinux:master] efi/pxe: Reuse handle
...p; > struct efi_binding *b; > EFI_STATUS status; > - EFI_HANDLE protocol, child, *handles = NULL; > - UINTN i, nr_handles = 0; > + EFI_HANDLE protocol, child; > > b = malloc(sizeof(*b)); > if (!b) > return NULL; > > - status = LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles); > + status = uefi_call_wrapper(BS->OpenProtocol, 6, pxe_handle, > + bguid, (void **)&sbp, > + image_handle, pxe_handle, > + EFI_OPEN_...
2015 Mar 05
4
Problem boot PXE UEFI on HP ML350 Gen9
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
2015 Jun 22
0
EFI: PXE: "My IP is 0.0.0.0"
...patch, the boot sequence ended with the following: > NBP file download successfully. > Getting cached packet > My IP is 0.0.0.0 > > After the patch it ended with the following (note that the IP is the same > as the Station IP address): > NBP file download successfully. > LibLocateHandle returned nr 8 > Handle [0] gave -3 00000000 > Handle [1] gave -3 00000000 > Handle [2] gave 0 0ad402a7 > Getting cached packet > My IP is 10.212.2.167 > > Greetings, > > > Sebastian > > On Sun, Jun 21, 2015 at 8:48 PM, Gene Cumm via Syslinux < > syslinux at...
2015 Jun 24
0
EFI: PXE: "My IP is 0.0.0.0"
...patch, the boot sequence ended with the following: > NBP file download successfully. > Getting cached packet > My IP is 0.0.0.0 > > After the patch it ended with the following (note that the IP is the same as > the Station IP address): > NBP file download successfully. > LibLocateHandle returned nr 8 > Handle [0] gave -3 00000000 > Handle [1] gave -3 00000000 > Handle [2] gave 0 0ad402a7 > Getting cached packet > My IP is 10.212.2.167 > > Greetings, > > > Sebastian > > On Sun, Jun 21, 2015 at 8:48 PM, Gene Cumm via Syslinux <syslinux at zytor...
2015 Jul 05
0
EFI: PXE: "My IP is 0.0.0.0"
...nd TCP handles _should_ be the same... > -- > -Gene > <<< > > OK now it works. > Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) > from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. > Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &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 MA...
2015 Jul 25
0
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
...t; > ... > -EFI_SERVICE_BINDING *sbp; > +EFI_SERVICE_BINDING *sbp =NULL; > ... > > - if (status != EFI_SUCCESS) > + if (status != EFI_SUCCESS || sbp == NULL) > goto free_binding; > ... The presumption was that we'd see an error rather than non-error from LibLocateHandle() when nr_handles is 0 and be guaranteed to find a matching handle. Your additional measures seem the best choice. -- -Gene
2015 Aug 15
0
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
...ICE_BINDING *sbp =NULL; > > ... > > > > - if (status != EFI_SUCCESS) > > + if (status != EFI_SUCCESS || sbp == > NULL) > > goto free_binding; > > ... > > The presumption was that we'd see an error rather than > non-error from LibLocateHandle() when nr_handles is 0 and be guaranteed to find a > matching handle. Your additional measures seem the best choice. > -- > -Gene > <<< > > OK I have adopted this code approach; testing it since last > week, so far so good. > Presumably there are other people te...
2015 Sep 15
0
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
...> - if (status != EFI_SUCCESS) >>> > + if (status != EFI_SUCCESS || sbp == >>> NULL) >>> > goto free_binding; >>> > ... >>> >>> The presumption was that we'd see an error rather than >>> non-error from LibLocateHandle() when nr_handles is 0 and be guaranteed >>> to find a >>> matching handle. Your additional measures seem the best choice. >>> -- >>> -Gene >>> <<< >>> >>> OK I have adopted this code approach; testing it since last >&g...
2015 Jun 20
2
EFI: PXE: "My IP is 0.0.0.0"
Starting a new thread for the moment and BCCing the two reporters of the issue. Looking over the code, I think I finally see why we get junk data from the PXE base. If we tell the PXE base that a buffer is 0 bytes long, we should expect junk/null data. I'm hoping to have a patch for testing over the weekend. If either of you would rather start a bug on the bugzilla, feel free. -- -Gene
2015 Jun 25
0
EFI: PXE: "My IP is 0.0.0.0"
...not having much time. I just need to publish mine. > This is the approach I'm going to try: > 1) detecting the right NIC at pxe.c\net_parse_dhcp(void) (as you do) > 2) saving its associated MAC address. > 3) at main.c\efi_create_binding() (let's consider the UDP case) > LibLocateHandle() returns the handles of the devices that publish a EFI > UDPv4 Service Binding Protocol GUID. Each device with a published EFI UDPv4 > Service Binding Protocol GUID supports the EFI UDPv4 Protocol and may be available for use. > Considering a "Device Path Protocol" is attached t...