It BSODs after grabbing boot.sdi. Excellent and super useful info on the screen got me nowhere... Ideas?
My PE image contained only one boot.sdi, so I don't know if I need to make a different one (I'd have to learn how, too).
What signatures are checked and failing? (And why is it limited to PXE booting?) Could it be a server/connection issue? Any way to get boot/kernel debug output?
19:20:56.506192 IP 192.168.1.103.1804 > box.tftp: 41 RRQ "bootx64.efi" octet tsize 0 blksize 1468
19:20:56.507717 IP 192.168.1.103.1805 > box.tftp: 33 RRQ "bootx64.efi" octet blksize 1468
19:20:57.154604 IP 192.168.1.103.8943 > box.tftp: 26 RRQ "\Boot\BCD" octet tsize 0
19:20:57.157846 IP 192.168.1.103.8944 > box.tftp: 39 RRQ "\Boot\BCD" octet tsize 0 blksize 1456
19:20:57.317944 IP 192.168.1.103.8945 > box.tftp: 34 RRQ "\sources\boot.wim" octet tsize 0
19:20:57.322753 IP 192.168.1.103.8946 > box.tftp: 31 RRQ "\Boot\boot.sdi" octet tsize 0
19:20:57.327146 IP 192.168.1.103.8947 > box.tftp: 59 RRQ "\EFI\Microsoft\Boot\fonts\segoe_slboot.ttf" octet tsize 0
19:20:57.331822 IP 192.168.1.103.8948 > box.tftp: 59 RRQ "\EFI\Microsoft\Boot\fonts\segmono_boot.ttf" octet tsize 0
19:20:57.333607 IP 192.168.1.103.8949 > box.tftp: 58 RRQ "\EFI\Microsoft\Boot\resources\bootres.dll" octet tsize 0
19:20:57.335063 IP 192.168.1.103.8950 > box.tftp: 56 RRQ "\EFI\Microsoft\Boot\fonts\wgl4_boot.ttf" octet tsize 0
19:20:57.336483 IP 192.168.1.103.8951 > box.tftp: 56 RRQ "\EFI\Microsoft\Boot\fonts\wgl4_boot.ttf" octet tsize 0
19:20:57.338377 IP 192.168.1.103.8952 > box.tftp: 44 RRQ "\boot\boot.sdi" octet tsize 0 blksize 1456
Forgot to mention that it just shuts off after a little bit. Also, I can go get a laptop (more accurately, the laptop I want this to work on primarily) if we think it's the VM causing problems.
Also - the VM is set to EFI firmware by adding this option to the .vmx file.
firmware = "efi"
Second Edit: Finished reading your post... more to come
I referenced your post because it was the one with most useful information for getting me where I am.
As I have things now:
Router is DD-WRT with DNSMasq set as DHCP. DNSMasq options:
box is running tftpd with a rebind for \ to /
I have a PE 4 image I use, I built it from the ADK. I used WinToolkit to turn it in to an ISO, and then used Rufus to make an EFI flash drive of it. (I'll be honest, until I started doing this, never bothered to learn how manually: it's easy and always worked.) At this point what I have done is extracted that ISO to the TFTP root, copied bootx64.efi from \EFI\Boot\ to the root, replaced the BCD in \Boot\ with the one from \EFI\Windows\Boot\ and disabled digital signature checking.
Volume in drive Z is box
Volume Serial Number is F007-BA11
Directory of z:\tftproot
11/13/2014 01:28 AM <DIR> .
11/12/2014 06:19 PM <DIR> ..
02/20/2014 04:06 AM 1,617,752 bootx64.efi
11/13/2014 05:12 PM <DIR> Boot
11/13/2014 01:28 AM <DIR> EFI
02/20/2014 04:06 AM 1,613,656 bootmgr.efi
08/21/2013 09:31 PM 427,680 bootmgr
11/13/2014 01:28 AM <DIR> en-us
11/13/2014 01:28 AM <DIR> sources
3 File(s) 3,659,088 bytes
6 Dir(s) 182,364,905,472 bytes free
I don't want to use standard PXE, it's annoying as crap on these laptops - adds 15 seconds to boot if it's before the hard drive, no matter what. UEFI PXE however doesn't even show up unless it's booting (this was frustrating at first, mind you).
How do you use PXE to chainload to efi?
Edited by AceBlade258, 14 November 2014 - 01:33 AM.