Jump to content
5539 posts in this topic

Recommended Posts

After reading a few things on OpenCore website I managed to fix sleep issue with v0.6.1

 

I upload my EFI here, but be advised, I'm nowhere near as knowledgeable as most of the people here in regards to OpenCore (or Clover), so while the EFI I made may work for me, it may not be a good EFI both for me but you as well.

 

If you consider yourself knowledgeable enough on this area, and if you want to spend a few minutes checking my EFI, please let me know what dump things I may have done :D (even if it works for me fine - so far)

 

Two of the guides that I couldn't follow is this and that.

 

for the first one, I don't have Windows and as I understood it is required to follow the guide.

 

On the second one it says: 

Quote

To find the USB Controller that needs fixing, search for _PRW in your DSDT and see what Device is mentioned within it, generally this will be something like SB.PCI0.XHC.

 

but I don't know how to find the USB Controller that needs fixing in the first place... 

 

PS: You have been advised, use this EFI on your own risk

EFI.zip

9 hours ago, Filmluver said:

I'm having an issue where I can't login to facebook. I'm running the opencore Audiogod 19,1 latest build and it has been rock solid in productivity. I am able to run Premiere, FCPX, Resolve, perfectly. I can watch Netflix through a browser, and I can even login to Instagram. I have never been able to login to Facebook though. Not matter if I use Chrome or Safari. Everytime I attempt to sign in, it hangs for a while, then says "Sorry, something went wrong. We're working on getting this fixed as soon as we can." This has been going on for 3 days. I only recently fully switched over to my Hackintosh so I never tried to sign into Facebook previously. I can however log in through my Macbook and my old iMac without a problem. Anybody have any ideas? Thanks. 

 

I'm not sure how that could be related to hackintosh (I mean browser login, not actually account in your system preferences), but it is highly likely I may be missing something here.

 

Have you tried to troubleshoot it? You mentioned you tried with Chrome and Safari, I assume those two browsers are been used by you frequently, could you try another browser that you haven't use at all? Like Firefox, Opera, Microsoft Edge? (btw I switched 100% to MS Edge for over a year and and I love it).

 

Also, could you try enabling guest account and try to login from there to make sure it is not an account-wide issue?

 

If you manage to login with a browser other than Safari and Chrome, then have a look at your browser plugins, one or many plugins you have could be the source of the issue (also try to clear caches).

 

If you cannot login with any browser but you can login via guest account, then you might have an app running for your user (like AdGuard maybe) that for some reason preventing your login process. (btw I use AdGuard everywhere without any issue, but I'm just saying).

Edited by panosru

For testing purposes I've installed the latest Big Sur Beta. Before I've updated OpenCore to 0.6.1 and the kexts. No change to config.plist.

Installation went without issues. And MacOS seems to work fine.

Now I'm migrating from Mojave to see if it gonna work.

 

Update:

Apparently migration went successful. Maybe I just need to reinstall some software.

Edited by Neblogas
On 9/28/2020 at 1:13 PM, cyrdroid said:

So, for anyone having similar issue, I found the issue and solution. Today I noticed high load caused by accountsd, I googled that issue and I happened to stumble upon that discussion:

https://discussions.apple.com/thread/251846520?answerId=253525046022#253525046022

 

And the resolution was to Remove your iCloud Keychain.

Ugh, I hate to say it but this why I am still on Mojave. Rock solid.

On 9/29/2020 at 5:22 AM, panosru said:

 

I'm not sure how that could be related to hackintosh (I mean browser login, not actually account in your system preferences), but it is highly likely I may be missing something here.

 

Have you tried to troubleshoot it? You mentioned you tried with Chrome and Safari, I assume those two browsers are been used by you frequently, could you try another browser that you haven't use at all? Like Firefox, Opera, Microsoft Edge? (btw I switched 100% to MS Edge for over a year and and I love it).

 

Also, could you try enabling guest account and try to login from there to make sure it is not an account-wide issue?

 

If you manage to login with a browser other than Safari and Chrome, then have a look at your browser plugins, one or many plugins you have could be the source of the issue (also try to clear caches).

 

If you cannot login with any browser but you can login via guest account, then you might have an app running for your user (like AdGuard maybe) that for some reason preventing your login process. (btw I use AdGuard everywhere without any issue, but I'm just saying).

 

 

Thanks for your help. Well folks, my being unable to log into Facebook is NOT a Hackintosh issue. I just got a new Macbook Pro and I am unable to log in from any browser. My old Macbook and my old iMac allow Facebook log in. Or shall I say, they automatically log in when I go to Facebook.com from info of previous log ins. I've searched the topic and some folks have encountered the issue with it eventually resolving itself. Oh well.... 

On 9/27/2020 at 8:52 PM, OGlikeNES said:

Is anyone having time issues with windows? Time works fine on catalina but when I switch to windows its like the time picks back up from where it left off. I did the UTC thing in regedit but still no fix. 

In my experience, it seems the Gigabyte UEFI BIOS just likes resetting itself to UTC (upon checking network time?), with UI controls to change time, but nothing I can find to change the time zone. That’s OK as it likely affects primarily multi-boot setups. That said, if you’re like me, the second option listed here works in Windows, doesn't mess up Catalina or Linux (Mint): https://www.howtogeek.com/323390/how-to-fix-windows-and-linux-showing-different-times-when-dual-booting/

 

I see you tried editing regedit, but hopefully the above is a clearer step-by-step than you might have found? Dunno, and of course YMMV. But good luck!

Edited by juan e. jot
Acknowledge a version of my suggestion has already been tried.

OpenCore 0.6.2 EFI Update - 10.15.7 & Big Sur Ready, 5th October 2020 

(Use With Bios Revision F12d or Newer)

 

 

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

Changes made include,

AppleALC 1.5.3

Lilu 1.4.8

WhateverGreen 1.4.3

VirtualSMC 1.1.7

AirportBrcmFixup 2.1.0

IntelMausi 1.0.4

OpenCore Updated to Revision 0.6.2 (Big Sur Ready)

OpenCanopy is Enabled as Standard

Plus other major tweaks and changes to all of the configs

 

 

OpenCore EFI Update v0.6.2 - 05/10/2020

 

OpenCore 062 Z390 Pro 19,1 051020.zip - OpenCore v0.6.2, SMBios iMac19,1

OpenCore 062 Z390 Pro 1,1 051020.zip - OpenCore v0.6.2, 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

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


 

 

Bios Update F12K (F12J Pro Wifi) and Bios Settings (Profile's Coming Soon)

 

mb_bios_z390-aorus-pro_f12k.zip - Aorus Z390 Pro Bios Firmware F112K

mb_bios_z390-aorus-pro-wifi_f12j.zip - Aorus Z390 Pro Wifi Bios Firmware F112J


PLEASE NOTE - MSR Unlock is now baked into the BIOS as a setting so you no longer need my bios profile to unlock your MSR.

 

BIOS SETTINGS (Bios Revision F12k & F12j Pro Wifi)

 

 Enter BIOS -> Press Delete -> Enter Setup

 Save & Exit -> Load Optimized Defaults

• Boot -> CFG Lock -> Disabled

• Boot -> Windows 8/10 Features -> Win 8/10 WHQL

 Boot -> CSM Support -> Disabled (Can be set to Enabled if need be but try to have it set to Disabled first)

 Favourites -> Extreme Memory Profile (X.M.P.) -> Profile1

 Favourites -> VT-d -> Disabled (Can be set to Enabled or Disabled, Your choice)

 Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot

 Settings -> IO Ports -> Internal Graphics -> Enabled (Disabled If Using SMBios 1,1)

 Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

 Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M

 Settings -> IO Ports -> Aperture Size -> 256MB
 Settings -> IO Ports -> Wifi -> Disabled (Z390 Pro Wifi Only)

 Settings -> IO Ports -> Audio Controller -> Enabled

 Settings -> IO Ports -> Above 4G Decoding -> Enabled

• Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Auto

 Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled

• Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled

 Settings -> Platform Power -> Platform Power Management -> Enabled

 Settings -> Platform Power -> ErP -> Enabled

 Settings -> Platform Power -> RC6(Render Standby) -> Enabled

 Save & Exit  Save & Exit Setup

 

 

F12K BIOS Profile With MSR Unlocked & All The Correct Settings Dialled in for you - The Easy Way 

@texem has 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.



Z390 PRO BIOS PROFILE - F12k.zip - Use with Z390 PRO Bios Revision F12K ONLY

Z390 PRO WIFI BIOS PROFILE - F12J.zip - Use with Z390 PRO WIFI Bios Revision F12J ONLY (Coming Soon)

 

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 or something like that.

6 - Save the changes and then restart and your done, your motherboard will now be CFG (MSR) Unlocked and all the correct settings will be dialled in for you.

 

 

Clover EFI Update Coming Soon (I am holding off from updating the Clover EFI until it is fully Big Sur Compatible and will update the EFI as soon as it is so)

Edited by AudioGod
  • Like 7
  • Thanks 3

Hey @AudioGod good to see you ain't disappeared, had literally pulled 0.62 from the github site and here you are, popping up with it all done for us .. nice one .. thanks :)

 

One quirk i hit with this for some reason i did not see before in any version, incase someone else hits it, was that i had to change:

 

UEFI > Output > Resolution to Max as when i left it as it was, it for some reason made all my monitors go to 1080p with no resolutions available to change to 2k or whatever.   I have 1 1080p monitor attached and i suspect it was syncing to this for all 3 which made the displays fscking horrid and blurry. 

 

Other than that no issues so far.. 

 

Cheers

 

 

  • Thanks 1
1 hour ago, Cass67 said:

Hey @AudioGod good to see you ain't disappeared, had literally pulled 0.62 from the github site and here you are, popping up with it all done for us .. nice one .. thanks :)

 

One quirk i hit with this for some reason i did not see before in any version, incase someone else hits it, was that i had to change:

 

UEFI > Output > Resolution to Max as when i left it as it was, it for some reason made all my monitors go to 1080p with no resolutions available to change to 2k or whatever.   I have 1 1080p monitor attached and i suspect it was syncing to this for all 3 which made the displays fscking horrid and blurry. 

 

Other than that no issues so far.. 

 

Cheers

 

 

 

Whoopsy, Ive corrected the EFI so its set to max as standard. I have it set up at 2k on my monitor as I don't like the boot menu in 4k. My bad buddy sorry. :poster_oops:

  • Like 1
28 minutes ago, pkdesign said:

Under UEFI>ReservedMemory, why do we have those two entries? One looks like it is for HD3000 iGPU and the other for Lenovo ThinkPad T490.

 

Correct but they are disabled so just ignore.

  • Like 1
  • Thanks 1

Thanks again for the Update

 

For info when i rebooted i got a warning that the Hackintosh could not be booted :

 

Quote

OCSB: No suitable signature - Security Violation OCB: Apple Secure Boot prohibits this boot entry, enforcing! OCB: LoadImage failed - Security Violation

 

I had to edit plist in Windows and change the following entry to get it to boot

 

Misc > Security> SecureBootModel change to > Disabled

 

2 hours ago, thering1975 said:

Thanks again for the Update

 

For info when i rebooted i got a warning that the Hackintosh could not be booted :

 

 

I had to edit plist in Windows and change the following entry to get it to boot

 


Misc > Security> SecureBootModel change to > Disabled

 


All you actually had to do was clear your nvram...

4 hours ago, AudioGod said:


All you actually had to do was clear your nvram...

You have to change this to <Disabled> if you are using iMac19,1 (page 46 of OC Reference Manaul.) <Default> is set for iMacPro1,1.

  • Thanks 1

Having just finished updating my Dell Laptop and reading the OC guide a hundred times :(, I noticed that our EFI does not include a SSDT-EC-USBX.kext. Is there a reason for that @AudioGod? Does our board not need the embedded controller patched? Or is this obvious since it works with out it :whistle:

42 minutes ago, pkdesign said:

Having just finished updating my Dell Laptop and reading the OC guide a hundred times :(, I noticed that our EFI does not include a SSDT-EC-USBX.kext. Is there a reason for that @AudioGod? Does our board not need the embedded controller patched? Or is this obvious since it works with out it :whistle:

I’m doing the power tables via the usb.kext instead, this is why I don’t use or need usbx.

I do a few things different from the guide but all for good reason like the booter quirks for windows and Linux. Remember buddy it’s a guide not a gospel... :hysterical:

  • Haha 1

Ah, I see it now. I never realized that SSDT-EC-USBX.aml, SSDT-UIAC.aml, and USBPorts.kext all contain the same data. Hmm, is that addressed in the OC Guides? It would make sense to explain that. Now I wonder if I need both on my laptop :shock:

1 hour ago, texem said:

btw: some guys are hoping for Big Sur release today. TBH .. please not Apple. It's too buggy still also with latest public beta 9 .. and OS-restrictions are going to far (for me at least)


No way is it releasing today. They haven’t done a golden master for the devs yet so that would be nothing short of absurd plus like you say it’s way to buggy still. I thought there would be at least 1 more beta togo yet. 
Saying that though clover put out there big sur ready release up this morning so maybe.

Edited by AudioGod
1 hour ago, texem said:

For me the newest clover is like connecting the water pipe to the gas pipe :hysterical:

OC as a helper to solve the problem having no prelinked kernel anymore.

Correct me if i'm wrong here.

 

 

 

 


No your spot on, that’s exactly what they ended up doing....lol

 

It works though and we are at the end the road nearly as far as x86 macOS goes so I guess it makes no difference at this point.

Sure they might support macOS on x86 for a good few years yet but just like last time the software written by other people and Apple themselves is gonna go down the pan now cos it will all be designed and written for Apple silicon first from here on in.

 

Anybody that thinks I’m wrong about this then just wait and see my friends, the next 24 months will show you. Only thing that could make my views all wrong is if the silicon ain’t up to it against x86 but somehow I think that’s just not going to be the case especially considering it’s all built on the TSMC 5nm process and will move to 3nm not to long after. (Intel still use there own 14nm++++++++++++++++++++++++++++++ and AMD use 7nm TSMC and the difference between the 2 is incomparable when it comes to everything really and thanks to the Ryzen 5000 series that now includes single core speed too) The TSMC 5nm process is on a next level, nearly 1 billion extra transistors are in the A14 chip compared to the 7nm A13 chip so I have a feeling the A14x chip and Apple silicon will be next level too. We will see.

Edited by AudioGod
  • Like 1

for all using OC 0.62 from here :

 

if you are going to update your Big Blurr to beta 10, please modify "DmgLoading" to "Any"  ( and as noted above )  SecureBootModel to "Disabled".

Else you'll get an OCB: LoadImage failure

 

  • Like 1

And sadly to say but we still suffer from MemAlloc issues. We only have a very few slides available / can be seen in OC debug log.

BS beta10 requires more slides allocated . Vit fixed this last night in OC 063. 

To get it more stable,  modify config.plist 

<key>DevirtualiseMmio</key>
<true/>

and 

<key>ProtectUefiServices</key>
<true/>

 

Edited by texem
42 minutes ago, texem said:

And sadly to say but we still suffer from MemAlloc issues. We only have a very few slides available / can be seen in OC debug log.

BS beta10 requires more slides allocated . Vit fixed this last night in OC 063. 

To get it more stable,  modify config.plist 


<key>DevirtualiseMmio</key>
<true/>

and 

<key>ProtectUefiServices</key>
<true/>

 

 

Ive had my plist with them settings enabled from time buddy so nobody needs to do anything that's already using my EFI and also im running and upgraded to Big Sur Beta 10 with no issues or trouble using my standard 0.6.2 EFI :thumbsup_anim: (I haven't even bothered compiling and trying 0.6.3 yet)

 

1006872078_Screenshot2020-10-16at10_27_29.png.e560bd8a881ae8ae7a863f8f2f39f6df.png

 

616165643_Screenshot2020-10-16at10_44_19.png.bb4079bda7e7bde087badc7e45d24471.png

 

Edited by AudioGod
  • Like 1
×
×
  • Create New...