Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ewheat

Cancelled
Apr 21, 2016
7
0
Success! I finally got my MP1,1<2,1 to boot El Capitan! I believe the problem to be the Hynix aftermarket RAM that I was using. I switched to some other OWC RAM I have (2x2GB) and after manual editing the 2 boot.efi's and Platformsupport.plist on the El Cap SSD (previously installed) I can boot! My restart problem was also tied to the Hynix RAM. I read on another forum about someone with the same problem tied back to non-Apple RAM.

I am going to order some more RAM from OWC and will probably try to install to another disk using pikified USB installer (just to see). I would echo the same thing that everyone else on this forum says about checking your RAM! Not just for the amount (12GB) but also for aftermarket qualities that El Capitan doesn't like (not sure what they are). I put some Hynix back in and El Capitan wouldn't even recognize them.

A big Thank You to everyone who figured all of this out and to all the help I've gotten from the users on this forum. Resources like this are an invaluable tool and have given me a renewed appreciation for the wealth of knowledge contained in the collective minds of this world.
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Yes and nothing... I tryed reinstal El Capian today - nothing. But - and it is interesting - i used Parallels Desktop for install El Capitan on real external disk and it is functional method. You doesn't need another mac with El Capitan for it (!). Maybe it is a new method instalation for this forum.
Hi, I think I have seen reference to using Parallels somewhere but still useful info. My guess is it may be a hardware issue as 2 installs have given the same result. The list of things in the link included resetting printing - no idea what this would do but worth trying. I assume your Mac slept before? Can you boot into earlier OS to test? Another guy had a problem with not being able to restart that was caused by bad RAM.
 

ManMor

macrumors newbie
Dec 29, 2015
19
2
Yes, I have 10.8.4 and 10.5.8 on secundary discs aned they haven't problem with sleep mode.
 

Andreaux

macrumors member
May 8, 2016
52
7
Hi there,

How can I tell if SIP is really disabled? I am unfortunately unable to boot into the Recovery partition (I don't know why), but I tried booting the installer disk and issued the csrutil disable command...
Now if I boot normally and issue a csrutil status command, I get this:

bash-3.2# csrutil status

System Integrity Protection status: enabled (Custom Configuration).

Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Is this how it's supposed to look like?

Any advice welcome.

Cheers,

Andreaux
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Hi there,

How can I tell if SIP is really disabled? I am unfortunately unable to boot into the Recovery partition (I don't know why), but I tried booting the installer disk and issued the csrutil disable command...
Now if I boot normally and issue a csrutil status command, I get this:

bash-3.2# csrutil status

System Integrity Protection status: enabled (Custom Configuration).

Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Is this how it's supposed to look like?

Any advice welcome.

Cheers,

Andreaux
Did you use Boot64 or similar after installing El Cap? I wondered if that may have created the "custom" state?
 

ManMor

macrumors newbie
Dec 29, 2015
19
2
Now I have installation of Yosemite and to similar problem with sleep. I don't know. Maybe firmware upgrade - what do you think? 10.8 and 10.5 OK.
 

ManMor

macrumors newbie
Dec 29, 2015
19
2
No - no from menu, no from start button
[doublepost=1462754723][/doublepost]Firstly, i wanted repair "prevention" from "pmset -g assertions", but when is "clean" problem is stiil here.
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
(Reset SMC) Shutdown computer, UNPLUG from wall, wait 30 seconds, power back up,

Before the grey screen appears, press the Command, Option, P, and R keys at the same time

to reset PRAM. Cross fingers........may have to do this MORE than once. I have.

Now do you have the MacPro 1,1 --> 2,1 Flash upgrade?
 

ManMor

macrumors newbie
Dec 29, 2015
19
2
Název modelu: Mac Pro
Identifikátor modelu: MacPro1,1
Název procesoru: Dual-Core Intel Xeon
Rychlost procesoru: 2,66 GHz
Počet procesorů: 2
Celkový počet jader: 4
L2 mezipaměť (na procesor): 4 MB
Paměť: 12 GB
Rychlost sběrnice: 1,33 GHz
Verze Boot ROM: MP11.005C.B08
Verze SMC (systém): 1.7f10

OSX 10.11.4
OSX 10.10.5

OSX 10.8.4
OSX 10.5.8
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
Název modelu: Mac Pro
Identifikátor modelu: MacPro1,1
Název procesoru: Dual-Core Intel Xeon
Rychlost procesoru: 2,66 GHz
Počet procesorů: 2
Celkový počet jader: 4
L2 mezipaměť (na procesor): 4 MB
Paměť: 12 GB
Rychlost sběrnice: 1,33 GHz
Verze Boot ROM: MP11.005C.B08
Verze SMC (systém): 1.7f10

OSX 10.11.4
OSX 10.10.5

OSX 10.8.4
OSX 10.5.8

Check that you have no internet sharing running, no printer "paused" . I do not remember that the 2,1 Firmware had
anything to do with sleep, just Quad-intel and maybe USB booting.
 

UberDuper

macrumors newbie
Jan 20, 2008
6
0
I just put El Capi on my 2006 mac pro. Had the same sleep issue. Pulling the 7300GT out seems to have solved the sleep issue. Conveniently also solves the phantom display and pegged cores when the screensaver kicked on.
Is there no longer a kext for the 7300GT? I didn't check before I yanked it.
 

Andreaux

macrumors member
May 8, 2016
52
7
Did you use Boot64 or similar after installing El Cap? I wondered if that may have created the "custom" state?

No. The only non-standard thing is that I cannot boot into Recovery OS to set this, but managed to set it (at least it seemed to be so) from the Installer disk. Although it may have not entirely disabled it...

I since then upgraded to 10.11.4 without any hickups... and also installed Pike's CaptainPike daemon successfully that should take care of boot.efi changes (if any ever)...

Though still can't boot into Recovery OS... Am I supposed to do something special to be able to?
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
I think CaptainPike works in a similar way to Boot64 so may be causing the "custom" status. My understanding is that SIP is disabled on the boot.efi files so they can be replaced automatically if / when the OS update tries to change them. There are ways to be able to boot into recovery - look for posts by rthpjm - but as others have noted, it doesn't matter that much as you probably have an earlier OS you can boot into to make any changes to things such as boot.efi files.
 

Andreaux

macrumors member
May 8, 2016
52
7
There are ways to be able to boot into recovery - look for posts by rthpjm - but as others have noted, it doesn't matter that much as you probably have an earlier OS you can boot into to make any changes to things such as boot.efi files.

I tried to overwrite boot.efi from 10.7.5 and it threw some unknown error and did not do it. I have the impression that there is some additional attribute to the files when created with 10.11 and with SIP enabled that causes 10.7.5 to throw an error.

Also, I have a GPU that is EFI64-only (Apple NVIDIA GT120 if I remember well) and I have no boot screen until GUI startup... may that be the cause?
 

Andreaux

macrumors member
May 8, 2016
52
7
GT 120 shouldn't be a problem. It just doesn't have 32bit EFI so no boot screen, as you said.

I thought I am missing something that should be displayed... By the way, what happens when I press Command-R at boot and there is 2 Recovery OS partitions? I thought that at least one should boot, but neither 10.7.5, nor 10.11.4 recovery partitions boot :(
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.