Jump to content
5539 posts in this topic

Recommended Posts

3 minutes ago, canstoptherokk said:

i know :) it's all good. 

i haven't tried the RGB fix yet, as i have to finish a song until tomorrow (yikes). but i'll look into it.

alltho i would wonder why it then works in safe mode but not in regular mode.

 

its bypassing whatevergreen and all other drivers and kexts for hardware when you boot into safe mode including colour pallets too,  

Edited by AudioGod

Quick question, since I need BrcmFirmwareData.kext, BrcmPatchRAM2.kext, and FakePCIID.kext for my system, do I just copy those into the OC Kexts folder? Do I need to configure anything in the config.plist?

Edited by pkdesign
1 minute ago, pkdesign said:

Quick question, since I need BrcmFirmwareData.kext and BrcmPatchRAM2.kext for my system, do I just copy those into the OC Kexts folder? Do I need to configure anything in the config.plist?

You need to create entries on Kernel -> Add

  • Like 1
  • Thanks 1

Argh. I have a new issue. I wonder if anyone else has had something similar. I have read all 126 pages of this forum but I don’t have that big a brain to remember. :whistle:

 

After finally having sleep working for weeks, I realize that the new WiFi card I installed is causing my machine to panic (I'm guessing since I'm not in front of the computer) when it tries to go to sleep. When I come back, machine is off and I have to press the power button twice to get it to boot.

 

I have the card installed in the PCIEX_3 slot. Should I (can I?) put it in the PCIEX4 slot?

 

I'm pretty sure I have energy setting right:

1895823748_ScreenShot2020-05-08at8_21_53PM.thumb.jpg.9034ec5131c8dd928addc625fca89ee3.jpg

Edited by pkdesign
4 hours ago, pkdesign said:

Argh. I have a new issue. I wonder if anyone else has had something similar. I have read all 126 pages of this forum but I don’t have that big a brain to remember. :whistle:

 

After finally having sleep working for weeks, I realize that the new WiFi card I installed is causing my machine to panic (I'm guessing since I'm not in front of the computer) when it tries to go to sleep. When I come back, machine is off and I have to press the power button twice to get it to boot.

 

I have the card installed in the PCIEX_3 slot. Should I (can I?) put it in the PCIEX4 slot?

 

I'm pretty sure I have energy setting right:

1895823748_ScreenShot2020-05-08at8_21_53PM.thumb.jpg.9034ec5131c8dd928addc625fca89ee3.jpg

 

Try PCIEX4 (the far bottom port). There have been a lot of people (including me) who faced weird behaviours when the card was installed on ports other than this. 

  • Like 1

Nope. :wallbash: Tried moving card to PCIEX4 and still had odd sleep behavior. Set my energy settings as you have above (I had all not checked, thought Powernap for sure didn't work) and still no.

 

I can tell immediately its not going to work because my RGB RAM lights turn off. That never happened in normal sleep. It is so odd because I press power button once and the AIO pump light sort of half lights up, then goes out. Press power again and the lights all light up then go out completely. Third time computer boots, but to the log in screen which I do not have normally.

 

I'm guessing it is some voodoo with the particular PCI adapter that I have (Fenvi FV-101). Like everything in hackintosh world, one step forward two steps back. At least I have Airdrop and Continuity working! No worries, I'll just go back to not having sleep. Not a big deal really.

Edited by pkdesign
On 8/22/2019 at 2:29 PM, AudioGod said:

@panosru 

 

SLEEP  – Resolving Instant Wake

 

Resolve Instant Wake From Sleep caused by the Corsair H100i V2 AIO Cooler

 

To enable wake using mouse and keyboard the Corsair H100i v2 USB cable must be disconnected from motherboard header F_USB1 

 

 

If you want to keep the Corsair H100i v2 USB cable connected then enable the patch in config.plist, instruction below. 

Hackintosh will then sleep, but can only wake using power button.

 

IF USING CORSAIR H100i v2, OR IF YOU HAVE INSTANT WAKE FROM SLEEP PROBLEM 

THEN

ENABLE PATCH --> XPRW change Method(GPRW...

and download --> SSDT-GPRW.aml and place inside EFI/Clover/ACPI/Patched 


 

1788948731_Screenshot2019-06-06at20_20_16.thumb.png.92d91aa7162c8904abc762098b16e3f6.png

 

Credit: Patch by Rehabman

 

 

 

 

hi there, I'm using opencore, how do I fix this problem? 

Just now, chewgoji said:

 

hi there, I'm using opencore, how do I fix this problem? 


 Best thing you can do is unplug the AIOs internal usb connection as it does nothing unless your using icue in windows plus macOS doesn’t understand it and nor does the uefi.

just plug it back in for them extremely rare times that you might want to use it for example changing the fan curves or colours.

4 minutes ago, AudioGod said:


 Best thing you can do is unplug the AIOs internal usb connection as it does nothing unless your using icue in windows plus macOS doesn’t understand it and nor does the uefi.

just plug it back in for them extremely rare times that you might want to use it for example changing the fan curves or colours.

wow thanks for the quick reply, it's the wifi/bluetooth adapter connect with USB port, when I disconnect it wifi will work, but bluetooth are dead, and sleep work fine, when I reconnect the instant wake problem shows.

7 hours ago, chewgoji said:

wow thanks for the quick reply, it's the wifi/bluetooth adapter connect with USB port, when I disconnect it wifi will work, but bluetooth are dead, and sleep work fine, when I reconnect the instant wake problem shows.

Ah I see so it’s not a Corsair aio?

what is the model of combo card?

if it’s a older Broadcom one then use this to fix the problem.

https://github.com/acidanthera/BrcmPatchRAM

Instructions are on the github on how to use it.

 

 

Hi everyone,
thanks for the guide but it doesn't work for me. I did as it is written in this guide.   I made a new installation and uploaded the latest EFI "clover z390 navi vega 05/04/20", and of course I installed bios setting 12d unlock.

I don't know why the language shows German, during installation I couldn't choose another one.


I have gigabyte z390 pro, i7 9700k, msi rx 5700xt, 16gb ram corsair, ssd 480 sandisk. 

Installationsprotokoll 10-May-2020 new.txt

50C07C82-0657-4119-9A8C-9A8E599EDC40.jpeg

Edited by RDZ
2 minutes ago, eSaF said:

 

You need to carefully read the installation notes and requirements to enable a trouble free install. To change the language, download 'PlistEdit Pro' and open your config.plist with it, go to the NVRAM section (As shown) and change to this value. Good luck.

Screenshot 2020-05-10 at 13.08.21.png


He’s using Clover not OC buddy.

@RDZ Where did you get your macOS installation from?

Download it again from the App Store if possible.

1 minute ago, RDZ said:

@AudioGod
exactly, I'm using Clover. If I need to use OC, I can do it.

 

I have from App Store, USB I did with this tutorial Part3 (i'm using terminal)


It should work in English OTB with Clover,

You sure you didn’t make a mistake somewhere along the line with the installation?

As a test do you get the same result with OpenCore?

@AudioGod

but how could I make a mistake?
I only connected Sandisk 480 disk, USB (Installation) keyboard and mouse.
USB connects automatically, setup Catalin installation. I wait, then formats the ASFT disk, I choose the installation. I wait 10 minutes, the computer resets. Then give installation from disk (the second option on the right). Then it loads, and I have an error. 

 

I will check the OC version now

Edited by RDZ
9 minutes ago, RDZ said:

@AudioGod

but how could I make a mistake?
I connected to the motherboard I only connected a Sandisk 480 disk, USB (Installation) keyboard and mouse.
USB connects automatically, setup Catalin installation. I wait, then formats the ASFT disk, I choose the installation. I wait 10 minutes, the computer resets. Then give installation from disk (the second option on the right). Then it loads, and I have an error. 

 

I will check the OC version now



I will double check on my end with a clover instal key as soon as I get a chance pal and let you know.

 

TBH though if it was a universal problem i would be flooded with reports of it and as I’m not and your the first person ever to say this then of course I’m going to look towards you as where the fault lies. Like I said though I will double check on my end to be sure as I use OpenCore full time myself now but do many installations using clover too for other people.

 

Update, No issue here what so ever with clover. Did you set the wrong country before the instal by any chance?

i can’t think what else it could possibly be.

Edited by AudioGod

I understand, I asked the question because maybe I did something wrong, but I specifically wrote how I did it.


I just didn't have a language choice, I don't know why. I live in Germany but it doesn't matter, right?


I'm checking OC versions now and here I also have no choice of language, but in OC I have it 

FDEA1121-B772-4F9F-A0F5-89A53C5F51DC.jpeg

0FE52C2E-B166-4F18-B619-1AFDBEA523BD.jpeg

0C2E41A8-53AA-49AD-AE68-A0ABFCEFA85E.jpeg

F21212C5-EDC4-47EC-842B-5D88F5DC03BA.jpeg

Edited by RDZ

One of the first things you set during the instal is your country, it auto sets it for you if it can but still gives you the choice.

maybe you missed this page?

 

by the way if you download it from the German App Store and your system is in Germany then it will default to that, this has nothing to do with the Efi that’s just the way it is.

 

Edited by AudioGod

so with the first USB stick, I had the same problem with OC and Clover. 
with the second usb stick, with OC I got such an error, and now I'm checking Clover.

 

I have OC 19.1 version, is good ? 

 

96B3B0A7-C825-4160-838B-CDDE8406514F.jpeg

Edited by RDZ
2 minutes ago, RDZ said:

so with the first USB stick, I had the same problem with OC and Clover. 
with the second usb stick, with OC I got such an error, and now I'm checking Clover.

 

I have OC 19.1 version, is good ? 

96B3B0A7-C825-4160-838B-CDDE8406514F.jpeg


All version of Oc are good.

this is no problem

all you have to do is remove all power from the system and then remove the battery from the motherboard for a few minutes and then put it back and load back in my profile and away you go.

this will totally clear out your UEFI from any junk lingering inside it. 
 

Also make sure your adding your sn uuid and mlb to the config.plist.

Edited by AudioGod
1 minute ago, AudioGod said:


All version of Oc are good.

this is no problem

all you have to do is remove all power from the system and then remove the battery from the motherboard for a few minutes and then put it back and load back in my profile and away you go.

this will totally clear out your UEFI from any junk lingering inside it. 
 

Also make sure your adding your sn uuid and mlb to the config.plist.

You could also use the OC ClearNvram option (at least that worked great for me) - but be aware, that this might reset your boot order settings in your Bios.

2 minutes ago, kolutshan said:

You could also use the OC ClearNvram option (at least that worked great for me) - but be aware, that this might reset your boot order settings in your Bios.

 

yes correct but sometimes a battery pull is the only way to be sure to get it totally cleared out.

more so if you have messed with other EFIs in the past.

×
×
  • Create New...