Jump to content
5539 posts in this topic

Recommended Posts

2 hours ago, AudioGod said:


The second you slap the card on a pcie adaptor it’s stop being native.

Hardly. It’s an additional layer but it still doesn’t change the actual component. Older BCMs had their own carriers too:

22499059-A5BC-483D-9E1B-8960082311C0.jpeg.178b72ad9b1f0e8ba89f00eec211e420.jpeg

The quality of the carrier card and the fact it’s attached to a non Apple logic board make things tricky, but the card itself is a true Broadcom and it will function like one. If I take an engine out of a Porsche, it’s still a true Porsche engine. It’s just going to be a matter of making sure it’s mounted how it should be in your Toyota.

 

The issues with sleep could be bugs in the USB stack/ACPI layer as both are integrated tightly in recent version of macOS. 

 

Such avenues to explore would be a much more fruitful discussion. You built the SSDT so you’re in the drivers seat to help find the potential bug and better yet, the fix. It could be unsolvable (as many things with Hacks) often are, but just throwing up your hands surely won’t fix this :cry:

@Tiem Talk to MaLD0n and he will give you straight facts about it and what I’m saying.

im not throwing my hands up about it far from it so chill your pants mate.


What I’m saying is correct but if you have a better solution then simply using a kext to resolve the problem then I’m all ears.

 

Dont be rude dude, 

  • Like 1
34 minutes ago, pkdesign said:

Yes! Welcome back. Don't scare us like that. I already have issues with OC 0.6.0 :hysterical:

 

 

If it wasn't for Mald0n this thread would be staying closed so thank him not me for talking me around.

 

A certain person (you know who you are) nearly spoilt it for everybody but the needs of the many outweigh the needs of the Few or the One. :dev:

 

New EFIs for OC and Clover with new DSDTs today or tomorrow.

Im just doing the master thread first then il turn over to here and do the same ;) 

Edited by AudioGod
  • Like 4
  • Thanks 3

Thank you @MaLd0n!

 

Waiting with bated breath, I was able to update to 0.6.0 with no issues, but I think the new kext for Broadcom or Airport made my wireless stop working. Will have to go in one by one to see which one is the culprit.

  • Like 2

Clover & OpenCore EFI Updates (10.15.6 Ready), 4th August 2020 

(Use With Bios Revision F12d)

 

 

The EFIs and DSDTs have now been updated to the my latest versions.

Changes made include,

AppleALC 1.5.1

Lilu 1.4.6

WhateverGreen 1.4.1

VirtualSMC 1.1.5

AirportBrcmFixup 2.0.8

IntelMausi 1.0.3

New DSDTs For Clover For firmware F12d

OCQuirks Revision 23 (Clover)

Clover Updated to Revision 5120

OpenCore Updated to Revision 0.6.0 (Big Sur Beta 4 Ready)

OpenCanopy is now Enabled as Standard

Plus other major tweaks and changes to all of the configs

 

 

Clover EFI Update - 04/08/2020 - Use with Bios revision F12d Only or Replace with the older F11 DSDT if you don't want to update the bios

 

Clover Z390 Pro Navi Vega EFI 040820.zip - Vega, Navi (5700, 5700XT etc), Radeon VII DSDT EFI

Clover Z390 Pro Polaris EFI 040820.zip - RX500 Polaris Series (RX590, 580, 570 etc) DSDT EFI

 

Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments.

 

Please Note - I have now set KernelPM to No as standard so if you don’t have a unlocked MSR or not using my MSR Unlocked Bios Profile then go into the Clover Config.plist and set KernelPM to Yes or you won’t be able to boot up. An even better fix would be to unlock your MSR using my profile method.

 

OpenCore EFI Update - 04/08/2020

Myself and @texem have now created a OpenCore EFI done the way the OpenCore Devs intended it to be made, There is no DSDT in use so you can use this EFI on any supported GPU and the SSDTs have been made so they will not be used in any other Operating System apart from MacOS.

 

OpenCore 060 Z390 Pro 19,1 030820.zip - OpenCore v0.6.0, SMBios iMac19,1

OpenCore 060 Z390 Pro 1,1 030820.zip - OpenCore v0.6.0, SMBios iMacPro1,1 (IGPU Disabled)

 

Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments.

Note 2 - Do not try to carry across your old OpenCore Config.plist to the new EFI as to many changes have occurred in 0.6.0. Use the new Config.plist instead.

 

 

For OpenCore Using PlistEdit Pro add your details by modifying the following 

453128831_Screenshot2020-01-16at19_25_01.thumb.png.7a9beac3ccc0096941fc4a0ec07b8248.png

 

PLEASE NOTE - These EFIs are setup to be used with your msr Unlocked so make sure you use the F12d Unlocked Profile but if for any reason you can not unlock MSR then just modify following in the OpenCore config.plist :



249434888_Screenshot2020-01-16at19_26_02.thumb.png.948834bc41d84df577e126ae92c9d773.png

 

 

Additional Downloads

mb_bios_z390-aorus-pro_f12d.zip - Aorus Z390 PRO Firmware F12d 

PlistEdit Pro.zip - PlistEdit Pro (use to edit OpenCore)


 

CFG Unlock (MSR) F12d (F12c Pro WIFI) BIOS Profile - The Easy Way 

I have made this bios profile for you all to use that will unlock CFG on your motherboard making it play alot more friendly with the NVRam.

It also has all the bios settings listed on this guide pre done and saved onto the profile.



F12d_UNLOCK.zip - Use with Z390 Pro Bios Revision F12d ONLY

F12c Unlock.zip - Use with Z390 Pro WIFI Bios Revision F12c ONLY

 

1 - Download the profile and save it to a USB Key

2 - Go into the bios,

3 - Load the profile, 

4 - Save and exit

5 - Go straight back into the bios and save your bios to a new profile and name it Default CFG Unlocked or something like that.

6 - Boot back into Catalina go into your clover config and under Kernal and Kext Patches Uncheck KernalPM 

7 - Save the changes and then restart and your done, your motherboard will now be CFG (MSR) Unlocked

 

    PLEASE NOTE - If you reset the bios or load bios defaults it will clear the Unlock making CFG Locked again. 

Edited by AudioGod
  • Like 4

Well, I finally made the jump to OpenCore. Kind of sad since Clover has been an old friend for 10 years! :bye: But, I got really tired of panics at boot which have completely stopped since I moved to OC.

 

Okay, it seems for me, AirportBrcmFixup.kext is the culprit for my wireless not working. I updated every other kext including:

BrcmBluetoothInjector.kext
BrcmFirmwareData.kext
BrcmPatchRAM3.kext

 

But when I update AirportBrcmFixup.kext my wifi stops working. Going back to 2.0.7 makes if work again.

 

I haven't updated to 0.6.0 but that is my next step now that I know what the wireless issue is.

 

EDIT:

I have just completed the update to 0.6.0 and all is well (except for AirportBrcmFixup.kext)

 

Thanks again @AudioGod! You are the best.

Edited by pkdesign
  • Like 1
Just now, AudioGod said:

@pkdesign Have you tried not using the kext at all and see if it works for you that way?

or just roll back to the previous version bro.

Yes, I took it out to see if that would be okay but it isn’t. My wireless card stops working without it.

 

I'm good for now by rolling back to 2.0.7. Will try to find where to post my issue directly to developers.

I think my answer is somewhere in this description even though I am still on Mojave:

https://github.com/acidanthera/AirportBrcmFixup#please-pay-attention

 

Now I just have to understand it! :frantics:

40 minutes ago, pkdesign said:

Yes, I took it out to see if that would be okay but it isn’t. My wireless card stops working without it.

 

I'm good for now by rolling back to 2.0.7. Will try to find where to post my issue directly to developers.

When you took it out did you clear out your config files from /Library/Preferences/SystemConfiguration? If you don’t, removing the kext may not have the effect you think it will.

Thanks @AudioGod & @texem for these early August EFIs, both Clover & OpenCore! After Clover updated to 5120 & their OCQuirks changes messed with memory on boot yet again, I figured I’d wait to see what you guys made of it. And I got further into the boot process (at least measuring by -v) than I had simply updating Clover myself. But yeah, it still hung on boot, even after an NVRAM reset.

 

So after deciding I really COULD deal with the cosmetic issues I griped at the top of page 138 of this thread about (regarding 0.5.9), I bit the bullet & tried your OC 0.6.0 EFI. After about a half a day of testing (knock on case), I’m happy enough with it to put it on my recovery USB stick too.

 

Good on you guys! Thanks!

Edited by juan e. jot
Corrected page # of thread.

Thanks @AudioGod, I just updated to the new OC 0.6 EFI. I'm running an RX560 and booted into a black screen after the update.

 

I updated the config.plist to turn SpoofVendor back to true, since that was one of the few changes I saw compared to the 0.5.9 version. Looks like that fixed it, and I'm booting up with video signal now. :) Any reason why SpoofVendor was turned off with this release?

PlatformInfo/Generic/SpoofVendor should be disabled as this board does not need it. Did you clear NVRAM after updating? Using it is not wise unless you know specifically why you're setting it to true.

  1. SpoofVendor
    Type: plist boolean
    Failsafe: false
    Description: Sets SMBIOS vendor fields to Acidanthera.

    It is dangerous to use Apple in SMBIOS vendor fields for reasons given in SystemManufacturer description. However, certain firmwares may not provide valid values otherwise, which could break some software.

For those wondering how this EFI works on Big Sur beta 4, pretty much like it works on Catalina. Update process is pretty straightforward, but here is a detailed guide: https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#deviceproperties-injection-failing

Thanks @AudioGod for the updated EFIs and making the thread live again ! I finally switched from Clover to OpenCore, no issues (apart maybe that most USB ports apart from the top row on the back of the computer are now USB3 only, very minor).

6 minutes ago, Pieroman said:

Thanks @AudioGod for the updated EFIs and making the thread live again ! I finally switched from Clover to OpenCore, no issues (apart maybe that most USB ports apart from the top row on the back of the computer are now USB3 only, very minor).


That’s right on the usb as I have to stick to the 15 port limit and I thought that was the best all round setup. It’s very easy to create your own usb kext though if you want to set it up differently, just remember not to go over 15 ports. (Having a usb3 port running usb2 aswell counts as 2 ports used)

 

3 hours ago, iamthekey said:

I can now boot from usb via Clover 5.0 r5120 in 10.15.6 but only with previous efi, with new one got freeze on boot screen. In verbose i can see some acpi errors :{ no idea what to do.


Are you using Catalina or Mojave?

If you take the new EFI and use the old Config.plist from the previous EFI does it still not work for you?

Edited by AudioGod
18 minutes ago, AudioGod said:

If you take the new EFI and use the old Config.plist from the previous EFI does it still not work for you?

Edited 13 minutes ago by AudioGod

 

 

i replace config.plist from older one and it start ok now, but before after EFI update was black screen with logo

×
×
  • Create New...