Asus X79 Rampage IV Extreme | Core i7-3930K (Successful)

[MK500]

Which bios are you running and did you generate a new DSDT w/patches? When I first updated I was having issues booting and it was a DSDT issue. I ended up deleting my DSDT then pulling a new one and patching it according to Shilohh's Guide: http://www.tonymacx86.com/dsdt/9233...eme-x79-guide-extract-edit-your-own-dsdt.html (big thanks Shilohh!). I did that with bios 3602, although I ended up updating to 4206 and generating a new one for that. Both work fine. I tried running 4403 but I couldn't OC, etc.

You might also try disabling kernelcache until you get things running solid. I recently added "kernelcache=no" to my boot args just to avoid any issues there. It takes a little longer to boot, but that doesn't bother me since my system is a production machine and stays on all day once I boot it up.

It's worth noting that I don't use Chimera from here, but Chameleon (currently on rev 2263). You can use Chameleon Wizard to update and stay current.

I'm set up pretty much exactly like you; except that I'm using the BIOS and DSDT from the guide. I'm emailing with Shilohh today with linux extracts to try to get a new standard DSDT into the guide based on 4206 (I think). I'm also using Chameleon wizard for newest Chameleon (for iMessages support) and will probably change the guide to reflect this. I always run with kernelcache=no and also -v when I make any changes to my system; and then set things back to normal once I have stability.

Since I don't know if the issue is caused by something else I've installed recently I'm just going to do a clean build of 10.8.5 with BIOS 4206 and a new DSDT. The guide needs updating anyway, so I'll hopefully get everything straightened out

 

[shilohh]

I too am using the most current version of chameleon. I also use champlist to generate my smbios.plist with unique serial number and uuid. I also update fake smc regularly using the HWMonitors installer packages regularly updated by kozlek.

 

[kundica]

It sounds like the three of us have our systems configured almost identically.

I'm experiencing a complication I wasn't having before... maybe you guys could shed some light on. My hot swapping for sata drives isn't working as in the past. For example, I have a removable drive bay connected to my intel controller that I use as an archive. Before, I could insert drives, eject them, and add a new drive without rebooting, no problem. Currently, I can only add a drive and eject it, but when I add a new drive, it isn't recognized. My bios is set to hot plug for that drive, but it doesn't seem to work like before. At one point I thought I might've made a DSDT edit before that I'm forgetting to make this time, but I compared my DSDTs and they're identical in the hard drive controller section. I've tried updating my AHCI 3rdParty Kext, and also using the eSATA version instead, but no luck.

 

[shilohh]

It sounds like the three of us have our systems configured almost identically.

I'm experiencing a complication I wasn't having before... maybe you guys could shed some light on. My hot swapping for sata drives isn't working as in the past. For example, I have a removable drive bay connected to my intel controller that I use as an archive. Before, I could insert drives, eject them, and add a new drive without rebooting, no problem. Currently, I can only add a drive and eject it, but when I add a new drive, it isn't recognized. My bios is set to hot plug for that drive, but it doesn't seem to work like before. At one point I thought I might've made a DSDT edit before that I'm forgetting to make this time, but I compared my DSDTs and they're identical in the hard drive controller section. I've tried updating my AHCI 3rdParty Kext, and also using the eSATA version instead, but no luck.

I do the same in bios for hot swap by machine has always worked this way. If bay is empty, it auto mounts a new drive. Once ejected, must remount from disk utility or log out and back in. If you put a different drive you can still mount from disk util but will show info from last drive. This may be able to be corrected by faking a different ejectable device in dsdt but OSX doesn't allow for sata hot swap even esata as the have no esata hardware to add support for

 

[kundica]

I do the same in bios for hot swap by machine has always worked this way. If bay is empty, it auto mounts a new drive. Once ejected, must remount from disk utility or log out and back in. If you put a different drive you can still mount from disk util but will show info from last drive. This may be able to be corrected by faking a different ejectable device in dsdt but OSX doesn't allow for sata hot swap even esata as the have no esata hardware to add support for

Hmm... Perhaps it never worked the way I thought. Thanks for the note.

 

[tubaguy50035]

Maybe I'm running into the same issue. I just downloaded the Mountain Lion installer from the app store yesterday and followed the steps listed here. I do this at boot:

-v cpus=1 npci=0x2000 PCIRootUID=0

I am running a GTX580 and I get to a white background with a spinning beach ball. It never advances past that.

If I just downloaded the installer yesterday, would it have been 10.8.5? Sorry if this is poorly worded and/or noobish, new to this.

 

[shilohh]

Maybe I'm running into the same issue. I just downloaded the Mountain Lion installer from the app store yesterday and followed the steps listed here. I do this at boot:

-v cpus=1 npci=0x2000 PCIRootUID=0

I am running a GTX580 and I get to a white background with a spinning beach ball. It never advances past that.

If I just downloaded the installer yesterday, would it have been 10.8.5? Sorry if this is poorly worded and/or noobish, new to this.

There should be code displayed on your screen when your boot process freezes. Could you please snap a clear readable picture of it an post it. In the meantime you can try without pcirootuid=0 and you can try GraphicsEnabler=No. My 580 works with or without graphics enabler so I doubt that's the issue but doesn't hurt to try. Also what bios version are you on? What USB port are you plugged into?

 

[MK500]

I do the same in bios for hot swap by machine has always worked this way. If bay is empty, it auto mounts a new drive. Once ejected, must remount from disk utility or log out and back in. If you put a different drive you can still mount from disk util but will show info from last drive. This may be able to be corrected by faking a different ejectable device in dsdt but OSX doesn't allow for sata hot swap even esata as the have no esata hardware to add support for

Hmm... Perhaps it never worked the way I thought. Thanks for the note.

Interesting. I'm going to verify this with my hot-swap bay also once I stabilize my machine...working on the new 10.8.5 guide at the moment.

With 10.8.4 I could have sworn I could eject and re-insert drives as much as I want. But I guess it's possible I wasn't trying different drives on the same port over and over. I was only using BIOS 3602, the "3rd Party eSATA" kext, and Shiloh's DSDT as outlined in the existing build guide.

 

[shilohh]

Interesting. I'm going to verify this with my hot-swap bay also once I stabilize my machine...working on the new 10.8.5 guide at the moment.

With 10.8.4 I could have sworn I could eject and re-insert drives as much as I want. But I guess it's possible I wasn't trying different drives on the same port over and over. I was only using BIOS 3602, the "3rd Party eSATA" kext, and Shiloh's DSDT as outlined in the existing build guide.

I still have a working 10.8.4 install. I'll try the third party esata kext and see if that changes anything

EDIT: So the 3rd Party E-SATA kext doesn't change my SATA hot swap behavior in 10.8.4. Still have to remount using Disk Utility and if I change drives, Disk Utility shows the model and capacity of the 1st drive mounted in that slot but does show the new mounted partions name. However if you "Get Info" on the newly mounted drive it shows the correct capacity. For me, setting hot swap in BIOS has eliminated the need for either of the 3rd party SATA kexts because if I set Hot Swap to disable it shows internal. If I set enable it shows orange ejectable. I thought maybe trying the 3rd Party E-SATA kext would give functionality but I think it's just doing the same as setting the BIOS SATA hot swop option.

 

[shilohh]

Maybe I'm running into the same issue. I just downloaded the Mountain Lion installer from the app store yesterday and followed the steps listed here. I do this at boot:

-v cpus=1 npci=0x2000 PCIRootUID=0

I am running a GTX580 and I get to a white background with a spinning beach ball. It never advances past that.

If I just downloaded the installer yesterday, would it have been 10.8.5? Sorry if this is poorly worded and/or noobish, new to this.

Try adding GraphicsEnabler=No to your list of boot flags