<div dir="ltr"><div><div>iPXE initialising devices...EFIDRV connecting our drivers<br>EFIPCI 0x69589a18 PciRoot(0x0)/Pci(0x5,0x4) cannot read PCI configuration: No such device (<a href="http://ipxe.org/2c044087">http://ipxe.org/2c044087</a>)<br>
EFIPCI 0x68ffe918 PciRoot(0x0)/Pci(0x1F,0x6) cannot read PCI configuration: No such device (<a href="http://ipxe.org/2c044087">http://ipxe.org/2c044087</a>)<br>EFIPCI 0x68ffb618 PciRoot(0x1)/Pci(0x5,0x4) cannot read PCI configuration: No such device (<a href="http://ipxe.org/2c044087">http://ipxe.org/2c044087</a>)<br>
SNP 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) is an SNP device<br>EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) has driver "SNP"<br>EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) disconnecting existing drivers<br>
EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) connecting new drivers<br>SNP 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) is an SNP device<br>EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) has driver "SNP"<br>
EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DRIVER_START<br>EFIDRV 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) could not open device path: Error 0x7f37e08f (<a href="http://ipxe.org/7f37e08f">http://ipxe.org/7f37e08f</a>)<br>
HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 315x (H) by 0x7da7ce98 DxeCore(?) for 0x0 <NULL><br>HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 80x (T) by 0x6a1d4d98 Emulex 10G NIC<br>
HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 11x (T) by 0x69bc1b98 Platform Console Management Driver<br>HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 11x (T) by 0x69bc1718 Platform Console Management Driver<br>
HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 1x (G) by 0x69c7e418 VLAN Configuration Driver<br>HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 1x (G) by 0x69c5c198 UEFI PXE Base Code Driver<br>
HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 7x (T) by 0x6ab6e898 BIOS[INT13] Block Io Driver<br>HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 1x (T) by 0x69c7ef18 Simple Network Protocol Driver<br>
HANDLE 0x691db218 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5CF3FC6E4738,0x0) DevicePath opened 1x (D) by 0x69c7ef18 Simple Network Protocol Driver<br>SNP 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) is an SNP device<br>
EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) has driver "SNP"<br>EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) disconnecting existing drivers<br>
EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) connecting new drivers<br>SNP 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) is an SNP device<br>EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) has driver "SNP"<br>
EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DRIVER_START<br>EFIDRV 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) could not open device path: Error 0x7f37e08f (<a href="http://ipxe.org/7f37e08f">http://ipxe.org/7f37e08f</a>)<br>
HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 273x (H) by 0x7da7ce98 DxeCore(?) for 0x0 <NULL><br>HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 80x (T) by 0x6a1d4d98 Emulex 10G NIC<br>
HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 11x (T) by 0x69bc1b98 Platform Console Management Driver<br>HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 11x (T) by 0x69bc1718 Platform Console Management Driver<br>
HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 1x (G) by 0x69c7e418 VLAN Configuration Driver<br>HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 1x (G) by 0x69c5c198 UEFI PXE Base Code Driver<br>
HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 7x (T) by 0x6ab6e898 BIOS[INT13] Block Io Driver<br>HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 1x (T) by 0x69c7ef18 Simple Network Protocol Driver<br>
HANDLE 0x68b7ad18 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(5CF3FC6E473C,0x0) DevicePath opened 1x (D) by 0x69c7ef18 Simple Network Protocol Driver<br>ok<br><br><br><br>iPXE 1.0.0+ (471f) -- Open Source Network Boot Firmware -- <a href="http://ipxe.org">http://ipxe.org</a><br>
Features: HTTP DNS TFTP EFI Menu<br><br>iPXE> ifstat <br>iPXE> <br><br></div>I guess my question on having to disconnect the protocols is how important that is in the snp or snponly cases. I was having a pretty nice experience just by leaving the platform protocols in place and adding the download and simple filesystem protocols to the device. I will confess to having thought about creating a simple filesystem device that in no way looks like a network device to avoid triggering network behaviors in EFI bootloaders, but that would probably be making a new device handle instead of trying to use the network device.<br>
<br></div>That said, forgive me if this sounds stupid but I don't know better... Would it make sense to chase the parentage of the device path of interested looking for a managed network protocol device in this case?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 6, 2014 at 9:41 AM, Michael Brown <span dir="ltr"><<a href="mailto:mcb30@ipxe.org" target="_blank">mcb30@ipxe.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 06/08/14 14:03, Jarrod Johnson wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Shell> dh 1ba<br>
Handle 1BA (68FFA518)<br>
Dpath (691ED298)<br></div><div class="">
AsStr: 'PciRoot(0x0)/Pci(0x1,0x0)/<u></u>Pci(0x0,0x0)/MAC(5CF3FC6E4738,<u></u>0x0)'<br>
Net (691DF020)<br>
MNPSb (68E94640)<br>
ARPSb (69379720)<br>
<br></div><div class="">
Shell> dh 1da<br>
Handle 1DA (68B87018)<br>
Dpath (68B86B18)<br></div><div class="">
AsStr:<br>
'PciRoot(0x0)/Pci(0x1,0x0)/<u></u>Pci(0x0,0x0)/MAC(5CF3FC6E4738,<u></u>0x0)/IPv4(0.0.0.0,0x0,DHCP,0.<u></u>0.0.0,0.0.0.0,0.0.0.0)'<br>
Load (68B87128)<br>
Net (691DF020)<br>
Pxebc (68B88110)<br>
</div></blockquote>
<br>
OK. We want to be driving handle 0x68ffa518. We need to disconnect MNPSb etc, so that we can gain control of the network device.<br>
<br>
However, the SNP instance (0x691df020) is being exposed via both handles. I'm not sure what logic we could sensibly apply in order to obtain the first handle as our designated handle.<br>
<br>
What happens if you try to load snp.efi (instead of snponly.efi) on this system?<span class="HOEnZb"><font color="#888888"><br>
<br>
Michael<br>
</font></span></blockquote></div><br></div>