Contribute
Register

i9-9900k - Asus Prime z390-a, Rx580 8gb, Mojave 10.14.2 - a Desperate’s Man diary!

Status
Not open for further replies.
This Thread helped me so much! Thank you all! It's working like a charm, but surely can be improved in the future. :)
 
Hi there, I have the same motherboard + cpu and have managed to get everything working really great! Sleep/Wake and respectable boot times on apfs etc.
I followed rehabman's guides on creating SSDT for USBInjectAll (read very carefully the part about injecting in groups with -uia_exclude flag), USB Power Property Injection (Read about Fake EC and USBX).

I have attached my EFI/Clover Folder for you to look at, (in the config.plist I have already created a new serial in the SMBIOS and checked coverage before uploading)
FYI
I install all kexts via terminal to /Library/Extensions and put a copy in the EFI/Clover/Kexts/Other. I set Inject Kexts to "Detect" So you can find all the kexts that i have used for this Motherboard in there.
I hope this is of some help!
Thanks!! Now I have all usb ports working full speed. My motherboard is a Asus Prime Z390-A.
 
Hi there, I have the same motherboard + cpu and have managed to get everything working really great! Sleep/Wake and respectable boot times on apfs etc.
I followed rehabman's guides on creating SSDT for USBInjectAll (read very carefully the part about injecting in groups with -uia_exclude flag), USB Power Property Injection (Read about Fake EC and USBX).

I have attached my EFI/Clover Folder for you to look at, (in the config.plist I have already created a new serial in the SMBIOS and checked coverage before uploading)
FYI
I install all kexts via terminal to /Library/Extensions and put a copy in the EFI/Clover/Kexts/Other. I set Inject Kexts to "Detect" So you can find all the kexts that i have used for this Motherboard in there.
I hope this is of some help!
Hi :)

Congratulations!
Did you set the iGPU as headless or do you have both iGPU and dGPU active?

Tx
-a-

EDIT:
Intel graphics is disabled in bios too.

I read that too late
 
@skroutz999, I'm continuing the troubleshooting discussion here based on your previous detailed update...

Can you please compress and upload your CLOVER folder? The config.plist found on Page 1 of this thread could benefit from a number of small edits that address various IRQ-related issues. But I would like to audit the entire CLOVER folder.

Because you have already replaced every major component at least once and sometimes thrice, may I ask why you are sticking to Asus motherboards? Regardless, my goal is not to nudge you towards more hardware replacements, but to audit the current configuration.
 
@skroutz999, I'm continuing the troubleshooting discussion here based on your previous detailed update...

Can you please compress and upload your CLOVER folder? The config.plist found on Page 1 of this thread could benefit from a number of small edits that address various IRQ-related issues. But I would like to audit the entire CLOVER folder.

Because you have already replaced every major component at least once and sometimes thrice, may I ask why you are sticking to Asus motherboards? Regardless, my goal is not to nudge you towards more hardware replacements, but to audit the current configuration.
All these years my previews build systems were with Asus motherboards w/o issues (maximus x38 formula, p5q pro, maximus vi formula, asus z97-p). When I built the new system 5 months ago, the first thought was compatibility issue with prime z390-a. That was the first thing to change my motherboard to maximus xi hero. My decision ofc was wrong and later I found ppl that had success stories with z390-a and maximus xi hero. From my research I have found many people that have the same kind of freezes and they were unable to find a solution. Also some of them have gigabyte motherboards so I came to conclusion that the issue is not motherboard related. Many times crossed my mind to go to gigabyte before that. All my previes builds had always nvidia gpus except the new one.
 

Attachments

  • CLOVER.zip
    4 MB · Views: 109
All these years my previews build systems were with Asus motherboards w/o issues (maximus x38 formula, p5q pro, maximus vi formula, asus z97-p). When I built the new system 5 months ago, the first thought was compatibility issue with prime z390-a. That was the first thing to change my motherboard to maximus xi hero. My decision ofc was wrong and later I found ppl that had success stories with z390-a and maximus xi hero. From my research I have found many people that have the same kind of freezes and they were unable to find a solution. Also some of them have gigabyte motherboards so I came to conclusion that the issue is not motherboard related. Many times crossed my mind to go to gigabyte before that. All my previes builds had always nvidia gpus except the new one.
Attached is a modified CLOVER folder. Please give it a try as follows:
  • Backup the current one then delete it from its original location -- and empty the trash.
  • Copy the new CLOVER folder to the EFI partition of the Mojave SSD and reboot.
Comments:
  • USB SSDT had an incorrect Package size (0x34). This has been changed to 0x1E.
  • Added a handful of checkboxes to ACPI and removed "DSDT.aml" from "DSDT Name" because you're not using a modified DSDT.
  • Checked the "Trust" flag in SMBIOS.
  • Added "-disablegfxfirmware" in Boot arguments.
  • Remove Clover iGPU injection and replaced with WhateverGreen injection in Devices --> Properties.
    • Platform ID = 0x3E980003 for headless 9th-Gen CPU. Only compatible with 10.14.4 and newer.
    • No "device-id" because 10.14.4 natively supports 0x3E98.
However:
  • Because you have "Inject Kexts" set to "Detect" (which is good), please make sure that all of the following are installed in /Library/Extensions (run Kext Utility to rebuild kernel cache if you modify /L/E):
    • Lilu
    • WhateverGreen
    • AppleALC
    • FakeSMC
    • XHCI-Unsupported
    • USBInjectAll
    • IntelMausiEthernet
    • FakeSMC sensors (GPU, LPC, SMM, ACPI, CPU)
Also:
  • If memory serves, I saw some NTFS issues in one of your screenshot. If you're using an NTFS driver in /Library/Extensions, try removing it temporarily (and rebuild kernel cache with Kext Utility).
 

Attachments

  • CLOVER-skroutz999.zip
    4.1 MB · Views: 144
Attached is a modified CLOVER folder. Please give it a try as follows:
  • Backup the current one then delete it from its original location -- and empty the trash.
  • Copy the new CLOVER folder to the EFI partition of the Mojave SSD and reboot.
Comments:
  • USB SSDT had an incorrect Package size (0x34). This has been changed to 0x1E.
  • Added a handful of checkboxes to ACPI and removed "DSDT.aml" from "DSDT Name" because you're not using a modified DSDT.
  • Checked the "Trust" flag in SMBIOS.
  • Added "-disablegfxfirmware" in Boot arguments.
  • Remove Clover iGPU injection and replaced with WhateverGreen injection in Devices --> Properties.
    • Platform ID = 0x3E980003 for headless 9th-Gen CPU. Only compatible with 10.14.4 and newer.
    • No "device-id" because 10.14.4 natively supports 0x3E98.
However:
  • Because you have "Inject Kexts" set to "Detect" (which is good), please make sure that all of the following are installed in /Library/Extensions (run Kext Utility to rebuild kernel cache if you modify /L/E):
    • Lilu
    • WhateverGreen
    • AppleALC
    • FakeSMC
    • XHCI-Unsupported
    • USBInjectAll
    • IntelMausiEthernet
    • FakeSMC sensors (GPU, LPC, SMM, ACPI, CPU)
Also:
  • If memory serves, I saw some NTFS issues in one of your screenshot. If you're using an NTFS driver in /Library/Extensions, try removing it temporarily (and rebuild kernel cache with Kext Utility).
I just did thank you!
Yes I have all these kexts in Library/Extensions with additional 3 kexts which the 2 of them are from Canon pixma MG7550 and the other one from Paragon NTFS (I have 2x internal hdd 3tb barracuda which are ntfs partition). I tried before without these 3 kexts cause @pastrychef have told me that paragon causes issues with hackintoshes but it didn't solve my problem and put it back. Do you suggest to uninstall the software and reformat the drivers to hfs?

P.S. I have the exact same kexts except the 3 I mentioned above in kexts/other. Shall I have igpu enabled or not inside bios?
 

Attachments

  • Screenshot 2019-03-31 at 18.06.09.png
    Screenshot 2019-03-31 at 18.06.09.png
    250.1 KB · Views: 72
Last edited:
I just did thank you!
Yes I have all these kexts in Library/Extensions with additional 3 kexts which the 2 of them are from Canon pixma MG7550 and the other one from Paragon NTFS (I have 2x internal hdd 3tb barracuda which are ntfs partition). I tried before without these 3 kexts cause @pastrychef have told me that paragon causes issues with hackintoshes but it didn't solve my problem and put it back. Do you suggest to uninstall the software and reformat the drivers to hfs?

P.S. I have the exact same kexts except the 3 I mentioned above in kexts/other.
I'm a bit confused by the red statement above. Are you using the two 3TB Barracuda HDDs for Windows or only for Mac data storage?
 
I'm a bit confused by the red statement above. Are you using the two 3TB Barracuda HDDs for Windows or only for Mac data storage?
I have 5 disks internal and 1x dvdrw. First one is nvme 970 pro 500gb which is my main and mojave 10.14.4 is on it. Second is 850 evo 250gb which has high sierra 10.13.6 (the one i tested gtx1050 for 10 days w/o any freezes) and the 3rd ssd is a 840 evo 250gb which has win10 x64 eng. Also I have 2x 3tb Seagate barracudas (ntfs partition) for backup and my work also (videos, photos, music etc). That's why I asked cause I thought to make a backup of barracudas, format them to hfs and put my data back on them wihtout the need this time of paragon ntfs software.
 
Last edited:
Understood. No need to reformat any of the drives, but it may be a good idea to temporarily delete the NTFS kext from just the Mojave 10.14.4 SSD.
 
Status
Not open for further replies.
Back
Top