Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I presume, you mean "Sleep." Mine works fine (1,1, updated to 2,1 - flashed SMC & FW, plus Quad Core 3GHz Xeons). I do have occasional issues with the Apricorn SOLO X1 in slot 2 disappearing. It is used with an SSD for BootCamp Windows 8.1, so no potential for corruption.
My main 960GB SSD is connected to the internal slot 6.


Yeah I mean sleep mode :)

When the sleep mode is active for an hour or so, the computer is booting again by itself, but this behavior is random
 
Help with App Store upgrade not working

First, many many thanks to Tiamo and Tobyg for their work on the boot.efi and the apps for running 10.9.2 on my old trusty MP 2,1.

My only issue is if I try and download the Mavericks installer from the App store, I get the message that OSX Mavericks can not be installed on this computer. So somewhere I must have missed a step.

I don't need it now but I will want to do an upgrade down the road without going through all that I did to get this first install up and running.

Can anyone point me to what I have missed and how to fix it.

Thanks to everyone.
 
First, many many thanks to Tiamo and Tobyg for their work on the boot.efi and the apps for running 10.9.2 on my old trusty MP 2,1.

My only issue is if I try and download the Mavericks installer from the App store, I get the message that OSX Mavericks can not be installed on this computer. So somewhere I must have missed a step.

I don't need it now but I will want to do an upgrade down the road without going through all that I did to get this first install up and running.
Why are you trying to run the Mavericks install again? The steps involving "OSInstall.mpkg" are hacking this error message out. You're trying to run the unhacked installer. There's no need to do this - checking for OS updates happens outside of the app store installer.
 
You didn't bother to quote the entire line:



Essentially, the time stamp on the files should be updated every time you reboot with the current time you rebooted. So if you want to make sure the files are being updated properly upon reboot, reboot once and when you log back in, check the date/time on the files. They should be stamped with the date/time you just previously rebooted. That tells you the shutdown script is working properly.

I spoke to soon. The Mac seemed to be running fine and 99% is. The only thing that doesn't work is messages. I wonder if this is why?
Both of my boot.efi files are created/modified November last year.
 
One question, I know this has been covered but would appreciate some clarification.

How should software updates be handled? Don't want to accidentally overwrite the boot efi.
 
Thank jou!

Jou are the man! ik breath new life in my mac pro!
:) :) :) :) :) :) :) :) :) :) :) :)
PS: as you can't find the boot.efi use find anny file
 
One question, I know this has been covered but would appreciate some clarification.

How should software updates be handled? Don't want to accidentally overwrite the boot efi.

Well if 10.9.1 --> 10.9.2 was any indication of what's to come its good news bad news.

It will bork your computer, HOWEVER, all you have to do is replace the boot.efi file and you're good to go again.
 
iMessage & Facetime

Having successfully installed Mavericks on my MacPro 2,1 using the Tiamo efi method. I have successfully had iMessage & FaceTime running.

Since the 10.9.2 update both iMessage and FaceTime cease to work and will not activate.

I have a valid paid iCloud account. I have tried all the usual things mentioned o all the forums.

The one thing I believe is being checked upon activation of these services is the network interface. If I reinstall the original efi's and boot from the disk using a Mac min eligible to run Mavericks. All works and I notice in the networkconfiguration.plist unders system configuration an entry now exists for the Mac mini

Reverting the efi's back and booting up in my MacPro 2,1 and still no joy with iMessage or FaceTime.

It's as if the hardware is being checked to see if it meets min requirement for the service. Trying to fudge the plist doesn't work either as it is overwritten at startup.

Has any one experienced the same issue and does any one know of a way to fix?

Thanks in advance
 
Having successfully installed Mavericks on my MacPro 2,1 using the Tiamo efi method. I have successfully had iMessage & FaceTime running.

Since the 10.9.2 update both iMessage and FaceTime cease to work and will not activate.

I have a valid paid iCloud account. I have tried all the usual things mentioned o all the forums.

The one thing I believe is being checked upon activation of these services is the network interface. If I reinstall the original efi's and boot from the disk using a Mac min eligible to run Mavericks. All works and I notice in the networkconfiguration.plist unders system configuration an entry now exists for the Mac mini

Reverting the efi's back and booting up in my MacPro 2,1 and still no joy with iMessage or FaceTime.

It's as if the hardware is being checked to see if it meets min requirement for the service. Trying to fudge the plist doesn't work either as it is overwritten at startup.

Has any one experienced the same issue and does any one know of a way to fix?

Thanks in advance

What is your error message?

----------

I am running a Mac Pro 2,1 with Tiamo's boot.efi and Mavericks 10.9.3. As the latest, I added an Apricorn Velocity Solo X1 PCIe eSata card that allows mounting an SSD. I use it with a 256GB Crucial SSD to allow Boot Camp booting of Windows 8. I have a 960GB SSD hooked to the 6th internal SATA port for booting Mavericks.
The Solo X1 has a 32 and 64 bit EFI, so it boot with the early Macs. Everything is woking splendidly. Disk performance is a little more than 90% of the built in ports with the same SSD.

But I do have occasions were the card does not configure after recovering from Sleep. The disk cannot be found and does not remount. I generally have to reboot to get it back.

I have not tried this on Lion to see, whether it is specific to Mavericks...

Has anybody else run into this?

----------

One question, I know this has been covered but would appreciate some clarification.

How should software updates be handled? Don't want to accidentally overwrite the boot efi.

The safest is to always have at least one alternate boot partition - ideally Lion. This will allow you to fix issues easily.
 
Well if 10.9.1 --> 10.9.2 was any indication of what's to come its good news bad news.

It will bork your computer, HOWEVER, all you have to do is replace the boot.efi file and you're good to go again.

I ran the 10.9.1 => 10.9.2 updater and rebooted my 1,1 in Mavericks without a problem. I did replace the boot.efi files after the fact. Seems to me that is when I started having problems with Preview. I might go and overwrite the boot.efi files again for the heck of it.
 
Having successfully installed Mavericks on my MacPro 2,1 using the Tiamo efi method. I have successfully had iMessage & FaceTime running.

Since the 10.9.2 update both iMessage and FaceTime cease to work and will not activate.

I have a valid paid iCloud account. I have tried all the usual things mentioned o all the forums.

The one thing I believe is being checked upon activation of these services is the network interface. If I reinstall the original efi's and boot from the disk using a Mac min eligible to run Mavericks. All works and I notice in the networkconfiguration.plist unders system configuration an entry now exists for the Mac mini

Reverting the efi's back and booting up in my MacPro 2,1 and still no joy with iMessage or FaceTime.

It's as if the hardware is being checked to see if it meets min requirement for the service. Trying to fudge the plist doesn't work either as it is overwritten at startup.

Has any one experienced the same issue and does any one know of a way to fix?

Thanks in advance

I'm assuming you mean in /Library/Preferences/SystemConfiguration/? The only file I have with both of the words network and configuration there is;
com.apple.network.eapolclient.configuration.plist there
 
iMessage & FaceTime

I'm assuming you mean in /Library/Preferences/SystemConfiguration/? The only file I have with both of the words network and configuration there is;
com.apple.network.eapolclient.configuration.plist there

The error message from iMessage is:

Could not sign in to iMessage.

An error occurred during activation. Try again.

The error message from FaceTime is:

An unknown error occurred during registration.

My apologise I have given incorrect information in the OP, it is the NetworkInterfaces.plist

Attached is a screen shot of what is in the plist
 

Attachments

  • NetworkInterfaces.png
    NetworkInterfaces.png
    252.6 KB · Views: 182
The error message from iMessage is:

Could not sign in to iMessage.

An error occurred during activation. Try again.

The error message from FaceTime is:

An unknown error occurred during registration.

My apologise I have given incorrect information in the OP, it is the NetworkInterfaces.plist

Attached is a screen shot of what is in the plist
The plist is overwritten at startup, that's interesting. What kind of fudge were you talking about?
 
Having discovered that I may be able to upgrade my MacPro 2,1 Lion to Mavericks I decided to take the plunge. Using a new MacBook Pro I downloaded Mavericks and created a USB install disk using the terminal method (external seagate hard drive is the USB install disk)Of course to be honest now is how do I upgrade my Lion to Mavericks with this drive with the boot.efi? Will SFOTT patch this premade USB install drive? Or will I need to make new one? Will i have to install to a new hard drive? Or can I simply upgrade Lion to Mavericks once I patch the Mavericks usb hard drive installer ? I am sure this is covered somewhere. But hunting through the thread it gets rather confusing on the actual procedure in my case.

MacPro 2,1 has an AMD 5770 so I should not have any main issues (nor does this Mac have blutooth or wifi, since work didn't require my system to have these addons when I first got the system).
 
Last edited:
Nevermind - had to copy the install over to the desktop and just follow the clear instructions for SFOTT to get the key (external harddrive) set and ready to install Mavericks. First install attempt failed - but that's probably due to this hard drive being a little 'I work this second... might not the next.' Ran the install again, and Mavericks 10.9.2 is now fully installed on this humble MacPro 2,1. And by the looks of it the failed initial install caused no issues, all my files are here and all my applications are working wonderfully.

Having discovered that I may be able to upgrade my MacPro 2,1 Lion to Mavericks I decided to take the plunge. Using a new MacBook Pro I downloaded Mavericks and created a USB install disk using the terminal method (external seagate hard drive is the USB install disk)Of course to be honest now is how do I upgrade my Lion to Mavericks with this drive with the boot.efi? Will SFOTT patch this premade USB install drive? Or will I need to make new one? Will i have to install to a new hard drive? Or can I simply upgrade Lion to Mavericks once I patch the Mavericks usb hard drive installer ? I am sure this is covered somewhere. But hunting through the thread it gets rather confusing on the actual procedure in my case.

MacPro 2,1 has an AMD 5770 so I should not have any main issues (nor does this Mac have blutooth or wifi, since work didn't require my system to have these addons when I first got the system).
 
Having successfully installed Mavericks on my MacPro 2,1 using the Tiamo efi method. I have successfully had iMessage & FaceTime running.

Since the 10.9.2 update both iMessage and FaceTime cease to work and will not activate...Has any one experienced the same issue and does any one know of a way to fix?
I installed 10.9.2 clean on my Mac Pro 2,1. Doing so requires replacing the EFI files on the boot drive after the install completes, but is otherwise the same as the existing procedures. iMessage / FaceTime worked out of the box for me without any issue. So, it can't be due to a "minimum requirement" check that you're failing, if it were I'd be failing it also.

My mac is connected by Ethernet.
 
Will Mercury Playback Engine Work?

Hi all,

Very tempted to try this out. I'm early enough into my project that it shouldn't damage anything if it goes south.

I've recently switched to Adobe Creative Cloud and editing in Premiere CC (moved over from FCP) and couldn't get the Mercury Playback Engine to work after adding my card (GTX 560 Ti) to the kexts. I then read that it'll only work on a 64 bit EFI.

So, can anyone who's done the upgrade confirm that this'll work? It would be nice to use the video card's CUDA capabilities and eek out a little more performance on this old Mac Pro...

Thanks!
 
I am running a Mac Pro 2,1 with Tiamo's boot.efi and Mavericks 10.9.3. As the latest, I added an Apricorn Velocity Solo X1 PCIe eSata card that allows mounting an SSD. I use it with a 256GB Crucial SSD to allow Boot Camp booting of Windows 8. I have a 960GB SSD hooked to the 6th internal SATA port for booting Mavericks.
The Solo X1 has a 32 and 64 bit EFI, so it boot with the early Macs. Everything is woking splendidly. Disk performance is a little more than 90% of the built in ports with the same SSD.

But I do have occasions were the card does not configure after recovering from Sleep. The disk cannot be found and does not remount. I generally have to reboot to get it back.

I have not tried this on Lion to see, whether it is specific to Mavericks...

Has anybody else run into this?.
It looks like the problem might be related to disk sleep. It is possible, there is an EFI call in the card's 32 bit ROM that is not getting translated.
 
Xserve supported?

Anyone know if this supports the original Intel Xserve 1,1?

It's got 32bit EFI, but unlike the 23Bit MacPros, the Xserve cannot emulate BIOS either...

Anyone tried or can answer this?
 
Modify Installablemachines.plist

Anyone care to share their methods for modifying installablemachines.plist? I've found that using the createinstallmedia terminal method is the only way to achieve a successful boot stick with the current 10.9.2 installer which leaves the installablemachines.plist file wrapped up in the packages folder within InstallESD.dmg. I've accessed it with Xcode although I'm not able to unlock the file to commit the modification. I've also mounted the dmg, modified the file and re-packed in toast. This gives an error message at install that the installation media is corrupt.

Any advise would be greatly appreciated, thanks again!
 
I've made it easier to update 10.9.2.

Instead of following the instructions above, just install the attached package. It will put the LaunchDaemon out there.

So here are the new steps.

1. Install TiamoMacProFix.pkg (attached to this thread)
2. Reboot (yes this is necessary)
2a. Reboot again if you want to then verify the date/time stamp on the two boot.efi files (/usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi) are updated properly. They won't be updated until the second shutdown/reboot. (optional step but a good one if you want to verify the files are updating properly)
3. Install 10.9.2 update.
4. ...
5. Profit.

Consider this a version .1 beta package. I'll work on building a new package file that won't require a reboot and will do additional checks (to make sure you're not installing this on something like a MacPro3,1+ and that you're definitely using 10.9.0 or greater, etc).

Again, after you install this package you can freely update to 10.9.2 and not worry about having to manually replace boot.efi files.

This was tested on a MacPro1,1 with a fresh install of 10.9.2 and updated using the AppStore on a single drive.
This was NOT tested on a fusion drive.

Do I need to apply the TiamoMacProFix.pkg to my Late-2006 Core2Duo ATI1600 iMac 5.1 to update from OS 10.7.5 to Mountain Lion, or is that just for Mac Pros, as its name suggests?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.