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

[james1129]

I actually don't use any script so I had to do it manually
If you use CapitanPikeFix probably should work but I can't help you, sorry

How would you suggest I boot back up my Mac since both my .efi's were replaced? I had the "fix" for the updates installed but apple must have worked around that. Now I'm in this endless loop of booting into OS X utilities. Is my best bet to just rerun the original installer for El Capitan? I'm having an especially hard time since my keyboard is wireless (cant seem to boot the recovery drive with a wireless keyboard)

 

[mmonse_de]

How would you suggest I boot back up my Mac since both my .efi's were replaced? I had the "fix" for the updates installed but apple must have worked around that. Now I'm in this endless loop of booting into OS X utilities. Is my best bet to just rerun the original installer for El Capitan? I'm having an especially hard time since my keyboard is wireless (cant seem to boot the recovery drive with a wireless keyboard)

Best would be to boot from another HD or USB stick (the pikify Stick should work if it had been blessed after install) and replace the boot efis via terminal. Or if you have a Mac with a FireWire, you can start the Pro in target mode and connect it to the running mac to replace the two files. And the startup shortcuts (alt-T, alt-R and so on) should work with a wireless (bluetooth) Apple keyboard. But your description sounds like the problem with a non-blessed USB stick after install... Read some pages above here.

 

[Frixo Cool]

Just to confirm that upgrade to 10.11.4 went smooth on Mac Pro 2,1 using the App Store and Boot64.v3.mpkg.

Thanks a lot guys, your support is ace! Long live Mac Pro!

 

[mmonse_de]

On my machine it didn't work (2.1) After the reboot prompt it just showed the grey folder sign with the ? inside...
Now I will use my MacBookPro to connect the MP in Target mode and replace the boot efis.
I'll report later....

 

[james1129]

Best would be to boot from another HD or USB stick (the pikify Stick should work if it had been blessed after install) and replace the boot efis via terminal. Or if you have a Mac with a FireWire, you can start the Pro in target mode and connect it to the running mac to replace the two files. And the startup shortcuts (alt-T, alt-R and so on) should work with a wireless (bluetooth) Apple keyboard. But your description sounds like the problem with a non-blessed USB stick after install... Read some pages above here.

My trouble is two fold, my monitor is run by the video card with an hd adaptor. It's Mac 1,1 so the display for the recovery menu is not visible even if I can get the wireless keyboard to get me there. The Bluetooth keyboards cannot get me there though, because they do not register key presses until 5 seconds after chime. I need to get a wired keyboard and an old display cable.

 

[dcloud45]

have the efi files been updated yet or the old ones still work?

 

[mmonse_de]

have the efi files been updated yet or the old ones still work?

to be sure, you should dl the latest version of pikify (v3.1 v8) there's imho the latest version of the boot efi included.
[doublepost=1458679230][/doublepost]OS X 10.11.4 is up and running on my machine! CapitanPikeFix lost the battle against Apple ! The reboot whilst install ended with the grey screen and the ?-folder. So I started the MP in target-mode and connected with my MBP (currently on 10.11.3). I swapped the boot.efis with those from the pikify-folder and rebooted. Install went on normally, it took about 5min until my MP was "alive" again. I couldn't resist and rebooted, that worked fine! Now I will have a look and discover the new features of 10.11.4

 

[chackett]

My trouble is two fold, my monitor is run by the video card with an hd adaptor. It's Mac 1,1 so the display for the recovery menu is not visible even if I can get the wireless keyboard to get me there. The Bluetooth keyboards cannot get me there though, because they do not register key presses until 5 seconds after chime. I need to get a wired keyboard and an old display cable.

The easiest thing to do, if it's an option for you, is to put something that will boot (USB stick or USB external drive) on the computer and then restart. It will automatically (after a while) boot onto the non-El Capitan drive without any interaction from you. At least that's what happens on my computer - it always has an external USB drive with Mavericks installed attached. That's how I know the boot.efi files were replaced - when I see that Mavericks log-in screen. And I'm in the same situation you are; my video card doesn't display the boot-up screens.

 

[charlan7]

to be sure, you should dl the latest version of pikify (v3.1 v8) there's imho the latest version of the boot efi included.
[doublepost=1458679230][/doublepost]OS X 10.11.4 is up and running on my machine! CapitanPikeFix lost the battle against Apple !

Not for me: CapitanPikeFix works for me.

 

[dcloud45]

Not for me: CapitanPikeFix works for me.

ok so went with the update now my mp is stuck in the reboot ,grey screen with apple logo and line on the bottom ,but the line doesn't move. any ideas?

 

[bullschuck]

Really excited to get the Mac Pro 1.1 up to 10.11.3 today. Finally got the right kind of installer. Thanks to rthpjm, Pike, and Tiamo for accomplishing all this.

One issue, I put my Apple ID and password in during the setup and the thing just kept running. I walked away for a half hour, still running. So I rebooted and selected to skip setting up for iCloud and the App Store.

Now I'm trying to sign into the App Store. Been looking at that spinning wheel for several minutes. Probably 10. Any advice? I still have a 10.6 partition on another HD. Could that be goofing this up?

FYI, 2 x 2.66 MHz Dual Core, 13 GB Ram, ATI Radeon HD 4870 512 MB, if anyone asks.

Thanks,

Bull

 

[mmonse_de]

Really excited to get the Mac Pro 1.1 up to 10.11.3 today. Finally got the right kind of installer. Thanks to rthpjm, Pike, and Tiamo for accomplishing all this.

One issue, I put my Apple ID and password in during the setup and the thing just kept running. I walked away for a half hour, still running. So I rebooted and selected to skip setting up for iCloud and the App Store.

Now I'm trying to sign into the App Store. Been looking at that spinning wheel for several minutes. Probably 10. Any advice? I still have a 10.6 partition on another HD. Could that be goofing this up?

FYI, 2 x 2.66 MHz Dual Core, 13 GB Ram, ATI Radeon HD 4870 512 MB, if anyone asks.

Thanks,

Bull

Maybe it was a bad idea to connect with Apple shortly after many updates for all devices had been issued....
I just had trouble with the iOS 9.3 download via iTunes, 2times Apple kicked me out. Now it has loaded, but very slow connection.
[doublepost=1458715118][/doublepost]

Not for me: CapitanPikeFix works for me.

Nice to hear.
The funny thing is that on nearly identical MP's, some work with CPF, some not. And I heard/read nearly the same thing with the "Boot64"-script.
It would be interesting to examine that for future updates...

My idea why it didn't work for me is my home-brewed fusion drive. During the initial setup it wasn't possible to install EC onto a FD until pikify3.1 v6.
Maybe CapitanPikeFix is missing the correct code lines for fusion drives....

 

[pveatx]

Managed to upgrade my MacPro 1,1 to 10.11.4 yesterday. After upgrade, the system rebooted in recovery mode.

I opened a terminal and copied the Pikify boot.efi to the correct places:

cd /Volumes/Drive\ 2/Users/pveatx/pikify3.1
chflags nouchg /Volumes/Drive\ 2/System/Library/CoreServices/boot.efi
cp boot.efi /Volumes/Drive\ 2/System/Library/CoreServices/boot.efi
cp boot.efi /Volumes/Drive\ 2/usr/standalone/i386/boot.efi
reboot

And it worked...

 

[rthpjm]

The App Store update for 10.11.4 does contain /usr/standalone/i386/boot.efi. Apple seems to distribute to here and then copy this to /S/L/CoreServices/boot.efi.

So yes, MAS (OSXUpd10.11.4Patch.pkg), and the Support downloads (incremental OSXUpd10.11.4.pkg
and cumulative OSXUpdCombo10.11.4.pkg) will replace the efi.

I had SIP disabled, and Boot64 launch daemon running, so my MAS update worked nicely....
I expect those with SIP disabled and CapitanPikeFix installed will also have a smooth upgrade.

I have not tried SIP enabled (with boot.efi excluded - 2 locations), and Boot64 yet...

 

[F1Mac]

The App Store update for 10.11.4 does contain /usr/standalone/i386/boot.efi. Apple seems to distribute to here and then copy this to /S/L/CoreServices/boot.efi.

So yes, MAS (OSXUpd10.11.4Patch.pkg), and the Support downloads (incremental OSXUpd10.11.4.pkg
and cumulative OSXUpdCombo10.11.4.pkg) will replace the efi.

I had SIP disabled, and Boot64 launch daemon running, so my MAS update worked nicely....
I expect those with SIP disabled and CapitanPikeFix installed will also have a smooth upgrade.

I have not tried SIP enabled (with boot.efi excluded - 2 locations), and Boot64 yet...

Goog to know rthpjm, thanks. On a side note, I'm regularly reading this thread even if I don't have any issue with 10.11 on my 1,1 - and I'd like to emphasize your contribution to this thread. I'll just take a moment to say thank you, for your time and the invaluable help you're providing to others.

 

[rthpjm]

Goog to know rthpjm, thanks. On a side note, I'm regularly reading this thread even if I don't have any issue with 10.11 on my 1,1 - and I'd like to emphasize your contribution to this thread. I'll just take a moment to say thank you, for your time and the invaluable help you're providing to others.

Thanks Morpheo, appreciate your comment...

 

[Mr. Zarniwoop]

I have not tried SIP enabled (with boot.efi excluded - 2 locations), and Boot64 yet...

Boot64 with SIP worked for me. Used 10.11.4 App Store update.

 

[bullschuck]

Maybe it was a bad idea to connect with Apple shortly after many updates for all devices had been issued....
I just had trouble with the iOS 9.3 download via iTunes, 2times Apple kicked me out. Now it has loaded, but very slow connection.

I left that wheel spinning overnight and it was in the same place this morning.

I then created a new Apple ID, same result. I went downstairs and logged into the App Store on another Mac I
have (I asked it to check my account info) and had no problems. I don't think it's some kind of latency on Apple's side.

Maybe it's trying to pre-fetch 10.11.4?

FYI, I did use pikify 3.1.8 and boot64. I did realize this AM that I haven't restarted it since applying boot64. So I rebooted it before I left the house for work today. We'll see if that cleared anything up.

Anybody else seen this kind of issue?

 

[mmonse_de]

I left that wheel spinning overnight and it was in the same place this morning.

I then created a new Apple ID, same result. I went downstairs and logged into the App Store on another Mac I
have (I asked it to check my account info) and had no problems. I don't think it's some kind of latency on Apple's side.

Maybe it's trying to pre-fetch 10.11.4?

FYI, I did use pikify 3.1.8 and boot64. I did realize this AM that I haven't restarted it since applying boot64. So I rebooted it before I left the house for work today. We'll see if that cleared anything up.

Anybody else seen this kind of issue?

absolutely no. All Apple-ID issues work fine for me with 11.4.
There was an iTunes update together with the 11.4 update. Maybe there something went wrong.
And sometimes it helps to completely disconnect all items Apple-ID-related (cloud, iTunes,App Store and so on) and then connect again

 

[cdmawolf]

absolutely no. All Apple-ID issues work fine for me with 11.4.
There was an iTunes update together with the 11.4 update. Maybe there something went wrong.
And sometimes it helps to completely disconnect all items Apple-ID-related (cloud, iTunes,App Store and so on) and then connect again

When I initially tried to download I hit "Update All" and it hung. I cancelled and just downloaded 10.11.4 upd
and it worked fine without iTunes in the download.

 

[mmonse_de]

When I initially tried to download I hit "Update All" and it hung. I cancelled and just downloaded 10.11.4 upd
and it worked fine without iTunes in the download.

IMHO that is the problem: There has to be an issue with the update to 10.11.4 and the (missing) iTunes update. iTunes is a mighty tool for OS X , not only managing your music and videos. Idk whether there's a way to update iTunes without apple-ID, maybe directly from the Apple website... I'd give that a try

 

[dreamersofeden]

Mac Pro 2,1 (3GHz 8-core) updated from 10.11.3 to 10.11.4 via App Store update.
After the installation finished, I rebooted and, as expected, it didn't boot.
Replaced the two EFI files (http://piker-alpha.github.io/macosxbootloader/ -> Download "boot_grey.efi" -> Rename it to: "boot.efi") at:
/System/Library/CoreServices/boot.efi
and
/usr/standalone/i386/boot.efi

Rebooted and it worked like a charm again.
It's the same process as always.

 

[bullschuck]

absolutely no. All Apple-ID issues work fine for me with 11.4.
There was an iTunes update together with the 11.4 update. Maybe there something went wrong.
And sometimes it helps to completely disconnect all items Apple-ID-related (cloud, iTunes,App Store and so on) and then connect again

Apologies if I wasn't clear. I did not attempt the 10.11.4 upgrade. I was just trying to log in to the App Store for the first time after using pikify3.1.8 and boot64 to install El Capitan with the 10.11.3 installer.

I got home today and the thing had booted back to 10.6.8. I rebooted, held down the option key, booted into 10.11.3. Then I pulled up iTunes, went through the EULA and such. Then declined the update and tried to sign in to the Apple Store. I'm getting the spinning wheel.

The password is correct. I know because it will error out right away when I use an incorrect one. The account opens fine on other Macs, even other Macs on the same network.

Anybody else had this kind of issue? Trouble logging into the App Store or iTunes?

Thanks,

Bull

 

[dcloud45]

ok got it working . now one problem am trying to replace the recovery partition file but again its locked and i can get it replace.

 

[JedNZ]

Mac Pro 2,1 (3GHz 8-core) updated from 10.11.3 to 10.11.4 via App Store update.
After the installation finished, I rebooted and, as expected, it didn't boot.
Replaced the two EFI files (http://piker-alpha.github.io/macosxbootloader/ -> Download "boot_grey.efi" -> Rename it to: "boot.efi") at:
/System/Library/CoreServices/boot.efi
and
/usr/standalone/i386/boot.efi

Rebooted and it worked like a charm again.
It's the same process as always.

Yes, exactly the same steps worked for me too.