- Sep 21, 2013
- Gigabyte Z390 Designare
- RX 580
- Classic Mac
- Mobile Phone
Dropping into this thread to say hello and thank you. I've got my new i9 9900k based machine up and running, and it appears to be stable! I successfully used unibeast, clover, and the files from the catalina micro-guide in this thread to install MacOS. I even used the migration assistant to restore my user profile, apps and files from a timemachine backup. Magic!
My semi-ancient MOTU828x audio interface is successfully running over thunderbolt 2 (with adapter). I'm not sure this is 100% reliable at the moment, I have three issues:
1- When I came to my desk this morning, the interface had disconnected and I needed to reboot to get MacOS to recognise it. The machine did not sleep overnight, so I'm unsure what caused this to happen.
2- When I installed the fenvi wifi adapter, it seemed to cause the thunderbolt interface to disappear - it wasn't detected under PCI devices in the system report. I reseated the card, checked the BIOS settings and on reboot it was detected again. I'll keep an eye on this.
3- hot plugging the MOTU doesn't work, it seems it must be connected on boot to be detected by MacOS. Maybe there's something in this thread I missed about how to get hotplug running?
Congrats on that. Is that a binned chip? What speed are you running it at and what's the vcore set at?
When you say hot plugging, do you mean power-off/power-on, TB device reconnects (or not)?
If you're using Catalina, I guess all the MOTU drivers, etc. are 64 bit if your DAW is running.
Thunderbolt can be goofy. I'm assuming you're already loading your Clover, patches, kexts, and drivers from the EFI: Go to the top of the build guide and make sure your BIOS settings for Thunderbolt didn't get changed. Also, if you have a "safety EFI" on one of your attached drives, make sure that the right EFI is mounting: After restarting, hammer away at F12 and make sure the right EFI source is loading your setup.
Use only your MOTU device for all i/o. Avoid using built-in audio or aggregate devices.
IME, sleep causes nothing but problems for DAWs and interfaces.
Disable any kind of energy-saving, disk-spindown type of feature. The only exception being maybe letting your monitor go to black after an hour of inactivity.
Gimme a minute and I'll post my BIOS setup. Update: Here ya' go.