Jump to content
5539 posts in this topic

Recommended Posts

Did you clear your NVRAM first of all ? Possibly adding AirportBrcmFixup.kext helps here ?!

XhciPortLimit should be enabled cause it patches kexts's to remove the 15 port limit, else you must reconfigure the USBPorts.kext using only max 15 (logical) ports . Depends on your needs for your case.

 

 

 

22 hours ago, AudioGod said:

@fart pants Your using SMBios 19,2 and this is incorrect. Use SMBios 19,1 or MacPro 1,1 with IGPU disabled but not 19,2

You don't need to over install clover like you have and if you do then DO NOT INSTALL RC Scripts as its not needed.

 

Try again and this time dont do anything other then create new details for 19,1 everything is setup correctly for your setup with my EFI.

 

Heres your EFI back cleaned up and changed to the correct smbios for you. Ive made some minor changes and put the GPU injection back to how it should be and reinserted WEG 1.3.6. make new details and try it as it is please and let me know how you get on?


 

FartPants EFI.zip


Cool, thanks @AudioGod

4 hours ago, 8ender said:

A few questions about your latest update. I'm running a similar but not quite the same EFI but following along with your changes on a Z390 Pro Wifi. Aside from the kext updates what did you find darkwake=8 and MemoryAllocation.efi fixed? I can't seem to find any information on MemoryAllocation.efi and where it came from.

 

Also should I see the Intel GPU in Graphics/Displays in System Report? I feel like I used to see it there and now I don't.


Comcerning MemoryAllocation.efi, it’s all in the notes why I’m now using it and your not finding much about it out there because it’s new and me and MaLD0n have only just started using it.

It works fantastically at doing its job and ending KP boot failures at startup.

Darkwake=8 is now used because i find that it works better basically.

 

No when running in headless mode you should not be able to see your igpu in system report.

Edited by AudioGod
2 hours ago, texem said:

Did you clear your NVRAM first of all ? Possibly adding AirportBrcmFixup.kext helps here ?!

XhciPortLimit should be enabled cause it patches kexts's to remove the 15 port limit, else you must reconfigure the USBPorts.kext using only max 15 (logical) ports . Depends on your needs for your case.

 

 

 

 I did clear NVRam from Clover EFI to OC but not from OC iMacPro1,1 to OC iMac19,1. I will try to clear again and report back.

 

I can understand about AirportBrcmFixup I will try that as well. But it is very strange that none of the ports are working. No mouse no keyboard, nothing.

13 minutes ago, WizeMan said:

 I did clear NVRam from Clover EFI to OC but not from OC iMacPro1,1 to OC iMac19,1. I will try to clear again and report back.

 

I can understand about AirportBrcmFixup I will try that as well. But it is very strange that none of the ports are working. No mouse no keyboard, nothing.

Yes that is very strange brother.  Texem will help you out with that one. I’ve got my hands full with the new clover EFI....lol

have you tried it yet by the way?

Edited by AudioGod
41 minutes ago, AudioGod said:

Yes that is very strange brother.  Texem will help you out with that one. I’ve got my hands full with the new clover EFI....lol

have you tried it yet by the way?

No I haven’t tried clearing again the NVRAM yet as it’s the weekend and I’m spending time with the family :) will report back once I try though.

Edited by WizeMan
10 minutes ago, WizeMan said:

No I haven’t tried clearing again the NVRAM yet as it’s the weekend and I’m spending time with the family :) will report back once I try though.

I meant have you tried the new clover EFI yet buddy?

have a nice time with your family :) 

1 minute ago, AudioGod said:

I meant have you tried the new clover EFI yet buddy?

have a nice time with your family :) 

Yes that’s what I used after the OC EFI was having the issues I described. Didn’t get to test it throughly though but seems to be working A-A. (I only replaced the boot arg with shikigva and shiki-id, as with the previous versions and kept my 19,1 serial etc).

 

is there something else you need me to test?

  • Like 1
3 minutes ago, WizeMan said:

Yes that’s what I used after the OC EFI was having the issues I described. Didn’t get to test it throughly though but seems to be working A-A. (I only replaced the boot arg with shikigva and shiki-id, as with the previous versions and kept my 19,1 serial etc).

 

is there something else you need me to test?

Did you try the shiki value I use already?

it seems to universally work but mind you you do have a Rx Polaris so maybe not...lol

Edited by AudioGod
37 minutes ago, AudioGod said:

I meant have you tried the new clover EFI yet buddy?

have a nice time with your family :) 

Yes that’s what I used after the OC EFI was having the issues I described. Didn’t get to test it throughly though but seems to be working A-A. (I only replaced the boot arg with shikigva and shiki-id, as with the previous versions and kept my 19,1 serial etc).

 

is there something else you need me to test?

20 minutes ago, WizeMan said:

Yes that’s what I used after the OC EFI was having the issues I described. Didn’t get to test it throughly though but seems to be working A-A. (I only replaced the boot arg with shikigva and shiki-id, as with the previous versions and kept my 19,1 serial etc).

 

is there something else you need me to test?


no not really just tell me if anything goes wrong or if you Do or don’t get anymore boot kp errors ever.

otherwise just enjoy my friend :) 

Edited by AudioGod
23 minutes ago, AudioGod said:


no not really just tell me if anything goes wrong or if you Do or don’t get anymore boot kp errors ever.

otherwise just enjoy my friend :) 

I did not experience any KPs with the previous build either :) the most stable hackintosh I’ve ever had :) 

3 minutes ago, WizeMan said:

I did not experience any KPs with the previous build either :) the most stable hackintosh I’ve ever had :) 

That’s good to hear, In that case think of this update as a extra layer of polish with added shine..:hysterical:

Edited by AudioGod
  • Like 1
1 hour ago, AudioGod said:

Did you try the shiki value I use already?

it seems to universally work but mind you you do have a Rx Polaris so maybe not...lol


shikigva=80 crashes Apple TV(+) on Polaris. I use shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 and I have Apple TV though with Polaris. I’m getting a second hand MSI Vega 56 soon so DRM won’t be an issue for me in the near future :)

2 minutes ago, WizeMan said:


shikigva=80 crashes Apple TV(+) on Polaris. I use shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 and I have Apple TV though with Polaris. I’m getting a second hand MSI Vega 56 soon so DRM won’t be an issue for me in the near future :)

Stupid Polaris, set it on fire. :blowup: :hysterical:

4 hours ago, fart pants said:


Cool, thanks @AudioGod


No worries buddy but use the latest EFI I uploaded last night instead. 
 

Edited by AudioGod
3 minutes ago, AudioGod said:

Stupid Polaris, set it on fire. :hysterical:


Stupid me for becoming Morgo...’s Patreon for a month. If I didn’t listen to her telling me RX580 is the “sweet spot” I would have gotten a Vega at first. I was this close. But my hackintosh knowledge was very outdated (10+ years back) so I fell into the trap.

 

I’m getting a second hand MSI 56 Airboost and selling my brand new RX580 :\

Edited by WizeMan
1 minute ago, WizeMan said:


Stupid me for becoming Morgo...’s Patreon for a month. If I didn’t listen to her telling me RX580 is the “sweet spot” I would have gotten a Vega at first. I was this close. But my hackintosh knowledge was very outdated (10+ years back) so I fell into the trap.


I wish Nvidia and Apple would get off there high horses and just bring new drivers to the table. I would much rather have a 2080 super or ti as my gpu then the 5700XT. Nothing against the 5700xt or even the vega. They are both fantastic cards but they ain’t a 2080 super or Ti.

Either let Nvidia use Cuda or give in to Apple and use metal. It’s so stupid that something like that stops everybody from enjoying the Nvidia way on there real macs or hacks. 

  • Like 1
On 1/3/2020 at 11:06 AM, hackinhacker said:

 

I did try with both HDMI and DisplayPort, it didn't work.  :( thank you very much for your help but still no luck.  

 

 

 

It is working now with "Headphones" output.  I can hear audio sound clearly with the my headphones.  However still no luck with the HDMI/DisplayPort output.  What would be the next step to troubleshoot?

 

 

Screen Shot 2020-01-04 at 12.35.19 PM.png

11 minutes ago, hackinhacker said:

 

It is working now with "Headphones" output.  I can hear audio sound clearly with the my headphones.  However still no luck with the HDMI/DisplayPort output.  What would be the next step to troubleshoot?

 

 

Screen Shot 2020-01-04 at 12.35.19 PM.png

That looks correct now at least.

great ok so like I said before it should just work. Can you confirm using windows that you have sound going though the HDMI line to your monitor all ok please bud?

Hi,

 

First of all i would like to thank you for what obviously is a LOT of work you’re putting into this, and sharing it with everybody!

That’s really awesome!

 

I also have a audio machine and almost the exact same setup as you have:

 

Aorus Z390 Pro Wifi

I9-9900k

HyperX Predator 4x8GB 3200Mhz DDR4

PowerColor Radeon RX 5700 XT Red Devil

 

a couple weeks ago i upgraded to 10.15.2, and with the Radeon RX 590 Nitro+ all worked just fine.

(some issues with the Steinberg UR44C, but that’s not relevant right now.)

 

I now put in my new RX 5700 XT, and i dug through a lot of info and just cannot get it to work.

 

I’ve followed your instructions:
- updated to Bios F11

- made most of the changes in the bios (for some reason i don’t have any DVMT Total GFX0-Allocated setting)

- i did NOT import those Bios Settings that were attached to one of the first posts, as it complained to be a different version.

- i used your latest EFI Clover bootloader from some hours ago.

 

But i still have the exact same thing happening to me as with all the different settings and kext changes i tried:

 

it boots up, shows the first apple with the loading bar, then that dissapears and the screen just stays blank.

Its not losing the signal somehow, because the screen isn’t turning off. it’s just not displaying anything.

The machine as far as i can tell keeps running normally, i just can’t see anything.

 

the gfx card works fine when i boot with windows though.

 

i’ve tried the 19,1 with igfx enabled and disabled and there’s no noticeable difference in that.

 

Does anyone have any idea what else i could try?

 

ah, and the -v log doesn’t really say anything obvious to me, either. plus it goes away really fast.

 

any help or hint that points me into the right direction is greatly appreciated!

 

58 minutes ago, canstoptherokk said:

Hi,

 

First of all i would like to thank you for what obviously is a LOT of work you’re putting into this, and sharing it with everybody!

That’s really awesome!

 

I also have a audio machine and almost the exact same setup as you have:

 

Aorus Z390 Pro Wifi

I9-9900k

HyperX Predator 4x8GB 3200Mhz DDR4

PowerColor Radeon RX 5700 XT Red Devil

 

a couple weeks ago i upgraded to 10.15.2, and with the Radeon RX 590 Nitro+ all worked just fine.

(some issues with the Steinberg UR44C, but that’s not relevant right now.)

 

I now put in my new RX 5700 XT, and i dug through a lot of info and just cannot get it to work.

 

I’ve followed your instructions:
- updated to Bios F11

- made most of the changes in the bios (for some reason i don’t have any DVMT Total GFX0-Allocated setting)

- i did NOT import those Bios Settings that were attached to one of the first posts, as it complained to be a different version.

- i used your latest EFI Clover bootloader from some hours ago.

 

But i still have the exact same thing happening to me as with all the different settings and kext changes i tried:

 

it boots up, shows the first apple with the loading bar, then that dissapears and the screen just stays blank.

Its not losing the signal somehow, because the screen isn’t turning off. it’s just not displaying anything.

The machine as far as i can tell keeps running normally, i just can’t see anything.

 

the gfx card works fine when i boot with windows though.

 

i’ve tried the 19,1 with igfx enabled and disabled and there’s no noticeable difference in that.

 

Does anyone have any idea what else i could try?

 

ah, and the -v log doesn’t really say anything obvious to me, either. plus it goes away really fast.

 

any help or hint that points me into the right direction is greatly appreciated!

 

Hi,

my Navi Efi is made to work with a 5700xt, myself and a lot of other people on this thread are using one right now. You don’t need to make any changes other then to add your details and everything should be fine.


by your description your Missing a boot argument that’s already in my EFI so I’m Wondering if your using the the RX Polaris EFI by mistake as that one is incorrect for your 5700xt and would cause exactly what your describing.

 

try again and use this EFI and don’t add or remove anything from it just add your details and done.

 

19,1 Aorus Z390 Pro Navi Vega EFI.zip 

Edited by AudioGod

 

3 hours ago, AudioGod said:

Hi,

my Navi Efi is made to work with a 5700xt, myself and a lot of other people on this thread are using one right now. You don’t need to make any changes other then to add your details and everything should be fine.


by your description your Missing a boot argument that’s already in my EFI so I’m Wondering if your using the the RX Polaris EFI by mistake as that one is incorrect for your 5700xt and would cause exactly what your describing.

 

try again and use this EFI and don’t add or remove anything from it just add your details and done.

 

19,1 Aorus Z390 Pro Navi Vega EFI.zip 

 

Thanks for getting back to me so quickly!

 

Unfortunately, also with this, i get the same result. all i've changed in the config of your efi is generate a UUID and the RT Variables, that's it.

i'm not sure whats going on, to be honest.

Edited by canstoptherokk

Thanks for all the hard work on this effort.  I did an install this morning and things are looking great, with no modifications needed for the Auros Z390 Elite motherboard with BIOS version F10A.  I have not tried modifying the CFG setting.

 

Here's the rest of my build configuration (I disconnected the Windows drives during install):

 

Gigabyte Z390 Aorus Elite

Intel i7 9700K

Corsair Vengeance 16GB 3000 DDR4

EVGA AIO

Fenvi T919 WIFI/BT

NVME 512 GB XPG (Windows)

SATA 2TB WD HDD (Windows data)

SATA 128 GB ADATA SSD (MacOS)

  • Like 1
34 minutes ago, Sharkus said:

Thanks for all the hard work on this effort.  I did an install this morning and things are looking great, with no modifications needed for the Auros Z390 Elite motherboard with BIOS version F10A.  I have not tried modifying the CFG setting.

 

Here's the rest of my build configuration (I disconnected the Windows drives during install):

 

Gigabyte Z390 Aorus Elite

Intel i7 9700K

Corsair Vengeance 16GB 3000 DDR4

EVGA AIO

Fenvi T919 WIFI/BT

NVME 512 GB XPG (Windows)

SATA 2TB WD HDD (Windows data)

SATA 128 GB ADATA SSD (MacOS)


that’s awesome buddy well done. :thumbsup_anim:

The Z390 Elite is not a mile away from the Z390 Pro so im not that surprised the dsdt is working with it but the power tables could very well be off..

have you tested things like sleep and wake and shut down after sleep and make sure that all works for you?

check the usb outputs all work for you too as the ssdt isn’t designed for your board but still might work as they are so close,

keep an eye on the motherboard when you shut down the system and make sure the board fully shuts down.

 

35 minutes ago, canstoptherokk said:

 

 

Thanks for getting back to me so quickly!

 

Unfortunately, also with this, i get the same result. all i've changed in the config of your efi is generate a UUID and the RT Variables, that's it.

i'm not sure whats going on, to be honest.


did you also add a serial number as well as the uuid and rt variables?

 

1450569214_Screenshot2019-08-01at10_23_36.thumb.png.75e4985553e858b20f2e9343c77b32bc.png

 

After selecting SMBIOS, example iMac Pro 1,1 ( image above ) then go to Apple and ensure you have the "serial number is not valid " message. Done!


im baffled,

what 5700xt is it?

Edited by AudioGod
6 hours ago, canstoptherokk said:

i’ve tried the 19,1 with igfx enabled and disabled and there’s no noticeable difference in that.

 

Does anyone have any idea what else i could try?

 

any help or hint that points me into the right direction is greatly appreciated!

 

You can’t change hardware using old nvram variables. Even changing settings in the BIOS can cause problems with your install.

 

You also didn’t set up tour BIOS properly by the sounds of it. I would make a TM backup and use Migration Assistant to copy all your stuff over after doing a fresh install.

 

First reset your board. Pull the battery and unplug it from the AC. Wait a minute. Reboot and set up your BIOS as recommended. Note that if your IGPU is disabled and you enable it. You will have to save and reboot and go back into the BIOS to see settings like DVMT Total GFX0-Allocated. Also you have a wifi variant of the board. While they are nearly identical they still have different firmwares.

 

Then reinstall macOS. Grab the latest EFI for the Navi card and add a serial number, a uuid and your RT variables. That’s it.

 

Its honestly way faster than trying to hunt down any mistakes you’ve made.
 

PS: you always want to match your hardware as close to a real Mac as possible. Using 19,1 enables Sidecar. You will not get that working using the GPU in MacPro1,1.

Edited by Tiem
×
×
  • Create New...