Jump to content
5539 posts in this topic

Recommended Posts

Clearing NVRAM is fine for 99% of things. And you really should do it every time you make any change to your EFI. It's basically a reboot. Not that big of a deal.

 

You really don't need to reset your BIOS for these things.

Hi, i just fix my problem of my radeon VII by disabling audio and used a DAC, ( https://www.tonymacx86.com/threads/radeon-vii-repeated-kps-10-14-6.281254/ ) ( https://www.tonymacx86.com/threads/radeon-vii-and-new-amd-gpus-compatibility.269128/page-45 )
In my log than i posted forward yesterday there is one line about AppleGFXHDA but this kext is not present in my S/L/E. As they said on tony topics to remove it, I tryed to put the AppleHDADisabler.kext to to fix my problem. It seems to be working. No more KP. 
I had ordered two Radeon VII to find the best overclock ( https://docs.google.com/spreadsheets/d/1Iim9e_ejX3nkgxLIZ3vLu1seQ1m0lDTKUhClJpAO-Gk/edit?usp=sharing ). My first one radeon has no problem, but the new gave me the Kp and UC undercontrol. the radeon isn't still overclocked, i am waiting a stable macos. It depends of the radeon VII I suppose. 
Can you tell me if I need to patch SDST my Watercooling using usb for working well  ?

Edited by hansik
9 hours ago, Tiem said:

Clearing NVRAM is fine for 99% of things. And you really should do it every time you make any change to your EFI. It's basically a reboot. Not that big of a deal.

 

You really don't need to reset your BIOS for these things.

When it comes to dropping MA.EFI your completely wrong bud and 9 it of 10 times your going to need to pull the battery or short the pins to bring it too life. Anybody that does it without doing that and gets away with it will down the line get boot failures but nine out of ten times it just won’t boot at all.

this is why I say to do it and I stick to my guns about it.

 

To explain abit more to why without getting all technical about it, MA.EFI and free2000 unlock a section of memory that is reserved and not meant to be used and when you drop the driver again you leave a pile of mess in that reserved area of memory. F11 via clover or a NVRam reset via OC doesn’t clean out the reserved area of memory, there is only two ways to do that properly. 1 is to pull the battery from the mortherboard or 2 is to reflash the bios. Anything else doesn’t clean that area of memory out.

I hope that clears up why I am so instant on the process and makes sense to everybody as to why it need to be done. :) 

Edited by AudioGod
  • Like 3

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

Edited by WizeMan
2 minutes ago, WizeMan said:

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?

30 minutes ago, AudioGod said:

Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?


I do not recall seeing a darkwake argument on the NVRAM Boot Arguments section, mate.

8 minutes ago, AudioGod said:

Add one mate darkwake=8 

Thanks. Will do and post results tomorrow morning or Monday morning.

 

PS shouldn’t this be on the EFI by default? I remember the Clover variants did actually have it.

Edited by WizeMan
  • Like 1
2 hours ago, AudioGod said:

Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?

sorry for quote this msg with my off topic, but looking for any configuration where you can get working a thunderbolt with video setup in this forum, and I don't know if I need thunderbolt in the motherboard or the graphic card.

13 minutes ago, c1ru said:

sorry for quote this msg with my off topic, but looking for any configuration where you can get working a thunderbolt with video setup in this forum, and I don't know if I need thunderbolt in the motherboard or the graphic card.

 

  • Thanks 1
14 hours ago, WizeMan said:

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

 

13 hours ago, AudioGod said:

Add one mate darkwake=8 

 

I added darkwave=8 and it seems to have fixed the issue. Thank you @AudioGod

Proposal: Since this boot argument is by default on the Clover variant I think we should add it by default on the OpenCore one as well.

1 hour ago, WizeMan said:

 

 

I added darkwave=8 and it seems to have fixed the issue. Thank you @AudioGod

Proposal: Since this boot argument is by default on the Clover variant I think we should add it by default on the OpenCore one as well.

Don’t worry I will,

next EFI updates I will make it so :startreck:

  • Like 1
Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?


Where does the 8 come from? There is another thread on this here board which looks into the kernel source code and this seems to show 8 is a non existent value these days. Likely defaults to 0 with this value. 0 has been working well for me.


https://www.insanelymac.com/forum/topic/342002-darkwake-on-macos-catalina-boot-args-darkwake8-darkwake10-are-obsolete/
2 hours ago, Cass67 said:

 


Where does the 8 come from? There is another thread on this here board which looks into the kernel source code and this seems to show 8 is a non existent value these days. Likely defaults to 0 with this value. 0 has been working well for me.


https://www.insanelymac.com/forum/topic/342002-darkwake-on-macos-catalina-boot-args-darkwake8-darkwake10-are-obsolete/

 

If you read back a few posts your see I said use 0 or 8 pal and 8 works perfectly fine, try it yourself and see. Proof is in the pudding no?

If you read back a few posts your see I said use 0 or 8 pal and 8 works perfectly fine, try it yourself and see. Proof is in the pudding no?
Never said it didn't bud. Just asking where 8 came from. In this case 8 seems to = 0

Sent from my LYA-L09 using Tapatalk

1 minute ago, Cass67 said:

Never said it didn't bud. Just asking where 8 came from. In this case 8 seems to = 0

Sent from my LYA-L09 using Tapatalk
 

Yes correct and again why I said use 0 or 8 :thumbsup_anim:

Edited by AudioGod

Darkwake discussed here as well: https://www.tonymacx86.com/threads/darkwake-deciphered.236850/#post-2054010

 

According to source, there is no darkwake=8

 

I've been running with no boot arguments at all and haven't had any sleep issues.

 

What I do have is an issue with attached external drives. The computer will sleep fine but the drives always complain about not being ejected properly.

Edited by pkdesign
6 minutes ago, pkdesign said:

Darkwake discussed here as well: https://www.tonymacx86.com/threads/darkwake-deciphered.236850/#post-2054010

 

According to source, there is no darkwake=8

If you use darkwake 8 it  just acts as darkwake 0, if you use it now and see for yourself then your see.

 

2 minutes ago, pkdesign said:

Your too fast friend. I added to my post.

Keep your hair on breadwin....lol

i know what you meant bud but heads up us Londoners consider that a insult when you tell somebody they are too fast.
 

anyway here this will fix it for you.

 

 

To fix "disk did not eject properly" message use fixUSB.sh   ( Credit to Bernhard Baehr & syscl )  install open terminal:

 

1- Copy and paste :

// command will download the latest fixUSB.sh ( if link does not work, then follow alternative instructions at bottom)

git clone https://github.com/syscl/Fix-usb-sleep

Enter

 

 

2- Copy and paste:

chmod +x ~/Fix-usb-sleep/fixUSB.sh

Enter

 

3- Copy and paste:


cd ./Fix-usb-sleep
./fixusb.sh

  

Enter

Hi @AudioGod

Does the new EFI folder work with Mojave? I'm still having KP reboots related to GPU from time to time but not so frequently as before. and sometimes it reboots instead of shutdown(happened once).

 

Cheers!

Edited by Neblogas
19 hours ago, AudioGod said:

Keep your hair on breadwin....lol

i know what you meant bud but heads up us Londoners consider that a insult when you tell somebody they are too fast.

I've never of that. :) What does it refer too?

 

I will try your USB suggestion and see how it works.

  • Like 1
  • Haha 1
3 hours ago, pkdesign said:

What does it refer too?

What's the one thing you don't want to be fast at it? The one thing most dude's joke over... most girl's LOL over... the one thing you want to last.

 

Get it? ;)

  • Haha 2
×
×
  • Create New...