This works: https://support.apple.com/kb/DL1845?locale=en_US
Once 10.11 works reliably, just install this.
Oh, I see you used a MBP, I used this method but had a spare drive installed to re-copy the boot files.
Hope this helps.
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
This works: https://support.apple.com/kb/DL1845?locale=en_US
Once 10.11 works reliably, just install this.
Oh, I see you used a MBP, I used this method but had a spare drive installed to re-copy the boot files.
Hope this helps.
Copy back the Files is no Problem, but i also have no Installation of 10.11.0 so o can't use a Update only. I would need also the 10.11.0 Download.
Last edited:
Tried again to use 10.11 one my mac pro 1.1 without success. It keeps rebooting on me... I have 8 x 512 mb ram. Would that be the problem ? It boots fine but after a little while it keeps shutting down..
Attachments
Same here. I tried to remove my 2 512 MB RAM and only Start with 2x2GB RAM. But de behaviore is the sam. It Starts an After a while it reboot.
With 10.11.1 i didn't have this Problem. But to set back to 10.11.1 I ned the 10.11.0 installer, which i can't find anywhere. Only the 10.11.1 Update.
With 10.11.1 i didn't have this Problem. But to set back to 10.11.1 I ned the 10.11.0 installer, which i can't find anywhere. Only the 10.11.1 Update.
You can run Yosemite or El Capitan on a 2006 MacBook 2,1, but the issue becomes the GMA 950 GPU isn't supported in 10.9 and later. I recommend installing Mountain Lion using MLPostFactor, see this thread.
Any idea if you can upgrade to 10.11.3 ???? Did you problem occur after installing an software update from 10.11.1?
Last edited:
I have had alook at that n i dnt understand it pal if you would be so kind to help a noob out on how to do it step by step plz pal
I don't know. I did a complete reinstall after chanching HD's and from this point I installed 10.11.3 and the problems begins. With 10.11.1 I had no problems the Mac Pro 1,1 runs like a rock.
With the recent Certificates expiring, I do not know where you could download a viable installer. Did you check your applications folder on the MBP?
I have an Oct version of 10.11.0 I will try it this weekend and see what happens. I have old 120G drives I use to test.
I replaced the 512MB modules with 4GB modules, bringing my total memory to 24GB.
Now when I try to boot, I see a kernel panic as before--some codes are different, but I didn't pay close enough attention to know if this changes for every crash.
Is it possible to download El Capitan 10.11.3 installer source for generating a UFD with the latest installer, or to "patch" or "slipstream" an older installer to make it current? I tried redownloading from a machine that already has El Capitan. I see a message "OS X v10.11.3 is already installed...to download the full OS X installer click Continue. If I click continue, the progress "gear" spins in the upper left, but nothing seems to happen.
(W|Sh)ould it make a difference if I reinstall with the latest El Capitan installer?
Any other suggestions?
Thank you!
Now when I try to boot, I see a kernel panic as before--some codes are different, but I didn't pay close enough attention to know if this changes for every crash.
Is it possible to download El Capitan 10.11.3 installer source for generating a UFD with the latest installer, or to "patch" or "slipstream" an older installer to make it current? I tried redownloading from a machine that already has El Capitan. I see a message "OS X v10.11.3 is already installed...to download the full OS X installer click Continue. If I click continue, the progress "gear" spins in the upper left, but nothing seems to happen.
(W|Sh)ould it make a difference if I reinstall with the latest El Capitan installer?
Any other suggestions?
Thank you!
Got this error (pic link attached)
I think there is something to do with dismounting and mouting the partition
It said something about not been able to erase either
I have created a guid mac partition of 8gb on a ssd
First time it said DONE PIKIFYING but no files were created on my partition.
Yes i have the instalation file on my application folder
Thank you for your help
I think there is something to do with dismounting and mouting the partition
It said something about not been able to erase either
I have created a guid mac partition of 8gb on a ssd
First time it said DONE PIKIFYING but no files were created on my partition.
Yes i have the instalation file on my application folder
Thank you for your help
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 - this is the installer (starting point)
-----------------------------------------------------------------------------------------------
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:
Usage:
- 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
- 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 competes it will print ### DONE PIKIFYING ### and you should have an installer volume named 'Install OS X El Capitan'
Your machine should boot into the Installer, run the installer
- Reboot your machine
- 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
- 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.
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.
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:
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.
- 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
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!
Attachments
I re-downloaded OS X El Capitan installer (10.11.3) and ran the createpikeinstallmedia script to redo my installer UFD.
After re-installing El Capitan on my Mac Pro 1,1 from that installation source, I seem to have a reliable install.
Also excluded boot.efi from SIP and installed Boot64. Thanks, all!
After re-installing El Capitan on my Mac Pro 1,1 from that installation source, I seem to have a reliable install.
Also excluded boot.efi from SIP and installed Boot64. Thanks, all!
Hello ufopeace,
Please try this again, but this time make sure nothing is "using" your SSD partition. That includes you Terminal session(s). Before you escalate your account to the root user (the sudo command) make sure you have changed directory to the location of the Pikify folder, then issue the sudo command and begin the process.
If it still complains, then there must be some other process "using" the SSD partition. Try using the following command
Code:
lsof /Volumes/installation
Hello all. I have been very busy so have not had time to continue my efforts to get El Capitan installed on my 2006 Mac Pro. For others who have just found this forum I did upgrade my video card to one with the minimum requirements to run El Capitan and my RAM to 12 GB. The good news is that last night I followed the instructions in post #1390 on page 56 of this topic and was able to get El Capitan installed on my MacPro. After I unzipped the pikify3.1.v8 posted by rthpjm and followed his instructions I was able to create an El Capitan installer on a USB drive and install the same on my 2006 Mac Pro 1,1.
When I came back to the Desktop on my 2012 Mac Mini I found a zip file entitled, pikify3-1-v8-zip.608081.zip. Since I did not run a MD5 or SHA1 on the downloaded file I was a little concerned that the pikify3.1.v8.zip file could have been compromised in transit to my computer from this forum since I found the zip file's now had 608081.zip added to its name and I was unaware of anything I had done to cause this. I checked my entries in Terminal and did not see commands I had issued that I thought could have done this. This is probably something that I am ignorant of and do not need to worry about but just in case I thought I should post about it for others who may see this and be concerned.
When I came back to the Desktop on my 2012 Mac Mini I found a zip file entitled, pikify3-1-v8-zip.608081.zip. Since I did not run a MD5 or SHA1 on the downloaded file I was a little concerned that the pikify3.1.v8.zip file could have been compromised in transit to my computer from this forum since I found the zip file's now had 608081.zip added to its name and I was unaware of anything I had done to cause this. I checked my entries in Terminal and did not see commands I had issued that I thought could have done this. This is probably something that I am ignorant of and do not need to worry about but just in case I thought I should post about it for others who may see this and be concerned.
Thanks for letting us know Bruce. It's not something I've done, but maybe the forum software had a glitch, who knows!....?
I will post the MD5 hashes of the uploaded files when I return home (in about 7 days)
---------- edit -----------
I just checked the attachment on post 1390. The forum link does indeed include 608081 (it also converts the dots to hyphens). However after a successful download the resultant file is pikify3.1.v8.zip.
My best guess is that you have an incomplete download, or you used a download manager that used the link to name the file rather than the meta data from the server....
Last edited:
Thank you for sharing this with the rest of us. Your instructions and attachments made it super easy to install ;-) I am surprised at how well the Mac Pro 1.1 runs with El Capitan. It actually runs a lot better with El Capitan. I am not sure what kind of magic sauce they have with El Capitan, but my Bruce X time went from around 35-40 seconds on Yosemite to a consistent 20 seconds on El Capitan. The other score that improved by a pretty good margin was LuxMark 2.1. The score with LuxMark 2.1 running Yosemite was normally around 1700, and now with El Capitan installed the score jumped to 2500.
My Mac Pro 1.1 runs really well with El Capitan. I really notice the difference when using Final Cut ProX. Installing El Capitan along with the AMD 280X, SSD drive and USB3.0 card definitely extends the life of this oldy but goody for another couple years. Thanks again to the Mac Rumors community and all of those involved in making this possible for the Mac Pro 1.1.
On a side note it is really sad that Apple no longer makes awesome machines like this any more. I have waited a long time for Apple to release a refresh but realized it was in vain. Unfortunately had to move on so decided to build a hackintosh. I would have really preferred to buy another Mac Pro with out all the hassles that go along with a hackintosh, but oh well at least I have a machine that runs OSX and Windows 10.
I think that you are right rthpjm. I am keenly aware of the gaps in my knowledge and these only seem to grow as I approach the 60th year of my life on this earth. Also in most cases I am guided by the principle of, "Better Safe Than Sorry". Anyway I right clicked on the zipped file and under More Info found:
Where from: https://forums.macrumors.com/attachments/pikify3-1-v8-zip.608081/. So I probably don't need to be concerned.
On a positive note I am hoping that it won't be much longer before I report a good solid install with no errors. I am so thankful for this forum, Piker-Alpha, you, 666sheep, donjames and Peter Holbrook.
Where from: https://forums.macrumors.com/attachments/pikify3-1-v8-zip.608081/. So I probably don't need to be concerned.
On a positive note I am hoping that it won't be much longer before I report a good solid install with no errors. I am so thankful for this forum, Piker-Alpha, you, 666sheep, donjames and Peter Holbrook.
Anyone can help me?, i have the latest version of "el capitan" in my mac pro 1.1, with radeon 4780 mac original, and all works fine, but yesterday, i do a PRAM, and the mac boots up, but when finish the load of the apple screen logo, the screen goes to black (but is on, the monitor receive signal) and nothing happens.
I think the PRAM / NVRAM do something wrong to this old mac pros with capitan. Anyone know whats the problem? look for solution in this thread and google, and no luck. sorry for my poor english. Regards.
I think the PRAM / NVRAM do something wrong to this old mac pros with capitan. Anyone know whats the problem? look for solution in this thread and google, and no luck. sorry for my poor english. Regards.
Anyone can help me?, i have the latest version of "el capitan" in my mac pro 1.1, with radeon 4780 mac original, and all works fine, but yesterday, i do a PRAM, and the mac boots up, but when finish the load of the apple screen logo, the screen goes to black (but is on, the monitor receive signal) and nothing happens.
I think the PRAM / NVRAM do something wrong to this old mac pros with capitan. Anyone know whats the problem? look for solution in this thread and google, and no luck. sorry for my poor english. Regards.
Hello Centrino,
My first suggestion would be to boot. If the monitor is still black once the system is up and running, then simply turn the monitor off, then turn the monitor back on again. My monitors occasionally lose their sync with the gfx card, this procedure works for me.
My second suggestion is to reboot, immediately after you hear the boot chime hold down the Alt key to enter the boot chooser. Make sure the correct volume is chosen for your intended system (when you clear the PRAM, the system will boot from the first available partition, which may not be the one you intend)
Thanks rthpjm, the disk boot is OK, and power off the monitor, nothing happens. But I disconnect the dvi cable and reconnect, and now the cursor mouse appears, but the screen is black, and the users screen don't appear.
Other issue is that if I try to start in safe mode, kernel panic with verbose mode with messages appears.
Thanks
Other issue is that if I try to start in safe mode, kernel panic with verbose mode with messages appears.
Thanks
HELP!!! ATI Original HD4870 Mac Pro 1.1 / 2.1 Yosemite 10.5.5 Tiamo FOSS 12GB Ram
I've got this from a friend who upgraded long ago and was having issues with this system. I upgraded it to Yosemite reaching the top of my skills (meaning by that that I'm a newbie and that it was "advanced" for my technical level). I used the Tiamo loader and FOSS. I have no graphics acceleration with the ATI HD4870 that's in this machine which is made for the Mac (it has a MDP port and all so it is not a flashed card). Originally I was able to select the resolution and all but there was quite a bit of flickering. Then I installed "QE_CI Exotic patch OS X Yosemite 10.10.0" from a post on insanelyMac in an effort to bring hardware acceleration to it. The patch was a couple of zipped kexts: AMD8400Controller.kext and ATIRadeonX2000.kext I used an utility called "Easy Kext Utility" version 2.0 in order to install the two kexts. Now, not only I do not have hardware acceleration but I cannot even change the resolution. Matters are now worse. I wonder if those kexts and the installer were meant for hackintoshes and therefore might not play well with reall MACs. Nevertheless, Can anyone please help me get hardware acceleration on my HD4870? I will be forever grateful.
Quick Parenthesis
I am resisting upgrading to "El Capitan" as my understanding is that "El Capitan" isn't themeable and I've read there are some utilities for theming Yosemite back to Snow Leopard (lol, sorry I have a serious problem with the aesthetics of most recent iterations of OSX).
Regards!!!
I've got this from a friend who upgraded long ago and was having issues with this system. I upgraded it to Yosemite reaching the top of my skills (meaning by that that I'm a newbie and that it was "advanced" for my technical level). I used the Tiamo loader and FOSS. I have no graphics acceleration with the ATI HD4870 that's in this machine which is made for the Mac (it has a MDP port and all so it is not a flashed card). Originally I was able to select the resolution and all but there was quite a bit of flickering. Then I installed "QE_CI Exotic patch OS X Yosemite 10.10.0" from a post on insanelyMac in an effort to bring hardware acceleration to it. The patch was a couple of zipped kexts: AMD8400Controller.kext and ATIRadeonX2000.kext I used an utility called "Easy Kext Utility" version 2.0 in order to install the two kexts. Now, not only I do not have hardware acceleration but I cannot even change the resolution. Matters are now worse. I wonder if those kexts and the installer were meant for hackintoshes and therefore might not play well with reall MACs. Nevertheless, Can anyone please help me get hardware acceleration on my HD4870? I will be forever grateful.
Quick Parenthesis
I am resisting upgrading to "El Capitan" as my understanding is that "El Capitan" isn't themeable and I've read there are some utilities for theming Yosemite back to Snow Leopard (lol, sorry I have a serious problem with the aesthetics of most recent iterations of OSX).
Regards!!!
Thanks rthpjm, the disk boot is OK, and power off the monitor, nothing happens. But I disconnect the dvi cable and reconnect, and now the cursor mouse appears, but the screen is black, and the users screen don't appear.
Other issue is that if I try to start in safe mode, kernel panic with verbose mode with messages appears.
Thanks
Hola Centrino,
Can you move the cursor off the screen on the left edge or the right edge? If you can (make the cursor go off an edge), then disconnect your DVI cable from the card and reconnect it to the other DVI port (assuming your card has at least 2 ports)....