It works fine on 10.8.5, I'm still using it because of the loss of iTunes local sync of contacts and calendar.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Pro 2,1 and OS X Mavericks
- Thread starter 5050
- Start date
- Sort by reaction score
Posts 479, 481 and 484 indicate some sort of problem on 10.9.2 for people who installed 10.9.1 correctly, however post 482 indicates it may be done through a slightly different installation procedure.
So it's not clear what the issue is (or even if there is one).
I have no access to the 10.9.2 seeds so can't test.
Rob
It seems to me the issue is VERY clear: There's no issue, other than 10.9.2 trashing Tiamo's boo.efi, thereby rendering the boot process of early Mac Pros running Mavericks and Mountain Lion impossible. The solution requires a roundabout step: Simply boot the Mac Pro into Snow Leopard or Lion, then go to the relevant Mavericks folders and substitute Tiamo's boot.efi for the updated version that 10.9.2 installed. Reboot into Mavericks. That should be all.
Peter, I disagree that the issue is VERY clear. People have reported different issues even with putting Tiamo's boot.efi back in place. We have at least one report that this didn't work, we also have other reports that it did work. People may have made mistakes so until we get confirmation from a number of people, I would say its still undecided and still unclear.
I hope very much that your reading of the situation is correct, personally I would be a little more cautious and assume the worst until I know the best.
Rob.
Er, well, no. Not at all. Contrary to your claims, the issue is crystal-clear. The 10.9.2 update replaces boot.efi, which means booting old machines is no longer possible. Which part of that don't you understand? Now, if a knowledgeable user substitutes (using Snow Leopard or Lion) Tiamo's boot.efi for the new version copied by the update, booting is again possible. Which part of that don't you understand? User clumsiness can never be used as an excuse for failure to execute an otherwise clear procedure.
What are the "different issues" you are describing apart from a single "doesn't work" report within this thread?
Replacing chameleon boot on 10.8.5
I had a quick question: I installed ML 10.8.5 on my Mac pro 1,1 last year using chameleon boot; everything is working. Still, I would now like to use Tiamo's boot.efi with 10.8.5 and dispense with the extra hdd and chameleon booting (the main reason is to get back my true official UUID). On pg2 of this thread, Tiamo mentions that it in 10.8, his boot.efi will bypass driver cache; hence one has to always enable kernel cache. Can someone tell me how this is done. Plus any other 'best practice' advice when using Tiamo's efi in 10.8.5? I see some threads, but they are mostly on installation (which I don't need), and there is a lot of MLpostfactor info – so, I just wanted to re-check the simplest procedure for my situation. many thanks, Tat64
I had a quick question: I installed ML 10.8.5 on my Mac pro 1,1 last year using chameleon boot; everything is working. Still, I would now like to use Tiamo's boot.efi with 10.8.5 and dispense with the extra hdd and chameleon booting (the main reason is to get back my true official UUID). On pg2 of this thread, Tiamo mentions that it in 10.8, his boot.efi will bypass driver cache; hence one has to always enable kernel cache. Can someone tell me how this is done. Plus any other 'best practice' advice when using Tiamo's efi in 10.8.5? I see some threads, but they are mostly on installation (which I don't need), and there is a lot of MLpostfactor info – so, I just wanted to re-check the simplest procedure for my situation. many thanks, Tat64
Last edited:
I had the same starting point: ML 10.8.5 (server) and Mavericks running with the chameleon boot.
I JUST replaced the boot.efi in both the places in both the installations with the Tiamo's one (I neither "dismounted" the disk with the chameleon boot ....) AND I blessed (with the startup disk control panel) one of the two Systems and..... voilà: everything is working !!
I have never minded about driver chaches and this is my experience....
Bruno
I JUST replaced the boot.efi in both the places in both the installations with the Tiamo's one (I neither "dismounted" the disk with the chameleon boot ....) AND I blessed (with the startup disk control panel) one of the two Systems and..... voilà: everything is working !!
I have never minded about driver chaches and this is my experience....
Bruno
Last edited:
Bootcamp issues
Hi everyone,
first a special thanks to Tiamo for his Boot.efi hack. Wonderful work.
Another thanks for OEM for his sfott tool.
Basically I got OSX Mavericks working on my MP2,1 with a Sapphire 6870 just fine. Only thing that's not working was the boot screen (which an old 2600 fixed).
However, when I try and startup Bootcamp (win 7) I get the fammiliar BSOD with an IRQL_NOT_LESS_OR_EQUAL error.
Has anyone seen any issues with the Boot.efi hack and Bootcamp? I did not may any other modifications to the system, so usual suspect this time is the boot.efi modification....
Hi everyone,
first a special thanks to Tiamo for his Boot.efi hack. Wonderful work.
Another thanks for OEM for his sfott tool.
Basically I got OSX Mavericks working on my MP2,1 with a Sapphire 6870 just fine. Only thing that's not working was the boot screen (which an old 2600 fixed).
However, when I try and startup Bootcamp (win 7) I get the fammiliar BSOD with an IRQL_NOT_LESS_OR_EQUAL error.
Has anyone seen any issues with the Boot.efi hack and Bootcamp? I did not may any other modifications to the system, so usual suspect this time is the boot.efi modification....
Hi, just to be clear for my own reference, if 10.9.2 gets released and I run the update and it overwrites the Tiamo EFI.
Just boot the Mac with another startup disk and then copy over Tiamo's boot.efi into the updated system?
Copy Tiamo's boot.efi ===> System/Library/CoreServices/
Correct? Thanks! (I won't immediately update when it does roll out, but it is good for my own reference).
UPDATE: Sorry being repetitive here, I'm re-reading parts of this thread.
Last edited:
copy it to System/Library/CoreServices/boot.efi and usr/standalone/i386/boot.efi
then reboot
its best practice to wait on 10.9.X updates until a few have done it and the proper process has been vetted out.
then reboot
its best practice to wait on 10.9.X updates until a few have done it and the proper process has been vetted out.
I think, you might not realize that this tone is not polite in a forum. Please refrain, since it might be considered insulting.
I have run into the same issue. Replacing the boot.efi and related files after updating in another system did not restore functionality on my system. I ended up going back to 10.9.1. This has nothing to do with clumsiness. I have personally automated the process for myself with an installer, so it is not subject to errors.
I develop software and hardware and manage a team that is creating a product line across all platforms and the cloud, so I am not altogether ignorant
----------
Nope. I have even let the update complete on a system supporting 10.9 natively, then reinstalled boot.efi and plists. But it still would not boot, which leads me to believe that there might be issues on some systems dependent on drivers loading etc. I have not run a delta to see, what files were changed, and given that it is an interim beta, it is not worth the effort. There are no bug fixes that in any way impact my system.
For now, I am back on 10.9.1 and will wait for the final release before spending more time.
MacPro1,1 with 8800GT. Used the SFott script to make USB key. But does not boot, fails due to "Still waiting for root device".
But always had issues booting USB on this machine (even Windows USB install did not boot).
Use SFott to make a spare HDD an installer, booted said HDD without issues, then installed to 2nd spare HDD.
Everything is running well, updated to 10.9.1
I wonder if setting system-immutable on boot.efi before 10.9.2 would work, or would the installer fail ...
But always had issues booting USB on this machine (even Windows USB install did not boot).
Use SFott to make a spare HDD an installer, booted said HDD without issues, then installed to 2nd spare HDD.
Everything is running well, updated to 10.9.1
I wonder if setting system-immutable on boot.efi before 10.9.2 would work, or would the installer fail ...
Tiamo, thanks a lot!!!!!!!!! I'm up and running with a 1,1 nvidia 7300 GT, all the original stuff, bind to a mini server, mobile accounts, etc, etc. Just had my Mac Pro restart in target disk mode, installed from my Mavericks MBP, replaced boot.efi as described and rebooted to continue on my mac pro like setting up a new machine.
Only thing with the 7300 is that even it's recognised and works, appears as having only 9MB of VRAM which causes some flickering and of course don't work well with video (actually new iMovie doesn't install).
I'll buy a 8800 which seems to work, but if anybody has some idea of what may be happening, I'd like to try the original setup
Thanks again
I have not spent the effort to create a boot USB, since it is much faster to bring up the disk on another system. But Mac Pro 1,1 is supposed to support booting from USB, since it does work with a drive.
However, legacy boot via USB does not work. It only supports CD and SATA. There are issues with Windows 7 and later boot CDs due to the 32 Bit EFI requiring some patching of the image, since the Windows boot system recognizes an EFI system.
I've had a very quick look at the new 10.9.2 13C44.
The boot.efi is still dated Dec 2013, so Tiamo's boot.efi should still work.
I have not installed the update on my MP yet so do not know whether or not Tiamo's boot.efi gets overwritten again, just needing a quick replacement on our parts.
It will be Saturday at the earliest before I can explore the update on my MP 1,1 -> 2,1
-Rob
The boot.efi is still dated Dec 2013, so Tiamo's boot.efi should still work.
I have not installed the update on my MP yet so do not know whether or not Tiamo's boot.efi gets overwritten again, just needing a quick replacement on our parts.
It will be Saturday at the earliest before I can explore the update on my MP 1,1 -> 2,1
-Rob
This time not. At least on 5,1. See Peloche's post below about 2,1.
Last edited:
It's a shame that "Nope" has entirely diluted your argument. So, it would appear, if you contradict another forum user, you are merely bringing them into reason, whereas, if others do the same, it is "insulting". Sorry, but it doesn't add up. Now you may say you were expecting as much, or whatever. Suit yourself.
If you are trying to impress me with the notion that, somehow, you are impervious to clumsiness, you are not succeeding. Clumsiness appears in all walks of life, and all sorts of people can be clumsy one time or another. For instance, you might be technically able to copy Tiamo's boot.efi in place of the "official" one, reboot and see it "doesn't work." Your self-proclaimed technical ability seems to be telling you something mysterious is at work, something you are not responsible for and have no control of. Great. An astute user would probably think of related issues that might be involved in their particular situation, such as the need to reset NVRAM, "blessing" the Mavericks partition if needed, et cetera.
Hmm, it must be some mechanism which compares file versions. I updated my 5,1 installation to C44 and both boot.efi files weren't replaced.
Correct me if I am wrong, but is there really such a thing as a "file version" of boot.efi? The relevant Info Box doesn't provide a file version on my system. The only thing I can think of that might prevent the 10.9.2 updater from trashing Tiamo's boot.efi might be the creation/modification timestamp of the file itself. For instance, if the "official" boot.efi is dated, let's say, on 1 February 2014, but we cause Tiamo's boot.efi to be dated, say, on 1 September 2187, perhaps the updater wouldn't replace the file. Any thoughts?