Contribute
Register

5960x x99-e ws instant reboot even in -x or -s

Status
Not open for further replies.
Joined
Jul 5, 2015
Messages
114
Motherboard
Asus X99-E WS
CPU
i7-5960X
Graphics
Titan X
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
I am doubting anybody has an answer for this, but wanted to give it a try.

To give some background, 5960x and x99-e ws installs of yosemite are only possible through uni-beast, after which clover can be installed. The issue with direct clover installs is that you get an immediate reboot even if trying to boot using safe mode or single user verbose mode.

Now the big problem. The same is true for el capitan. I have been trying for several months to get to boot into the installer for el capitan with instant reboot using safe mode or single user verbose mode. I can't even read any panics in verbose because I can't get it to hang; it reads through the code too fast to read and reboots. I can easily boot back into yosemite through clover, but not the installer update on clover. I have tried every method out there over the past couple of months, disable sip, put kexts in 10.10 and 10.11 vs Other, tried all of the mac bios. nothing. I have tried clean installs and update method, again all have the same outcome. I have tried with and without nullcpupowermanagement and with and without kernel patching. The fact it is a shared problem with yosemite makes me think it is not fixable without a uni-beast release and clean install.

If there is anyone that has uncovered a solution to this problem on yosemite or el capitan can you help so that I can get the el capitan update going? Heck I'd even appreciate help finding a method to get an install hang successfully in verbose so that I can get a readout of any panics causing the reboot. Thanks!
 
I am doubting anybody has an answer for this, but wanted to give it a try.

To give some background, 5960x and x99-e ws installs of yosemite are only possible through uni-beast, after which clover can be installed. The issue with direct clover installs is that you get an immediate reboot even if trying to boot using safe mode or single user verbose mode.

Now the big problem. The same is true for el capitan. I have been trying for several months to get to boot into the installer for el capitan with instant reboot using safe mode or single user verbose mode. I can't even read any panics in verbose because I can't get it to hang; it reads through the code too fast to read and reboots. I can easily boot back into yosemite through clover, but not the installer update on clover. I have tried every method out there over the past couple of months, disable sip, put kexts in 10.10 and 10.11 vs Other, tried all of the mac bios. nothing. I have tried clean installs and update method, again all have the same outcome. I have tried with and without nullcpupowermanagement and with and without kernel patching. The fact it is a shared problem with yosemite makes me think it is not fixable without a uni-beast release and clean install.

If there is anyone that has uncovered a solution to this problem on yosemite or el capitan can you help so that I can get the el capitan update going? Heck I'd even appreciate help finding a method to get an install hang successfully in verbose so that I can get a readout of any panics causing the reboot. Thanks!

I have the same board and CPU as you. I'm working on this as well.

Right now I'm trying to do a direct upgrade through Clover on an X79 platform and that's not going well either. It'll load half way through, not indicate that the upgrade is progressing (although the boot progress bar loads half way), and then reboot.

/ gx
 
On person had a reboot problem when using only one stick of RAM and putting it in slot #2. So make sure your RAM is in dual channel mode, or if you don't have an even number of sticks, try different slots.

I was able to capture a reboot panic like that with my iPhone by holding down the photo button so it took a stream of 50+ shots, and then after the fact I could pick out the one that had a legible message. It still took about five tries, and the message ended up not being helpful. The problem there was with one of the MultiBeast-installed kexts from Yosemite, but I'm not sure which one -- I removed them all and the problem went away.
 
On person had a reboot problem when using only one stick of RAM and putting it in slot #2. So make sure your RAM is in dual channel mode, or if you don't have an even number of sticks, try different slots.

I was able to capture a reboot panic like that with my iPhone by holding down the photo button so it took a stream of 50+ shots, and then after the fact I could pick out the one that had a legible message. It still took about five tries, and the message ended up not being helpful. The problem there was with one of the MultiBeast-installed kexts from Yosemite, but I'm not sure which one -- I removed them all and the problem went away.

Yeah, I the appropriate RAM sticks in. Thanks for the suggestion though! Even in verbose mode, it reboots too quickly for me to see what the errors are at the end. Frustrating.

/ gx
 
I am doubting anybody has an answer for this, but wanted to give it a try.

To give some background, 5960x and x99-e ws installs of yosemite are only possible through uni-beast, after which clover can be installed. The issue with direct clover installs is that you get an immediate reboot even if trying to boot using safe mode or single user verbose mode.

Now the big problem. The same is true for el capitan. I have been trying for several months to get to boot into the installer for el capitan with instant reboot using safe mode or single user verbose mode. I can't even read any panics in verbose because I can't get it to hang; it reads through the code too fast to read and reboots. I can easily boot back into yosemite through clover, but not the installer update on clover. I have tried every method out there over the past couple of months, disable sip, put kexts in 10.10 and 10.11 vs Other, tried all of the mac bios. nothing. I have tried clean installs and update method, again all have the same outcome. I have tried with and without nullcpupowermanagement and with and without kernel patching. The fact it is a shared problem with yosemite makes me think it is not fixable without a uni-beast release and clean install.

If there is anyone that has uncovered a solution to this problem on yosemite or el capitan can you help so that I can get the el capitan update going? Heck I'd even appreciate help finding a method to get an install hang successfully in verbose so that I can get a readout of any panics causing the reboot. Thanks!
I doubt this helps much as El Cap on X99 is a PITA, but I'll share this anyway in hopes it helps in someway. I've spent hours doing a clean El Cap install which became a real challenge compared to installing the GM... It's up and running finally, I created an installer with "createinstallmedia" and Clover r3272 and had to continually modify the config.plist to get it installed without a KP. I've attached what finally worked...

View attachment config.plist

Screen Shot 2015-10-01 at 12.44.11 AM.png

Luck with it.
 
Just a quick update that I got the install on the X79 system working. Going to try and do so for X99 and report back.

/ gx
 
Gotta wonder why X79 is relevant... lol
 
I doubt this helps much as El Cap on X99 is a PITA, but I'll share this anyway in hopes it helps in someway. I've spent hours doing a clean El Cap install which became a real challenge compared to installing the GM... It's up and running finally, I created an installer with "createinstallmedia" and Clover r3272 and had to continually modify the config.plist to get it installed without a KP. I've attached what finally worked...

View attachment 153016

View attachment 153017

Luck with it.

That's great news. How did you do the kernel patching? Just use Clover's built in Haswell-E patch?

/ gx
 
Ahhh Uni-beast 6.0 has been released :) I have a good feeling that tonight will be my time to get the el capitan installed successfully. I'll let 5960x / x99 owners know how it goes through unibeast. That program seems to be the savior of this issue.
 
That's great news. How did you do the kernel patching? Just use Clover's built in Haswell-E patch?

/ gx
Did no kernel patch and not running Haswell-E patch.
 
Status
Not open for further replies.
Back
Top