dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 5733Z0, Thank you for those recommendations. I was unaware of the OCValidate utility; I've been using OC-tool, and it didn't detect those discrepancies. At your suggestion, I ran OCValidate and made the recommended changes. The boot problem, however, persists. Here is a link to my EFI folder with debug logs: http://damdas.myqnapcloud.com:8082/share.cgi?ssid=bb3ead008f9d442c95fc459574fcbf7b Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 22, 2021 Share Posted August 22, 2021 @dmcnaugh15 Okay. A tip for furture uploads: exclude the "Resources" and "Kexts" Folders. If you don't use the boot chime and/or Audio Assistance for blind people you can delete the complete Audio Folder which reduced the size of the EFI by about factor 10. Here are my Findings so far for V3: ACPI Section: Important: SSDT-EC-USBX-DESKTOP.aml contains all sort of name variations and locations of the Embedded Controller. The idea is to delete ALL the entries which are not suited for your system. Alternatively you could use SSDTTime to generate SSDT-PLUG and SSTD-EC-USBX specific to your system. DeviceProperties: PciRoot(0x0)/Pci(0x2,0x0): I see you are using an empty Framebuffer for using the iGPU for computing tasks. But Headless framebuffers (where the dGPU is the display out) do not need framebuffer-patch-enable and framebuffer-stolenmem. I deleted those keys. Then I added a few keys which display some more info about the iGPU in the "About…" Section Added Key AAPL,slot-name "Built-In Added Key device_type "Display Controller" Added Key: model "Intel UHD Graphics 630 (Headless)" PciRoot(0x0)/Pci(0x1b,0x0): Are you sure layout ID 1 is the correct Layout for your board? Kernel Moved AppleALC to top right after Whatevergreen. Disabled CodecCommander.kext. I think this is no longer necessary Deleted Entry "AppleMCEReporter disabler" > unnecessary Why are you using both Intel and Broadcom Bluetoth Kexts? > Disabled Broadcom kexts for now to avoid Kernel Panics Restrict Events > Why are you needing this? NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82 contains strange Boot-Args: debug=0x12a msgbuf=1048576 The rest of it looks fine and I couldn't see any obivious reason for the issue from what I can tell so far. Here's the config file:config.plist Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 (edited) 5T33Z0, Can't thank you enough for all your work on this! I used your config file and made changes, as outlined below, but the problem persists. Created a new EFI folder with panic logs, V04, available at: http://damdas.myqnapcloud.com:8082/share.cgi?ssid=bb3ead008f9d442c95fc459574fcbf7b Per your recommendations: Deleted all contents from kext and resource folders. ACPI Section: Replaced the prebuilt Dortania aml's with SSDTTime generated aml's. DeviceProperties: PciRoot(0x0)/Pci(0x2,0x0): Kept your changes. PciRoot(0x0)/Pci(0x1b,0x0): Regarding your question about whether Layout 1 is correct: My codec is Realtek AppleALC 1220 (determined by checking in linux terminal, as per Dortania instructions). Layout 1 is one of many possible layouts for that codec, confirmed by reviewing it's information on github. Layout 1 has always worked for me in the past, up until the change from AppleALC 1.6.0 to 1.6.1. Other than than that, I don't know of a more direct way to confirm layout 1 is actually the correct one. Additionally, I tried all the other layouts for the 1220 codec, one-by-one (good old trial and error), and none of them fixed the problem. Kernel Kept the kext order change for AppleALC to top right after Whatevergreen. Deleted CodecCommander.kext. Deleted AppleMCEReporter disabler kext Answer to your question: "Why are you using both Intel and Broadcom Bluetoth Kexts?". I don't remember, for sure, why I added those. I think I started with the intel kexts and was having problems with bluetooth not working, so I added the BRCM kexts. Regardless, I've deleted those kexts for now. Answer to your question: "Restrict Events > Why are you needing this?". I have no memory why or when I added it. I've deleted it for now. NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82 contains strange Boot-Args: debug=0x12a msgbuf=1048576: Those recommendations were taken from Dortania's in depth debugging article (https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/kernel-debugging.html#efi-setup). But, I went ahead and changed them back to what they were before: -v keepsyms=1 debug=0x12a alcid=1 Attached is the updated config file. config.plist Edited August 22, 2021 by dmcnaugh15 Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 As a matter of follow up, I found the specific ALC build that is causing the problem, and made the Github commit under bug tracker. The committed build - first one not working - is e2d0a03. You can find the ALC builds at the following url: https://dortania.github.io/builds/?product=AppleALC&viewall=true. If interested in the Github ticket, that url is here: https://github.com/acidanthera/bugtracker/issues/1756 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 22, 2021 Share Posted August 22, 2021 (edited) I had a look at the specs of this board: https://rog.asus.com/us/motherboards/rog-maximus/rog-maximus-xi-hero-wi-fi-model/spec You are using the wrong Kexts for LAN. And a lot of unnecessary kexts in general. My advice would be to start with a minimal set of Kexts to see if the problem is persisting. I've generated an EFI using OC Gen X for Coffeelake CPUs and fixed a few missing keys and added the Entries for your ACPI and DeviceProperties etc. After downloaing the EFI Please do the following: - Copy over your existing .aml Files to the ACPI Folder - Copy your Resources Folder over to EFI > OC - Copy the whole EFI Folder to a FAT32 formatted USB stick and try booting from it. And see if it crashes - Add in your USBMap.Kext and the entry for it in the Kext > Add section. I forgit about that one. NOTE: - Wi-Fi wont work. You need the correct variant of this kext based on the macOS variant you are using: https://github.com/OpenIntelWireless/itlwm/releases/tag/v2.0.0 - Bluetooth wont' work either. You have to find out what hardware is in it. If it is Intel as well, you need ths: https://github.com/OpenIntelWireless/IntelBluetoothFirmware/releases If the problem still persits I doubt that it will be configuration-based. It could be a bug in AppleALC or a hardware issue. For refernece you could check this github. Looks like a well documented and well-maintained repo for your board. https://github.com/vovinacci/OpenCore-ASUS-ROG-MAXIMUS-XI-HERO EFI_OC072_Coffelake_fresh.zip Edited August 22, 2021 by 5T33Z0 Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 5T33Z0, Couple things: 1. The problem was an AppleALC kext bug (https://github.com/acidanthera/bugtracker/issues/1756). It has just been fixed in 1.6.4 build e0cdf39. See: https://dortania.github.io/builds/?product=AppleALC&viewall=true 2. I can't thank you enough for all your advice. I've long suspected I've been carrying unnecessary kext baggage around; kind of like the human genome. Those kexts have accumulated over time, since the Clover days. Whenever something worked, and as long as it continued to work, I just kept things as is. But, with your advice and direction, I'm going to fix things up on the config side. 2 Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 Follow up / New Problem: 1. Old problem Fixed: Once macOS launches, everything is working. Intel bluetooth, wifi, internet, audio. 2. New problem (Post to safe mode): The computer posts to safe mode (see photo) with each reboot; I have to press F1 to get past the safe mode screen. Should I post this as a separate question with it's own thread, or do you know of an easy solution? Wondering if it's related to my bootcamp installation. I added back the "APPLE" folder inside the EFI. See updated config and EFI folder (V06 V_06 AppleALC_Fixed-NewProb_Boot_to_safe) at the following url: http://damdas.myqnapcloud.com:8082/share.cgi?ssid=bb3ead008f9d442c95fc459574fcbf7b config.plist Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 22, 2021 Share Posted August 22, 2021 (edited) 1. Disable SSDT-RHUB-Reset.aml. That's only necessary if you want to reset USB Ports before mapping them. This shouldn't be enabled. 2. Try enabling Kernel > Quirks > DisableRtcChecksum. It was enabled in your config. I forgot to reenable it for the fresh one. Edited August 22, 2021 by 5T33Z0 Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 Yep. That fixed it. You the man. Hey... do you have a Venmo account? Sure would like to make it worth your time? 1 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 22, 2021 Share Posted August 22, 2021 No I don't. it's okay. Nevermind. But if you are into synthwave you could cop my album on bandcamp https://stansteez.bandcamp.com/ Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 Holy {censored}! That's awesome music. Following now! Link to comment Share on other sites More sharing options...
Allan Posted August 22, 2021 Share Posted August 22, 2021 Glad to see that you got a working Hackintosh! @5T33Z0 really rocks! 👏👏👏 I'm going to move your thread to the AppleALC forum area ok? 😉 1 Link to comment Share on other sites More sharing options...
dmcnaugh15 Posted August 22, 2021 Author Share Posted August 22, 2021 Good idea, Allan. Thanks for all your help with this too. 1 Link to comment Share on other sites More sharing options...
Recommended Posts