***Preface: Booting a Yosemite install on a single SSD; have a separate srive completely I'll be attempting to boot Windows from soon**
So, some other general things about my install, in case anyone with the exact same setup as the me (and I think the OP?) has.,.
1. Updated to UEFI; see above. In retrospect, best to remove card readers (can include printers!); this can cause some Ebios boot read error 0x31 thingy to display that's annoying during restarts (solved by leaving legacy booting to 'auto' and forcing those readers to be 'floppy disks' in UEFI
2. I have graphics enabler set to yes, with duckweed, 4 ports, and atirom settings checked in my symbols (chameleon was my boot loader). Yes, with the whole DVI monitor issue with the Radeon 6850/6870 cards, one monitor or mirroring seemed to be the only problem but I had acceleration. Through trial and error, I found if I plugged a DVI AND HDMI cable in for the same monitor, plus the dvi for my other, I got two monitors working after finicking around with my monitor button input selects. Never needed to boot or enable onboard graphics manually to get it done; although it does seem odd to have three outs from the comp for two displays.
3. Not sure how technically USB 3.0 should be installed, but I had to install the Multibeast 3.0 kext, restart then delete and replace the entire ISUSBFamily.kext from this post -->
http://www.tonymacx86.com/yosemite-...stall-gigabyte-z68x-ud3h-b3-4.html#post892596 to get em enables, recognized, and working.
4. Had to do some fiddling to get the SSD to boot without the unibeast USB loader; turns out some config for the kernel path is already good to go on the latest chameleon release and I had forced it to something... Else? Installed chimera and it worked, now I'm using chameleon again to modify things here and there. Again; no idea what the proper way is, and if I invested into looking into clover that may have saved me time and kept my iMessage active... Did story though.
5. Random: My perm repair always involved some varpolicyd things being set wrong, like 0 instead of 244 or the other way around...? Disabled guest login in user profile settings and seemed to take care of it.
6. No DSDT's or SSDT's in my extra folder. Maybe it would help, or hurt, but apart from investigating some turbo over clocking issues that I think is related to an SSDT, I don't need them atm. Installing the Multibeast SSDT only did bad things to my system so I'm wary of it.
To wrap up, amidst my late night tweak/repair/reset caches/restarts, I've learned:
1. Read a bit more before changing a setting,
2. Never, EVER, get an ATI / AMD card again if For a Mac OS On a hacked machine, and
3. Only ever change one thing at a time even if you think you aren't a newbie anymore
Ugh I need to keep that in mind for life in general as well... Lol