- Joined
- Jul 6, 2010
- Messages
- 2,573
- Motherboard
- Asus Z170M-Plus
- CPU
- i5-6600K
- Graphics
- R9 280
- Mac
- Mobile Phone
Yes, at least in Sierra. Up to El Capitan they'd work without additional "help".
I have a tip and a question concerning the 280X.
I lived without sleep for a long time (actually my Hackintosh is the one wich didn´t get sleep) because whenever I switched the iGPU to boot first, I had this empty display without any monitor showing up in in my system, which was too annoying to cope with.
Resolution: Select "InjectIntel" in Clover, so OSX may detect that there is no display connected to the internal graphics.
Besides the obvious blind boot, nearly everything works fine including sleep.
(Sorry if this has been extensively discussed before but but I had not been able to google the connection between InjectIntel an the systems ability to detect attached displays.)
Unfortunately I had to find out that it´s not everything that works fine:
FCPX will instantly crash with "InjectIntel"=true.
Is there any possibility to get rid of the "virtual" monitor not connected to the internal graphics without InjectIntel?
Or any other tweak to the internal graphics I didn´t find?
The basic error message with wich FCPX crashes is: "CGLSetVirtualScreen failed"
My System:
ASUS Z97-A
Intel i7-4790k
16GB RAM
Saphhire Radeon 280X
10.11.6 with all patches
I tested it in 10.11.6, did´t test it in Sierra...does the inject intel work also for Sierra? did you test this on El Cap?
Spoof device ID to R7 360X. If you're using Sierra, you'll most likely have to use iGPU=Primary.
Additionally, since it's an XFX card, you might have to use a different VBIOS. Most of this is covered in the first post of this thread.