Sound is still a no-go, but continuing to work on that. Have not seen a specific sequence of steps to get it to work on this specific board with the new version of MB (which seems to be missing some options from previous versions like rebuild permission, etc..?) I'm also curious about bios revisions. I'm running 1104. Not sure if I should update to the latest/greatest (currently 3009)?
QUICK EDIT: I updated to 1203, up and running fine. Past 1203, Asus requires you to 'convert' the bios to a 'CAP' format. Assuming that is a no-going-back deal so I thought I'd stay put until someone reports in on how newer 'CAP' bios formats work. Latest/Greatest is version 3009.
Hi, I am just reading your thread trying to find the last bit that is missing:
I am on a very similar setup having:
Asus Sabertooth z79 on 3009 Bios (you asked if it works okay)
Gigabyte Nvidia GTX 670 OC2 Card
For the bios, I needed to upgrade to cap version as this it the only one that is capable of handling windows 8. So far it handles my memory with 2133 MHz, the previous version did only allow 1600 Mhz without failures. So for me 3009 solved other problems and I used a modified DSDT for my board with HDMI Audio and everything worked at once. No problems booting up.
One little thing that keeps bugging me is something with the GPU I use in connection with the FakeSMC.kext package.
I installed the MultiBeast (5.2) FakeSMC.kext with the GPUsensor.kext included. I seem to have a problem with the GPUSensors.kext as my machine keeps freezing once I login and OS x loads the istat menu or HWStats tool after login. This seems to be connected to the GPUSensors.kext because if I take it out, it works. istatmenu would not offer the possibility to read the GPU temperature which is okay for me but it seems that you don't have any problems with it running Cinebench.
If I have this plugin installed and run cinebench, the gpusensors.kext seems to collide with rising temperatures and freezes my computer instantly.
Did you see anything like this on your setup as well or is there anything you did to prevent this? In different entries I could find something that points to this faulty(?) extension but I am not sure if it is just it by itself or a collission between two kexts that are not compatible.
Any ideas?