2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

Rick W. · Jan 18, 2016

rthpjm said:
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:

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)

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'

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.

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.

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!

Happy to say my 2007 MacPro is now 8 core, 20hb ram and running El Capitan with no problems whatsoever. My thanks to all the people who made this possible.

Rick.

sweetspud · Jan 19, 2016

You guys, Pike et al. (forgive not being more specific!) are environmental heroes!

Watch this trailer a friend of mine worked on:

https://www.facebook.com/video.php?v=216005428736594

Keep those vintage machines on line as long as you can!!

Thank you guys!

jamgold · Jan 19, 2016

Anybody bit the bullet and upgraded to 10.11.3 yet?

jeanlain · Jan 19, 2016

Yep. It doesn't replace the boot.efi (I installed the delta update from Apple's website). Everything went smoothly.

jamgold · Jan 19, 2016

jeanlain said:
Yep. It doesn't replace the boot.efi (I installed the delta update from Apple's website). Everything went smoothly.

thank you. I will do the same and report back.

mavrik64 · Jan 19, 2016

Just wanted to thank all the clever folk on here for all their hard work. I've just finished installing El Capitan on my MacPro1 1. Also just updated it to 10.11.3 which it did just fine. Now to see what i can do about a half decent graphic card

Thanks Again

Mav

LaurentR2D2 · Jan 19, 2016

[doublepost=1453240491][/doublepost]

jamgold said:
thank you. I will do the same and report back.

Thank you. I've done the same, and everything works fine. Mac Pro rev 1,1 / ATI Radeon HD 5870 1024 Mb.

jamgold · Jan 19, 2016

LaurentR2D2 said:
[doublepost=1453240491][/doublepost]

Thank you. I've done the same, and everything works fine. Mac Pro rev 1,1 / ATI Radeon HD 5870 1024 Mb.

without a hitch. All is well after the upgrade

-texan- · Jan 19, 2016

Update to 10.11.3 from App Store - no problem att all. And it doesn't replace the boot.efi

mrhali · Jan 20, 2016

Hi rthpjm,

Thanks so much to you and all the amazing folks here like Pike, et al, for all your great work in the macpro1,1 community. I followed the below steps exactly but after I finish and reverify by trying to touch the boot.efi, I still get the Operation Not Permitted when I try to touch it again after the fact. This is after all the steps of disabling SIP (in Recovery), running the rootless-init (in Normal Boot), and then reenabling SIP (in Recovery), Do you have any ideas as to why this might be happening in the case?

Just to let you know about my install. I installed, not with your installer script, but by pulling the drive out and running the native installer on a newer mac. Then I disabled SIP, and grabbed the pikeralpha from source and updated the two locations by hand. Inserted the drive into the Macpro1,1, then made the drive be the startup drive and it came up fine. Then after that, I followed your instructions to install Boot64v3 including those Steps 1-4.

Then, I try to reverify with the below post and it doesn't seem to be working.

Let me know if you have any bright ideas!

Thanks!

rthpjm said:
Hello everyone,

If you have been using my Boot64 package to allow seamless upgrades to El Capitan (10.11.1 and 10.11.2), then be aware that I found the 10.11.2 update caused Boot64.v2 an issue. I believe that I have fixed the issue, and Boot64.v3.mpkg.zip is now posted back at #1391

However, those of you that have been using Boot64, and have already upgraded to 10.11.2 might wish to check if your system is working well with Boot64.

To check:
On your normal working El Capitan partition, open a Terminal and type

Code:

sudo -s [your password] touch /System/Library/CoreServices/boot.efi

If you get a response 'Operation not permitted', then we need to fix it. Sorry!

To fix it:

Download and install Boot64.v3.mpkg.zip from post #1391

Boot from the Recovery Partition

Once in the Recovery HD, open a Terminal from the Utilities menu

Code:

csrutil disable

Reboot back to your normal working El Capitan partition

Code:

sudo -s [your password] /usr/libexec/rootless-init exit

Reboot back into your Recovery HD

Once in the Recovery HD, open a Terminal from the Utilities menu

Code:

csrutil enable

Reboot back to your normal working El Capitan partition

You can test that the fix has worked by re-running the check code above again. This time there should be no message returned after the touch command is executed.

clawfinger · Jan 20, 2016

-texan- said:
Update to 10.11.3 from App Store - no problem att all. And it doesn't replace the boot.efi

********************************** PSA **********************************

App Store based System Updates from Jan 19th did in fact replace boot.efi on my system

PROCEED WITH CAUTION

********************************** PSA **********************************

Code:

Restored Jan 20, 2016, 8:49:41 AM]
Mac-Pro:test root$ cd /usr/standalone/i386/
Mac-Pro:i386 root$ ls -alO
total 31912
drwxr-xr-x   5 root  wheel  restricted      170 Oct 21 14:03 .
drwxr-xr-x   4 root  wheel  restricted      136 Sep 17 03:03 ..
drwxr-xr-x  14 root  wheel  restricted      476 Aug 22 22:20 EfiLoginUI
-rw-r--r--   1 root  wheel  restricted 15729264 Aug 22 18:29 Firmware.scap
-rw-r--r--   1 root  wheel  restricted   604728 Sep 22 01:15 boot.efi
Mac-Pro:i386 root$ md5 boot.efi
MD5 (boot.efi) = 046533fc6a5f6bc49e68e688e6522df5
Mac-Pro:i386 root$
Restored Jan 20, 2016, 9:26:52 AM]
Last login: Wed Jan 20 09:25:01 on console
Restored session: Wed Jan 20 09:17:28 EST 2016
Mac-Pro:i386 root$ ls -alO
total 31912
drwxr-xr-x   5 root  wheel  restricted      170 Jan 20 09:21 .
drwxr-xr-x   4 root  wheel  restricted      136 Sep 17 03:03 ..
drwxr-xr-x  14 root  wheel  restricted      476 Aug 22 22:20 EfiLoginUI
-rw-r--r--   1 root  wheel  restricted 15729264 Aug 22 18:29 Firmware.scap
-rw-r--r--   1 root  wheel  restricted   604728 Oct 31 07:33 boot.efi
Mac-Pro:i386 root$ md5 boot.efi
MD5 (boot.efi) = aaf7822574d77f3d3756cec5ab022213
Mac-Pro:i386 root$

clawfinger · Jan 20, 2016

My recommendation at this point would be to use the Delta Update available here:

https://support.apple.com/kb/DL1858?viewlocale=en_US&locale=en_US

As only the Combo update includes boot.efi:

Code:

Mac-Pro:ElCapitan_10.11.3_Updates root# ls -al
total 0
drwxr-xr-x  4 root  staff  136 Jan 20 10:54 .
drwx------+ 7 root  staff  238 Jan 20 10:50 ..
drwxr-xr-x  4 root  staff  136 Jan 20 10:30 OSXUpd10.11.3 Folder
drwxr-xr-x  3 root  staff  102 Jan 20 10:48 OSXUpdCombo10.11.3 Folder
Mac-Pro:ElCapitan_10.11.3_Updates root# find . -name boot.efi
./OSXUpdCombo10.11.3 Folder/manual Folder/OSXUpdCombo10.11.3 Folder/usr/standalone/i386/boot.efi
Mac-Pro:ElCapitan_10.11.3_Updates root#

Riwam · Jan 20, 2016

rthpjm said:
Follow these instructions if you have just installed El Capitan, or are already using El Capitan and want automatically put the modifications in place during updates.

============== Edit ==================
This has been tested from initial install 10.11 to 10.11.1, and from 10.11.1 to 10.11.2.
There may be an issue once at 10.11.2 which might prevent a smooth upgrade to 10.11.3 when it arrives - under investigation
For now it should work well....
I think it was just bad setup on my system (I had a bad entry in the paths file), worry over I hope!
===================================

While Pike is recuperating (take your time Pike ), I have figured out how to set up our working El-Capitan installs so that they will survive the Apple update mechanisms. You will need to install your choice of "pike yos fix" the updated version now called CapitanPikeFix is at post #1253 (courtesy of @666sheep) , or my very own Boot64 stuff, they both pretty much do the same thing. My Boot64 stuff installs a Launch Daemon that watches the boot.efi files, if they get changed (by the Apple update) it simply puts the Pike copies back!

"Ah, but SIP stops them working!" I hear you cry. True!

But, we can exclude the boot.efi files from SIP - here's how:

I will assume your working El-Capitan is on the hard disk named Macintosh HD - change it to suit

You don't need to do steps 1, 2, 3, and 4 if you have just used pikify3.1 (v3 or higher) to install El Capitan From the post above because it's already done for you)

Boot off another partition, I use the Recovery partition.

Open a Terminal

Code:

chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi echo "/System/Library/CoreServices/boot.efi" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths echo "/usr/standalone/i386/boot.efi" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths echo "/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths

Reboot from your other partition back into your normal El Capitan disk (Macintosh HD)

Install CapitanPikeFix, or my Boot64 (attached)

If you are going to install my Boot64, download the zip file below, unzip it, and double-click it, follow the installer prompts (you might need to allow it with Gatekeeper - if you get a "can't install" message, try opening System Preferences > Security & Privacy > General, look for the "Open anyway" button). If that doesn't work, choose 'Anywhere' from the options and try again... (Don't forget to put this option back to your preference after Boot64 is installed!)

Sit back and enjoy El-Capitan

I don't claim to have discovered this fix. I'm simply good at using search engines, and then realising how this fits together. The credit goes to the Hackintosh community again. See http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/

I've tested this with a clean install of El Capitan 10.11 and successfully installed the 10.11.1 update from the App Store, and from a clean install using the 10.11.1 downloadable update.

I will modify my pikify3.1 script bundle with this mod already in. Look out for ~~pikify3.1.v3.zip~~ pikify3.1.v#.zip at post #1390 ...

===================== Version 2 ============================

V2 includes mods to watch the SIP/Sandbox paths file in addition to the boot.efi files

===================== Version 3 ============================

Fixes an issue identified with the 10.11.2 update.
If you are using Boot64 AND you have already updated to 10.11.2 then you should probably check your system, see post #1484

*******
Hello rthpjm
A friendly person directed me to the method you post, which he used with success to install El Capitan.
My question is only if this procedure is intended just for MacPros 1.1, 2.1 or it can be used as well with entirely different macs.

In my case it would be a MacBook 4.1 early 2008.
Thank you very much in advance for your kind answer.

Ed

rkanaga · Jan 20, 2016

clawfinger said:

********************************** PSA **********************************

App Store based System Updates from Jan 19th did in fact replace boot.efi on my system

PROCEED WITH CAUTION

********************************** PSA **********************************

Code:

Restored Jan 20, 2016, 8:49:41 AM]
Mac-Pro:test root$ cd /usr/standalone/i386/
Mac-Pro:i386 root$ ls -alO
total 31912
drwxr-xr-x   5 root  wheel  restricted      170 Oct 21 14:03 .
drwxr-xr-x   4 root  wheel  restricted      136 Sep 17 03:03 ..
drwxr-xr-x  14 root  wheel  restricted      476 Aug 22 22:20 EfiLoginUI
-rw-r--r--   1 root  wheel  restricted 15729264 Aug 22 18:29 Firmware.scap
-rw-r--r--   1 root  wheel  restricted   604728 Sep 22 01:15 boot.efi
Mac-Pro:i386 root$ md5 boot.efi
MD5 (boot.efi) = 046533fc6a5f6bc49e68e688e6522df5
Mac-Pro:i386 root$
Restored Jan 20, 2016, 9:26:52 AM]
Last login: Wed Jan 20 09:25:01 on console
Restored session: Wed Jan 20 09:17:28 EST 2016
Mac-Pro:i386 root$ ls -alO
total 31912
drwxr-xr-x   5 root  wheel  restricted      170 Jan 20 09:21 .
drwxr-xr-x   4 root  wheel  restricted      136 Sep 17 03:03 ..
drwxr-xr-x  14 root  wheel  restricted      476 Aug 22 22:20 EfiLoginUI
-rw-r--r--   1 root  wheel  restricted 15729264 Aug 22 18:29 Firmware.scap
-rw-r--r--   1 root  wheel  restricted   604728 Oct 31 07:33 boot.efi
Mac-Pro:i386 root$ md5 boot.efi
MD5 (boot.efi) = aaf7822574d77f3d3756cec5ab022213
Mac-Pro:i386 root$

Did you do a delta update or was it the combo update that caused your Boot EFi to be replaced?

The update via the menu bar software update should only use the delta update AFAIK so should be safe?

clawfinger · Jan 20, 2016

@rkanaga I don't think there has been a "Software Update" option in the menu bar for many versions now, lol. There is an "App Store..." option that perhaps replaced it.

In any case, I installed 10.11.3 via the "standard" method of the App Store letting me know there were system updates available and then going to the Update tab in App Store and verifying what updates were available, and then doing an "Install All".

I'm not 100% sure there is an exact 1-to-1 correlation between the standalone update packages and that which comes from the App Store. I'm not saying the results are different per se, just that they may not be the exact same files.

The other update that I received at the same time was called "OS X El Capitan Recovery Update" which I haven't look into too much yet.

Basically, I wasn't trying to state an absolute fact, just that for my specific configuration (Mac Pro 3,1 that doesn't require Pike's macoxbootloader as it happens) the bootloader was in fact touched/replaced, which means it's possible that this may occur for others as well.

AFAIK Pike is mostly still recovering so I'm not sure what if any developments have gone on since his last release towards surviving updates, other than perhaps posts #1390/1391 by @rthpjm.

rkanaga · Jan 20, 2016

ok thanks, I stand corrected re the menu bar option, yes I meant the App Store option!

Do I understand correctly that you installed the OS X El Capitan Recovery Update as the same time and after this (and the 10.11.3 update) you noticed that the Boot EFi file had been replaced? In which case this makes sense as the Recovery Update definitely does replace the Boot Efi (as did the El Cap 10.10.2 updater.)

This might explain why others have installed only the 10.10.3 update and had no problems.

Still I would like to hear from anyone else who has safely installed only 10.10.3 before taking the plunge. As I have a non flashed GPU, if the Boot Efi gets replaced it's a bit of a pain to fix, involving putting the old GPU back in and rebooting from an old OS copy etc!

thanks for your reply

Robin

Ant3000 · Jan 20, 2016

I updated using the App store on a 1.1 / 2.1 and all seems good. I had done the Recovery Update a few weeks ago and assume this is the same update you were referring to as I wasn't offered a separate Recovery update this time. When I originally did the RU it did break booting into recovery, which I fixed with rthpjm's script although as others noted, Recovery on a 4 HD system isn't necessary if another OS is available to boot from should a problem arise.

rthpjm · Jan 20, 2016

mrhali said:
Hi rthpjm,

Thanks so much to you and all the amazing folks here like Pike, et al, for all your great work in the macpro1,1 community. I followed the below steps exactly but after I finish and reverify by trying to touch the boot.efi, I still get the Operation Not Permitted when I try to touch it again after the fact. This is after all the steps of disabling SIP (in Recovery), running the rootless-init (in Normal Boot), and then reenabling SIP (in Recovery), Do you have any ideas as to why this might be happening in the case?

Just to let you know about my install. I installed, not with your installer script, but by pulling the drive out and running the native installer on a newer mac. Then I disabled SIP, and grabbed the pikeralpha from source and updated the two locations by hand. Inserted the drive into the Macpro1,1, then made the drive be the startup drive and it came up fine. Then after that, I followed your instructions to install Boot64v3 including those Steps 1-4.

Then, I try to reverify with the below post and it doesn't seem to be working.

Let me know if you have any bright ideas!

Thanks!

Hello mrhali

I have a similar issue in my Mac 2,1 (1,1). I haven't figured out why yet.

Can you try the following for me please?...
Boot to your Recovery HD
Disable SIP (csrutil disable)
Reboot to the OS partition
Issue the command

Code:

sudo -s
[your password]
/usr/libexec/rootless-init

Does it return the phrase "...not trusted" ?

If you are worried about installing the 10.11.3 update, do it now with SIP disabled

Don't forget to boot into the Recovery HD and re-enable SIP.
[doublepost=1453326106][/doublepost]

Riwam said:
*******
Hello rthpjm
A friendly person directed me to the method you post, which he used with success to install El Capitan.
My question is only if this procedure is intended just for MacPros 1.1, 2.1 or it can be used as well with entirely different macs.
In my case it would be a MacBook 4.1 early 2008.
Thank you very much in advance for your kind answer.
Ed

It should work for the MacBooks too, you might want to do some research on your graphics card. The 4,1 has an Intel Graphics Media Accelerator (GMA) X3100 I believe. You need to consider if Mac OS X includes drivers for your card. If not, you will most like likely end up with El Capitan running without hardware graphics acceleration. Most people say this makes the machine nearly unusable. (It's not such a big problem for Mac Pro owners because we can simply upgrade to a supported graphics card)

-------- edit. -------
Isn't the 4,1 MacBook 64-bit efi?
If it is, surely this is a supported Mac without any need to use Pike's boot.efi files ( and therefore no need to run the pikified install method)
Anybody know for sure?....

OGNerd · Jan 20, 2016

rkanaga said:
Still I would like to hear from anyone else who has safely installed only 10.10.3 before taking the plunge.

I performed the 10.11.3 update from the App Store without incident.

Riwam · Jan 21, 2016

rthpjm said:
Hello mrhali

I have a similar issue in my Mac 2,1 (1,1). I haven't figured out why yet.

Can you try the following for me please?...
Boot to your Recovery HD
Disable SIP (csrutil disable)
Reboot to the OS partition
Issue the command

Code:

sudo -s [your password] /usr/libexec/rootless-init

Does it return the phrase "...not trusted" ?

If you are worried about installing the 10.11.3 update, do it now with SIP disabled

Don't forget to boot into the Recovery HD and re-enable SIP.
[doublepost=1453326106][/doublepost]
It should work for the MacBooks too, you might want to do some research on your graphics card. The 4,1 has an Intel Graphics Media Accelerator (GMA) X3100 I believe. You need to consider if Mac OS X includes drivers for your card. If not, you will most like likely end up with El Capitan running without hardware graphics acceleration. Most people say this makes the machine nearly unusable. (It's not such a big problem for Mac Pro owners because we can simply upgrade to a supported graphics card)

-------- edit. -------
Isn't the 4,1 MacBook 64-bit efi?
If it is, surely this is a supported Mac without any need to use Pike's boot.efi files ( and therefore no need to run the pikified install method)
Anybody know for sure?....

*****
Thank you very much.
As far as I know the MacBook doesn't need a tool for a 32 bit boot,that's true.
However it is not among Apple supported computers for OSX over Lion at its most.
The Graphic card has no graphic acceleration.
With for instance MCPF I got up to Mavericks and no further.
That was the reason I asked you if you believe your method could maybe work.
Thank you again for your goodwill to help.
Ed

Frixo Cool · Jan 21, 2016

I have just updated my Mac Pro 2,1 to 10.11.3 via AppStore without any problems. Thanks everyone for such a great community here!

cgezzy · Jan 21, 2016

I'm having a lil trouble with My Mac Pro 1,1. I've can boot the OS X El Capitan Installer it appears to think about for a lil while and then boots my the startup drive. I'm currently using A Mac Pro 1,1 with 16 GB RAM running 10.6.8. Am I making too much of a leap from 10.6.8 to 10.11? I also had to make the bootable partition on a different Mac Pro 3,1 running 10.11 because I was receiving error that the partition wasn't able to be unmounted. Is there a additional step I need because of that? Sorry if this has already been answered, I did try scan though the post but 71 pages is a lot. Thanks for your help.

cgezzy · Jan 21, 2016

cgezzy said:
I'm having a lil trouble with My Mac Pro 1,1. I've can boot the OS X El Capitan Installer it appears to think about for a lil while and then boots my the startup drive. I'm currently using A Mac Pro 1,1 with 16 GB RAM running 10.6.8. Am I making too much of a leap from 10.6.8 to 10.11? I also had to make the bootable partition on a different Mac Pro 3,1 running 10.11 because I was receiving error that the partition wasn't able to be unmounted. Is there a additional step I need because of that? Sorry if this has already been answered, I did try scan though the post but 71 pages is a lot. Thanks for your help.

I've got it working now. I had to install 10.11.3 a Mac Pro 3,1 then copy in the boot.efi files and the place the HD in the Mac Pro 1,1

sgt-killer · Jan 22, 2016

LaurentR2D2 said:
[doublepost=1453240491][/doublepost]

Thank you. I've done the same, and everything works fine. Mac Pro rev 1,1 / ATI Radeon HD 5870 1024 Mb.

Hi LaurentR2D2 can you tell me if your ATI Radeon HD 5870 1024 Mb is modified in any way or just a straight install in the MacPro 1,1 and working with El Capitan without any problems, I've just got a ATI Radeon HD 5870 and going to install it but just want to make sure I won't get any problems.

LaurentR2D2 · Jan 23, 2016

sgt-killer said:
Hi LaurentR2D2 can you tell me if your ATI Radeon HD 5870 1024 Mb is modified in any way or just a straight install in the MacPro 1,1 and working with El Capitan without any problems, I've just got a ATI Radeon HD 5870 and going to install it but just want to make sure I won't get any problems.

Sorry for the late answer. I've just installed my card in my Mac Pro without touching anything. It's a genuine Apple graphic card, not a PC flashed one. It works perfectly.

2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

macrumors newbie

macrumors member

macrumors member

macrumors 68020

macrumors member

macrumors newbie

macrumors member

macrumors member

macrumors member

macrumors newbie

macrumors newbie

macrumors newbie

macrumors 65816

macrumors member

macrumors newbie

macrumors member

macrumors 6502

macrumors 6502a

macrumors regular

macrumors 65816

macrumors regular

macrumors newbie

macrumors newbie

macrumors newbie

macrumors member

Our Staff