Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
There have been a couple of presumably importante commits after d8a066f41627cedbe4e466775b4fd7fbd27e0acb. I missed the first one. The second one, e926e92a06912e418e52b01c2e2629bbdaddd537, lacks some identification. Stand by until Pike fixes it.
3dde3ae06519933c9b1bec2a910e59d53a513972
cleared NVRAM prior to first boot. booted into Recovery HD -> csr-active-config present in NVRAM with value “EAAAAA==”. csrutil disable failed. bootroot-active absent in ioreg.
values found in ioreg:
"boot-file-path" = <040448005c0063006f006d002e006100700070006c0065002e007200650063006f0076006500720079002e0062006f006f0074005c0062006f006f0074002e0065006600690000007fff0400>
"boot-file" = <"\com.apple.recovery.boot\prelinkedkernel">
"boot-device-path" = <02010c00d041030a0000000001010600021f03120a0000000000000004012a0003000000e81c410200000000205f1300000000003986379e20a15945a80df01d39e08ecf02027fff0400>
reboot into El Capitan with cleared NVRAM failed (blurry screen & BBOD).
cleared NVRAM prior to first boot. booted into Recovery HD -> csr-active-config present in NVRAM with value “EAAAAA==”. csrutil disable failed. bootroot-active absent in ioreg.
values found in ioreg:
"boot-file-path" = <040448005c0063006f006d002e006100700070006c0065002e007200650063006f0076006500720079002e0062006f006f0074005c0062006f006f0074002e0065006600690000007fff0400>
"boot-file" = <"\com.apple.recovery.boot\prelinkedkernel">
"boot-device-path" = <02010c00d041030a0000000001010600021f03120a0000000000000004012a0003000000e81c410200000000205f1300000000003986379e20a15945a80df01d39e08ecf02027fff0400>
reboot into El Capitan with cleared NVRAM failed (blurry screen & BBOD).
I think the confusion is that the dgwilson site seems to imply perfect function and you guys are diligently working on it, which looks on the surface to mean you aren't done. From my understanding you are just working out the Recovery partition and thus the ability to disable the SIP, yes? The ability to run El Capitan on 1,1 is there, just needs fine tuning.
Yes, that's correct. Apart from the RecoveryHD issue, there's the problem of how to prevent a system update from erasing the custom-made boot.efi. Up to now, the "PikeYoseFix" solved that problem, but now, with SIP in place, that may be much harder to accomplish. Pike has been made aware of the problem. Let's see what he comes up with.
Naturally, there's always the possibility of a hack (such as using SIPUtility temporarily, so that the launch agent will run with the necessary privileges), but Pike won't be a part of that.
cool! no more hang at the blurry screen when attempting to boot El Capitan with cleared NVRAM.
Hi, I am just chiming in with my results and sharing my experience installing El Capitan.
I have a MacPro 1.1 (2006). I had long updated it to 2.1. I had been running Mavericks and then Yosemite.
I used my 2011 MBP and an external drive to install El Capitan GM Candidate (I was part of the public testing so I got to download it from Apple Store). I changed the boot.efi with the same ones I had used for Yosemite while the drive was still attached to the MBP. Tried first to boot from external drive in the MacPro. Success. I moved the external drive (SSD) to the inside of the MacPro. I checked everything and it seemed fine, so I went back and installed yosefix to make sure the files don't get updated by future updates.
The computer is running really well. I did all this using a Mac Edition ATI 5770 as the installed graphics adapter. Since I read it does not support Metal, I managed to get my hands on a flashed MSI Radeon 7950. Boot screen works, Metal works, all runs great and the games run way better than before. I booted in Windows and that was success as well. The Witcher 3 looks so much better than before that it looks like a different game...
NOTE: Since installing the first non-compatible version of OSX on this Mac, I had never been able to use iMessage. It works perfectly with El Capitan, out of the box.
I have a MacPro 1.1 (2006). I had long updated it to 2.1. I had been running Mavericks and then Yosemite.
I used my 2011 MBP and an external drive to install El Capitan GM Candidate (I was part of the public testing so I got to download it from Apple Store). I changed the boot.efi with the same ones I had used for Yosemite while the drive was still attached to the MBP. Tried first to boot from external drive in the MacPro. Success. I moved the external drive (SSD) to the inside of the MacPro. I checked everything and it seemed fine, so I went back and installed yosefix to make sure the files don't get updated by future updates.
The computer is running really well. I did all this using a Mac Edition ATI 5770 as the installed graphics adapter. Since I read it does not support Metal, I managed to get my hands on a flashed MSI Radeon 7950. Boot screen works, Metal works, all runs great and the games run way better than before. I booted in Windows and that was success as well. The Witcher 3 looks so much better than before that it looks like a different game...
NOTE: Since installing the first non-compatible version of OSX on this Mac, I had never been able to use iMessage. It works perfectly with El Capitan, out of the box.
Last edited:
I'm afraid the PikeYoseFix won't work in El Capitan with SIP in place the way it is now. The only thing I can think of for now, once Pike's boot.efi (El Capitan edition) is able to disable SIP from the Recovery HD, is for the user to remember to disable SIP before doing a system update and then re-enabling it after the system update has been installed. With SIP in place, if the user doesn't remember and the system update includes a newer stock boot.efi, Pike's version will be overwritten and the unsupported Mac will fail to boot.
latest commit seems to work just fine. booted both, El Capitan and Recovery HD without any problems. sidenote: some versions of the new boot.efi were booting El Capitan quicker than others. this latest version is one of the fast-booting ones.
Commit a7bab183375a3c52b43643576ffdb09a1ea59a1e (latest one). Did csrutil disable work on the RecoveryHD of the previous commit? Does it work in this newer version?
commit a7bab183375a3c52b43643576ffdb09a1ea59a1e
booted standard & recovery fine. the hardware/platform-UUID reported still looks somewhat invalid to me (and is absent in NVRAM until I boot Yosemite). El Capitan boots with empty NVRAM. tried "csrutil disable" -> failed.
booted standard & recovery fine. the hardware/platform-UUID reported still looks somewhat invalid to me (and is absent in NVRAM until I boot Yosemite). El Capitan boots with empty NVRAM. tried "csrutil disable" -> failed.
5b3de341d8975bcdc388ea558711e9376f966a38
csrutil disable still gives error: failed to modify... needs to be executed from Recovery OS.
As per Pike's request. Unzip and open csrstat in Terminal window (in El Capitan Recovery HD, I suppose). Report the results to Pike.
THNX, peter!
System Integrity Protection status: enabled (0x00000000)
Configuration:
Apple Internal: enabled
Kext Signing Restrictions: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
System Integrity Protection status: enabled (0x00000000)
Configuration:
Apple Internal: enabled
Kext Signing Restrictions: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
It's odd that, in regular Yosemite, I get System Integrity Protection status: enabled (0x00000010)(Apple Internal). Is there an explanation as to why you should get 0x00000000 in El Capitan Recovery HD? I mean, this is hexadecimal, not binary. So, what's behind that change from 0 to 10 (16 in decimal)? In binary, that would be 10000. That would be the fifth byte from the right, wouldn't it?
Last edited:
it seems others are getting the same value as you, peter ->
https://pikeralpha.wordpress.com/2015/09/10/csrstat-c-to-show-csrsip-status/#comments
I ran it on El Capitan's Recovery HD (MacBook Pro 2015).
https://pikeralpha.wordpress.com/2015/09/10/csrstat-c-to-show-csrsip-status/#comments
I ran it on El Capitan's Recovery HD (MacBook Pro 2015).
I've done the procedure. I'm running on El Capitan with my Mac Pro 1.1
But I've have problems with this:
Then, after installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi and repair permissions.
I can copy boot.efi to /System/Library/CoreServices/
But i can't copy the file to /usr/standalone/i386. What can I do?
Thank you very much!
But I've have problems with this:
Then, after installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi and repair permissions.
I can copy boot.efi to /System/Library/CoreServices/
But i can't copy the file to /usr/standalone/i386. What can I do?
Thank you very much!
@Zelegorm
This is a work in progress. When everything is ready, Hennesie2000 or someone else will probably update his excellent Yosemite guide to make this entire process as fool-proof as possible. For now, you'd better study the first message of the 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite. You'll find Hennesie's guide there. Follow it to the letter.
This is a work in progress. When everything is ready, Hennesie2000 or someone else will probably update his excellent Yosemite guide to make this entire process as fool-proof as possible. For now, you'd better study the first message of the 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite. You'll find Hennesie's guide there. Follow it to the letter.