- Joined
- Sep 29, 2017
- Messages
- 99
- Motherboard
- ASUS P9X79 WS
- CPU
- i7-3930K
- Graphics
- HD 7950
- Mac
- Classic Mac
- Mobile Phone
I tried to use your version of the OpenCore EFI directory.RehabMan's repository is for Clover, initially, but elements can be reused in OpenCore. The quoted plist is not a complete config.plist anyway, it is meant to be used by copying relevant segments into the actual config.plist.
@Feartech confirmed what I suspected: ACPI renames are missing—and also in your Clover installation.
@UtterDisbelief says X79 has no native USB 3 controller (XHC) but only USB 2 (EHC); and also confirmed that ACPI renames are missing. This means that all our discussions on XhciPortLimit have been futile.
There is no EHC or XHC in your DSDT, but using the MacPro6,1 SMBIOS introduces a SSDT which defines EHC1 and XHC1 as used by the hardware of the actual "trashcan" MacPro (all SMBIOSes do that sort of thing), and these interfere with the mapping of ports from your board.
Here is your Clover EFI with the two relevant patches added in the config.plist. You can check and see what I did with any plist viewer or text editor. If you're willing to try with your Sierra installation (boot from a USB thumb drive, don't mess with the EFI of your working hard drive), this might improve the USB listing by Hackintool.
I have reviewed the ACPI dump. Based on it, you may need SSDT-IMEI after all but I think that SSDT-UNC is of no use, your board appears not to have the unused uncore bridges seen in X99/C610 chipsets (these commonly define four processors even when there is only one socket… and OS X doesn't like it). Checked the motherboard specifications (13 USB 2 ports from X79; USB 3 from an ASMedia controller—these should work out of the box). I have added the two ACPI rename patches, the IMEI device-id injection from the desktop SandyBridge guide because WEG complains about it, and checked the quirks recommended by the SandyBridge-E HEDT guide.
The situation of the MSR patches is confusing: The HEDT guide ticks AppleCpuPmCfgLock (old style for MSR 0xE2) and AppleXcpmExtraMsrs (MSR 0x1AA, present on LGA2011 CPUs); the desktop guide ticks both old-style AppleCpuPmCfgLock and new-style AppleXcpmCfgLock for the same MSR 0xE2. In doubt, I have set all three quirks.
PlateformInfo has been copied from your unredacted (oups!) Clover EFI since you said you use it for both systems. Ultimately, you should have a different serial number for each hackintosh.
This is what I would try to boot from at this stage. Since there is no XhciPortLmit quirk (thanks @UtterDisbelief !), Catalina or Big Sur should make no difference, and neither should the choice of USB port (but you may always try one from the ASM chip and one USB 2 from the chipset). If you try, please let us know if it works, and if not take pictures of the kernel messages.
There's a conflict: you have the entry for "XHCI-unsupported.kext" in config.plist but the actual kext isn't there (which means an immediate error is generated — see first photo below). (Obviously I'm not complaining! It's just an oversight, and you're doing all this hard work for a total stranger, for which I'm grateful.)
I wasn't sure whether "XHCI-unsupported.kext" was supposed to be there or not, so I tried both ways — for half the trials, I added "XHCI-unsupported.kext" and for the other half I removed the entry in config.plist.
I tried both of these ways with my "Install macOS Catalina" USB and then one of these ways (with "XHCI-unsupported.kext" removed) with another USB stick I'd formatted with "Install macOS High Sierra" (just in case the problem is with the Apple portion of the USB sticks). I used each of the 12 USB ports for each configuration. Every single time, the logging froze at what seemed to be an arbitrary point, stopping in mid-line (with a prompt) and freezing there.
I photographed all the freezes — all the photos are attached below. I kept track of which photo corresponds to which configuration (EFI version/USB port — I was cycling through all 12 USB ports in order), but honestly there doesn't seem to be any rhyme or reason to why it's stopping...as you can see, it stops midway through the same lines or different lines in the log, seemingly arbitrarily.
I'm sorry I can't provide more precise information.
Attachments
Last edited: