In that case, I'll be holding off. Was almost done creating the USB except for bootbase.efi.
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
In that case, I'll be holding off. Was almost done creating the USB except for bootbase.efi.
Bruce,
Did your Mac Pro come with bluetooth? Is it original or have you upgraded to the newest one? The older chipsets are not compatible I think, not sure since mine is not equip with bluetooth. Might be something to look into, my 2006 MP has been rock solid through all the public betas and through to 10.11.1
Did your Mac Pro come with bluetooth? Is it original or have you upgraded to the newest one? The older chipsets are not compatible I think, not sure since mine is not equip with bluetooth. Might be something to look into, my 2006 MP has been rock solid through all the public betas and through to 10.11.1
In Terminal you will need to show hidden file using the following commands:
defaults write com.apple.finder AppleShowAllFiles YES
killall Finder
Open a Finder window. Even thought the :”usr” directory is greyed out, it will open if clicked on and the “standalone” and “i386” directories are not greyed out. You may need to switch the view in the Finder from Icon to List.
The two directories are: /usr/standalone/i386/ and /System/Library/Coreservices/. The boot.efi in the CoreServices folder was write protected so I clicked on it once, hit CMD+I to show information and disabled the protection. Once I did that I could replace the boot.efi. I checked the size of the new boot efis twice as they should have 314/315 kb, not 600 something as the original ones had.
Dfritchie, no it did not. I found one as I remember for a less that the local store wanted and installed it myself. I was more of a pain than I anticipated. If you look long enough you can probably find one at a reasonable price. Good luck with your search.
Sorry for taking so long to respond Don. If I remember correctly from when I began following these instructions bootbase.efi as a file. That is about all I remember. The author of the instructions, Peter Holbrook said, "Please, stop quoting those instructions. They need to be rewritten! In this case, except for the replacement of boot.efi, the entire section needs to be summarily dismissed! So I would just wait until the members of the group who have a deep understanding of how this process works figure out what works for those of us who have Mac Pro 1,1's and 2.1's.
I just fried my RAID 0 array so have to clean install a new OS.
So skipping the bootbase.efi step, post-install wouldn't the system just boot? Yosemite was as simple as making a USB installed and replacing boot.efi (or installing package).
EDIT: Attempting to do an install right now. I assume it is necessary to cp the boot.efi using terminal to the drive after installation.
Apologize for the double post.
UPDATE: Let me be the first to report on Bruce L's guide. Successful installation of El Capitan.
Here's some things I did:
- Create the USB per Bruce L's instructions (same process as instructions posed by others for OS X Yosemite and previous versions)
- Clean install El Capitan
- Reboot back into USB after installation
- Used terminal to run csrutil disable (which disables SIP, don't reboot, unsure if it has any effect)
- Used terminal to rm -rf /Volumes/Macintosh\ RAID/System/Library/CoreServices/boot.efi
- then cp /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi /Volumes/Macintosh\ RAID/System/Library/CoreServices
- Reboot into OS X El Capitan
- Don't attempt to run repair permissions on the drive as you may fry your install if OS X changes the perms on the copied boot.efi (unconfirmed but, I personally would not risk it)
- Running OS X El Capitan 10.11.1 downloaded off MAS.
Completely Unrelated Notes (for those interested in reading):
On a side note, why I upgraded was because my system crashed running Yosemite. Had to cp -r important directories off my SSD RAID 0 array as the OS X Yosemite installations got fried after multiple hard power offs, corrupting the files. It was up to reinstalling Yosemite or the perfect time to upgrade.
Further, I am running 3x 30" ACDs and one of them (left display) shows dancing green lines (the display works fine if only two are connected), was hoping El Capitan would fix it however, problem still exists. The UI smoothness is worlds apart from Yosemite as driving 7680x1600 pixels feels as smooth as any other display arrangement. Thankfully one can disable mouse shake animation in El Capitan. The algorithms are absolutely poor as moving the cursor from one display to another then back to the first display, it causes the cursor to explode.
My PS/2 keyboard no longer works with a PS/2 to USB adapter. With Yosemite, I would have to reboot often as it was not always detected upon boot, now it's completely non-functional.
Apologize for the double post.
UPDATE: Let me be the first to report on Bruce L's guide. Successful installation of El Capitan.
Here's some things I did:
- Create the USB per Bruce L's instructions (same process as instructions posed by others for OS X Yosemite and previous versions)
- Clean install El Capitan
- Reboot back into USB after installation
- Used terminal to run csrutil disable (which disables SIP, don't reboot, unsure if it has any effect)
- Used terminal to rm -rf /Volumes/Macintosh\ RAID/System/Library/CoreServices/boot.efi
- then cp /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi /Volumes/Macintosh\ RAID/System/Library/CoreServices
- Reboot into OS X El Capitan
- Don't attempt to run repair permissions on the drive as you may fry your install if OS X changes the perms on the copied boot.efi (unconfirmed but, I personally would not risk it)
- Running OS X El Capitan 10.11.1 downloaded off MAS.
Completely Unrelated Notes (for those interested in reading):
On a side note, why I upgraded was because my system crashed running Yosemite. Had to cp -r important directories off my SSD RAID 0 array as the OS X Yosemite installations got fried after multiple hard power offs, corrupting the files. It was up to reinstalling Yosemite or the perfect time to upgrade.
Further, I am running 3x 30" ACDs and one of them (left display) shows dancing green lines (the display works fine if only two are connected), was hoping El Capitan would fix it however, problem still exists. The UI smoothness is worlds apart from Yosemite as driving 7680x1600 pixels feels as smooth as any other display arrangement. Thankfully one can disable mouse shake animation in El Capitan. The algorithms are absolutely poor as moving the cursor from one display to another then back to the first display, it causes the cursor to explode.
My PS/2 keyboard no longer works with a PS/2 to USB adapter. With Yosemite, I would have to reboot often as it was not always detected upon boot, now it's completely non-functional.
Last edited:
Hello
I have a MacPro1,1 and a MacPro5,1.
I just installed El Capitan 10.11 on an SSD (from my 5,1) using a bootable usb that i made on the 5,1.
Took the SSD out from the 5,1 and put it into the 1,1.
Turned on 1,1 and booted from the original drive which has 10.7.5 and downloaded the boot.efi (v3.1)
I went to terminal and typed "defaults write com.apple.finder AppleShowAllFiles YES"
then typed "killall Finder"
then i replaced the boot.efi file in usr/standalone/i386
then i replaced the boot.efi file in System/Library/CoreServices
rebooted the 1,1 with the SSD running El Capitan 10.11 and it worked fine!
Then I downloaded the 10.11.1 update from the website, ran the installer then upon reboot it booted back to the 10.7.5 drive.
So I went back to do the same thing as above to replace the boot.efi (v3.1) files in those two places and i could do it in the i386 folder but the one in the CoreServices folder was locked.
I tried to type in terminal "chflags nouchg boot.efi" and it said file could not be found
tried to type "chflags nouchg" then drag and drop the locked boot.efi file to terminal to get the exact file address and it said permission denied or operation not permitted
So I tried to start all over again, formatted the SSD and reinstalled 10.11 from the MacPro5,1 then brought it over to the 1,1 and booted with 10.7.5. This time, the boot.efi file was locked in CoreServices again and I had no luck to unlock it.
Please help! I have no idea how to unlock the boot.efi file. I tried unlocking it by putting the SSD drive into the 5,1 but that didnt work either.
I have a MacPro1,1 and a MacPro5,1.
I just installed El Capitan 10.11 on an SSD (from my 5,1) using a bootable usb that i made on the 5,1.
Took the SSD out from the 5,1 and put it into the 1,1.
Turned on 1,1 and booted from the original drive which has 10.7.5 and downloaded the boot.efi (v3.1)
I went to terminal and typed "defaults write com.apple.finder AppleShowAllFiles YES"
then typed "killall Finder"
then i replaced the boot.efi file in usr/standalone/i386
then i replaced the boot.efi file in System/Library/CoreServices
rebooted the 1,1 with the SSD running El Capitan 10.11 and it worked fine!
Then I downloaded the 10.11.1 update from the website, ran the installer then upon reboot it booted back to the 10.7.5 drive.
So I went back to do the same thing as above to replace the boot.efi (v3.1) files in those two places and i could do it in the i386 folder but the one in the CoreServices folder was locked.
I tried to type in terminal "chflags nouchg boot.efi" and it said file could not be found
tried to type "chflags nouchg" then drag and drop the locked boot.efi file to terminal to get the exact file address and it said permission denied or operation not permitted
So I tried to start all over again, formatted the SSD and reinstalled 10.11 from the MacPro5,1 then brought it over to the 1,1 and booted with 10.7.5. This time, the boot.efi file was locked in CoreServices again and I had no luck to unlock it.
Please help! I have no idea how to unlock the boot.efi file. I tried unlocking it by putting the SSD drive into the 5,1 but that didnt work either.
Last edited:
I had the same "Operation Not Permitted" when I attempted to cp the boot.efi from the USB to the drive. Boot into the USB (OS X El Capitan Installer) and delete the boot.efi on your drive first then, cp it from the USB to the drive.
- Used terminal to rm -rf /Volumes/YOUR-HDD-NAME-HERE/System/Library/CoreServices/boot.efi
- then cp /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi /Volumes/YOUR-HDD-NAME-HERE/System/Library/CoreServices
You might have to use sudo if you're doing that while running Lion hence, I recommend booting into the USB installer which should probably have greater r/w permissions (or at least I didn't have to nouchg the file as it didn't appear locked against deletion).
Sorry i dont understand what is "used terminal to rm"
and "then cp"
what are these abbreviations? is that part of the terminal command?
what do those commands do? unlock the boot.efi file?
EDIT:
okay i dont know how it worked but
i booted into the USB Installer for El Capitan
Opened terminal and typed:
rm -rf /Volumes/YOUR-HDD-NAME-HERE/System/Library/CoreServices/boot.efi
cp /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi /Volumes/YOUR-HDD-NAME-HERE/System/Library/CoreServices
then rebooted to that drive and it was unlocked! replaced the files manually.
Attachments
Last edited:
Hi Don,
First. Please read what PeterHolbrook said in #post1066 because most of what Bruce wrote – sorry Bruce – is history now!
1.) We now have SMBIOS board-id injection, which tells the App Store and Installers that you have a supported Mac Model. In short. There is no need to edit files anymore!
2.) Another new feature is automatic Installer detection, and thus you can now use boot.efi as replacement for both boot.efi and bootbase.efi – but you will have to rename boot.efi to bootbase.efi yourself after the download – and boot.efi will take care of the required SIP (System Integrity Protection) settings, so that the Installers runs without issues.
3.) Apple won't let us load kexts, which we need when there is no prelinkedkernel, but another new feature also takes care of this restriction.
This was also why it took me six weeks to finish my work, because A) I don't have unsupported hardware myself, and B) There is no documentation whatsoever that helped me to implement it. And most of what you can find on the Internet now about SIP, was written either with my help, of by people who used my work without giving appropriate credits – which sucks, but that is the Internet where people can cheat, steal and lie without repercussions. Buy hey, such is life.
I'd also like to thank the handful of people who donated, as a token of appreciation for my hard work, and hope that others will follow, because what I had to do was far more work than what I did when I added support for Yosemite. Thanks!
I'd also like to thank the nightly testers, because without their help... you won't have had what you have now... which is support for El Capitan. Thank you!
Note: Most of what I wrote here is not addressed at you, but to the general public.
-Pike
Last edited:
rm is for remove - cp is for copy.
You add -rf to the rm command to make sure the file is going to be removed regardless of its contents (-r for recursive) or read/write privileges (-f for force, so if the file is locked, this argument takes care of that)
As for cp, only 2 arguments are needed here, the source directory, and the target directory.
First of all, in my first post here, I want to give a big thank you to Pike and all the people involved in testing of the boot.efi file that gave an extra live to my Mac Pro. What a great work you have done!. Thank you very much
I've been using the boot.efi since Yosemite and now on El Capitan and after reading a lot of posts I decide to share my experience with to objective to try to help or simply give my feedback.
In terms of hardware as I say I have a Mac Pro 1,1 2006 with a Nvidia PC Graphic Card Asus GeForce GT740 OC 2GB GDDR5 PCI-E. Since I have a pc card I cannot see the boot screen neither intaller or otherthings until the login window. The graphic card works with yosemite and el capitan native driver but is recomended to instal latest nvidia webdriver. I had some kernel panics that lead to 2 or 3 reboots before login wind. After that instal the webdriver and everything went good.
I do not have an extra mac that supports yousemite or el capitan and after several trials I found a diferent way to install the OSX with the Pike boot efi. I've done this to yousemite and after to el capitan but you can do it, probably in any machine or system.
1-I started to install the OSX in a virtual machine. I've used Vmware.
2-After this I created a account (like a normal osx install).
3-With disk utility I've done a OSX disk image. After disk image is done you should do a scan/check of the disk image with this utility. I think in yosemite is scan image for restore ( I am not in front of my mac sorry).
4-After this you shold copy the osx image file to your "normal" mac startup system (desktop for example)
5-Create a partition for your new OSX instalation;
6-Restore the osx image created on the virtual machine;
7-Replace the boot efi in their locations;
8-Repair the new disk partition with you current system disk utility.
9-Your new osx should appear now (also in previous step) on your startup disks; Select it and reboot.
Now you should see your login window.
The only thing is that I could not have the recovery Hd but in my case I can not use it. I think you can restore with carbon copy cloner for example.
Hope this can help someone.
Take care
I've been using the boot.efi since Yosemite and now on El Capitan and after reading a lot of posts I decide to share my experience with to objective to try to help or simply give my feedback.
In terms of hardware as I say I have a Mac Pro 1,1 2006 with a Nvidia PC Graphic Card Asus GeForce GT740 OC 2GB GDDR5 PCI-E. Since I have a pc card I cannot see the boot screen neither intaller or otherthings until the login window. The graphic card works with yosemite and el capitan native driver but is recomended to instal latest nvidia webdriver. I had some kernel panics that lead to 2 or 3 reboots before login wind. After that instal the webdriver and everything went good.
I do not have an extra mac that supports yousemite or el capitan and after several trials I found a diferent way to install the OSX with the Pike boot efi. I've done this to yousemite and after to el capitan but you can do it, probably in any machine or system.
1-I started to install the OSX in a virtual machine. I've used Vmware.
2-After this I created a account (like a normal osx install).
3-With disk utility I've done a OSX disk image. After disk image is done you should do a scan/check of the disk image with this utility. I think in yosemite is scan image for restore ( I am not in front of my mac sorry).
4-After this you shold copy the osx image file to your "normal" mac startup system (desktop for example)
5-Create a partition for your new OSX instalation;
6-Restore the osx image created on the virtual machine;
7-Replace the boot efi in their locations;
8-Repair the new disk partition with you current system disk utility.
9-Your new osx should appear now (also in previous step) on your startup disks; Select it and reboot.
Now you should see your login window.
The only thing is that I could not have the recovery Hd but in my case I can not use it. I think you can restore with carbon copy cloner for example.
Hope this can help someone.
Take care
Hello Pike. I really appreciate everything you've done to keep my old MacPro 1,1 still relevant. I'm running Yosemite thanks to your hard work. Obviously I'm keen to install El Capitan and have downloaded the current version of your boot.efi from your project page. However, I have no idea what to do next. Do I download El Capitan to a second supported Mac and do all the jiggery pokery outlined at the start of this thread? Or does your downloaded boot.efi somehow install on my Yosemite running machine so, after entering the line(s) of code listed on your project page into the Terminal, I can then download El Capitan direct from the MacApp store and then install? Any help would be gratefully received.
Yours, MacIdiot.
Yours, MacIdiot.
Last edited:
Hi Pike,
Thanks for telling me the status.
How do we use "SMBIOS board-id injection"?
Thanks for all of your hard work.
Sincerely,
Don James
Hi Bruce,
Thanks for the update. I was unable to install El Capitan.
You are right -- we should wait for complete and final instructions for installing El Capitan.
Sincerely,
Don James
You don't need to do anything. What Pike means is that the App Store sees your Mac Pro as a compatible model, which allows you to download 10.11 directly.
Hi all,
I have already been running El Capitan for a month on my MacPro 2,1 now. Are there any known issues with the El Capitan update that came out a couple of days ago? Is it safe to update or will it erase my working boot.efi?
Thanks! Keep up the good work!
I have already been running El Capitan for a month on my MacPro 2,1 now. Are there any known issues with the El Capitan update that came out a couple of days ago? Is it safe to update or will it erase my working boot.efi?
Thanks! Keep up the good work!
You have to put his latest boot.efi in /System/Library/CoreServices and /usr/standalone/i386.
Put Pike's efi (v3.2) in the usual places and reboot. At that point you should be able to download the installer. What I'm struggling with is what to do after that; haven't worked up the energy to re-read the entire thread to find out. Just running the installer doesn't work. I may just borrow my daughter's laptop and use the target-disk installation method instead.