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

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
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.
________________________________________________________________


________________________________________________________________

Security Update 2018-001 for Mac OS X El Capitan from Apple will break your MacPro 1,1 or 2,1. The best advice we have is.... DO NOT INSTALL IT!

If you do install the 2018-001 Update you will find that your machine will go into a boot loop. The boot process will start, almost immediately the machine will crash and restart...

The majority of this Security Update focusses on fixing the Spectre and Meltdown issues that have been widely reported. One of the major software components that has been modified to address these issues was the Mac OS X kernel file. The Mac Pro 1,1 and 2,1 machines use Intel Xeon chip families that are NOT listed by Intel as affected by the Spectre and Meltdown issues. The changes made to the kernel file are believed to be unnecessary for the 1,1 and 2,1, worse, we believe that those changes are responsible for the crash/reboot loop.

You can recover from the boot loop. Forum member rthpjm has written one procedure at post #3896. Other members have recovered by re-installing El Capitan from source, and yet more members have recovered by using a Time Machine backup, read some of the posts surrounding #3930.

Opinion varies. Most members (including rthpjm) recommend not installing the Security Update and hiding it in the Mac App Store app. rthpjm's recovery procedure just overwrites the kernel file with the last-known-good kernel. If you do this, then you must also consider if you will run with an older kernel combined with updated kernel extensions (kexts). It must be your choice, if you choose this option be aware Apple hasn't tested this combination and it could cause your machine to be unstable and to exhibit unexpected behaviour. Once you have recovered, you then have the luxury of deciding to re-install El Capitan at your leisure. If you do this then we believe you will be back to a more stable/tested combination of kernel and kernel extensions.

Future Security Updates from Apple are likely to roll up the Security Update 2018-001, so please, turn off Automatic Updates, and check before choosing to install...
________________________________________________________________


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.

While it's not exactly plug-and-play, it's close if you use rthpjm's Pikify App, and most importantly, as long as you also upgrade the stock legacy graphics card that originally came with these Macs from 2006/2007. El Capitan requires a newer graphics card to function, see below.

Unfortunately, macOS 10.12 Sierra and 10.13 High Sierra can't work on these Macs, even with a new boot loader. This is because newer macOS versions require the SSE4.1 instruction set, and the Intel Xeon 5100-series "Woodcrest" and 5300-series "Clovertown" CPUs in these Macs don't have that support.


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, or the new Pikify App 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.
 
Last edited:

netkas

macrumors 65816
Oct 2, 2007
1,198
394
Have same thinks about nvidia cards.

But this thing can't get out of my head, OS X 10.11 Capitan Obvious

bmr9Mrh.jpg
 

netkas

macrumors 65816
Oct 2, 2007
1,198
394
Developer Beta System Requirements The OS X v10.11 Developer Beta supports the following Macs: • iMac (Mid 2007 or newer) • MacBook Air (Late 2008 or newer) • MacBook (Late 2008 Aluminum, or Early 2009 or newer) • Mac mini (Early 2009 or newer) • MacBook Pro (Mid/Late 2007 or newer) • Mac Pro (Early 2008 or newer) • Xserve (Early 2009)
 

netkas

macrumors 65816
Oct 2, 2007
1,198
394
Well, requirement for dx12 are radeon 7xxx+ or geforce gtx 4xx+.

Metal reqs will be same or more, not less.
 

Demigod Mac

macrumors 6502a
Apr 25, 2008
836
280
Developer Beta System Requirements The OS X v10.11 Developer Beta supports the following Macs: • iMac (Mid 2007 or newer) • MacBook Air (Late 2008 or newer) • MacBook (Late 2008 Aluminum, or Early 2009 or newer) • Mac mini (Early 2009 or newer) • MacBook Pro (Mid/Late 2007 or newer) • Mac Pro (Early 2008 or newer) • Xserve (Early 2009)
Nice... My ancient MBP gets yet another lease on life. I'd expect Nvidia to introduce Metal support to the web drivers, even if Apple does nothing.
 

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
From "Metal supported GPU" on netkas.org:
This info comes from metal driver availability, not from real test

Metal supported card families:

Nvidia – GeForce gtx 4xx and newer
Intel – HD4000 and newer (ivy bridge and newer)
AMD – HD7000 and newer
If correct, this information coupled with the DB1 system requirements implies that certain older GPUs (like ATI 5770) work in El Capitan but without support for Metal.
 
  • Like
Reactions: PeterHolbrook

NOTNlCE

macrumors 65816
Oct 11, 2013
1,087
476
Baltimore, MD
I don't suppose the current Yose boot.efi works. Probably a stupid question, but I have all morning to play around (once this stuff downloads.) I'll give it a shot.

EDIT:

There does not appear to be a "CreateInstallMedia" script in the beta app in the DMG, possibly just in the app.

EDIT2:

If you have the App bundle, the createinstallmedia command works as usual. If you downloaded the DMG from the Developer Portal, you can use Disk Utility to restore it to a USB.

PS: I like the new beachball. :)

EDIT3:

From TMRJIJ:
OS X El Capitan has been confirmed to have rootless type restriction for system files even for root access. Boot.efi changing is now much harder and may require single user mode to be used more often than not.
I will try to get in contact with some more developers and hackintosh people for help with some issues. Expect OSXH 1.3 Beta 1 to only be available for 64bit EFI capable Macs right now.
 
Last edited:

666sheep

macrumors 68040
Dec 7, 2009
3,686
291
Poland
What the prize was? ;) :p :D

Installed on a 5,1 first, I was too lazy to build an installer.
Removing boot.efi requires adding rootless=0 to com.apple.Boot.plist.
Or just remove it under another OS.
 

Attachments

  • Screen Shot 2015-06-09 at 13.10.29.png
    Screen Shot 2015-06-09 at 13.10.29.png
    116.5 KB · Views: 10,496
Last edited:

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,617
439
What the prize was? ;) :p :D

Installed on a 5,1 first, I was too lazy to build an installer.

Congratulations, and thanks for the good news. I take it for granted that you substituted Pike's boot.efi for the original one. Or did you use any of the boot.efi files created by Andy Vandijck for Yosemite?
 
Last edited:

sarthak

macrumors 6502
Nov 19, 2012
467
6
What the prize was? ;) :p :D

Installed on a 5,1 first, I was too lazy to build an installer.
Removing boot.efi requires adding rootless=0 to com.apple.Boot.plist.
Or just remove it under another OS.

Is Metal working with the 5870? Assuming it's ready to use in the dev preview.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,617
439
Great news ! Going to make Tahiti cards the "go to" choice.
From what I've read, my Apple-purchased ATI Radeon HD 5770 1024 MB might not be Metal-compatible under El Capitan. Which other Startup Manager-compatible card do you recommend for a Mac Pro 1,1? Any caveats I should be aware of?
 

NOTNlCE

macrumors 65816
Oct 11, 2013
1,087
476
Baltimore, MD
Is Metal working with the 5870? Assuming it's ready to use in the dev preview.

Netkas posted above that at present, only 7000+ series Radeon cards have Metal support. That's not to say it's not possible or doable, but at the moment, it appears to be unsupported.
 

RX2904

macrumors member
Aug 26, 2014
52
1
From what I've read, my Apple-purchased ATI Radeon HD 5770 1024 MB might not be Metal-compatible under El Capitan. Which other Startup Manager-compatible card do you recommend for a Mac Pro 1,1? Any caveats I should be aware of?

I have the same card installed. Let me know if it works. Would hate to have to buy another card. I bought that one just last year to upgrade my 2,1 to Mavericks/Yosemite. :)
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,617
439
I have the same card installed. Let me know if it works. Would hate to have to buy another card. I bought that one just last year to upgrade my 2,1 to Mavericks/Yosemite. :)
I installed the beta preview of El Capitan yesterday, but only as a VMware Fusion virtual machine. I don't think I'll be physically installing El Capitan until it's released in the autumn.

If the ATI 5770 card isn't Metal-compatible, we might be running short of options, as we'll need a 32-bit EFI card (in case we want it to display the Startup Manager), and that condition might be mutually exclusive with the advanced Metal capabilities, and if it isn't fully exclusive yet, it will be increasingly so.
 

RX2904

macrumors member
Aug 26, 2014
52
1
I installed the beta preview of El Capitan yesterday, but only as a VMware Fusion virtual machine. I don't think I'll be physically installing El Capitan until it's released in the autumn.

If the ATI 5770 card isn't Metal-compatible, we might be running short of options, as we'll need a 32-bit EFI card (in case we want it to display the Startup Manager), and that condition might be mutually exclusive with the advanced Metal capabilities, and if it isn't fully exclusive yet, it will be increasingly so.

Damn :(

But does that mean that El Capitan won't run at all on a 5770 or will it run fine unless you wanna do stuff that requires Metal?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.