-
Notifications
You must be signed in to change notification settings - Fork 125
Does not work with UEFI Boot #167
Comments
Yes, UEFI should work. I don't have a system to test UEFI PXE, so I'll need your help debugging this. Can you share what error messages you get from your NUC, your PyPXE configuration settings, and debug output from PyPXE (add |
I'm also facing EFI\UEFI issues, I believe at least one of the errors is finding the proper architecture file name. Earlier, the DHCP request options are moved into self.options[client_mac], not in self.leases[client_mac]['options']
|
@ef83, can you post your full command and debug logs? (add With debug logging enabled, the parsed options are printed between |
I've been testing with some other PXE server software and they're working using my same media\kernels\boot loaders. Therefore, at this line of code, you should be using self.options not self.lease So far I've fixed that code on my local setup but that only gets me to the proper bootloader based on the architecture. 2656 1492 2019-06-10 18:10:00,684 DEBUG <--BEGIN OPTIONS--> I've identified the issue, at least with my clients, and I'm trying to understand why. I think it has to do with the client side in EFI mode. Basically when you are sending the DHCP offer, it's being sent to some derived broadcast address. I have some custom logging but here is my environment: SO here you'll see, the offers are being sent to the broadcast of [192.168.234.255] and that does not work. If I send it to the subnet broadcast of 255.255.255.255 then it is working just fine and I'm able to at least load my boatloaders. |
Ok, first part, try see if the fix-architecture branch of my fork fixes the architecture detection. Second part is harder to pin down. |
On Intel NUC, I had to switch to "Legacy Boot", in order to make it boot.
Should it work with UEFI Boot?
The text was updated successfully, but these errors were encountered: