Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

[Hennesie2000]

If I perform the firmware flash from a bootable lion drive at a later date will that cause issues booting back to Yosemite?



And I take it its okay to install over my copy of lion? (I will have a copy if stuff goes wrong).

No, that's how I did mine

 

[YakkerGuy]

Risking redundancy here, I was about to post a question of the *exact* steps required for the 666sheep Fix package since it wasn't immediately clear that it needs to be installed, machine restarted, and THEN updates applied. It also wasn't immediately clear from his initial post that it was automated for all future Yosemite updates with no further action required.

Absolutely amazing! Thank you, guys!!!

My apologies to those who already understood. I just want to include these collected quotes in one post for anyone it can help to avoid confusion.

I modified the script and Tobyg's package with Pike's fork of boot.efi.
I hope that tobyg won't mind this.

Above steps are no longer needed with updated version. Enjoy!

Credits go to Pike and Tobyg and of course to tiamo, who started this all.
Boot.efi inside the 1st package is black version.

Updated the post with gray version for these who prefer older look.
It's Hennessie's build from post #1616, black is mine from latest version of Pike's sources.

So simply open and install package now and reboot and we're all set? Thanks!

OK. And after a new update, like 10.10.2, no more problem with the boot.efi ?

Correct. It changes the boot.efi right before the computer restarts or shuts down every time. So updates will not break it anymore.

If you have the TobyG script modded for Yosemite as in post #1584 or 666Sheep's version then updating via the App Store should not be a problem.

So I tried again tonight to get to 10.10.2, this time using the recommended approach. The result this time was the computer wouldn't boot at all...

...Just to double-check, here are the steps taken:

1) DL 666sheep's file called PikeYoseFix-Black from post #2166.
2) Run the package script contained therein.
3) When prompted to restart, instead went to App Store and DL'd 10.10.2
4) Once app store download complete, allowed computer to reboot.

...

Any thoughts on what the issue might be?

Thanks.

You need to do the restart that you, for some reason, chose not to do. The launch daemon was installed but it wasn't running yet. So when you installed 10.10.2 it over wrote the boot.efi files again. With TobyG's original script he recommended rebooting twice but the second time wad just to verify that it was working by checking the timestamp on the boot.efi files.

Hi guys,

Thanks a lot! I installed the patch then 10.10.2 from the Mac App Store, it worked great.

I just want to make sure I'm clear...this will now work for all updates in the future, I won't have to install or modify these again (including the eventual OS X 10.11)?

You won't need to for 10.10.X but it is likely 10.11.0 will need a new boot.efi.

Originally Posted by charlan7:

"Same here with the update patcher

1. Trim Enabler: remove; computer restart

2. Update 10.10.2; computer restart

3. Trim Enabler: activate and restart

4. Success!"

System Preferences > App Store

I just updated my MacPro2,1 to 10.10.2 with no issues but I previously had the PikeYoseFix installed. Others who had their Piker boot.efi overwritten by the 10.10.2 update either installed PikeYoseFix and then didn't reboot, so it never actually ran, or don't use the script at all.

The correct sequence:

• first, install PikeYoseFix
• if exceptionally cautious and running Trim Enabler, you may want to disable it
• you must reboot before installing an OS X Update that overwrites Pike's boot.efi so the PikeYoseFix script installs fully for future automatic execution
• only then install OS X Update
• safe to re-enable Trim Enabler if you disabled it earlier

 

[macprobuffalo]

I can happily report I am typing this from my mac pro running Yosemite.

I put the install image on an internal hard drive instead of a USB stick. The whole process went extremely smoothly, going from Lion to Yosemite in 30 min. Installed PikeYoseFix and updated to 10.10.2 no problem.

Updated my EFI before the install and am now just waiting for my X5365 cpu's and a Velociraptor to get delivered. I have 24GB of RAM and a ATI 5770. Performance is surprisingly good, feels very similar to my 2012 Macbook Pro running 10.9

Thank you to everyone who made this possible! Just as software developers are starting to drop lion support, I now have many more years out of my trusty desktop

 

[Hennesie2000]

I can happily report I am typing this from my mac pro running Yosemite.



I put the install image on an internal hard drive instead of a USB stick. The whole process went extremely smoothly, going from Lion to Yosemite in 30 min. Installed PikeYoseFix and updated to 10.10.2 no problem.



Updated my EFI before the install and am now just waiting for my X5365 cpu's and a Velociraptor to get delivered. I have 24GB of RAM and a ATI 5770. Performance is surprisingly good, feels very similar to my 2012 Macbook Pro running 10.9



Thank you to everyone who made this possible! Just as software developers are starting to drop lion support, I now have many more years out of my trusty desktop

Yup, it really is this easy. If you truly follow the steps, it just works.

 

[phdjsep]

So I've cleared a hurdle...

The hurdle being that I couldn't boot into any startup mode and therefore couldn't install Yosemite. Turns out its for a pretty dumb reason.

I have an ultrawide monitor and my video card seemed to get stuck when trying to render at such a large resolution. I've changed the resolution to 1024x768 and guess what, I'm installing Yosemite as we speak. (facepalm)

I currently have the ATI Radeon X1900 XT installed since my new card isn't working yet (I assume due to it being flashed for compatibility for Yosemite, i dunno).

Anyhow, hope that helps someone out there. Thanks for all the help! I may be back lol

 

[Jamrashid]

Still No "About This Mac" and Apps not launching

Very interesting. I've never experienced this myself. You're sure the HD is good? Try booting in Safe Mode (hold shift at startup).

I rebooted in safe mode and still the same results. Preview, Maps, Photo Booth, Contacts, Reminders, and Facetime apps still not launching. I tried to launch System Information (Version 10.10) and got a dialog box "The application “System Information” can’t be opened." Activity Monitor is showing the process "identityservicesd" as Not Responding. Also I have 12 gigs of ram installed but Activity Monitor is only recognizing 4 gigs. Like I stated before, the installation went pretty smooth with the pre=patched installer. Did I need to edit the PlatformSupport.plist or should I attempt a reinstall?

 

[MacVidCards]

I rebooted in safe mode and still the same results. Preview, Maps, Photo Booth, Contacts, Reminders, and Facetime apps still not launching. I tried to launch System Information (Version 10.10) and got a dialog box "The application “System Information” can’t be opened." Activity Monitor is showing the process "identityservicesd" as Not Responding. Also I have 12 gigs of ram installed but Activity Monitor is only recognizing 4 gigs. Like I stated before, the installation went pretty smooth with the pre=patched installer. Did I need to edit the PlatformSupport.plist or should I attempt a reinstall?

Sounds like permission issue. Have you done repair?

 

[Jamrashid]

Fixed app problem, but memory issue remains

Sounds like permission issue. Have you done repair?

Thanks for the help. I decided to just go ahead with a reinstall and it fixed the apps and System Information issue, but Yosemite is still only recognizing the 4 gb of ram I have installed on riser B. It says the riser A is empty.

 

[Hennesie2000]

Thanks for the help. I decided to just go ahead with a reinstall and it fixed the apps and System Information issue, but Yosemite is still only recognizing the 4 gb of ram I have installed on riser B. It says the riser A is empty.

Are any of the red LEDs on the rise lit?

 

[MacVidCards]

Thanks for the help. I decided to just go ahead with a reinstall and it fixed the apps and System Information issue, but Yosemite is still only recognizing the 4 gb of ram I have installed on riser B. It says the riser A is empty.

Use scientific method.

Move RAM from one riser to another.

Either RAM or riser or riser slot is bad.

Some thought applied will give you answer faster than forum guesses.

 

[TheRealPorkchop]

That Raptor will be nice but you'd be surprised how much better an SSD would be. Put your OS on the SSD, the most frequently used programs also and everything else store on the Raptor or another drive. That's what I did, so I could afford a smaller SSD from OWC...

I can happily report I am typing this from my mac pro running Yosemite.

I put the install image on an internal hard drive instead of a USB stick. The whole process went extremely smoothly, going from Lion to Yosemite in 30 min. Installed PikeYoseFix and updated to 10.10.2 no problem.

Updated my EFI before the install and am now just waiting for my X5365 cpu's and a Velociraptor to get delivered. I have 24GB of RAM and a ATI 5770. Performance is surprisingly good, feels very similar to my 2012 Macbook Pro running 10.9

Thank you to everyone who made this possible! Just as software developers are starting to drop lion support, I now have many more years out of my trusty desktop

----------

Use scientific method.

Move RAM from one riser to another.

Either RAM or riser or riser slot is bad.

Some thought applied will give you answer faster than forum guesses.

Or he could have the same issue I had, one riser not plugged into completely. I did a processor upgrade and didn't have the plastic snapped in all the way, caused the riser to look correct but not be correct.

 

[Jamrashid]

Use scientific method.

Move RAM from one riser to another.

Either RAM or riser or riser slot is bad.

Some thought applied will give you answer faster than forum guesses.

Thanks for the reply. I rearranged the memory sticks in the riser instead and now everything is fine. Applied thought definitely gave me the answers, but it never hurts to ask.

 

[macprobuffalo]

That Raptor will be nice but you'd be surprised how much better an SSD would be. Put your OS on the SSD, the most frequently used programs also and everything else store on the Raptor or another drive. That's what I did, so I could afford a smaller SSD from OWC...

This computer runs a virtual machine alongside OSX so it sees alot of I/O's. I was worried burning out the SSD, I know they only have a set number of read/writes.

The VM can only be ran from the boot disk (I've tried all sorts of tricks to get it to work on a separate HD). Therefore I would need a very large SSD, i'd rather wait until they get cheaper.

The Raptors will actually be used in a RAID0 configuration for the boot disk. I've searched this thread and dont see any issue directly related to booting from a RAID0 array.

Plan is to clone my boot disk, boot from the 10.10 installer, create the RAID array, transfer data to the newly created array.

I know the risks of running a striped array as the boot disk. I have a separate disk split into two partitions- one being the Yosemite installer and the other is a boot drive clone. Besides the hour of downtime spent to restore the system, I should be covered in the event of a disk failure.

 

[atinwi]

No Luck with DIY Fusion Drive

Firstly, thanks to everyone involved in this project, and thanks to anyone who takes the time to reply to this post. My issue is as follows:

My home-made fusion drive will not boot.

I installed Yosemite using an SFOTT key, over the top of a previously perfectly working mavericks installation.

I have even tried a fresh install of Yosemite onto my fusion drive, then, before first boot,booting up to a different partition and installing PIKEYOSEFIX to my fusion drive using the installer.

Additionally, when boot with my SFOTT key, to try to update the the boot EFI (is that correct?) and launch the terminal it tells me that there is no such file or directory (Please see attached image)

The key itself has worked before . I have used it successfully to install Yosemite on one drive in my Mac Pro 1.1. but that drive is so slow I want to get my fusion drive back up and running. IT was working perfectly with Mavericks.

THANKS IN ADVANCE

Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 8

 

[NOTNlCE]

Firstly, thanks to everyone involved in this project, and thanks to anyone who takes the time to reply to this post. My issue is as follows:

My home-made fusion drive will not boot.

I installed Yosemite using an SFOTT key, over the top of a previously perfectly working mavericks installation.

I have even tried a fresh install of Yosemite onto my fusion drive, then, before first boot,booting up to a different partition and installing PIKEYOSEFIX to my fusion drive using the installer.

Additionally, when boot with my SFOTT key, to try to update the the boot EFI (is that correct?) and launch the terminal it tells me that there is no such file or directory (Please see attached image)

The key itself has worked before . I have used it successfully to install Yosemite on one drive in my Mac Pro 1.1. but that drive is so slow I want to get my fusion drive back up and running. IT was working perfectly with Mavericks.

THANKS IN ADVANCE

Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 8

In order to get the Fusion Drive in my 1,1 up and running, I needed to install on a single drive and then use a utility such as CCC or SuperDuper! to clone the install onto the Fusion Drive. If you have the means, you might give that a shot.

 

[atinwi]

In order to get the Fusion Drive in my 1,1 up and running, I needed to install on a single drive and then use a utility such as CCC or SuperDuper! to clone the install onto the Fusion Drive. If you have the means, you might give that a shot.

I might try that thanks, foolishly, I did not make a clone of my working Mavericks system so my backups are bit of a mess. But I might have to do that later, thanks.

I am really hoping for a less drastic solution however!

 

[Paulzy123]

Compatible

Hello

What a great thread this is, and many thanks to all those who have contributed .

My question is simple.

I have 1 late 2006 20" iMac (2.16 GHz Intel Core 2 Duo)
Will this process work to install on my iMac?

Many Thanks

Paul

 

[Hennesie2000]

Hello



What a great thread this is, and many thanks to all those who have contributed .



My question is simple.



I have 1 late 2006 20" iMac (2.16 GHz Intel Core 2 Duo)

Will this process work to install on my iMac?



Many Thanks



Paul

I don't believe so because of a lack of GPU drivers for the x1600 or GMA950.

 

[atinwi]

I might try that thanks, foolishly, I did not make a clone of my working Mavericks system so my backups are bit of a mess. But I might have to do that later, thanks.

I am really hoping for a less drastic solution however!

I have done as you suggested, seems to work, now to sort out my mess of files all over the place thanks again

 

[128kmacintosh]

The new beta version is out. did any of you 1.1/2.1 peeps install it?

 

[macprobuffalo]

Does anyone know if it is possible to add the time machine restore function to the installer image? I can't boot into recovery and would like this application on a separate partition within my backup hard drive along with the prepackaged installer.

Using the debug mode in disk utility I was able to extract the Recovery HD image but I can only view 20mb of the 600mb image. All viewable files are .plists

 

[NOTNlCE]

Does anyone know if it is possible to add the time machine restore function to the installer image? I can't boot into recovery and would like this application on a separate partition within my backup hard drive along with the prepackaged installer.

Using the debug mode in disk utility I was able to extract the Recovery HD image but I can only view 20mb of the 600mb image. All viewable files are .plists

I am unaware of any methods. I instead use SuperDuper! to clone my working install to a spare drive.

 

[macprobuffalo]

I am unaware of any methods. I instead use SuperDuper! to clone my working install to a spare drive.

Decided to do the same using carbon copy

 

[NOTNlCE]

Day off today to fiddle with the Xserve.

I'm sad to report that the cause of the reboots under Yosemite is most certainly NOT the Mezzanine card. MacVidCards is absolutely right in that the card is removable. It's not a traditional PCIe card, but in both the 2006 AND the 2008 Xserve, the built in X1300 GPU is actually a discrete card located underneath the right PCIe slot.

I removed the card a few moments ago and attempted to boot a SFOTT stick with a GeForce 405 installed in a PCIe slot, my Fibre Card in the other. Constant reboot, just as before. And, as before, it boots Lion Server just fine, even with the 405 in the second slot. Crazy strange.

 

[rvgulik]

Day off today to fiddle with the Xserve.

I'm sad to report that the cause of the reboots under Yosemite is most certainly NOT the Mezzanine card. MacVidCards is absolutely right in that the card is removable. It's not a traditional PCIe card, but in both the 2006 AND the 2008 Xserve, the built in X1300 GPU is actually a discrete card located underneath the right PCIe slot.

I removed the card a few moments ago and attempted to boot a SFOTT stick with a GeForce 405 installed in a PCIe slot, my Fibre Card in the other. Constant reboot, just as before. And, as before, it boots Lion Server just fine, even with the 405 in the second slot. Crazy strange.

I removed that card afterwards, sad thing is that i don't see the initial bootscreen but i ordered a couple of GT120 512MB from MacVidCards so that issue will be gone i hope.
So does it work with the card installed?