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

[CaseySJ]

Hi @CaseySJ

Long time no issues
Until recently. I know you shouldn't be the first point of call for this however my googling has not uncovered any solutions. My issue is with Liquidctl, once upon a time this was running flawlessly with scripts to start it at boot and set my colours and fan speeds, however, recently I have discovered that I am now getting the below:

lukesummerscales@Lukes-iMac ~ % liquidctl status

ERROR: could not open Gigabyte RGB Fusion 2.0 8297 Controller, possibly due to insufficient permissions

ERROR: could not open NZXT Kraken X (X42, X52, X62 or X72), possibly due to insufficient permissions

lukesummerscales@Lukes-iMac ~ %

I am not sure what has happened here but I am no longer able to control these two devices. Have you seen this before and have others possibly found a solution to this? I don't believe I have made any system changes with OC nor have I changed using any of my original KEXTS other than when updates have been released.

This sounds like an Accessibility denial. Some basic questions:

• Which version of macOS?
• Which version of Liquidctl?
• Have you attempted to update homebrew?

 

[Lukey1979]

This sounds like an Accessibility denial. Some basic questions:

• Which version of macOS?
• Which version of Liquidctl?
• Have you attempted to update homebrew?

Hi @CaseySJ

Im using macOS Monterey 12.5.1 with Liquidctl v1.10.0 (I had the same issue with the previous version and then updated to the current version which produces the same error)
I have also updated Homebrew to the latest version.

 

[MusicMan]

Running Windows is actually a good test. During my experience with faulty memory, Memtest did not help, but Windows would routinely crash. This convinced me that a hardware component was at fault. I had another pair of DIMMs on hand so my first thought was to replacement memory -- and that in fact turned out to be the root cause.

So running Windows is a good idea. If Windows is stable for long periods of time (including idle periods), then there is a reduced chance that hardware is at fault.

I've actually spent a couple weeks running Windows (cumulatively... most sessions are a few hours but some are a few days) and haven't had a single crash.

Edit: I just let Windows run idle for 80 minutes and no crash. Then I realized Sleep was off, so I turned it on and it woke from sleep just fine after 20mins. On macOS it happens consistently after 10-15 minutes (sometimes it goes into sleep, sometimes it just crashes and eventually restarts).

Just for fun, disable all sleep and "energy saver" options in System Preferences and see if that makes any difference. Of course, if you have an external audio interface, don't let your system "save energy" when it is connected and powered on.

(see attached) I actually have them all off already and I do have an external audio interface (just added to signature) but I didn't realize that's something to consider here? Could you explain that to me?

 

[CaseySJ]

Hi @CaseySJ

Im using macOS Monterey 12.5.1 with Liquidctl v1.10.0 (I had the same issue with the previous version and then updated to the current version which produces the same error)
I have also updated Homebrew to the latest version.

I’ll run some tests in the morning on the same version of macOS.

 

[jiffyslot]

I've actually spent a couple weeks running Windows (cumulatively... most sessions are a few hours but some are a few days) and haven't had a single crash.

Edit: I just let Windows run idle for 80 minutes and no crash. Then I realized Sleep was off, so I turned it on and it woke from sleep just fine after 20mins. On macOS it happens consistently after 10-15 minutes (sometimes it goes into sleep, sometimes it just crashes and eventually restarts).


(see attached) I actually have them all off already and I do have an external audio interface (just added to signature) but I didn't realize that's something to consider here? Could you explain that to me?

Sure, depending on the audio device and your various software, there's often the issue of drivers and/or playback engines going bonkers when the device that's connected to them "sleeps" or is otherwise disconnected or shut off. Sometimes there can be issues with iLoks and other dongles getting ejected during sleep. As a Pro Tools user, I never let my machine sleep. It's either On or Off.

 

[zipb]

Read/write speed with Sonnet M2 4x4 with 4 x 2TB Samsung 980 Pro in Raid-0. Using 8 PCIe lanes.

Testing for a client. In Windows, read/write is twice as slow even with 16 lanes?

 

[MusicMan]

@CaseySJ @jiffyslot I'm happy to report that I fixed the issue.

After trying many hardware and Opencore-related fixes, I decided to just watch Activity Monitor until it crashed, and determined that it was the classic mediaanalysis_d issue. Since it takes 6-7mins of idle to kick in, I confused it for a sleep issue. Sneaky!

My fix was to use this, from @ueer3fc on this post:

launchctl unload -w /System/Library/LaunchAgents/com.apple.mediaanalysisd.plist

This unloads the process forever, which will disable facial/object recognition for the videos in your Photos library. Confirmed working even after restarting.

If I update Monterey or to Ventura, what are the odds that process comes back?

Ironically, sometimes the trickiest problems to pin down are those that aren't hackintosh-related, because macOS is the last place I check! (at least in a new build)

 

[jiffyslot]

@CaseySJ @jiffyslot I'm happy to report that I fixed the issue.

After trying many hardware and Opencore-related fixes, I decided to just watch Activity Monitor until it crashed, and determined that it was the classic mediaanalysis_d issue. Since it takes 6-7mins of idle to kick in, I confused it for a sleep issue. Sneaky!

My fix was to use this, from @ueer3fc on this post:

launchctl unload -w /System/Library/LaunchAgents/com.apple.mediaanalysisd.plist

This unloads the process forever, which will disable facial/object recognition for the videos in your Photos library. Confirmed working even after restarting.

If I update Monterey or to Ventura, what are the odds that process comes back?

Ironically, sometimes the trickiest problems to pin down are those that aren't hackintosh-related, because macOS is the last place I check! (at least in a new build)

If you have Monterey-friendly audio device drivers, etc., it's worth a try onto a spare drive. I've been using 12.5.1 (21G83), and I really like it. It's my favorite OS since Sierra. If Ventura proves to be as good, I'll be very pleased. FWIW, I'm running ProTools 2022.7 with the Apollo 8 Quad (Thunderbolt 2), VEP7, Waves v14, and Lightroom 4.4.1. Everything is SSD and M2. HFS+ for samples and media, APFS only for the system. SIP and Filevault is enabled on my stuff. No mediaanalysisd hangs over here. (Daystrom is still Mojave, but no mediaanalysisd hangs, either.

 

[DeBilbao]

Updated to latest version of OpenCore 0.8.4 and the kernel extensions I'm using without any issue.

 

[JingleDjango]

I vague recall someone reporting a problem like this. Not sure about the details, but here's something to consider:

• If you've logged into iCloud, try signing out
• Check your config.plist for the following:

View attachment 554210

• Worst case, try erasing the disk and re-installing macOS. But do not log into iCloud. Check if all System Preferences panes open properly.

Do you mean disable iCloud Drive or log out of my Apple ID altogether? In any case, it seems to make no difference whether I'm logged in or not.

That value is present in my config.plist.

I'd really like to resolve this without starting from scratch if I can because a lot of effort went into getting this system ready for production.