Michael Brown

Generalised to also support /32 subnets and merged via #1243

Built-in laptop keyboards are typically wired in as PS/2 keyboards, since the wire protocol consumes less power than USB. iPXE does not get involved in driving the hardware for these,...

> ``` > > ... > > .. > > > > > ipxe.ip=192.168.1.8 > ipxe.scriptlet=ifopen net0 && chain ${filename} > > > > ``` > > Would this feature...

> Would you like to ask whether the iPXE code does not support USB2.0 devices? If not, how to modify the code to be compatible with USB2.0 devices? iPXE is...

Testing with some extra debug shows that the freeze occurs when we attempt to open the PCI I/O protocol with `BY_DRIVER` attributes: ```c /* Open PCI device */ if (...

This failure of the VirtualBox "E1000 network interface card Driver" to disconnect properly can be reproduced without any iPXE code using the UEFI shell: 

I have found the root cause bug within the VirtualBox VBoxPkg E1kNetDxe driver. The VirtualBox driver's `Stop()` method will do absolutely nothing unless called with a non-zero number of children:...

Please try building with `DEBUG=intel,intelx`. Since you say the card works on this system in BIOS mode but not in UEFI mode, it would be worth capturing the debug output...

Yes, you can use all three together. As described at https://ipxe.org/download#debug_builds the `DEBUG=` argument is essentially a comma-separated list of source files: using `DEBUG=intel,intelx,netdevice` will enable debugging (at level 1)...

Thanks for the debug information. First, a couple of clarifications: In the BIOS case, you are using `undionly.kpxe` which (by design) will only ever see a single network interface since...