Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
@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.
El Captain is running fine with the instructions from the first post. The only problem is copying boot.efi to /usr/standalone/i386

I could copy boot.efi to /System/Library/CoreServices/ and El Captain is running already
 
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.

I figured it might have been a problem, but I had already installed it after it came to my mind. In any case, however, thank you for pointing that out and confirming my doubt. The only thing I was "hoping" for, was that the boot stage would not have the protection, but I guess it'd be stupid on my behalf to think so. So, for the time being, I guess the way to go would be to update from my MBP and then put the drive back in.
 
Hi every one, I need help ; I was unable to go further than the screen installation of el Capitan GM_Candidat:
my keyboard is not recognized and my touchpad so. I have put the last efi.boot.:
I have a white macbook 2,1 of 2007 no Pro.
thanks advance.
 

Attachments

  • 20150923_134911.jpg
    20150923_134911.jpg
    2.8 MB · Views: 310
  • 20150923_140518(0).jpg
    20150923_140518(0).jpg
    2.4 MB · Views: 223
  • 20150923_134946.jpg
    20150923_134946.jpg
    2 MB · Views: 260
  • 20150923_135018.jpg
    20150923_135018.jpg
    1.9 MB · Views: 223
  • 20150923_135035.jpg
    20150923_135035.jpg
    2.5 MB · Views: 220
  • 20150923_135145.jpg
    20150923_135145.jpg
    2.6 MB · Views: 271
How To do to disable csrutil on macbbok 2,1 of 2007 Pleased ? thanks advance.
I don't know if your machine supports El Capitan or it doesn't. I will assume, just as a hypothesis, that it does. To disable SIP (not carutil as you say), you simply boot to the El Capitan Recovery HD, open Terminal, enter "csrutil disable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. When it does reboot to the regular El Capitan partition, SIP will be disabled. To re-enable it, simply boot to the Recovery HD again, open Terminal, ente "csrutil enable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. Do it and, when it reboots to the regular El Capitan partition, SIP will be enabled.

Edit: Sorry, I hadn't paid due attention to the fact that you were quoting my mention of Pike's request about Clover. If you are booting El Capitan on your presumably unsupported Macbook via Clover, your input would be useful to Pike, but I don't know how you can access the Recovery HD from Clover (supposing there is one). You should probably ask people that use Clover on a regular basis. The farthest I went with such bootloaders was with a version of Chameleon that booted Mavericks.
 
Last edited:
I don't know if your machine supports El Capitan or it doesn't. I will assume, just as a hypothesis, that it does. To disable SIP (not carutil as you say), you simply boot to the El Capitan Recovery HD, open Terminal, enter "csrutil disable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. When it does reboot to the regular El Capitan partition, SIP will be disabled. To re-enable it, simply boot to the Recovery HD again, open Terminal, ente "csrutil enable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. Do it and, when it reboots to the regular El Capitan partition, SIP will be enabled.

Edit: Sorry, I hadn't paid due attention to the fact that you were quoting my mention of Pike's request about Clover. If you are booting El Capitan on your presumably unsupported Macbook via Clover, your input would be useful to Pike, but I don't know how you can access the Recovery HD from Clover (supposing there is one). You should probably ask people that use Clover on a regular basis. The farthest I went with such bootloaders was with a version of Chameleon that booted Mavericks.
I'm not installed clover. I have just unsupported macbook 2,1.
 

Attachments

  • Capture d’écran 2015-09-23 à 20.05.07.png
    Capture d’écran 2015-09-23 à 20.05.07.png
    77.8 KB · Views: 240
  • Capture d’écran 2015-09-23 à 20.05.29.png
    Capture d’écran 2015-09-23 à 20.05.29.png
    67.3 KB · Views: 264
You'll note that this thread is specifically about Mac Pros. There is a separate thread about El Cap on other Macs. The USB issue is well established there.

People with Mac Pros don't have the USB issue so we will be unable to help.
 
As an aside, here's a "quick and dirty" way of installing El Capitan on an old Mac Pro. It's already been tried by others (666sheep was the first, and he can correct me if I am wrong, or he can explain the procedure in more detail):
  • You'll need an unmodified installer for El Capitan
  • You'll also need a genuine Mac that is compatible with El Capitan (a reasonably recent MacBook, iMac, Mac Mini or Mac Pro)
  • You'll also need a copy of Pike's boot.efi
  • You'll also need an HDD or an SSD where El Capitan is going to reside (to be placed inside your old Mac Pro when the whole process is over).
  • Lastly, you MAY need an external USB, FireWire or Thunderbolt enclosure where said HDD or SDD is to reside during this procedure.
  • Copy the installer to the "modern" Mac.
  • Run the installer. Choose the presumably external HDD or SSD as the target for installing El Capitan.
  • Once El Capitan has been installed, search for boot.efi on that HDD or SSD (it's in a couple of folders, identified in Hennesie2000's guide) and erase it (in both places). Copy Pike's boot.efi (in both places) and set permissions as prescribed in Hennesie2000's guide (you'll probably have to run Terminal for this).
  • Eject said HDD or SSD from the "modern" Mac, extract it from its enclosure (if necessary) and place it in one of the old Mac Pro's bays.
  • Boot the old Mac Pro. You'll probably have to use an alternative OS X partition on the old Mac Pro (such as Snow Leopard or Lion, or a DVD installer thereof, or a valid Recovery HD partition) and, once booted, select the disk with El Capitan as the Startup Disk, then reboot.
  • If all has been done correctly, you should get to El Capitan desktop. Enjoy.
Please, notice that for these modern operating systems to work on an old Mac Pro, you'll need a more modern graphics card, not just Pike's boot.efi.

I wanted to thank Peter for this post! I may be a little late to the game so to speak but I got El Capitan installed and working on my 2007 MacPro 1,1 (firmware updated to 2,1) this evening using the procedure above. I have to say having my Mid 2012 rMBP to install El Capitan made doing this so much easier. Once my 500GB SSD was formatted and new OS installed, all I had to do is plug in the drive to one of my bays and start the computer up. Yeah... it was just that easy. Thanks again Peter and to everyone else who was involved for making all of this possible!

21479774299_d3bd9f4f5c_c.jpg
 
Last edited:
@Macdctr
You are welcome. Just remember that Pike's Yosemite boot.efi, although capable of booting El Capitan on an old Mac Pro, is not entirely compatible with it. The one he's been developing these past weeks especially for El Capitan should work much better on the new operating system. It's ALMOST there, but it can't disable SIP yet when booted to the Recovery HD. Another foreseeable problem is that, when SIP is in place, your custom-made boot.efi may be inadvertently replaced by Apple's stock 64-bit version when an update to El Capitan is downloaded. In my note you quoted above, I neglected to mention the so-called PikeYoseFix daemon. Although that has worked flawlessly since before Yosemite (there was a previous version for Tiamo's boot.efi for Mavericks), it won't work on El Capitan, unless you disable SIP first. Good luck and just be careful with system updates.
 
System-id changes.

as far as I can tell, commit 0f76ac85bee944287f7a01866a5f71cb13c7d0bc behaves the same as the version before. " ioreg -lw0 -p IODeviceTree | grep system-id" gives value "00000000000000000000000000000000". El Capitan boots flawless if NVRAM empty. csrutil disable fails. csrutil status -> enabled (Apple Internal).
 
@Macdctr
You are welcome. Just remember that Pike's Yosemite boot.efi, although capable of booting El Capitan on an old Mac Pro, is not entirely compatible with it. The one he's been developing these past weeks especially for El Capitan should work much better on the new operating system. It's ALMOST there, but it can't disable SIP yet when booted to the Recovery HD. Another foreseeable problem is that, when SIP is in place, your custom-made boot.efi may be inadvertently replaced by Apple's stock 64-bit version when an update to El Capitan is downloaded. In my note you quoted above, I neglected to mention the so-called PikeYoseFix daemon. Although that has worked flawlessly since before Yosemite (there was a previous version for Tiamo's boot.efi for Mavericks), it won't work on El Capitan, unless you disable SIP first. Good luck and just be careful with system updates.

I was thinking until a "fix" is in place so we can disable SIP, I can put my SSD into an external enclosure and connect to my rMBP for updates then reinstall the modified boot.efi files again....more work but at least I can continue updating the software in this manner until there's a more permanent fix to this issue :)
 
I was thinking until a "fix" is in place so we can disable SIP, I can put my SSD into an external enclosure and connect to my rMBP for updates then reinstall the modified boot.efi files again....more work but at least I can continue updating the software in this manner until there's a more permanent fix to this issue :)
Sure thing. That should be feasible.
 
Commit a556a2e555bf773886ec312da7af2e3d58ee5946: system boots normal, all tests conducted give the same results as before.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.