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

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Hi guys, I could do with some tips. I have 10.11.3 installed on my Mac Pro, and just updated to 10.11.4 and I think I've bodged something. Now on the El Capitan drive when I try and boot I just get a circle with a line through it. I also get it on the El Capitan recovery drive. The El Capitan drive also has Windows 7 64bit installed. I still have 10.7.5 in my 4th bay and I have Time Machine backups on my mirrored 2/3 bays.
I've tried using the 10.7.5 recovery drive to restore the El Capitan backup but it won't let me. The original Pikify USB installer I created no longer boots (I've waited over an hour and it doesn't load).
I can't think of a simply way to restore my 10.11.3 install and then I can try it again.
Good news. No need to re-install and restore from backup! You probably just need to find a way to replace the boot.efi files...

Boot from your 10.7.5 disk (normally)

From the Finder you should be able to get to the El Capitan disk/partition (let's assume your El Capitan disk/partition is named 'Macintosh HD' - change to suit your environment)

You are going to need a copy of the Pike boot.efi. You have a few choices:
  1. download a copy from http://piker-alpha.github.io/macosxbootloader/ (into Downloads)
  2. OR using the Finder navigate to the folder where you first downloaded the pikify3.1.v8.zip file and unpacked the pikify3.1 folder, go into the pikify3.1 folder (it will probably be Macintosh HD from the side bar > Users > username > Downloads > pikify3.1)
  3. OR if you had Boot64 installed, using the finder navigate to Macintosh HD > Library > Application Support > Boot64
  4. OR if you had CapitanPikeFix installed, using the Finder navigate to Macintosh HD, then from the Finder's Go menu choose 'Go to Folder...', in the dialogue box that pops open type usr then click the Go button, continue to navigate to standalone > i386
    Screen Shot 2016-03-29 at 13.12.19.png
One of the 4 options above should reveal a boot.efi file.
----- edit ------
Oops, the CapitanPikeFix Pike boot.efi file is named boot.efi.capitan.pike, and the Boot64 files are named boot.efi.grey or boot.efi.black. Copy one of these to your Desktop and rename it to be just boot.efi
----- end edit -----


We are going to copy this file, from the Finder right-click (or CTRL-click) the file and choose Copy 'boot.efi'
Screen Shot 2016-03-29 at 13.10.15.png

Now we will use Finder to navigate to Macintosh HD > System > Library > CoreServices
From the Finder's Edit menu choose Paste Item
Screen Shot 2016-03-29 at 13.22.58.png
You may be asked to to authenticate, and you may need to choose replace.

If this paste fails, we will need to use the terminal (sorry, can't think of another way)
Open a Terminal app from the Applications > Utilities folder
Type the following into the terminal with a space as the last character, but don't press the enter or return key yet
Code:
sudo chflags nouchg
(remember the space on the end) then from the Finder drag the boot.efi file from the CoreServices folder onto the Terminal
the terminal command line should now read
Code:
sudo chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi
Now press the enter or the return key to issue the command.
You will be asked for your password, type it in (don't worry that there is no feedback when typing), then press the Return or Enter key.
Using the Finder, paste the item into the CoreServices folder again....

Now using the Finder, navigate to Macintosh HD, then from the Finder's Go menu select Go to Folder..., in the dialogue box that pops open type usr then click the Go button, continue to navigate to standalone > i386
From the Finder's Edit menu select Paste Item.
Screen Shot 2016-03-29 at 13.17.41.png
You may be asked to to authenticate, and you may need to choose replace.

Using the System Preferences > Startup Disk, select your El Capitan disk and restart....

Don't forget that
Macintosh HD here is my example, change it where necessary to your El Capitan disk partition

In the best traditions of Apple presentations, I made a movie


You can then try to recover your El Capitan Recovery HD see my post at #1607
 
Last edited:

spin498

macrumors member
Nov 24, 2010
42
1
I move around
I've updated to 10.11.4, followed the instructions here and replaced the boot.efi. What happens now is, the system boots to the black screen, my cursor appears in the top left corner and flashes. It continues to loop here. The mouse allows me to move the cursor around, but no login screen appears. Any ideas? Did I miss a step? I've tried the update from apple thru App Store, the combo update download, and both the black efi and the grey one it all produces the same result.
 

mmonse_de

macrumors newbie
Mar 20, 2016
23
7
Wuppertal, Germany
I've updated to 10.11.4, followed the instructions here and replaced the boot.efi. What happens now is, the system boots to the black screen, my cursor appears in the top left corner and flashes. It continues to loop here. The mouse allows me to move the cursor around, but no login screen appears. Any ideas? Did I miss a step? I've tried the update from apple thru App Store, the combo update download, and both the black efi and the grey one it all produces the same result.
Did you replace both boot.efi? Did you protect the one in the "CoreServices" folder after change? (terminal, the nouchg/uchg command)?
Some people say you have to do that with the boot.efi from the recovery partition, too. IDK wether that's useful, I do not have a recovery partition on my systems.
 

spin498

macrumors member
Nov 24, 2010
42
1
I move around
Did you replace both boot.efi? Did you protect the one in the "CoreServices" folder after change? (terminal, the nouchg/uchg command)?
Some people say you have to do that with the boot.efi from the recovery partition, too. IDK wether that's useful, I do not have a recovery partition on my systems.

Tried it, didn't work, thx anyway.
 

LordSpunky

macrumors newbie
Feb 22, 2016
8
0
Good news. No need to re-install and restore from backup! You probably just need to find a way to replace the boot.efi files...

Boot from your 10.7.5 disk (normally)

From the Finder you should be able to get to the El Capitan disk/partition (let's assume your El Capitan disk/partition is named 'Macintosh HD' - change to suit your environment)

You are going to need a copy of the Pike boot.efi. You have a few choices:
  1. download a copy from http://piker-alpha.github.io/macosxbootloader/ (into Downloads)
  2. OR using the Finder navigate to the folder where you first downloaded the pikify3.1.v8.zip file and unpacked the pikify3.1 folder, go into the pikify3.1 folder (it will probably be Macintosh HD from the side bar > Users > username > Downloads > pikify3.1)
  3. OR if you had Boot64 installed, using the finder navigate to Macintosh HD > Library > Application Support > Boot64
  4. OR if you had CapitanPikeFix installed, using the Finder navigate to Macintosh HD, then from the Finder's Go menu choose 'Go to Folder...', in the dialogue box that pops open type usr then click the Go button, continue to navigate to standalone > i386
    View attachment 623703
One of the 4 options above should reveal a boot.efi file.
----- edit ------
Oops, the CapitanPikeFix Pike boot.efi file is named boot.efi.capitan.pike, and the Boot64 files are named boot.efi.grey or boot.efi.black. Copy one of these to your Desktop and rename it to be just boot.efi
----- end edit -----


We are going to copy this file, from the Finder right-click (or CTRL-click) the file and choose Copy 'boot.efi'
View attachment 623702

Now we will use Finder to navigate to Macintosh HD > System > Library > CoreServices
From the Finder's Edit menu choose Paste Item
View attachment 623705
You may be asked to to authenticate, and you may need to choose replace.

If this paste fails, we will need to use the terminal (sorry, can't think of another way)
Open a Terminal app from the Applications > Utilities folder
Type the following into the terminal with a space as the last character, but don't press the enter or return key yet
Code:
sudo chflags nouchg
(remember the space on the end) then from the Finder drag the boot.efi file from the CoreServices folder onto the Terminal
the terminal command line should now read
Code:
sudo chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi
Now press the enter or the return key to issue the command.
You will be asked for your password, type it in (don't worry that there is no feedback when typing), then press the Return or Enter key.
Using the Finder, paste the item into the CoreServices folder again....

Now using the Finder, navigate to Macintosh HD, then from the Finder's Go menu select Go to Folder..., in the dialogue box that pops open type usr then click the Go button, continue to navigate to standalone > i386
From the Finder's Edit menu select Paste Item.
View attachment 623704
You may be asked to to authenticate, and you may need to choose replace.

Using the System Preferences > Startup Disk, select your El Capitan disk and restart....

Don't forget that
Macintosh HD here is my example, change it where necessary to your El Capitan disk partition

In the best traditions of Apple presentations, I made a movie


You can then try to recover your El Capitan Recovery HD see my post at #1607


Thanks very much - that has fixed it. Haven't tried the recovery partition yet. But will do soon.
 

wolf1734

macrumors regular
Nov 9, 2014
147
17
France
Hello rthpjm

I come towards you to know if you can put me a copy of a key usb with the installation of EL Capitan for pimp 2.1, because I do not arrive created my key usb nevertheless I was good your advice(council) and use pikify3.1 but has every time it fail. Thank you beforehand if you can put me it has to download for then I goes(takes) up him(it) or the clone on my USB key thank you has you
 

spin498

macrumors member
Nov 24, 2010
42
1
I move around
Option-Open Apple-P-R ??

Sorry, I don't know what it is you are indicating. Just to be clear, I was able to replace the boot.efi files. the machine will boot but only to the black or grey screen (depending on which boot file, I tried both) the cursor is present but flashing at which point it can be moved around using the mouse. I'm thinking it has something to do with the Nvidia graphics card.
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
Sorry, I don't know what it is you are indicating. Just to be clear, I was able to replace the boot.efi files. the machine will boot but only to the black or grey screen (depending on which boot file, I tried both) the cursor is present but flashing at which point it can be moved around using the mouse. I'm thinking it has something to do with the Nvidia graphics card.


Sorry was in a hurry, have you tried resetting the Parameter Ram at boot-up? What model/version NVidia do you have?
 

spin498

macrumors member
Nov 24, 2010
42
1
I move around
Sorry was in a hurry, have you tried resetting the Parameter Ram at boot-up? What model/version NVidia do you have?

I'm testing the updates out on an external drive. If I reset the Parameter Ram it boots to my internal drive that's running 10.11.3.

It's a Zotac branded GT 740. I installed Nvidia's Web Drivers to see if that makes a difference but it didn't. I'm trying to figure out which file the boot.efi would load right after the mouse drivers since that's where it seems to start looping.
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
I'm testing the updates out on an external drive. If I reset the Parameter Ram it boots to my internal drive that's running 10.11.3.

It's a Zotac branded GT 740. I installed Nvidia's Web Drivers to see if that makes a difference but it didn't. I'm trying to figure out which file the boot.efi would load right after the mouse drivers since that's where it seems to start looping.

Reset PRam then hold down Option(Alt) key and select the ElCapitan drive? Or am I missing something? Will look over old messages.
 

mmonse_de

macrumors newbie
Mar 20, 2016
23
7
Wuppertal, Germany
Sorry, I don't know what it is you are indicating. Just to be clear, I was able to replace the boot.efi files. the machine will boot but only to the black or grey screen (depending on which boot file, I tried both) the cursor is present but flashing at which point it can be moved around using the mouse. I'm thinking it has something to do with the Nvidia graphics card.
I'm not sure that it is a GPU issue. You can see the moving cursor on the screen, so there is some "useful" output to the graphic card. I think it has something to do with the boot.efi files you used. Have you tried to use that file from another source. I had a problem with the update to 11.4 too, when, after reboot, I replaced the boot.efi files with some copies I found on my HD. Machine stuck on boot. I then replaced the efis with the version out of the pikify3.1 folder and then the machine works fine and smooth.
BTW.: in between I updated another MPr1.1 to 10.11.4. It had 10.11.3 running, installed with pikify3.1 v8, I installed the latest version of the Boot64-script and downloaded the 11.4 update from the AppStore. It worked without any problems.
 

spin498

macrumors member
Nov 24, 2010
42
1
I move around
I'm not sure that it is a GPU issue. You can see the moving cursor on the screen, so there is some "useful" output to the graphic card. I think it has something to do with the boot.efi files you used. Have you tried to use that file from another source. I had a problem with the update to 11.4 too, when, after reboot, I replaced the boot.efi files with some copies I found on my HD. Machine stuck on boot. I then replaced the efis with the version out of the pikify3.1 folder and then the machine works fine and smooth.
BTW.: in between I updated another MPr1.1 to 10.11.4. It had 10.11.3 running, installed with pikify3.1 v8, I installed the latest version of the Boot64-script and downloaded the 11.4 update from the AppStore. It worked without any problems.

I've lost track now, I'm pretty sure I've tried every combination of boot.efi that's out there.
Reset PRam then hold down Option(Alt) key and select the ElCapitan drive? Or am I missing something? Will look over old messages.
Reset PRam then hold down Option(Alt) key and select the ElCapitan drive? Or am I missing something? Will look over old messages.

Oh, I think what's missing is the fact that I didn't identify the Graphics card is a PC version, it doesn't display any of the EFI boot screen, I can't see the option of which drive to boot from. I have a cloned version of my system (10.11.3) on an external drive. I do all my updating to the external drive first to make sure it works before updating my OS. When I reset the Pram it defaults to the internal drive with the good OS on it. I have used Startup Disk to set the external drive and that's when it will boot but go into the loop at the loading of the cursor. If I leave it running long enough, say overnight, it will eventually boot from the internal drive.
 
  • Like
Reactions: cdmawolf

R Rieck

macrumors newbie
Apr 2, 2016
1
0
Just wanted to say thank you to all the work that has gone into the utilities to allow the Mac Pro to run the latest versions. Just bought a second hand 2,1 Mac Pro and it runs El Capitan great first time through with the Pikify script..
 

mmonse_de

macrumors newbie
Mar 20, 2016
23
7
Wuppertal, Germany
I've lost track now, I'm pretty sure I've tried every combination of boot.efi that's out there.



Oh, I think what's missing is the fact that I didn't identify the Graphics card is a PC version, it doesn't display any of the EFI boot screen, I can't see the option of which drive to boot from. I have a cloned version of my system (10.11.3) on an external drive. I do all my updating to the external drive first to make sure it works before updating my OS. When I reset the Pram it defaults to the internal drive with the good OS on it. I have used Startup Disk to set the external drive and that's when it will boot but go into the loop at the loading of the cursor. If I leave it running long enough, say overnight, it will eventually boot from the internal drive.

Did you ever had a running ElCapitan with this GPU? I had a little Google session and found out that many Win Nvidia GT 740 are working fine, as long as you don't reboot... So I now assume you're right with your diagnostics, it may be the GPU preventing the OS from booting properly. Many issues also in the "hackintosh" forums, where a BIOS reset is necessary to reboot.
I always had bought used ATI GPUs (4870, 5770 with various RAM), re-flashed for Apple and working fine, inclusive boot screen.
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
I've lost track now, I'm pretty sure I've tried every combination of boot.efi that's out there.



Oh, I think what's missing is the fact that I didn't identify the Graphics card is a PC version, it doesn't display any of the EFI boot screen, I can't see the option of which drive to boot from. I have a cloned version of my system (10.11.3) on an external drive. I do all my updating to the external drive first to make sure it works before updating my OS. When I reset the Pram it defaults to the internal drive with the good OS on it. I have used Startup Disk to set the external drive and that's when it will boot but go into the loop at the loading of the cursor. If I leave it running long enough, say overnight, it will eventually boot from the internal drive.
Hello Spin498

This will probably sound like strange advice, but please try this...

Boot to your black screen with the cursor, then unplug your monitor cable from the graphics card, then re-plug it back in. See if that helps?...

Also, please tell us what cable types you are using, and whether you have tried different cable types (HDMI, display port, DVI, I haven't checked what ports might be on your card...)
 
  • Like
Reactions: cdmawolf

spin498

macrumors member
Nov 24, 2010
42
1
I move around
Hello Spin498

This will probably sound like strange advice, but please try this...

Boot to your black screen with the cursor, then unplug your monitor cable from the graphics card, then re-plug it back in. See if that helps?...

Also, please tell us what cable types you are using, and whether you have tried different cable types (HDMI, display port, DVI, I haven't checked what ports might be on your card...)

I actually just go my hands on a TV with HDMI input, I'm going to use that and see. Right now it's output is from the DVI.
 

joot

macrumors regular
Nov 3, 2006
110
21
OK folks, I got El Capitan 10.11 installed. How do I go about updating it to 10.11.4? Do I have to do anything special to the Boot.efi file in coreservices folder before or after the update?
 

sscjeat

macrumors newbie
Jan 9, 2009
3
0
Just updated my 2006 Mac Pro 1,1 (14GB and flashed Radeon 5770) from 10.11.3 to 10.11.4 using "Boot64" and the procedure in post # 1391 and it worked beautifully. Thanks to all of the smart and generous people in this community.
 

zedoc

macrumors newbie
Jan 26, 2016
3
0
Hi,
Just installed 10.11.4 clean install creating a bootable USB key following post #1390.
everything went fine.
However, latest CUDA driver doesn't seem to work with my 8800GT 1G from Macvidcards.com. (CUDA-Z test failed)
Should i downgrade to an earlier version of CUDA?
 

warrenza

macrumors newbie
Apr 6, 2015
4
1
Richmond, VA
The race is on.

Who's the first to get OS X version 10.11 El Capitan booting perfectly on a 2006/2007 Mac Pro (1,1/2,1)?

UPDATE: Only one day later, 666sheep did it first!

This first post has now been updated with recent summarized information.


Simply looking to download the Piker-Alpha macosxbootloader for El Capitan? Links:
________________________________________________________________

If you have OS X El Capitan up and running on your 2006/2007 Mac Pro with Pike's boot loader, you should consider disabling "Install OS X updates" and "Install system data files and security updates" in System Preferences > App Store so that OS X doesn't automatically install any future updates that may overwrite Pike's boot.efi.
________________________________________________________________

If you find Pike's boot loader valuable in keeping your 2006/2007 Mac up-to-date, please consider simply thanking him via a comment on his blog, as he's done a lot of work without asking for anything in return or benefiting from this project. Thanks Pike!


How can these Macs run El Capitan?

Apple does not support OS X El Capitan on the original 2006/2007 Mac Pro and 2006 Xserve. These 64-bit Mac Pros and Xserves have EFI32 firmware and can't natively boot OS X El Capitan "out-of-the-box", but are easily capable of running it with a different boot loader. Once a new boot loader is used to launch the native 64-bit El Capitan kernel, OS X 10.11 boots and works normally exactly as it does on a 2008 Mac Pro or newer with EFI64 firmware.


Background:

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.

The last version of OS X officially supported by Apple on the original 2006 Mac Pro MA356LL/A (MacPro1,1), 2007 Mac Pro (8-core) MA1186/A (MacPro2,1) and Xserve (Late 2006) MA409LL/A (Xserve1,1) models was OS X 10.7 Lion, and then only when booted with a 32-bit kernel due to their EFI32 firmware. However, these Macs were the most powerful and upgradable EFI32 models and have a 64-bit architecture, so the user community has been keeping them running with 64-bit kernels and newer OS X releases using a variety of methods.


The Piker-Alpha bootloader can be used to boot OS X 10.11 El Capitan on unsupported Mac Pro models:

This approach, using a fork of boot.efi boot loader that thunks EFI64 calls from the 64-bit OS X kernel to the EFI32 firmware.

Additional information about Pike's boot.efi is available at Pike's blog, Universum. There are two variations available, one with a legacy light grey background/dark grey Apple logo boot screen boot.efi that blends with the native EFI32 pre-boot screen (2008-2012 Mac Pro-style), and a new black background/white Apple logo boot screen boot.efi (2013 Mac Pro-style).

The simplest method to boot El Capitan on these Macs is the "pikify" createpikeinstallmedia script to create a pre-patched El Capitan installer with the El Capitan branch of the Piker-Alpha bootloader. This directly allows an El Capitan installer to run to be run to completion on a 2006/2007 Mac Pro.

Another alternative install on a 2006/2007 Mac Pro is to use a second El Capitan-supported Mac and install El Capitan to the 2006/2007 Mac Pro's drive. This may be done either by attaching the 2006/2007 Mac Pro's drive as an external drive by placing the 2006/2007 Mac Pro in target disk mode or otherwise mounting the 2006/2007 Mac Pro's drive to an El Capitan-supported Mac.

This alternative approach still requires installation of the Piker-Alpha bootloader before it can be successfully booted on a 2006/2007 Mac Pro. 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. That drive should now be bootable on a 2006/2007 Mac Pro, although sometimes it still may need to be blessed in the 2006/2007 Mac Pro.

Disabling System Integrity Protection (SIP) may be required to replace the boot.efi in-place.

Alternatively, there's also an approach in the boot.efi development thread to exclude these files from SIP, but it has shown mixed results.

While this method is preferred because it's a native EFI boot, there is real risk that installing future El Capitan updates could overwrite Pike's EFI32 boot.efi if Apple were to update the stock EFI64 boot.efi. This has already happened in the few previous OS X El Capitan updates. When this happens, the system would no longer be natively bootable on a 2006/2007 Mac Pro until it had Apple's stock boot.efi re-replaced with Pike's boot.efi again. A simple approach to help protect against this is CaptainPikeFix, a launch daemon that re-copies the EFI32 boot.efi to proper locations at shutdown, but this approach requires disabling SIP.


Support for Handoff in El Capitan to allow AirDrop, Continuity and Instant Hotspot with iOS devices:

The original Airport Extreme (802.11a/b/g/draft-n Wi-Fi) and Bluetooth 2.0+EDR options from Apple don't support Handoff. Several vendors, including MacVidCards, sell new add-on hardware kits to retrofit older Mac Pros with 802.11ac Wi-Fi and Bluetooth 4.0 LE that work in 2006/2007 Mac Pros to allow Handoff. There have been reports of needing to sign out of iCloud and then sign in again after replacing WiFi and Bluetooth hardware to enable Handoff.

There has been a report of an OEM Bluetooth 2.0+EDR card causing a conflict with USB devices. If you experience issues with the built-in USB ports under El Capitan, you may also consider removing or upgrading your Bluetooth card.

In El Capitan, both Phone Calling and SMS from OS X with an iPhone work with a 2006/2007 Mac Pro and are not dependent on OS X Handoff support.


Unsupported original legacy graphics cards vs. 64-bit-kernel-supported graphics cards vs. Metal-supported graphics cards:

El Capitan does not include 64-bit kernel extension device drivers for the original NVIDIA GeForce 7300 GT, ATI Radeon X1900 XT, and NVIDIA Quadro FX 4500 PCIe graphics cards that shipped with these Mac Pros, nor the ATI Radeon X1300 that shipped with the Xserve (Late 2006), so they do not work properly in El Capitan. These graphics cards display issues such as a very sluggish GUI with no QE/CI support, no framebuffer support (for DVD Player, Geekbench and other programs), graphics artifacts, mouse tearing, inability to change resolutions, bad refresh rates, and other system instabilities. If you need normal graphics support in El Capitan, you will need a newer PCIe graphics card, with popular options being the Apple ATI Radeon HD 5770 Graphics Upgrade Kit for Mac Pro, SAPPHIRE HD 7950 3GB GDDR5 MAC Edition, or many different options of stock and Mac-"flashed" PC cards.

Many, but not all, modern stock non-flashed PC graphics cards with AMD (for OpenCL/OpenGL support) or Nvidia chipsets (for CUDA/OpenCL/OpenGL support) work "plug and play" with El Capitan in 2006/2007 Mac Pros, although the display will remain off until after the OS X Desktop initializes. This means you won't see anything during the boot process.

Compatible properly-Mac-flashed PC cards offer two benefits over stock non-flashed PC cards: allowing a normal boot screen just like a Mac-specific graphics card, and better compatibility in OS X with the card's capabilities/performance/ports. Most, but not all, Mac-flashed ATI/AMD cards have EBC firmware that work in all PCIe-based 2006-2012 Mac Pro models with either EFI32 or EFI64. All newer Mac-flashed Nvidia cards have EFI64 firmware and will act like non-flashed PC cards with no boot screens in EFI32-based 2006/2007 Mac Pros, except for older Mac-flashed Nvidia GeForce 8800 GT/9800 GT/GT 120 cards with EFI32 firmware.

Lastly, El Capitan has added a new graphics API called Metal that allows for much faster access to graphics card hardware. Note that only the most recent AMD (HD 7xxx "Tahiti" or newer) or Nvidia chipset (GeForce 6xx "Kepler" or newer) graphics cards fully and properly support Metal in a 2006/2007 Mac Pro.
Note also that the 2006/2007 Mac Pro has PCIe 1.1 expansion slots, with the bottom double-wide slot capable of being configured to use a maximum 2.5 GT/s link speed when configured as a x16 lane graphics slot. El Capitan's Expansion Slot Utility, located in /System/Library/Core Services, supports the 2006-2007 Mac Pro to configure the number of lanes available in each slot. PCIe 2.0/3.0 cards that can run at 5.0 GT/s link speed in 2008-2012 Mac Pros can work in 2006/2007 Mac Pros, but only with a PCIe 1.1 maximum 2.5 GT/s link speed.

None of these options are officially supported in these Mac Pros by AMD, Apple, or Nvidia, but can work with the Piker-Alpha boot loader.


iMessage/FaceTime note:

Regardless of approach used, some users cannot initially login to iMessage or FaceTime using their Apple ID from their Mac Pro after installing El Capitan as a security precaution. When trying to login, they receive an iMessage Registration validation code. The solution is to contact Apple support, provide the Mac Pro's serial number, explain that El Capitan was installed and that iMessage isn't working and provide the validation code. Apple then unblocks the Mac Pro, allowing iMessage and FaceTime login immediately and in the future without other issues.

Whats the process for updating from a Mac Pro 1,1 running Yosemite?
 

mmonse_de

macrumors newbie
Mar 20, 2016
23
7
Wuppertal, Germany
Whats the process for updating from a Mac Pro 1,1 running Yosemite?
Simply download the ElCapitan-installer from AppStore, install it. When the reboot during install stucks, boot from another partition (or bootstick) and change the boot.efi files to the @rthpjm version and it's done. Have a look at the posts above (#2026 ff.) to get some instructions on how to change the files.
 

tarkie

macrumors newbie
Jun 23, 2007
14
0
OK, now im stumped.

Mac pro 1,1 flashed to 2, 1. Been running Pikerfied through Yosemite and El Capitan. Updated to 10.11.4 and it broke.
Been running with the Piker boot.efi for so long, that it was before all the fix scripts, etc, and was installed manually.

No great shakes I thought, system booted into 10.9.5, I replaced the boot.efi with Piker's from Github, and all was good! Erm, no it wasn't it wont boot.

So, been through the whole process now a dozen times, checked the MD5's in both locations, checked the settings, cant see what I am doing wrong. So, in summary:

bash-3.2# cd /Volumes/El\ Capitan\ SSD/System/Library/CoreServices/

bash-3.2# ls -lasi boot.efi

7616244 616 -rw-r--r--@ 1 root wheel 314880 7 Apr 07:53 boot.efi

bash-3.2# openssl md5 boot.efi

MD5(boot.efi)= 23348e2baff575405f527cf0a26e2838

bash-3.2# cd ../../../usr/standalone/i386

bash-3.2# ls -lasi boot.efi

7615209 616 -rw-r--r--@ 1 root wheel 314880 7 Apr 07:54 boot.efi

bash-3.2# openssl md5 boot.efi

MD5(boot.efi)= 23348e2baff575405f527cf0a26e2838

bash-3.2# cd -

/Volumes/El Capitan SSD/System/Library/CoreServices

bash-3.2# ioreg -lp IOService | grep board-id

| "board-id" = <"Mac-F4208DC8">

bash-3.2# grep F4208DC8 PlatformSupport.plist

<string>Mac-F4208DC8</string>

bash-3.2# bless --info /Volumes/El\ Capitan\ SSD/

finderinfo[0]: 199 => Blessed System Folder is /Volumes/El Capitan SSD/System/Library/CoreServices

finderinfo[1]: 7616244 => Blessed System File is /Volumes/El Capitan SSD/System/Library/CoreServices/boot.efi

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 199 => OS X blessed folder is /Volumes/El Capitan SSD/System/Library/CoreServices

Any ideas?
 
Last edited:

mmonse_de

macrumors newbie
Mar 20, 2016
23
7
Wuppertal, Germany
OK, now im stumped.

Mac pro 1,1 flashed to 2, 1. Been running Pikerfied through Yosemite and El Capitan. Updated to 10.11.4 and it broke.
Been running with the Piker boot.efi for so long, that it was before all the fix scripts, etc, and was installed manually.

No great shakes I thought, system booted into 10.9.5, I replaced the boot.efi with Piker's from Github, and all was good! Erm, no it wasn't it wont boot.

So, been through the whole process now a dozen times, checked the MD5's in both locations, checked the settings, cant see what I am doing wrong. So, in summary:

bash-3.2# cd /Volumes/El\ Capitan\ SSD/System/Library/CoreServices/

bash-3.2# ls -lasi boot.efi

7616244 616 -rw-r--r--@ 1 root wheel 314880 7 Apr 07:53 boot.efi

bash-3.2# openssl md5 boot.efi

MD5(boot.efi)= 23348e2baff575405f527cf0a26e2838

bash-3.2# cd ../../../usr/standalone/i386

bash-3.2# ls -lasi boot.efi

7615209 616 -rw-r--r--@ 1 root wheel 314880 7 Apr 07:54 boot.efi

bash-3.2# openssl md5 boot.efi

MD5(boot.efi)= 23348e2baff575405f527cf0a26e2838

bash-3.2# cd -

/Volumes/El Capitan SSD/System/Library/CoreServices

bash-3.2# ioreg -lp IOService | grep board-id

| "board-id" = <"Mac-F4208DC8">

bash-3.2# grep F4208DC8 PlatformSupport.plist

<string>Mac-F4208DC8</string>

bash-3.2# bless --info /Volumes/El\ Capitan\ SSD/

finderinfo[0]: 199 => Blessed System Folder is /Volumes/El Capitan SSD/System/Library/CoreServices

finderinfo[1]: 7616244 => Blessed System File is /Volumes/El Capitan SSD/System/Library/CoreServices/boot.efi

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 199 => OS X blessed folder is /Volumes/El Capitan SSD/System/Library/CoreServices

Any ideas?

I'm quite speechless. Did you try the boot.efi file from the pikify3.1 v8 file? I had a non-running system until I used that file in both folders.
And did you protect the boot.efi in the coreservice folder again after replacing? AFAIK it is very important to have this file protected.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.