Closed jordanurbs closed 2 years ago
JonMcL
commented
2 years ago @jordanurbs Maybe the non existent dGPU has to be disabled? Or at least disable anything that tries to find it.
See the "Boot Flag" section on https://dortania.github.io/OpenCore-Install-Guide/extras/spoof.html
baughmann
commented
2 years ago @jordanurbs Looks like @JonMcL is onto something here
jordanurbs
commented
2 years ago @JonMcL @baughmann Naww I've tried that also in the boot-args, nada.
I changed some BIOS settings and now the loader bar gets to about 20%. But still no dice. I posted the debug log in the other thread; it's not too much different from up there. Problem is I don't see any actual issues from the debug log.
baughmann
commented
2 years ago @jordanurbs I don't see any either. Thats when you know it's bad.... You have all of the logs turned on right? You may want to switch to the DEBUG releases for OpenCore and for all of your Kexts if you haven't already. Those logs look kinda short (if you pasted the whole thing, that is)
You've also tried clearing NVRAM right? IIRC, that's where the boot args get loaded to
Btw, thanks for editing your comment in the general chat
jordanurbs
commented
2 years ago I've enabled debugging and reset NVRAM several times but the verbose is not displaying on the screen, it keeps going straight to the apple logo loading bar.... any ideas?
baughmann
commented
2 years ago Theres a bit more involved than just adding -v to the boot args. You'll also need to set -debug=0x100 and a few other things. You'll also need to replace the RELEASE versions of OC/OpenCore.efi, BOOT/BOOTx64.efi and any kexts that you have with the DEBUG versions of each. For example, if you google "opencore pkg" you will come across its releases page. You will see two versions of OC there: RELEASE and DEBUG. This repo ships with RELEASE. You will need to download DEBUG and replace each *.efi and *.kext with the DEBUG versions. The DEBUG versions have verbose logging enabled to help troubleshooting.
You can find out more about swapping out the versions and turning on debugging by following the link in the issue template for enabling logging.
Also, apologies if you already mentioned this, but you're current on BIOS version F9i right? You also followed the BIOS guide closely?
jordanurbs
commented
2 years ago @baughmann Yes I know, I followed the dortania OpenCore guide for debugging ... with the exception of -debug=0x100 (as that doesn't seem to be in that debug page), I'd already done everything else you mentioned. I'll add that and -v to the boot args and let's see. I followed the OC guide for my other machine's issue and it booted into verbose debug mode no problems.
I am downloading the 11.4 installer and going to try your earlier 0.7.1 release instead.
And yes, using F9i and imported your BIOS settings directly.
jordanurbs
commented
2 years ago Onto something!
jordanurbs
commented
2 years ago The only lead I have is that perhaps the Samsung 970 Evo Plus is incompatible. I am seeing online that there are firmware updates but can't tell if it's possible to update that via the Designare BIOS on its own...
EDIT: Just ordered an enclosure so I can update the firmware. Will be back in a few days with an update and hopefully close down the issue :) thanks again
baughmann
commented
2 years ago @jordanurbs I can 100% confirm that that 970 Evo is indeed compatible. Maybe try updating the firmware from Windows using Samsung Magician? You can also try it on another HDD. Can you boot to the installer? If you cannot even get to the installer, your EFI or BIOS are the problem, and not the drive you're trying to install to.
In the BIOS, you can go to EZ Flash (or whatever the update portion is) to check the BIOS version. When in doubt, download and install F9i from this repo's releases page. F9i is absolutely, undoubtedly, one-million percent a requirement when you import my BIOS config. It is also recommended otherwise as it is the latest BIOS firmware version that works.
jordanurbs
commented
2 years ago Oh, uh oh. I have no Windows machine. And no, it won't load the installer at all... what do you make of that screenshot up there? From what I've gathered, it indicates an NVMe drive issue no?
Btw, its the Evo PLUS. And yes I'm on F9i...
baughmann
commented
2 years ago Oh, uh oh. I have no Windows machine. And no, it won't load the installer at all... what do you make of that screenshot up there? From what I've gathered, it indicates an NVMe drive issue no
If you've found something in your research that indicates that output means there's likely an NVMe issue, I would follow that. However, I'd reckon you'd get the same issue even if you completely removed/unplugged your all of your disks and tried to boot the installer. I could always be wrong though, as I'm the furthest from an expert that there can be.
I know I'm kind of scraping the barrel here, but maybe try another clean USB? I don't know anything about how this bootloader or macOS function under the hood but when I see "Kernel Panic" and "AppleSMC" in the same log line I immediately think that it's something to do with VirtualSMC and its associated extra kexts or maybe even Lilu, though I don't know enough about these libraries to know the why, so I immediately jump to "EFI folder is messed up" / "BIOS is incorrect".
baughmann
commented
2 years ago @jordanurbs Is it possible to install Windows on another drive to update the firmware or pop the NVMe into your other machine to update it? Also, try removing all drives and booting the installer just to test my theory above. I'd hate for you to spend the money on an external enclosure when it's not going to help (unless you want to buy one anyway)
baughmann
commented
2 years ago @jordanurbs Also, IIRC, even when you import my bios configuration there are still a few settings you need to set manually. If you have a discord or other preferred chat app we can have a convo there and try to figure it out
jordanurbs
commented
2 years ago @baughmann I'm not a discord user but on Telegram or Signal I am [redacted] ... I appreciate it
By the way. Removed the M.2 drive and now all I get is PlatformPanicAction -> AppleSMC (the NVMe Controller issue is gone)
baughmann
commented
2 years ago I have signal. Paste your number here because it doesn't look like you can use usernames there. After I respond, just delete your comment.
baughmann
commented
2 years ago @jordanurbs One thing at a time, SMC issue first, then NVMe issue (there's a kext that might help)
arashster
commented
2 years ago In the BIOS, you can go to EZ Flash (or whatever the update portion is) to check the BIOS version. When in doubt, download and install F9i from this repo's releases page. F9i is absolutely, undoubtedly, one-million percent a requirement when you import my BIOS config. It is also recommended otherwise as it is the latest BIOS firmware version that works.
That's interesting since I was able to get your latest BIOS to work fine on two of my machines (Z390 Designare) running F9j. However, it doesn't work on another one - even with F9i.
I wonder what it is?
baughmann
commented
2 years ago After @jordanurbs And I talking yesterday we were able to get the installer booting by specifying the deviceId correctly.
baughmann
commented
2 years ago @arashster Honestly, man, I have no idea. All three same mobo, CPU, and GPU?
arashster
commented
2 years ago @baughmann More or less yes. All Z390 Designare, i9-9900K, and either RX570 or RX580 GPUs (Polaris).
baughmann
commented
2 years ago @arashster What're the symptoms on the one that doesn't work?
arashster
commented
2 years ago It freezes at the Apple logo just before before the loading bar shows.
baughmann
commented
2 years ago You able to throw the debug versions of OC, the kexts, and drivers on it, and enable verbose and debug mode?
arashster
commented
2 years ago I haven't had a chance to. I will try giving that a go tomorrow and report the results. How do you enable verbose and debug mode? Is it https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html?
baughmann
commented
2 years ago @arashster That's the one!
arashster
commented
2 years ago Haven't had a chance to try the debug mode. But on one of my machines that the EFI works with, the upgrade to Monterey also worked!
baughmann
commented
2 years ago @arashster @jordanurbs Closing this issue since @jordanurbs got this EFI (minus the USBPorts.kext) working on his new mobo.
Re-open or open a new issue if needed.
Describe the bug Same hardware as build with the exception of GPU. Installer freezes/stops at Apple logo.
OpenCore Logs
Expected behavior Installer should open.
Hardware Specifications: