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

jeffcalloway

macrumors newbie
Sep 1, 2009
10
1
This has breathed new life into my MacPro 2,1 with 24gb memory and ATI Radeon HD 5870 1gb, 2 x 3ghz Quad Xeon. Updated from 10.11.2 to 10.11.6 no problem after installing the boot64 package.

Great work!
 
Last edited:
  • Like
Reactions: jbarley

drkheure

macrumors newbie
Nov 4, 2015
28
1
There is no such thing as "supporting" SLAEG or SLAC4. It's just the stepping (internal revision number) SLAEG being the last revision, which accidentally runs a slightly lower temperature (70 vs 63 deg C).
just installed. a few hours work.
windows 7 sees the 8 cpu's.
firmware still not updated. It was easier than I thought.
 
  • Like
Reactions: hwojtek

davidmck

macrumors newbie
Dec 31, 2014
9
0
Some of the guys that were working with Pike split off into a new thread to concentrate on just the development and testing of Pike's frequent changes, "the developer thread". As these things go, the volunteers that were testing Pike's changes found that they needed to frequently wipe and re-install, me included, so I developed a bundle of scripts and items to ease the install of a new El Capitan. My innovation (if you want to call it that) was to find a way to patch the fresh install with Pike's efi files during the install. I called my bundle of scripts and items 'pikify3.1.zip'.

Since it is now well used and tested, I'll cross post here. The latest version pikify3.1.v8.zip will build install media with all the fixes in (but not including my Boot64 update protector, nor the equivalent pikeyosfix derivative CapitanPikeFix - see the next post). This version also excludes the boot.efi files from SIP-control (meaning SIP is running and protecting everything else, just not the boot.efi files).

So with pikify3.1 you will build an installer onto media, typically a USB memory stick, or a small disk partition.
You will then boot off the installer, to run the installation process. Once the installer finishes, you will have a working copy of El Capitan with no further need for changes. You can then choose to install the updated version of pikeyosfix now called CapitanPikeFix, or my Boot64 (both do pretty much the same thing), to allow you to run the Apple updates from either the App Store or from the DMG downloads.

READ ALL THE CAVEATS - memory, backup, fresh install, migration assistant, etc...

Use this if you have not yet installed El Capitan and you only have your Mac Pro available.

(If you have another "newer/compatible" machine available then you can attach your Mac Pro (disks) to this compatible Mac and install from there), otherwise....

This is the installer (starting point) if you only have your Mac Pro to work with...


-----------------------------------------------------------------------------------------------

ORIGINAL POST WAS AT POST #807 of the 'boot.efi developer's thread'

============= Edit =====================

It appears that MacPro1,1 and 2,1 need a lot of memory to achieve a successful install by this method. Others have kindly tested with varying configurations of RAM. See the later posts in the developers thread and my post at #855

A minimum of 12GB seems to be required...

============ end edit ====================

Hi @Inspector42, I'm glad you were able to use my script. I like your rsync idea!

Here is a new script and accompanying files. This one is based around Apple's createinstallmedia script.

The unique feature of this script is that it builds an installer which will pre-patch the resulting El Capitan volume. What this means is that the installer can be run, and then the reboot will work without any further modification. You have a working installation of El Capitan directly from the installer.

Download the zip file.
Unzip it.
You should have a folder named pikify3.1 (possibly with the version number pikify3.1.v2 etc)
In that folder should be a number of files, the script is createpikeinstallmedia. Keep all the files in one location. Some people have tried to use just the script on its own without the accompanying files and then come back for help because it didn't work. You can move the pikify3.1 folder wherever you please, just keep the contents of the folder together.

If you are not familiar with the Terminal and the command line, take a look at post #1569 it will probably help you.

Pre-requisites:

  • As per Peter's guide, you will need a volume that can be overwritten by the installer
    • This could be a USB memory stick
    • A small disk partition from one of your hard drives (not the disk that you intend to use for El Capitan)
      • You need to be able to boot from this volume
  • The installer volume needs to be at least 8GB
  • Your copy of 'Install OS X El Capitan.app' should be located in your /Applications folder
  • The pikify3.1 folder contains both the black and grey variants of the boot.efi file. When unzipped the boot.efi file is the grey one, if you want to change to the black background variant, simply copy the black one over the boot.efi before you start. e.g.
    Code:
    cp -f boot_black_3_1.efi boot.efi
Usage:
  • Open a terminal window
  • Change directory to the pikify3.1 folder from the zip file. Let us assume that you downloaded the zip file to your Downloads folder and unzipped it there. (If you have put the pikify3.1 folder somewhere else, please alter the path to suit your location)
  • Change [InstallerVolumeName] to the name of the USB memory stick or your small disk partition. For example if you are using a USB memory stick and it shows on the desktop with the name Untitled, then replace [InstallerVolumeName] with Untitled so that the path reads /Volumes/Untitled
Code:
cd ~/Downloads/pikify3.1
  • You need to run the script as the root user
Code:
sudo -s
[your password]
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

  • OR
Code:
sudo ./createpikeinstallmedia /Volumes/[InstallerVolumeName]
[your password]
  • OR (optionally switch to the black background variant before you start)
Code:
sudo -s
[your password]
cp -f boot_black_3_1.efi boot.efi
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

Be patient, the script will take some time to run through to completion, especially if your installer volume is a USB memory stick!

Once the script completes it will print ### DONE PIKIFYING ### and you should have an installer volume named 'Install OS X El Capitan'

--------------------- EDIT -----------------------------------------------
Some users have reported that after building a pikify3.1 USB memory stick they cannot boot their MacPro from it. Typical symptoms are that when rebooting, holding the ALT key immediately after the chime, enter the boot selector, choose the USB memory stick to boot from, yet the system then boots to the main OS from the hard disk(s), or the screen is blank (possibly showing the folder with a question mark).

I have replicated this on my machine. Here is what works for me....

After you build your pikify3.1 USB memory stick, but before you attempt to boot from it, try ejecting it, physically unplug it, wait a few seconds, then re-plug it in allowing it to mount.

Doing this seems to work for me. I think the important thing is to physically remove (power down) the device. It's a good old fashioned hardware restart.

-------------------- end EDIT ------------------------------------------
  • Reboot your MacPro with the newly created install media (partition or USB stick) attached
  • Hold the ALT key down immediately after the startup chime to enter the boot chooser
  • Choose the Install OS X El Capitan volume
    • For those people with graphics cards that don't show the boot screens
      • If you are using a USB stick (and it's the only one attached), then get to the boot chooser as above then press the left-arrow key once, followed by the return/enter key. (Removable media generally shows up last in the horizontal list, pressing the left arrow key takes you from the automatic first entry and wraps the highlight round to the other end of the list, which is usually where the USB stick is presented).
      • If you're using a small disk partition, the get to the boot chooser as above then press the right-arrow key once, followed by the return/enter key). If you have just your main disk and the installer volume this should work. If you have more than just those two, experiment pressing the arrow key more than once until you find the installer volume!
      • OR, consider getting hold of a DVI-vga adaptor. You should be able to find one of your DVI ports that will send out a VGA signal (to a VGA connected monitor) and show you the boot screen.
  • Your machine should boot into the Installer, run the installer
    • You may need to click the Reboot button at the end of the install (for some reason, the 10 second countdown doesn't seem to automatically start)
  • Your machine should reboot into the new El Capitan Installation and begin the OS X setup procedure.
============== edit ===============
I made a video! I hope you like it...

I used my iPhone for the second half, apologies for the moire patterns.

I decided to start from my MacPro running 10.7.x Lion, since this is the last officially supported version.
The only difficulty for people is to get hold of a copy of Apple's "Install Mac OS X El Capitan" app. I recommend using a newer "supported" Mac and then copying it to the MacPro....

One of the steps in the video shows me formatting my hard disk drive, do not do this step if you have data on your hard disk (unless you have a backup and are prepared to wipe the drive)


============== end edit =============

I have only tested this script as a clean install onto an erased destination disk. I don't know if it will work for an upgrade. I have successfully updated a Yosemite clean install to El Capitan.
If you are upgrading I would suggest a clean install of El Capitan onto a spare disk, then use the Apple Migration Assistant to migrate your previous system and user files.
If you are brave and want to try an in-place upgrade, make sure you backup your current system first...

Detail:

I created an additional package (pikify.pkg) which handles the post-install modification of the boot.efi files on the destination volume. The script puts pikify.pkg into the InstallESD.dmg, along with OSInstall.collection.
OSInstall.collection overrides the default behaviour of the Installer Assistant, it calls the default OSInstall.mpkg and appends pikify.pkg to the install chain.

In effect I'm running the exact same installation as an unmodified Apple install with the addition of my pikify.pkg.

Because the default behaviour has been overridden, there are a few differences:
  • An unmodified Apple installer will open with the /System/Installation/CDIS/OS X Utilities.app
    • The modified installer goes straight into the Installer
  • An unmodified Apple installer will automatically reboot 10 seconds after the installation completes
    • The modified installer doesn't, you will have to click the Reboot button
I've included both versions (black and grey) of Pike's 3.1 boot.efi file. If you want to change the colour, overwrite the boot.efi file in the pikify3.1 folder with the coloured version of your choice. The zip file unpacks with the grey version in place.

Enjoy...

======================== UPDATE ================================

The original Apple BaseSystem.dmg appears to be missing a number of fonts. This causes the installer log file to fill up with thousands of unnecessary lines complaining about the missing fonts. I've updated the installer creation script to fix the missing fonts. It just makes the log file smaller and easier to read and follow.

See pikify3.1.v2.zip in the attachments...

==================== ANOTHER UPDATE =============================

I figured out how to set up El Capitan so that we can make it survive an Apple update. See my post at post #1391

I've modified the pikify3.1 set so that those changes are automatically applied.

I'll leave v2 here in case anyone is paranoid, and doesn't want the slight lowering of SIP's security blanket!

==================== Version 5 ===================================

V5 includes some mods to the SIP exclusion paths file

==================== Version 7 ===================================
(includes version 6, which added support for home-baked fusion drives)
V7 adds error checking and a bit of an explanation to start

==================== Version 8 ===================================
V8 adds a check to ensure there is a copy of the Apple Install OS X El Capitan application located in the Applications folder!

==================== Version 9 ===================================
All previous versions would first write the Install media, and then modify that content. If the Install media is a USB memory stick, all those operations are slow due to the USB bus speed.

V9 attempts to speed up the operations. It will modify the /Applications/Install OS X El Capitan.app on the hard disk first (faster), and then write the contents to the USB memory stick. There is only one write across the USB bus.

Plus, the modifications are left in place. The script will detect if the copy of Install Mac OS X El Capitan has already been modified, giving you the option to reset to the Apple version, or to continue. If you choose to continue it will skip the modifications (because they're already present) and simply write a new copy to your USB memory stick (or installer partition)

It should be quicker :)

==================== Version 10 ==================================
Version 10 adds a check to see if the InstallESD.dmg and/or the BaseSystem.dmg are already mounted, if so it tries to detach them.

WARNING: It seems some people have tried V10 and it has caused problems. I'm re-posting V8 whilst I investigate....

==================== Version 11 ==================================
Version 11 fixes the issues with v9/v10. Basically I made an error in design when I created v9/v10. The resulting files were too big to fit onto an 8GB memory stick. Sorry folks!!

If you downloaded v9 or v10, please rapidly place them in their new home (the trash can), and re-download V11, it will now work much better :)

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v2.zip) = 80333eda8eecc3094f06d175bdba0a64
MD5 (pikify3.1.v8.zip) = 8ef0cf2b34e9c6751c0f1ac99b40dadc

MD5 (pikify3.1.v11.zip) = 7402feaa1ef48747c3908890b9fbe254


So I got all the way to Holding ALT and hitting enter on Instal OS X El Capitan.App and this text came flying down the screen and then reboots into "You comp had a problem press a button or wait" then it just goes into my regular OS...

any ideas? (I am not using a USB stick)

I used v11zip will try v2 next

Thanks

IMG_1427.JPG
IMG_1428.JPG



also this is said at the end.
Screen Shot 2016-09-08 at 8.31.34 AM.png
 
Last edited:

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
So I got all the way to Holding ALT and hitting enter on Instal OS X El Capitan.App and this text came flying down the screen and then reboots into "You comp had a problem press a button or wait" then it just goes into my regular OS...

any ideas? (I am not using a USB stick)

I used v11zip will try v2 next

Thanks

View attachment 649143 View attachment 649144


View attachment 649143 View attachment 649144

also this is said at the end. View attachment 649151
Don't worry about those last two lines after you created your Pikified installer. The last thing the script attempts to do is figure out if you are using a MacPro, and if so how much RAM you have in the machine. It is just that piece that sometimes throws those warnings. They can be ignored.

Your kernel panics are most likely due to your RAM configuration. Can you please reply here with the total amount of RAM that you have, and also the number of memory sticks of what capacity.

I'm expecting you to tell me that you have some of the original 512Mb RAM sticks in the machine, but I'll wait for you to confirm....
[doublepost=1473350495][/doublepost]
So I got all the way to Holding ALT and hitting enter on Instal OS X El Capitan.App
I assume you mean the startup disk icon named "Install Mac OS X El Capitan", not the App??!!
 
  • Like
Reactions: davidmck

davidmck

macrumors newbie
Dec 31, 2014
9
0
Don't worry about those last two lines after you created your Pikified installer. The last thing the script attempts to do is figure out if you are using a MacPro, and if so how much RAM you have in the machine. It is just that piece that sometimes throws those warnings. They can be ignored.

Your kernel panics are most likely due to your RAM configuration. Can you please reply here with the total amount of RAM that you have, and also the number of memory sticks of what capacity.

I'm expecting you to tell me that you have some of the original 512Mb RAM sticks in the machine, but I'll wait for you to confirm....
[doublepost=1473350495][/doublepost]
I assume you mean the startup disk icon named "Install Mac OS X El Capitan", not the App??!!

Thanks for speedy reply..

I have 12gigs of ram, but I had my 1gigs in slots 1-2 and read that could be an issue..

But wait!

I tried switching my ram around and the same issue showed up..

Reading the kernel panic I noticed it talking about USB..

So on a hunch I decided it was possibly my third party USB card that could be a problem.. So I removed it..

And success!

Now I'm not 100% sure that this was the issue but I wanted to add this to the forum so maybe someone else might be saved like I was..

Here's the culprit

image.jpeg


Thanks again and looking forward to this community getting me into Sierra in a few months :p;) (and yes I read this may be the end of 1,1's o_O)

I assume you mean the startup disk icon named "Install Mac OS X El Capitan", not the App??!!

hah, yes the start up disk name! not .app!

Thanks again! :apple:

and I am currently recovering from a surgery and at home 24/7... ignore the nails! I know! :confused::eek:
 
Last edited:

davidmck

macrumors newbie
Dec 31, 2014
9
0
Don't worry about those last two lines after you created your Pikified installer. The last thing the script attempts to do is figure out if you are using a MacPro, and if so how much RAM you have in the machine. It is just that piece that sometimes throws those warnings. They can be ignored.

Your kernel panics are most likely due to your RAM configuration. Can you please reply here with the total amount of RAM that you have, and also the number of memory sticks of what capacity.

I'm expecting you to tell me that you have some of the original 512Mb RAM sticks in the machine, but I'll wait for you to confirm....
[doublepost=1473350495][/doublepost]
I assume you mean the startup disk icon named "Install Mac OS X El Capitan", not the App??!!


I tried putting the USB back in after I had 11.6 fully running.. and it had same kernel panic crash on boot.

So all you people with an extra USB drive stuck into your machine this may be an issue.

On the same note,

Anyone here have a third party USB drive that is working with their 11.6 El Cap?

Thanks and happy hacking! :)

Dave :apple:
 

drkheure

macrumors newbie
Nov 4, 2015
28
1
Anyone here have a third party USB drive that is working with their 11.6 El Cap?

Thanks and happy hacking! :)

Dave :apple:
I use usb drives, but did you mean usb pci cards ?
I used a usb external drive yesterday on my macbookpro, I have had that same drive plugged in into my macpro 2006, but can't remember how recently that was. I also have had usb / sata adaptor plugged in for backing up, but also not recently.
 

davidmck

macrumors newbie
Dec 31, 2014
9
0
If you're talking about USB PCIe card, nobody had problems with Inateck KT4004 in 10.11.6 (AFAIK)

Thanks for $30 I pulled the trigger, I can always return it if fails!

Card I just bought that owbp referenced above, Here... I will update once it comes and if it works or not.

Also for reference here is the card that did not work with 11.6, Here

Thanks owbp! :D

I use usb drives, but did you mean usb pci cards ?
I used a usb external drive yesterday on my macbookpro, I have had that same drive plugged in into my macpro 2006, but can't remember how recently that was. I also have had usb / sata adaptor plugged in for backing up, but also not recently.

Sorry! I meant cards! but still good info for all. Thanks drkheure :apple::cool:


Thanks again guys
 

zazaki

macrumors member
Sep 10, 2016
35
5
Hi & many thanks for this "fundamental" project. I think I am making confusion trying to inject new blood to my Mac Pro 1.1.
I did the pikify3.1v1 on an USB drive from my Macbook (Yosemite) ; and then I have tried to install El Capitan on a Raid0 system running Snow Leopard on the Mac Pro. Failure : I get kernel panic on boot.

My question is:
— do I need to make the Pikify script from the Mac Pro (updated with Lion)? and why (I need to understand) ?
— can I install El Capitan on a Raid0 strip ?
— can you give me an advice for the purchase of a new graphic card (like a NVIDIA GT650)

Thanks
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
have you got the minimum RAM requirement - a lot of kernel panics are caused by this. You need 12gb and no 512mb modules if using the USB installer method.
 

drkheure

macrumors newbie
Nov 4, 2015
28
1
I replaced my gt650 ti witha zotac 1060.
The 1060 is still not supported, but runs fine under windows.
The 650 ( unflashed ) worked fine under el cap
 

Old Fred

macrumors newbie
Sep 9, 2016
1
0
Don't worry about those last two lines after you created your Pikified installer. The last thing the script attempts to do is figure out if you are using a MacPro, and if so how much RAM you have in the machine. It is just that piece that sometimes throws those warnings. They can be ignored.

Your kernel panics are most likely due to your RAM configuration. Can you please reply here with the total amount of RAM that you have, and also the number of memory sticks of what capacity.

I'm expecting you to tell me that you have some of the original 512Mb RAM sticks in the machine, but I'll wait for you to confirm....
[doublepost=1473350495][/doublepost]
I assume you mean the startup disk icon named "Install Mac OS X El Capitan", not the App??!!

Hello All,

I wanted to post a big thank you to this forum for all the great info on making an early Mac Pro run El Capitan. I want to especially thank rthpjm for all his hard work and tireless answering of questions. You must have the patience of a saint!

I have a 2006 1.1 Mac Pro which I bought cheap on EBay. I bought it a new old stock case and changed all the parts over while doing a processor upgrade. It ran Snow Leopard off an SSD and did everything that I wanted it to do.

Time passed and I didn’t like any of the newer operating systems from Apple until El Capitan came along. Like Snow Leopard it was a “fix-it” release getting everything right. I really wanted to get it working on the 1.1 and this forum made it possible.

I did it the easy way, cloning an El Cap drive off another Mac and moving it to my 1.1. I am not so swift with terminal, but I did get the boot.efi files replaced (I drag into terminal a lot). The results are amazing! El Cap on the big 30” cinema screen is a treat. Rthpjm’s Boot64 has been a big help. I don’t have to fear Apple trashing my boot loaders.
 

Mjsais

macrumors member
Feb 29, 2012
40
3
In Post #2773, I stated that I had kernel panic trying to boot to either a Captain Drive created using a compatible iMac, or to the pikify installer that i successfully created. I finally had time to try it again and I have attached two boot attempts log files. Hopefully, this will generate some solution to my problem. Thank you.
 

Attachments

  • Capt Error Report #1.pdf
    29.5 KB · Views: 342
  • Capt Error Report#2.pdf
    34.8 KB · Views: 201

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
In Post #2773, I stated that I had kernel panic trying to boot to either a Captain Drive created using a compatible iMac, or to the pikify installer that i successfully created. I finally had time to try it again and I have attached two boot attempts log files. Hopefully, this will generate some solution to my problem. Thank you.
Do you have any 512mb RAM modules installed? If so, remove them and try again. Reading the log - perhaps not. Have you checked for LEDs showing on the riser boards indicating faulty RAM?
 

dcloud45

macrumors member
Oct 5, 2015
52
0
alright you all . can anyone tell me if updating to 10.11.6 replaces the boot files? i have always used the replace method .
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
In Post #2773, I stated that I had kernel panic trying to boot to either a Captain Drive created using a compatible iMac, or to the pikify installer that i successfully created. I finally had time to try it again and I have attached two boot attempts log files. Hopefully, this will generate some solution to my problem. Thank you.

It starts complaining about BlueTooth. Since a MacPro 1,1 does not come stock with one could you remove the device that contains the bluetooth controller and try with wired mouse and keyboard?
 

Mjsais

macrumors member
Feb 29, 2012
40
3
Thats the weird thing, I'm using a wired keyboard and wired mouse. I don't have any bluetooth device or controller attached.
[doublepost=1473648703][/doublepost]ok, given that the error log continue to mention Bluetooth (which I did'nt have in the machine), I decided to plug a USB bluetooth adapter. Now El Capitan works!!! - I still don't understand.
 
  • Like
Reactions: cdmawolf

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Thats the weird thing, I'm using a wired keyboard and wired mouse. I don't have any bluetooth device or controller attached.
[doublepost=1473648703][/doublepost]ok, given that the error log continue to mention Bluetooth (which I did'nt have in the machine), I decided to plug a USB bluetooth adapter. Now El Capitan works!!! - I still don't understand.

Where did you get your copy of 'Install OS X El Capitan.app' from?
 

Mjsais

macrumors member
Feb 29, 2012
40
3
Where did you get your copy of 'Install OS X El Capitan.app' from?
My 2013 iMac has el captain installed. I re-downloaded the installer from the App Store and used a USB adapter to connect my mac pro hdd go it.
 

Mjsais

macrumors member
Feb 29, 2012
40
3
I still have not installed Boot64. Does Security Update 2016.001 10.11.6 updates the boot.efi files?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.