5/29/2023 0 Comments Macbook pro uefitool nvme driver![]() ![]() I tested 4 different firmware/bios posted in this thread: I'm new here! I spent the whole weekend trying to get this to work, but had limited success. NZbLi5QGeIĪnd this is my cmd line: sudo qemu-system-aarch64 -M virt -m 4096 -cpu cortex-a53 -smp 4 -device VGA -device nec-usb-xhci -device usb-kbd -device usb-mouse -drive file=/dev/rdisk2,id=system,if=none,format=raw -device usb-storage,drive=system -bios ~/Documents/QEMU_EFI_TEST.fd Here is the link to the firmware !4AoiTSSQ!yTIk_27DVCk2. (I tried looking for an ARM NVMe EFI driver but I could not find much) (this UEFI has basically the same thing I did done to it but Googulator did it at a source code level )Īnd then I extracted the QEMU VGA driver out of the custom debug firmware and I inserted it into the Latest UEFI firmwareĪnd it worked! i got working VGA and i was able to boot windows directly from USB sadly I did not see any NVMe driver in the latest UEFI and it cant see an NVMe storage device, so far now we will still have to manually image windows since the installer refuses to install to a USB device. upstream/ which has no VGA driverĪnd take the noKVM firmware file from here that is sadly a debug build which does not boot windows but has the VGA driver. take the latest release UEFI firmware from here. I managed to get windows booting via USB without the need to use the older firmware and having to preload the USB driver. While this post was validating I made a a thing/discovery This was my final cmd line in the end that I found ran the best for me (so far Cortex A53 runs a bit better then A57 for me on my System, a Mac Pro 5,1 10.13.2 Dual X5677s 32GB DDR3 ECC RDIMMs) it took FOREVER to do all the first time setup stuff but it did get there in the end! which also worked! (this part is basically exactly what Googulator did )Īnd I was finally able to boot windows to a desktop. wim properly! now to make sure i had the right bootloader files, I booted into the windows ARM ISOs installer in QEMU and applied the BCD stuff from there. using-dism ) in a windows 10 圆4 VM to deploy the ARM64 ISOs install.wim to a USB HDD formatted as NTFS (GUID with an EFI partition) luckily for me it did manage to deploy the. this got the EFI to see the USB CD ROM and i was able to boot from it, and the windows installer could now see "itself" but no matter what I did I could not get anything to show up for windows to install to! I tried NVMe AHCI nothing would show up, but inputting another USB Storage device would show up, but of course windows wont let you install to USB devices! In that I made a VMDK file containing the USB mass storage EFI Driver linked in this thread, and loaded it. The latest custom EFI linked in this thread is sadly a debug build and as such causes windows to BSODīut I had come across an RELEASE EFI build that was a bit older, that DID boot windows 10, here in post 3: unfortunately for me, from what I can tell it only worked with the bare minimum of devices, stuff like mass storage USB, NVMe or AHCI SATA none of that would show up as bootable in this EFI build but the last few posts gave me some ideas and hopes. It was a lot of hard work but I finally did it, I spent most of yesterday and all of today working on it but I finally did it! I got windows 10 build 16296 for ARM64 to boot in QEMU! ![]()
0 Comments
Leave a Reply. |