- Joined
- Feb 2, 2019
- Messages
- 125
- Motherboard
- Z390 Designare
- CPU
- i7-9700K
- Graphics
- Vega 56
- Mac
- Mobile Phone
Hi Casey, in the spirit of giving back to your superb build guide, I wrote up a short procedure to run the NZXT liquidctl script automatically at login. Maybe it's a bit too specific and edge-case but please feel free to add it to your guide if you think it's useful.
Configuring the liquidctl script to run on startup (for all users). Copy the liquidctl.sh script to a shared directory and create a short .plist file in /Library/LaunchAgents:
4. Change ownership of the liquidctl.plist file so that root owns it:
5. Check that you've done everything correctly by attempting to load the .plist manually:
If this command returns anything other than a blank line, go back and check your steps.
Done! Now, even if another operating system has messed with your NZXT Kraken, every time you boot back into Mac OS your Kraken will configure itself automatically no matter what settings might try to persist from other operating system instances.
Caveat: the liquidctl.sh script unloads IOUSBHostHIDDevice. This is necessary to avoid [Errno 13] Access denied (insufficient permissions) that you might encounter when running liquidctl commands. However, this can result in temporary disabling/resetting of your USB devices. My Logitech wireless receiver sometimes loses connection with my wireless mouse or keyboard after running the script. Simply unplug and plug back in the unifying receiver. I don't know what happens with other USB devices, but I suspect unplugging and plugging them back in will work to bring them back online.
Configuring the liquidctl script to run on startup (for all users). Copy the liquidctl.sh script to a shared directory and create a short .plist file in /Library/LaunchAgents:
- Copy the liquidctl.sh script to /Users/Shared.
- Create a new liquidctl.plist file in /Library/LaunchAgents.
- Edit the liquidctl.plist file with admin privileges and paste in the example below. Either use vi or a text editor with admin privileges:
sudo vi /Library/LaunchAgents/liquidctl.plist
. Remove the#Explanation:
sections from the example below:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>liquidctl.sh</string> #Explanation: This is a verbose label for your login script. Name it something unique and identifiable. I just named mine the same as the script itself
<key>ProgramArguments</key>
<array>
<string>/Users/Shared/liquidctl.sh</string> #Explanation: This is the absolute path to the liquidctl.sh script
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
4. Change ownership of the liquidctl.plist file so that root owns it:
sudo chown root /Library/LaunchAgents/liquidctl.plist
5. Check that you've done everything correctly by attempting to load the .plist manually:
sudo launchctl load /Library/LaunchAgents/liquidctl.plist
If this command returns anything other than a blank line, go back and check your steps.
Done! Now, even if another operating system has messed with your NZXT Kraken, every time you boot back into Mac OS your Kraken will configure itself automatically no matter what settings might try to persist from other operating system instances.
Caveat: the liquidctl.sh script unloads IOUSBHostHIDDevice. This is necessary to avoid [Errno 13] Access denied (insufficient permissions) that you might encounter when running liquidctl commands. However, this can result in temporary disabling/resetting of your USB devices. My Logitech wireless receiver sometimes loses connection with my wireless mouse or keyboard after running the script. Simply unplug and plug back in the unifying receiver. I don't know what happens with other USB devices, but I suspect unplugging and plugging them back in will work to bring them back online.
Last edited: