Jump to content
5539 posts in this topic

Recommended Posts

59 minutes ago, hansik said:

Ok, for music application . Not for me for a buyer. I will see with him.


I’ve been using RX 580 8GB Pulse with imac19,1 SMBIOS (headless) with OC and haven’t removed the shikigva boot argument. Maybe your green video issue was with the RX 570 for some reason. The only known problem shikigva=80 value Brings with our setup is crippling the video encoding of the application it patches. For example QuickTime.

 

If you don't intend watching DRM content then you can go ahead and remove the shikigva boot argument. If you don’t intent using QuickTime το export / encode videos you can just keep it.

  • Like 1
7 hours ago, AudioGod said:


If your using clover then my DSDTs are wrong for your motherboard, I do not support the ITX version of the Pro board as it’s not the same as the standard version and has a totally different PCB and power delivery.

However, My OpenCore EFI  might work with your setup as it doesn’t rely on a dsdt to function so why not give that a try instead. (Instructions on how to use it are on page one)

 

if you want to use clover then you will need to get a new dsdt created for your motherboard, If that is what you would prefer to do then you can make a request for a dsdt here.

https://www.olarila.com/forum/17-dsdt-patch-requests/

 

 Thank you AudioGod, I'm going to take your advice and try the OpenCore EFI first. *fingers crossed*

  • Like 1
22 minutes ago, pryles2000 said:

Hi Gang.

A million thanks to AudioGod.

I've got this working with one strange issue.

The install is in Russian.

Does someone know where in the config.plist you specify the language?

Appreciate any help.

 

Open the OpenCore Config.plist and Under NVRAM/Add/7C436110-AB2A-4BBB-A880-FE41995C9F82 Change the prev-lang:kbd value to 656E2D55533A30 save and restart then at the bootpicker press space and then select clear NVRAM.

The system will restart and then the installer will the in English from then onwards. :thumbsup_anim:

Edited by AudioGod
26 minutes ago, AudioGod said:

 

Open the OpenCore Config.plist and Under NVRAM/Add/7C436110-AB2A-4BBB-A880-FE41995C9F82 Change the prev-lang:kbd to 656E2D55533A30 save and restart then at the bootpicker press space and then select clear NVRAM.

The system will restart and then the installer will the in English from then onwards. :thumbsup_anim:

Hi AudioGod.

You sure about that new number?

When I paste it in I get an invalid number error.

Thats hex yes. Are there dashes in it I should use?
 

  • Confused 1
21 minutes ago, pryles2000 said:

Hi AudioGod.

You sure about that new number?

When I paste it in I get an invalid number error.

Thats hex yes. Are there dashes in it I should use?
 

 

Of course I'm sure... What do you think I guessed it or something? :hysterical:

 

656E2D55533A30

 

Type it in instead of using copy and paste you lazy boy...lol

Edited by AudioGod
8 minutes ago, AudioGod said:

 

Of course I'm sure... What do you think I guessed it or something? :hysterical:

 

656E2D55533A30

 

Type it in instead of using copy and paste you lazy boy...lol

No insult intended Sir. Appreciate all your help. That worked. Again......many thanks.

 

  • Like 1
5 hours ago, pryles2000 said:

Hi AudioGod.

You sure about that new number?

When I paste it in I get an invalid number error.

Thats hex yes. Are there dashes in it I should use?
 

Use Plist Editor Pro not Xcode. Save yourself a TON of grief.

 

https://www.fatcatsoftware.com/plisteditpro/

  • Like 1
  • Haha 1

I got this one on the last beta too. Let’s see if anyone else comes across this.

 

Rebooting and selecting the installer completes the process if anyone gets hit by it

2F433E0B-AC4F-4899-AA89-DFFD5571FAC7.jpeg

10 hours ago, Tiem said:

I got this one on the last beta too. Let’s see if anyone else comes across this.

 

Rebooting and selecting the installer completes the process if anyone gets hit by it

2F433E0B-AC4F-4899-AA89-DFFD5571FAC7.jpeg

Installed without a hitch for me on two builds. (0.5.8 & 0.5.9)

Edited by AudioGod
On 5/26/2020 at 12:07 AM, pryles2000 said:

Hi Gang.

A million thanks to AudioGod.

I've got this working with one strange issue.

The install is in Russian.

Does someone know where in the config.plist you specify the language?

Appreciate any help.

 

I also have to thank AudioGod.

I researched for two months about components for this build. I bought mostly the same stuff. And it worked like a charm but with a few quirks...

 

And ONE OF THEM WAS THE RUSSIAN INSTALLER :-D

 

But it was easy to solve. Didn't need to touch any nvram variables. You just need to do this:

 

"Choose the third menu from the left, which is labeled File when in English, and pick the first option, which is labeled Change Language in English. You should be able to select the language you want."

You have to choose the options from the top menu. Third from the left, and choose the first option It will take some time to reload things. And then the language selection screen will appear.

 

 

 

 

Hi Audiogod and other thread users, I updated to your latest clover EFI (which i tested works), updated to 10.15.5 and now I'm stuck on a boot loop with an early panic (IOAHCIFamily and AppleAHCIPOrt in backtrace, see screen photo below).

 

The only thing notable is that the update messed up my UEFI settings (started to boot on a non-working windows EFI option instead of clover), but with F12 I selected clover and then the MacOS Install to finish the install (I now fixed the boot order in the bios).

 

Thanks for any help ! 

 

IMG_9167.jpg

Edited by Pieroman

EDIT : So the panic goes away if I deactivate SATA in the BIOS (my macOS install is on an NVMe drive)... but that's not really a solution !

 

I seem to have the exact same error when I boot with the OC folder... I'm starting to think the update was botched. Any ideas before I reinstall ?

 

Edited by Pieroman
27 minutes ago, Pieroman said:

EDIT : So the panic goes away if I deactivate SATA in the BIOS (my macOS install is on an NVMe drive)... but that's not really a solution !

 

I seem to have the exact same error when I boot with the OC folder... I'm starting to think the update was botched. Any ideas before I reinstall ?

 


No problems that i know of with the EFIs or 10.15.5 so I would say it’s something within your system.

have you tried repairing your disk? (Clear cache and rebuild permissions nvram clear?)

 

Edited by AudioGod
Just now, AudioGod said:


No problems that i know of with the EFIs or 10.15.5 so I would say it’s something within your system.

have you tried repairing your disk? (Clear cache and rebuild permissions?)

 

Yes, I even reinstalled the latest Catalina (not a clean install though) before discovering the SATA issue... Could this be related to my NVMe model (WD Black SN750) ?

Scratch that, I didn't do a proper kextcache rebuild, just the permissions. THe kextcache rebuild has issues with AppleAHCI. Here is the output from kextcache :

Kext with invalid signature (-67030) allowed: <OSKext 0x7fcc915061d0 [0x7fff8d0a2b60]> { URL = "file:///Library/Extensions/AppleAHCIPortHotplug.kext/", ID = "com.apple.driver.AppleAHCIPort" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fcca78ff1a0 [0x7fff8d0a2b60]> { URL = "file:///Library/Extensions/AppleAHCIPortHotplug.kext/", ID = "com.apple.driver.AppleAHCIPort" }

 

7 minutes ago, Pieroman said:

Scratch that, I didn't do a proper kextcache rebuild, just the permissions. THe kextcache rebuild has issues with AppleAHCI. Here is the output from kextcache :


Kext with invalid signature (-67030) allowed: <OSKext 0x7fcc915061d0 [0x7fff8d0a2b60]> { URL = "file:///Library/Extensions/AppleAHCIPortHotplug.kext/", ID = "com.apple.driver.AppleAHCIPort" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fcca78ff1a0 [0x7fff8d0a2b60]> { URL = "file:///Library/Extensions/AppleAHCIPortHotplug.kext/", ID = "com.apple.driver.AppleAHCIPort" }

 

Well this gave the solution away... I believe that one day I somehow mis-clicked on an hackintool thing that installed "AppleAHCIPortHotplug.kext"... and this bites me back now with the update because a kextcache rebuild probably happened. Removed the extension, rebuilt and I'm back !

  • Like 1
×
×
  • Create New...