Contribute
Register

BoomR's “Power UP” for 360/VR Production Build: GA-Z370 AORUS UG - i7 8700K - GA AORUS RX580

Status
Not open for further replies.
Update for 10.13.4: On Sunday afternoon, I popped in a spare Corsair Force3 SSD, used the latest UniBeast to create a new UB install key for 10.13.4. I did a fresh install following the same steps - it went pretty much without a hitch. However, when following the same steps for audio that were successful for 10.13.3, I can confirm that the the same steps do not work when doing a fresh install of 10.13.4 (and probably break if/when you update from 10.13.3 > 10.13.4). So there must be some significant change in how audio is addressed between the 2 builds.

If anyone following the thread *has* had success under 10.13.4, I'm sure we all would really appreciate it if you could provide some detailed steps that got you over the audio finish line. On this build for me, getting onboard audio is not a huge deal-breaker, as I have my old OWC Thunderbolt2 dock that supports USB audio, and use that as my primary audio source (using Akitio TB3>TB2 adapter). BUT, it would make this a much nicer post if we could include getting onboard audio to work for 10.13.4.

Thanks in advance for any enlightenment!
--B

Thanks @BoomR for your guide, I bought almost the same components and everything is working perfect with 10.13.4, the machine is rock solid!!. Hope to get the internal audio and h.264 rendering fixed someday.

PS: Did you manage to get your boot drive with APFS working?
 
Thanks @BoomR for your guide, I bought almost the same components and everything is working perfect with 10.13.4, the machine is rock solid!!. Hope to get the internal audio and h.264 rendering fixed someday.

PS: Did you manage to get your boot drive with APFS working?
Yes...both my original m.2 drive and the Corsair SSD are APFS. When I booted up using my UniBeast USB key, I first ran Disk Utility to wipe out the SSD. It only gave me option for APFS to format. So right away, evidently it was able to do the conversion before I started....??
 
Last edited:
BoomR, If you lose your audio, run MultiBeast and just select the ALCxxxx codec, then install. After the install and before rebooting, run the Terminal command:
Code:
sudo touch /System/Library/Extensions/
Then, reboot.

That should do it. Sometimes "Fruitcake happens" when updating.:lol:
 
BoomR, If you lose your audio, run MultiBeast and just select the ALCxxxx codec, then install. After the install and before rebooting, run the Terminal command:
Code:
sudo touch /System/Library/Extensions/
Then, reboot.

That should do it. Sometimes "Fruitcake happens" when updating.:lol:
Seeing that I'm sort of a fruitcake to begin with, that would totally make sense. Just to clarify with you:
Should I follow the original steps as detailed in my OP that got audio working in 10.13.3, but then run your terminal command?
...or should I simply select the codec from MB and forego the other steps?

TIA!
--B
 
BoomR,
The latter - just the audio codec and run the 'touch' command. Don't need to do a full MB v10.2 configuration load if you used it for 10.13.3 (or earlier).

However, check the Download > Kexts for updated versions of what's in /Library/Extensions. If you find newer versions, put the new kexts on your Desktop (make sure these kexts are the only kexts on your Desktop) and run KextBeast. Reboot. Finally, Trash the Desktop kexts.

You should be good to go! :thumbup:
 
Last edited:
BoomR,
The latter - just the audio codec and run the 'touch' command. Don't need to do a full MB v10.2 configuration load if you used it for 10.13.3 (or earlier).

However, check the Download > Kexts for updated versions of what's in /Library/Extensions. If you find newer versions, put the new kexts on your Desktop (make sure these kexts are the only kexts on your Desktop) and run KextBeast. Reboot. Finally, Trash the Desktop kexts.

You should be good to go! :thumbup:
I just wiped my Corsair SSD and also (under Win10) deleted all partitions as well, so the drive is basically factory fresh. Ran my 10.13.4 UB installer, and writing to you from the fresh install. I also ran MB (latest), and this is the only thing I selected for audio:
Screen Shot 2018-05-01 at 5.29.51 PM.png
--No 100/200/300 Series option
--No 200/300 Series/X299 option
Will run the "touch" command and report back shortly!! :headbang:
 
Firstly - BoomR thanks for this thread and your guide to getting this system setup. I’ve varied with the gaming 7 motherboard and a 1080Ti Card as I rely heavily on CUDA for work, but very happy with how things have turned out having moved from an old sky lake hack which was starting to struggle.

Like several others it took me a while to get the thunderbolt 3 cars working in OSX until I changed the PCI slots config. However after working perfectly for a week or more I turned the machine on the other morning to find only one of the Tb3 ports is now recognising ANY Device (They all work on port 1 nothing on port 2) I should add this is under both windows and OS X - and initially both worked without issue.

Has anyone else experienced anything like this do you think it’s a hardware fault with the card? It’s odd for this to happen when there has been no change to the config and it was working perfectly - but very frustrating as the absolute key must for this build was thunderbolt 3!!

Thanks again
 
Status
Not open for further replies.
Back
Top