pastrychef
Moderator
- Joined
- May 29, 2013
- Messages
- 19,458
- Motherboard
- Mac Studio - Mac13,1
- CPU
- M1 Max
- Graphics
- 32 Core
- Mac
- Classic Mac
- Mobile Phone
If it's not one thing, it's another. I got past the black screen and machine was stable, so I thought I'd implement an SSDT for USB port limit. Spent a solid 3 days reading and re-reading @RehabMan post, got USB working without issues. Went back into BIOS to enable Intel Virtualization and noticed that ALL of my BIOS settings are set to default. Hmm...I had never reset them, or hit clear CMOS button while testing my USB ports (don't even try ). Anyway, I decided to go through and set all my settings to what they were one by one. I discovered that I'm getting the same error as I attached to this post. Funny thing is I implemented all of the suggestions made by @pastrychef and @manHands . If I disable Thunderbolt, boots no problem. But obviously there's no way I'm going to do that because I need to get Thunderbolt going. The card is in great working condition and my UAD Apollo Twin MKII is recognized in Windows 10 and previously in macOS. So I'm sitting here scratching my head....again.
Most posts like the one here by @P1LGRIM talk about ensuring that all the usual drivers are loaded in the drivers64UEFI. One that caught my attention is AptioMemoryFix.efi which is what I have in the folder now. Should it be AptioMemoryFix-64.efi instead?
This one here by @BreBo says that I need to make changes to my config.plist by ensuring that CsrActiveConfig is set to 0x67 not 0x03.
@CaseySJ on the other hand was able to solve similar issue by "by using OsxAptioFix2Drv-free2000.efi in combination with slide=0. All other memory fix drivers are ineffective" as he describes in his build. I am accounting for the fact that his system is different than mine but also a fairly recent build.
Any thoughts?
Sorry. I don't have any experience with Thunderbolt and have no idea how it behaves.
I know that AptioMemoryFix works for Z170, Z270, and Z370. From what I've read it doesn't work well with Z390. Reading about fixes that work for an entirely different chipset will probably not help you.