-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't boot due to strange error #12
Comments
From first glance this looks consistent with this issue (stuck on Would you be able to provide more information about what hardware your using? Another thing that'd be useful to collect is the OpenCore debug log, which you can enable with the release build of the project or by enabling these entries in the config.plist: Lines 79 to 102 in b16b38a
|
My CPU is an AMD Ryzen 5950x, I just saw #5 now and didn't realize I had to manually change stuff. Sorry, this is my first time doing anything hackingtosh related 😅 I've applied the patches and changed I can see these have been applied successfully in the debug log as well:
While this does get me past the previous error it now seems to be reboot looping and sending me back to the 3 boot options. I had to record the screen in order to capture this brief boot output before it reboots: Any ideas on how I can further debug this? |
What you're seeing on screen there is from OpenCore, which also hints that there is something wrong with the
I suspect that you've replaced the entire tree for |
I added the patch bit at the end of the But unfortunately the same reboot loop persists 🤔 I did manage to get serial output working with the following command:
|
Okay managed to get some more output via the log files on the EFI disk:
So it seems the above screenshot was a red herring and that's the initial boot output rather than the last. I tried playing around with the core config of the VM as well, when I patched the config.plist with the entries from the AMD repo I made the modification to fit 16 cores of the replace values as well as assigned 16 to the VM. However I noticed the logs said |
I have been following this thread for some time and I also got to this point with com.apple.dock.fullscreen error. I have an AMD 7950X3D. |
@physxP I just managed to get further: I found https://sanitychecker.ocutils.me mentioned somewhere on reddit, uploaded my plist and applied all the critical suggestions. |
The estimated time that the installer shows is usually pretty inaccurate; if you've gotten to that point then your networking should work fine in the OS. WhateverGreen isn't needed for Hyper-V at this time as there already exists basic framebuffer support through MacHyperVSupport itself. Lilu + WhateverGreen also can't detect devices soon enough to apply patches (see #6), so it won't be able to do anything either. Were there any other options you had to change that got you past your previous error? I can also add better base support for higher core counts OOB (testing with a 3950X) if you got to a more helpful error this way. |
@Qonfused this is the sanity checker result: https://sanitychecker.ocutils.me/results/do8ty7nqvfta76bk
|
The primary change I can observe is enabling After installing macOS, it may be worth checking if you can boot into Recovery reverting the changes to the booter quirks and w/ WhateverGreen disabled. I can test on a 3950X machine but I don't have access to it for the minute. |
It seems you were right that only the |
Thanks for the update! I've added a note in #5 to remind people as it's not mentioned in the AMD Vanilla repository and is very easy to miss in the Dortania Guide. |
Hi,
I've followed the instructions in the readme very carefully but it seems to just not work on my system as I get the following error:
I've tried to let it sit there for 10 minutes without it making any progress. Right before this screen I have 3 boot options: "EFI (dmg)", "Openshell.efi" and " Reset NVRAM". None of the The first option results in the above error while OpenShell gives a command prompt and the last option just seemingly doesn't do anything.
I've tried running
create-virtual-machine.ps1
with the following args which all give the same result:-Version 13
-Version 14
(This gives the same boot options but as text rather than graphical)I've tried the above combination of args with both the
EFI-0.0.0-64-bit-RELEASE.zip
fromreleases
as well as cloningmaster
, building withscripts\build.ps1
and running fromdist/
.This is my windows version:
Am I missing something obvious to make this work?
The text was updated successfully, but these errors were encountered: