Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is urban legend. CPU is bigger bottleneck (esp. in games) than PCIe in MP 1,1.



Much better OpenGL and OpenCL performance, lower heat emission and power draw, triple displays support, better reliability of 5870 aren't worth it?

I'd rather say that if you're a gamer, owning MP is not worth it ;)

I play video games on my Mac Pro 2.1 and its worth it to me :) I can play Battlefield 3 at Ultra Settings with no issues. Mac Pros have a lot of power they are worth it, not to mention now the ability to practically run Mavericks.
 
This is urban legend. CPU is bigger bottleneck (esp. in games) than PCIe in MP 1,1.



Much better OpenGL and OpenCL performance, lower heat emission and power draw, triple displays support, better reliability of 5870 aren't worth it?

I'd rather say that if you're a gamer, owning MP is not worth it ;)

This is why I got the card... :)
 
Hi there guys, first up a massive thank you to all those who worked on making it possible to get Mavericks onto the old MacPro machines. I am currently writing this message on my 2006 MP 1,1

I have a few questions related to the graphics card if you don't mind.

I have noticed the glitchy graphics as others have mentioned, when scrolling in a browser, but also I tried playing a few movie files in VLC and they didn't play? Could hear sound but no picture. Could the failure to play the movies be down to the graphics card, as I'm assuming VLC had all the necessary codecs? I have the NVIDIA GeForce 7300 GT 9 MB (according to the system profiler)

I have an original MacPro1,1 with firmware flashed to 2,1 but the SMC firmware has not been updated. Attempts to install Mavericks from USB stick results in a black screen with a white "-" minus sign about 1/4 down from the top and 1/4 from the left. Activity light on USB stick flashes for 30 seconds or so of booting. Original first generation 7300GT video card.

While running 10.7.5 I thought for laughs to try double-clicking the modified Mac OS X Mavericks Installer.app on the USB. Shortly a box appeared asking permission to check compatibility with the App Store, and failed.

Have ordered a used genuine Apple GeForce 8800GT hoping that would be more compatible than the 7300 but it has not arrived yet.

Have a PC Radeon 2600 to play with. No video at all in 10.7.5 with the 7300 in the machine too, or not. The PC 2600 does work in a 3,1 with an Apple 2600. Should it fire up after booting is complete in my 1,1/2,1 with 10.7.5? Should it work with this thread's Mavericks boot.efi?
 
I know one thing for certain from here on out...

Firstly, I do not know what has driven me to be this way as I am not the least bit trendy or cutting edge and all of my possessions and belongings while still functional and useful are very practical and modest. The exception to all of this in my case is that over the years, I have had an uncontrollable need to run the "latest and greatest" Mac operating system as soon as it has been made available to the general public on my many and various Mac computers. In reflecting as to why I possess such a need that otherwise is none existent in the vast majority of other decisions and choices I make concerning my life, admittedly I believe I may have very well fallen prey to "the latest and greatest is always better then what you have" philosophy conveyed by profitable machine otherwise known as Apple Computer.

Well I can honestly say that after this unprecedented and either grossly negligent or hideously devious SSL security breach debacle, I will never again jump on board blindly with ANY future Apple Mac OS X operating system release ever again. I never would have thought how fortunate I am that our Late 2006 iMac w/ ATI X1600 graphics can presently only be hacked to run Mountain Lion OS X 10.8.5, which is not severely flawed in the manner that OS X 10.9 Mavericks is at this very second of my writing this. Lesson learned !

PS. as in all honesty my Mac Pro 1,1 firmware and SMC flashed to 2,1 upgraded both to Xeon X5355's and Apple Radeon HD 5770 graphics and 16 GB's of RAM ram ran OS X 10.8 better then 10.9 anyway and as Tiamos boot.efi also works exceptionally well on Mountain Lion I believe a downgrade is forthcoming
 
Last edited:
I've just updated my MacPro 2,1 (flashed from 1,1-->2,1) to 10.9.2 update.
But I think it destroyd my Mavericks environment.

Right now the system auto boots into Snow Leopard, even when I manually select my Mavericks install, trough EFI it goes back to Snow Leopard.

I think Apple doesnt like it very much, and replaced the boot.efi back to oringinal or updated it maybay ?

anyway, we need an update from SFOTT maybay ?
The option to Patch an existing system in SFOTT, still doesnt work for me..

or another workaround for this problem to fix..

Any one a solution to boot 10.9.2 again on older systems ?

p.s
sry for my bad english, I'm from the Netherlands.
 
I've just updated my MacPro 2,1 (flashed from 1,1-->2,1) to 10.9.2 update.
But I think it destroyd my Mavericks environment.

Right now the system auto boots into Snow Leopard, even when I manually select my Mavericks install, trough EFI it goes back to Snow Leopard.

I think Apple doesnt like it very much, and replaced the boot.efi back to oringinal or updated it maybay ?

anyway, we need an update from SFOTT maybay ?
The option to Patch an existing system in SFOTT, still doesnt work for me..

or another workaround for this problem to fix..

Any one a solution to boot 10.9.2 again on older systems ?

p.s
sry for my bad english, I'm from the Netherlands.

Have you tried replacing the boot.efi manually using the Snow Leopard install? On another thread it was noted that the 10.9.2 betas replaced the boot.efi files.
 
I think Apple doesnt like it very much, and replaced the boot.efi back to oringinal or updated it maybay ?

anyway, we need an update from SFOTT maybay ?

You haven't destroyed anything. It was a known fact that boot.efi was replaced by 10.9.2. Simply boot into Snow Leopard, open Terminal and execute the relevant command in the relevant folders to copy Tiamo's version of boot.efi on top of Mavericks 10.9.2 boot.efi. As soon as you do that, you can boot back into Mavericks. No problem. I've just followed that procedure myself and typing this in Mavericks.
 
You haven't destroyed anything. It was a known fact that boot.efi was replaced by 10.9.2. Simply boot into Snow Leopard, open Terminal and execute the relevant command in the relevant folders to copy Tiamo's version of boot.efi on top of Mavericks 10.9.2 boot.efi. As soon as you do that, you can boot back into Mavericks. No problem. I've just followed that procedure myself and typing this in Mavericks.

Thank's this is exactly what I was wondering before I pulled the trigger on the update. I will be using the Chameleon partition I still have installed to replace the boot.efi files after the update.
 
thx for the quick response, I'm sure it can be fixed by just replacing the boot.efi file.

@PeterHolbrook,

which command should i need to run from my snow leopard terminal ?
can you post it for me maybay ?
 
thx for the quick response, I'm sure it can be fixed by just replacing the boot.efi file.

@PeterHolbrook,

which command should i need to run from my snow leopard terminal ?
can you post it for me maybay ?

No terminal commands needed. Just paste the boot.efi to the two places listed in Tiamo's post on page two and then boot into Mavericks.

I did it using a Lion install since I couldn't get my Chameleon install out of silent boot and it was going to Windows. Worked perfectly, I am now running 10.9.2 on my Mac Pro 1,1.
 
which command should i need to run from my snow leopard terminal ?
can you post it for me maybay ?

Contrary to some previous advice by someone else, copying boot.efi to the relevant folders of your Mavericks disk using the Snow Leopard Finder might be impossible, since, more likely than not, such folders might be read-only. That would work, however, booting Mavericks from Chameleon.

As for the specific commands you must use, that depends where your source Tiamo boot.efi is located and on the name of your Mavericks disk or partition. I'm going to assume that your Tiamo boot.efi is found in both relevant folders and that it's name is boot.efi.Tiamo. I'm also going to assume that your Maricks disk name is "Macintosh HD". If so, you might enter something like this in Terminal (this is just an example from memory; watch out for possible typos):

cd "/Volumes/Macintosh HD/System/Library/CoreServices"
sudo chflags nouchg boot.efi

Then you'll need to enter your administrative password

sudo cp boot.efi.Tiamo boot.efi
sudo chflags uchg boot.efi

cd "/Volumes/Macintosh HD/usr/standalone/i386"
sudo cp boot.efi.Tiamo boot.efi

Quit Terminal, reboot into Mavericks and you are done.
 
Contrary to some previous advice by someone else, copying boot.efi to the relevant folders of your Mavericks disk using the Snow Leopard Finder might be impossible, since, more likely than not, such folders might be read-only. That would work, however, booting Mavericks from Chameleon.

As for the specific commands you must use, that depends where your source Tiamo boot.efi is located and on the name of your Mavericks disk or partition. I'm going to assume that your Tiamo boot.efi is found in both relevant folders and that it's name is boot.efi.Tiamo. I'm also going to assume that your Maricks disk name is "Macintosh HD". If so, you might enter something like this in Terminal (this is just an example from memory; watch out for possible typos):

cd "/Volumes/Macintosh HD/System/Library/CoreServices"
sudo chflags nouchg boot.efi

Then you'll need to enter your administrative password

sudo cp boot.efi.Tiamo boot.efi
sudo chflags uchg boot.efi

cd "/Volumes/Macintosh HD/usr/standalone/i386"
sudo cp boot.efi.Tiamo boot.efi

Quit Terminal, reboot into Mavericks and you are done.

I did not need any commands when booted into a Lion install not using Chameleon. You are correct that they may be read only but that was not my experience.
 
NB This still works just fine.

Here's a quick 'n' dirty method for replacing the boot.efi(s)

Assuming you are booted from an earlier Mac OSX on a disk in your Mac Pro.

Put a copy of Tiamo's boot.efi in your home folder where you are booted NOW (Lion/Snow Leopard etc etc)

MavericksHD = the hard drive where Mavericks needs to be patched - change it to the EXACT name of your HD.

In the Terminal:

Code:
cd "Volumes/[b]MavericksHD[/b]/System/Library/CoreServices"
sudo rm -f boot.efi
sudo cp ~/boot.efi boot.efi

Now for the other instance:

Code:
cd "Volumes/[b]MavericksHD[/b]/usr/standalone/i386"
sudo rm -f boot.efi
sudo cp ~/boot.efi boot.efi

Reboot having selected MavericksHD in the Startup Disk control panel.

Note, if you delete the boot.efi before replacing it there's no mucking about with permissions needed. Nothing else is needed to be done.
 
Last edited:
This is going to be a bit of a PITA for those, like me, who also have a newer PC video card installed with no boot screen displayed. I don't really see any other alternative but to reinstall the old card temporarily until 10.9.2 is patched.

Anyone else see a simpler way? Maybe download and patch the installer file first, instead of patching after the installation?
 
This is going to be a bit of a PITA for those, like me, who also have a newer PC video card installed with no boot screen displayed. I don't really see any other alternative but to reinstall the old card temporarily until 10.9.2 is patched.

Anyone else see a simpler way?

I kept a working Lion install around just for this. I am running a MSI GTX 570.
 
I kept a working Lion install around just for this. I am running a MSI GTX 570.

I also have a GTX-570 installed.

Sorry, I must be missing something obvious here!

I don't have a Lion partition kicking around, but I do have an exact clone of my Mavericks partition. So, assume I upgrade my main partition to 10.9.2, it reboots after completion, everything is bonked and non-working, how then would I get booted into the other partition (lion or Mavericks or whatever) in order to facilitate the patch when I can't see a boot screen to make a selection? <scratches head>
 
My machine when faced with a non-functioning boot choice, automatically cascades to the next working one.

Same here. If it finds a working boot.efi it will boot that, the one on the non 10.9.2 drive. Replace the boot.efi files on the main hdd and then boot to that drive. Once booted it will continue the 10.9.2 install for about another 10 mins.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.