Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Thanks for the heads up. I've been running 64bit for a while, so should be OK on that front. Which SMBIOS are you using, iMac19 or iMac Pro?
Because I'm still on Mojave 10.14.4 therefore I set my smbios as Macmini instead of iMac 19.1. It won't cause any side effect to the processor or ram as I use macmini as smbios.

iMac Pros use Intel Xeon Processor not Coffeelake. So for you, you should stay with iMac 19.1 because you're using Intel i9-9900K not Xeon. If you look it up on Apple.com, you'll will find out the iMac Pro's spec
 
Last edited:
Because I'm still on Mojave 10.14.4 therefore I set my smbios as Macmini instead of iMac 19.1. It won't cause any side effect to the processor or ram as I use macmini as smbios.

iMac Pros use Intel Xeon Processor not Coffeelake. So for you, you should stay with iMac 19.1 because you're using Intel i9-9900K not Xeon. If you look it up on Apple.com, you'll will find out the iMac Pro's spec

O you haven't updated your Mojave install?

I know that the iMac Pros use a different platform, but I've seen a few posts in this thread mention switching to iMac Pro1:1 for better performance with audio/video. I think one of the revisions of the original guide even mentions this, though I could be wrong. This is why I'm hoping to get some input from those that work with audio and not just video, about their experiences with either of these SMBIOS and performance. Furthermore, does leaving the IGPU enabled if using iMac19:1 perform better? Or would it be better to turn it off (will Logic crash just like FCPX)? Just a few questions based on what I've been reading across this thread, since I know that status of things can change with new OS updates, kext updates, different config settings etc.
 
O you haven't updated your Mojave install?

I know that the iMac Pros use a different platform, but I've seen a few posts in this thread mention switching to iMac Pro1:1 for better performance with audio/video. I think one of the revisions of the original guide even mentions this, though I could be wrong. This is why I'm hoping to get some input from those that work with audio and not just video, about their experiences with either of these SMBIOS and performance. Furthermore, does leaving the IGPU enabled if using iMac19:1 perform better? Or would it be better to turn it off (will Logic crash just like FCPX)? Just a few questions based on what I've been reading across this thread, since I know that status of things can change with new OS updates, kext updates, different config settings etc.

The funny thing was I really wanted to update to the latest Mojave, but the "Software Update" gave me the only option is to upgrade to Catalina which is the last thing I wanna do.

I just read the info provide by CaseySJ on page 1. He only mentioned that smbios as iMac Pro1,1 may provide the best RENDERING speed. IMO it's a benefit for video editing user, but for music production? I'm not sure about that. At the moment, I am really satisfying with my current setup and OSX, I don't worry about how better the performance is as iMac Pro1,1. 1st, I'm not producing any cinematic or huge project with hundreds or thousands tracks. 2nd, I've been running several projects that contains less than 100 tracks, and I have not been through any crash so far. Lastly, why would I need to change the smbios if I don't have any system problem or crash?

You could give it a try to experiment with two difference smbios. Remember, always backup your system 1st.
 
Last edited:
The funny thing was I really wanted to update to the latest Mojave, but the "Software Update" gave me the only option is to upgrade to Catalina which is the last thing I wanna do.

I just read the info provide by CaseySJ on page 1. He only mentioned that smbios as iMac Pro1,1 may provide the best RENDERING speed. IMO it's a benefit for video editing user, but for music production? I'm not sure about that. At the moment, I am really satisfying with my current setup and OSX, I don't worry about how better the performance is as iMac Pro1,1. 1st, I'm not producing any cinematic or huge project with hundreds or thousands tracks. 2nd, I've been running several projects that contains less than 100 tracks, and I have not been through any crash so far. Last, why would I need to change the smbios if I don't have any system problem or crash?

You could give it a try to experiment with the two difference smbios. Remember, always backup your system 1st.


Thanks for the info! Are you using Logic? Is your IGPU enabled?

Also, regarding the latest Mojave update, this may help:
It's a download link for the 10.14.6 supplemental update from 9/26/2019 :)
 
Hi.
My system works perfectly, but I have a problem: After waking from sleep, the menus of the finder and the dock go very slow and stumble.
If I force to sleep always when returning the same happens.
If I restart the user session everything is correct.
I think it didn't happen to me before.
Has anyone got the same?

very grateful to the forum and teacher Caseysj

tanks to all
 
Last edited:
Stage 1: Boot a working copy of macOS like this:
  • Do you have a bootable backup?
    • If so, please boot from the backup disk.
  • If you do not have a working bootable backup:
    • Reinstall macOS from scratch on a new SSD.
    • You can use a cheap SATA SSD mounted inside a USB 3 enclosure.
    • Then boot the new installation of macOS.
Stage 2: Run Terminal and "cd" to the correct "usr/bin" folder like this:
  • After booting from a working copy of macOS, we are ready to try and remove ACL entries from your /usr/bin folder.
  • Open Terminal.
  • cd to the original (bad) macOS drive.
    • Example:
      • If the original macOS drive is called MacHD then type this:
      • cd /Volumes/macHD/usr/bin
Stage 3: Remove ACL entries:
  • Now that you are in the correct "usr/bin" directory, type this:
    • sudo chmod -N sudo
  • If there are no errors, type this:
    • sudo chmod -N *
Stage 4: Verify result:
  • Now let's make sure ACL entries are gone. Type:
    • ls -l
  • There should not be a "+" sign after the set of file permissions on the left.
  • Here's an example:
    Code:
    -rwxr-xr-x 1 root wheel 70288 Sep 29 13:28 AssetCacheLocatorUtil
    -rwxr-xr-x 1 root wheel 67360 Sep 29 13:28 AssetCacheManagerUtil
    -rwxr-xr-x 1 root wheel 57792 Sep 29 13:28 AssetCacheTetheratorUtil
    -rwxr-xr-x 1 root wheel 31488 Sep 29 13:28 BuildStrings
    -rwxr-xr-x 1 root wheel 31456 Sep 29 13:28 CpMac
  • Note that there is no "+" after "-rwxr-xr-x".
Stage 1: Boot a working copy of macOS like this:
  • Do you have a bootable backup?
    • If so, please boot from the backup disk.
  • If you do not have a working bootable backup:
    • Reinstall macOS from scratch on a new SSD.
    • You can use a cheap SATA SSD mounted inside a USB 3 enclosure.
    • Then boot the new installation of macOS.
Stage 2: Run Terminal and "cd" to the correct "usr/bin" folder like this:
  • After booting from a working copy of macOS, we are ready to try and remove ACL entries from your /usr/bin folder.
  • Open Terminal.
  • cd to the original (bad) macOS drive.
    • Example:
      • If the original macOS drive is called MacHD then type this:
      • cd /Volumes/macHD/usr/bin
Stage 3: Remove ACL entries:
  • Now that you are in the correct "usr/bin" directory, type this:
    • sudo chmod -N sudo
  • If there are no errors, type this:
    • sudo chmod -N *
Stage 4: Verify result:
  • Now let's make sure ACL entries are gone. Type:
    • ls -l
  • There should not be a "+" sign after the set of file permissions on the left.
  • Here's an example:
    Code:
    -rwxr-xr-x 1 root wheel 70288 Sep 29 13:28 AssetCacheLocatorUtil
    -rwxr-xr-x 1 root wheel 67360 Sep 29 13:28 AssetCacheManagerUtil
    -rwxr-xr-x 1 root wheel 57792 Sep 29 13:28 AssetCacheTetheratorUtil
    -rwxr-xr-x 1 root wheel 31488 Sep 29 13:28 BuildStrings
    -rwxr-xr-x 1 root wheel 31456 Sep 29 13:28 CpMac
  • Note that there is no "+" after "-rwxr-xr-x".
Thanks Casey, I'll try that as soon as I can, but it's a little complicated right now. I'll keep you informed
 
I've reported this issue in the forum before. But it has not been fixed yet. My mac freezes randomly.

After a while, the screen returns to the login screen and all applications are terminated. Or freeze all the time until I kill ...

Only the mouse pointer works. I can only turn off the system from the power button.

This behavior happens a lot when I use FCPX. However, it freezes sooner or later when using mac.
This problem persists when I enable IGPU in BIOS or set Vega 64 as primary in BIOS.
Is it related to PlatformID?

I will upload config.plist.
Please help someone. I thank you for reading this.
 

Attachments

  • EFI.zip
    36.8 MB · Views: 193
Thank you for offering to help with this... Please note that I probably misplaced or placed random kexts while trying everything I could from the guide to get back to stability. Here is the latest version of my configs.

Thanks!

View attachment 431797
Let's start with this:
  • Delete the files in the red boxes.
    • When using VirtualSMC, we must delete SMCHelper
    • The other 2 red boxes are duplicate files
  • Screen Shot 2019-10-21 at 4.18.18 AM.png
  • Try the attached config.plist, but copy serial numbers back into SMBIOS and RtVariables. This version adds External Icons Patch in Kernel & Kext Patches.
 

Attachments

  • config.plist
    6.9 KB · Views: 91
Since installing the Catalina update my system appears to be booting quicker, but I'm still having a weird problem with Bluetooth. On starting the computer, Bluetooth will either play up and drop connections or refuse to connect at all. If I delete the Bluetooth preference file and reboot, everything will be fine and will continue that way until I switch off. Next time I boot up I'll have the same problem again.
I have a card similar to the Fenvi with a Broadcom 94360 module, which worked 100% under Mojave
Any ideas anyone?
Following up on this, my system is now behaving itself and I haven't had any bluetooth issues for a couple of days now.
The only thing I changed was the name of my system disc which I'd changed from Mojave to Catalina - I've now switched it back.
I have also noticed what looks like a mistake in the bluetooth preferences file - at the bottom I see the following lines :-
<key>PrefKeyLoggingEnabled</key>
<false/>
<key>UplaodStatus</key>
<integer>2</integer>
<key>UploadStatus
</key>
<integer>2</integer>
</dict>
</plist>

Look at the third line, UplaodStatus? - looks a bit suspect to me

Is this line in everyone else's preference file, or is there something in my system causing this?

Thanks
 
Back
Top