Jump to content
5539 posts in this topic

Recommended Posts

Hi AudioGod, I'm about to try a new OpenCore install of 10.15.3 on the hardware below and have a couple of questions. 

 

In the NDK OC EFI file provided on page one, I note that there are no SSDT's in the ACPI folder but one DSDT.aml . Does this mean I don't need to generate any to put in there? As this would seem to go against the advice given on the OpenCore Vanilla Build guide which also advises that DSDT is not required in ACPI as "it's built in to the OpenCore firmware". 

 

Also when I tried OpenCore previously on the same hardware with my own EFI following the OpenCore Vanilla Build guide I would have an issue where by after virtually every reboot the PC would hang on the bios post screen. I'd have to physically turn off the PC, wait 30secs and then turn on again. 

 

This behaviour was not present when booting to windows, with the hackintosh drive removed. I also saw it when I quickly tried the NDK OC EFI folder on my current hack build. So not sure whats going on there.

 

My current build is: 

Intel I7 7900k 

 Gigabyte AORUS Z390 PRO F12d CFG Unlock Bios

 Sapphire Nitro RX570

 Corsair Vengeance 16GB @3000mhz (2 x 8GB)

 EVGA 750w 80 Plus Gold Power Supply Unit. 

 Samsung 960 EVO 500GB NVMe SSD macOS Catalina 10.15.3

 Samsung 960 EVO 256GB SSD Windows 10 Pro

 ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)   

 Gigabyte Titan Ridge Thunderbolt card in PCI-E x4 slot

LG 27" 5K Ultrafine Monitor

Edited by jimborae
3 hours ago, texem said:

There is either a "DSDT only" version or "SSDT only".  No need for any extra file.

The SSDT only is somewhere here in the thread but not on page 1

 

 

 Thanks texem, just did a bit more reading re NDK fork of OC and got a very basic understanding of what's going on. And while I think it's a great idea, I think I'll rollback on my plans to use it on my rebuild for the time being & stick with original OpenCore. Still need to work out why Hack is showing this odd boot behaviour though. 

10 hours ago, jimborae said:

 Thanks texem, just did a bit more reading re NDK fork of OC and got a very basic understanding of what's going on. And while I think it's a great idea, I think I'll rollback on my plans to use it on my rebuild for the time being & stick with original OpenCore. Still need to work out why Hack is showing this odd boot behaviour though. 

 

PM me for an "OC 0.5.7 original" EFI for z390pro and tell me about wich profile you plan to run ( i would prefer 1,1).  

 

  • Thanks 1

Hey guys, I use clover in dual boot with windows. Is there a way to prevent windows from creating new clover entries after Update? 

I always rename bootmgfw- to bootmgfw-orig.efi but it's super annoying with all the windows updates lately.

 

18 hours ago, jimborae said:

 Thanks texem, just did a bit more reading re NDK fork of OC and got a very basic understanding of what's going on. And while I think it's a great idea, I think I'll rollback on my plans to use it on my rebuild for the time being & stick with original OpenCore. Still need to work out why Hack is showing this odd boot behaviour though. 

The NDK fork is dead. He's moved it over to a proper external loader extension. With that said, OC has made their own (Bootliquor/OpenCanopy). NDK is effectively dead.

  • Confused 1
8 hours ago, texem said:

 

PM me for an "OC 0.5.7 original" EFI for z390pro and tell me about wich profile you plan to run ( i would prefer 1,1).  

 

Thanks will send PM shortly

OCQuirks R20 is out. I'm using R20 with plist from AudioGod's available download and all is working correctly for me.

 

EDIT:

Be sure to delete FwRuntimeServices.efi because it has been renamed OpenRuntime.efi

Edited by pkdesign
  • Like 2

if i enable igpu i can't boot. i get "error allocating 0x.... alloc type 2"

when i disable igpu i can boot but lose hevc support.

any idea?

 

i5-9600K

Gigabyte z390 Aorus Pro

G-Skill Ripjaws 32GB (2x16GB) DDR4 3200Mhz 

Sapphire RX580 Nitro+ 8GB

Edited by keepclubbin
5 hours ago, keepclubbin said:

if i enable igpu i can't boot. i get "error allocating 0x.... alloc type 2"

when i disable igpu i can boot but lose hevc support.

any idea?

 

i5-9600K

Gigabyte z390 Aorus Pro

G-Skill Ripjaws 32GB (2x16GB) DDR4 3200Mhz 

Sapphire RX580 Nitro+ 8GB

Clear your NVRAM. Clear your CMOS. Set DVMT Pre-Allocated to 32MB (NOT 64, never use 64 unless you build your own EFIs from scratch). Try again. What you're facing are malloc errors where the kernel cannot allocate enough memory; nothing to do with GPU (per se).

  • Like 1
6 hours ago, keepclubbin said:

if i enable igpu i can't boot. i get "error allocating 0x.... alloc type 2"

when i disable igpu i can boot but lose hevc support.

any idea?

 

i5-9600K

Gigabyte z390 Aorus Pro

G-Skill Ripjaws 32GB (2x16GB) DDR4 3200Mhz 

Sapphire RX580 Nitro+ 8GB


Place all the files within this folder into the driver folder in clover, replace when asked and then reboot, reset the nvram (F11 and restart) and it should work for you.

you should also be able to keep your memory at 64mb.

 

OcQuirks R19.zip

  • Like 2

Hello!

 

I hope everyone is safe and healty!

 

I realised that after Maldon patched my Original Extracted DSDT for correct pci info view(thank you so much Maldon), my top 4 usb ports in the back are not working... 

i tested with the old one Audiogod has provided and they work.

How can i solve this?

 

Here is my specific system DSDT patched by Maldon. What should i look for, i am not dsdt expert.

 

 

DSDT.aml

 

Update: Maybe not the best-native method, but UsbInjectAll.kext did the trick.

Edited by dsynos80
On 3/14/2020 at 10:32 AM, velopitex said:

Hello Friends,

 

Is anybody have an issue with USB ports? I mean all USB ports have no response (randomly happening) keyboard, mouse, midi-controller all at ones. But you can put to sleep your PC via power button on the case. All works fine but without USB ports and need to use reset button for reboot. 

I see the same error on a daily basis. It seems usb devices are loosing power randomly. But logs are not very helpful in my case either. 

3 hours ago, frankintosh said:

I see the same error on a daily basis. It seems usb devices are loosing power randomly. But logs are not very helpful in my case either. 


I’m looking into it for you guys.

 

  • Like 1
29 minutes ago, AudioGod said:

10.15.4 Release

 

Screenshot 2020-03-24 at 19.17.14.png

Hi AudioGod, I'm trying to update my hackintosh from 10.15.3 to 10.15.4 but it doesn't work :(
When i click on the update, it restarts on another partition, the apple is displayed but nothing moves ...

How did you do your update? Do you have any idea where my problem is ? ^^'

 

Thanks for your works :) 

IMG_1215.jpg

IMG_1216.jpg

6 minutes ago, clmlvx said:

Hi AudioGod, I'm trying to update my hackintosh from 10.15.3 to 10.15.4 but it doesn't work :(
When i click on the update, it restarts on another partition, the apple is displayed but nothing moves ...

How did you do your update? Do you have any idea where my problem is ? ^^'

 

Thanks for your works :) 

IMG_1215.jpg

IMG_1216.jpg

Update to the latest version of clover and make sure your running with a unlocked MSR

 

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5107

Edited by AudioGod
56 minutes ago, AudioGod said:

Update to the latest version of clover and make sure your running with a unlocked MSR

 

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5107

Many Thanks ! It's works :)

494387699_Capturedecran2020-03-24a21_55_27.png.98a21ef1a57715990b33eb188c2494db.png

  • Like 1

IMPORTANT 10.15.4 UPDATE NOTICE.  (CLOVER USERS)
Everybody that is using my Clover EFI please make sure you update to the latest version of Clover (5107) before updating too 10.15.4 or you may find your unable to update Catalina.

 

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5107

 

I will update the Clover EFI’s on the thread ASAP but if you don’t want to wait then just make sure you do the above and your be fine. :) 

 

Edited by AudioGod
  • Like 1


 

1 hour ago, ghozy said:

I have a Z390 Ultra, i5 9600k, and a Sapphire 5700 XT.  When I first booted up everything worked fine but after I turned off the computer and turend it back on i got a prohibited symbol and I can't do anything. 

Photo on 3-24-20 at 8.21 PM.jpg

 

First of all this topic is for the z390 Aorus Pro board and there are probably some differences on the DSDT and SSDT, I do not know how much compatible this EFI is for your board, but I guess not 100% for sure.

 

Now for that particular issue you are facing, try turning off the PSU switch and remove the board battery for a couple of minutes to clear CMOS and NVRAM. Then inset battery, turn on PSU switch and power on the machine. Enter the correct bios settings and try to boot again.

 

Also if you are using the OpenCore EFI and have MSR locked you need to make the appropriate changes to config.plist.

  • Like 1
5 hours ago, ghozy said:

I have a Z390 Ultra, i5 9600k, and a Sapphire 5700 XT.  When I first booted up everything worked fine but after I turned off the computer and turend it back on i got a prohibited symbol and I can't do anything. 

Photo on 3-24-20 at 8.21 PM.jpg


My DSDT is no good for your motherboard buddy so the best thing you can do really is use the link I provide you with and put in a request with MaLD0n and get yourself a new DSDT made up for your board.

 

To Create Your Own Patched DSDT Message @MaLd0n using the link bellow

https://www.olarila.com/forum/17-dsdt-patch-requests/

(If you want a perfect setup then getting your own patched DSDT made would be the best thing to do, Mine will work perfectly fine but different hardware no matter how small a change it is can tend to have some sort of effect on the DSDT and your setup)

 

Also using the latest posted version of OCQuirks will help with your boot failures.

 

 

OcQuirks Revision 19 & FwRunTimeServices Latest Versions (I am Now using the plist too)

Please include the plist in the drivers folder, I have made some changes to the plist that should make it play a lot more friendly now with the IGPU enabled. 

 

OcQuirks R19.zip

 

 

Hi @AudioGod, using your EFI without any issues, just updated to 10.15.4 and all things seems to be still fine, but I just noticed one minor thing which is really interesting for me:
On your "About this Mac" snapshots I see that "Memory" tab is available for you, but in my case it is not available for some reason. I have exactly the same motherboard, CPU and memory amount with yours, the only difference that yours memory goes at 3466 Mhz but mine goes at 3600 Mhz. Also I see that in both(your and mine) system reports memory shows as not upgradable. I'm using the exactly same EFI(including the same iMac 19,1 SMBIOS parameters) as you attached. So it is quite interesting for me why "Memory" tab is available on your setup but NOT available on my setup? Could you please provide any suggestions? Thanks

 

9 minutes ago, AlexeyNikitin said:

Hi @AudioGod, using your EFI without any issues, just updated to 10.15.4 and all things seems to be still fine, but I just noticed one minor thing which is really interesting for me:
On your "About this Mac" snapshots I see that "Memory" tab is available for you, but in my case it is not available for some reason. I have exactly the same motherboard, CPU and memory amount with yours, the only difference that yours memory goes at 3466 Mhz but mine goes at 3600 Mhz. Also I see that in both(your and mine) system reports memory shows as not upgradable. I'm using the exactly same EFI(including the same iMac 19,1 SMBIOS parameters) as you attached. So it is quite interesting for me why "Memory" tab is available on your setup but NOT available on my setup? Could you please provide any suggestions? Thanks

 

 

Hi There, 

im guessing your using clover configurator so open your config.plist using it and in the smbios section where it says Platform Feature change it from 0x22 to 0x00 save and restart and check and see but your memory tab should be there for you. :)

 

@AlexeyNikitin Fun Fact, A real 19,1 iMac doesn't have a memory tab so not having it is actually correct for the smbios but using the above method brings it back into play. :thumbsup_anim:

Edited by AudioGod
×
×
  • Create New...