It just replaces boot.efi with a newer one. It's NOT a measure taken against Tiamo's boot.efi.
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
It just replaces boot.efi with a newer one. It's NOT a measure taken against Tiamo's boot.efi.
Did the update via App Store
I did my update with the apple store. it Restarted on my lion partition on it s own. I replace the boot.efi in the corservice folder and then restart it. It booted on 10.9.2 finished the install. Everything is working like a charm.
I did my update with the apple store. it Restarted on my lion partition on it s own. I replace the boot.efi in the corservice folder and then restart it. It booted on 10.9.2 finished the install. Everything is working like a charm.
It is not removing the EFI. EFI is something different than the boot.efi file the update replaces with an updated one. Why? → tcook@apple.com
I have a hard time understanding this question. Is there a beginners' version?
After X.9.2 update and reinjected both efi files, i can not boot in mavericks :-(
My X.9 volume is fusion type with SSD + HDD. The EFI file i used are the following (gfx):
localhost:FusionOSX9 mac$ ls -l usr/standalone/i386/boot.efi* System/Library/CoreServices/boot.efi*
-rw-r--r--@ 1 root *wheel *461312 26 fév 01:21 System/Library/CoreServices/boot.efi
-rw-r--r--@ 1 root *wheel *505400 *6 déc 10:59 System/Library/CoreServices/boot.efi_x92
-rw-r--r--@ 1 root *wheel *461312 26 fév 01:16 usr/standalone/i386/boot.efi
Is there anybody else using fusion drive with MacPro 1,1 ? I'm thinking fusion is the problem...
My X.9 volume is fusion type with SSD + HDD. The EFI file i used are the following (gfx):
localhost:FusionOSX9 mac$ ls -l usr/standalone/i386/boot.efi* System/Library/CoreServices/boot.efi*
-rw-r--r--@ 1 root *wheel *461312 26 fév 01:21 System/Library/CoreServices/boot.efi
-rw-r--r--@ 1 root *wheel *505400 *6 déc 10:59 System/Library/CoreServices/boot.efi_x92
-rw-r--r--@ 1 root *wheel *461312 26 fév 01:16 usr/standalone/i386/boot.efi
Is there anybody else using fusion drive with MacPro 1,1 ? I'm thinking fusion is the problem...
Last edited:
Not specifically a fusion drive but I am using a Seagate SSHD with out any problems.
Mac Pro 1,1 and OS X Mavericks 10.9.2 success!
I too was able to successfully update Mac Pro 1,1 to 10.9.2 following the same steps quoted below.
I also have a dual boot 10.7.5 / 10.9.2 machine (with ATI Radeon HD 5770 1024MB video card).
I too was able to successfully update Mac Pro 1,1 to 10.9.2 following the same steps quoted below.
I also have a dual boot 10.7.5 / 10.9.2 machine (with ATI Radeon HD 5770 1024MB video card).
Fusion is like LVM : it's pure software embedded in OS.
BUT i post now from X.9.2 ;-)
In fact, after listing Fusion drive partionnement, i found 2 partitions as Apple_Boot :
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 119.7 GB disk0s2
3: Apple_Boot Boot OS X 134.2 MB disk0s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_CoreStorage 499.8 GB disk2s2
3: Apple_Boot Boot OS X 134.2 MB disk2s3
So after mounting each one, there was the updated boot.efi on each of them. Replacing them with modded one, i could start on X.9.2 !
cool
Fusion is like LVM : it's pure software embedded in OS.
BUT i post now from X.9.2 ;-)
In fact, after listing Fusion drive partionnement, i found 2 partitions as Apple_Boot :
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 119.7 GB disk0s2
3: Apple_Boot Boot OS X 134.2 MB disk0s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_CoreStorage 499.8 GB disk2s2
3: Apple_Boot Boot OS X 134.2 MB disk2s3
So after mounting each one, there was the updated boot.efi on each of them. Replacing them with modded one, i could start on X.9.2 !
cool
I have to say that I have been reading up on creating a fusion drive - the further I go into it, the less clear it becomes!
I have not been able to get Messages working properly with 10.9.2
It first complains that it could not log in and you have to restart. After restarting it, I can log in, but messages go out very slowly and there is no history. Incoming messages register on other machines, but not the Mac Pro.
I replaced what appeared to be the related frameworks and messages from 10.9, but that did not work at all.
Rebooting into 10.9 messages works well.
If it was not for the SSL bug, I would revert.
Hello haralds,
I have been doing a bit of informal testing of Messages since you reported the issue. I am sorry but I cannot replicate the issue currently, but I am keeping a watchful eye on it.
-Rob
ps Do you have an iPhone linked to your Messages accounts? If so, any issue on the iPhone?
New Sfott script version for 10.9.2
Hello everybody,
I've been lazy on coding last weeks....
but last day was scripting day.
So here it is I've updated the script to get 10.9.2 up and running "easily".
it just does what others have done aka copy the boot.efi back on the new 10.9.2 system AND repatch the plist files in CoreServices and such as they also are replaced by the update - I did not notice it would fail if they are not patched again but I think it's better to do so.
So basically you do :
- get the new sfott key, install it on the system you use to create the key and install it too on your sfott key (you can also update the script on the key it with the new script now)
- Update to 10.9.2
- reboot and wait to get the failure or the boot in Lion if you have one on a disc...
- shutdown
- insert the softt key
- boot from the key (option/alt key pressed at boot)
- at installer window, choose Utilities => terminal
- run sfott or /usr/sbin/sfott
it will make the volume readable and writable before launching the script.
you have to :
Set the computer to add (obviously this will be the current Mac ! choose option 1) or enter it manually ? )
Select the Os X version to: Mavericks (again obvious here)
Choose the target System to Re-patch (your current computer System Volume)
Eventually choose Tiamos verbose boot.efi, Tiamos graphic boot.efi is the default
then you're good to go and patch your system. once done, reboot and let the installer finish the update.
I've done it on both Macpro1,1 and Macmini2,1.
I'll focus now and continue my recovery utility I'm working on....
Cheers, going to sleep now
script page here : http://oemden.com/?page_id=531
some steps I explained above here : http://oemden.com/?p=791
Hello everybody,
I've been lazy on coding last weeks....
but last day was scripting day.
So here it is I've updated the script to get 10.9.2 up and running "easily".
it just does what others have done aka copy the boot.efi back on the new 10.9.2 system AND repatch the plist files in CoreServices and such as they also are replaced by the update - I did not notice it would fail if they are not patched again but I think it's better to do so.
So basically you do :
- get the new sfott key, install it on the system you use to create the key and install it too on your sfott key (you can also update the script on the key it with the new script now)
- Update to 10.9.2
- reboot and wait to get the failure or the boot in Lion if you have one on a disc...
- shutdown
- insert the softt key
- boot from the key (option/alt key pressed at boot)
- at installer window, choose Utilities => terminal
- run sfott or /usr/sbin/sfott
it will make the volume readable and writable before launching the script.
you have to :
Set the computer to add (obviously this will be the current Mac ! choose option 1) or enter it manually ? )
Select the Os X version to: Mavericks (again obvious here)
Choose the target System to Re-patch (your current computer System Volume)
Eventually choose Tiamos verbose boot.efi, Tiamos graphic boot.efi is the default
then you're good to go and patch your system. once done, reboot and let the installer finish the update.
I've done it on both Macpro1,1 and Macmini2,1.
I'll focus now and continue my recovery utility I'm working on....
Cheers, going to sleep now
script page here : http://oemden.com/?page_id=531
some steps I explained above here : http://oemden.com/?p=791
Apart from the boot.efi obviously, I've never patched anything else on my system(s) - everything seems to work ok - Messages, Game Center (for what it's worth!)
…and many thanks btw!!!
…and many thanks btw!!!
Thanks for trying to help.
I have reverted the disk to 10.9 and messaging is working great.
I have two other MacBooks (Air and Pro) plus 4 iDevices. All are linked via the the main iCloud email and iPhone cell. All work as expected.
Puzzling and frustrating. I have replicated the issue on multiple installation disks and accounts. My Mac Pro uses ethernet, not sure that is an issue. Have not tried that...
Combo 10.9.1 Updater
The only 10.9.1 updater I have found is for the new Mac Pro and MacBook Pro.
I currently cannot get messages to work, so I am on 10.9.0, but would like to go to at least 10.9.1
The only 10.9.1 updater I have found is for the new Mac Pro and MacBook Pro.
I currently cannot get messages to work, so I am on 10.9.0, but would like to go to at least 10.9.1
I believe this is a sort of security measure to have boot partitions on both disks that form a Fusion Drive - to allow booting in case of a hardware failure of any of the disks. Like it would help in anything anyway...I have to say that I have been reading up on creating a fusion drive - the further I go into it, the less clear it becomes!
Just finished tiamo's Mavericks process on a Mac Pro 1,1. Everything went ok. Migrated all my apps from Lion with only Vmware Fusion choking on the the difference int the OS.
However.... I have NO audio, and no audio devices show up. I've tried every combination of .kext changes, verifying permissions, resetting PRAM, etc but still can't figure out what's going on. I'm wondering if I stepped on something while trying out various solutions.
Should I wipe out my disk and start the upgrade process over?
Thoughts?
However.... I have NO audio, and no audio devices show up. I've tried every combination of .kext changes, verifying permissions, resetting PRAM, etc but still can't figure out what's going on. I'm wondering if I stepped on something while trying out various solutions.
Should I wipe out my disk and start the upgrade process over?
Thoughts?
Very good question indeed! (substitute "removing" with "changing" to get the idea).
Why altering the boot.efi? Is there some benefit I'd like to have?
Oops! Sorry!
From a quick look at and comparison of before and after of my MacBook Air* the boot.efi was not changed, so there appears to be a check mechanism in the OS X updater that checks the boot.efi, if the answer is unexpected, the boot.efi is replaced, else it is left alone.
*which obviously does NOT have Tiamo's boot.efi.
It's kind of strange the way the combo updater worked this time, slightly different than in the past.Oops! Sorry!
From a quick look at and comparison of before and after of my MacBook Air* the boot.efi was not changed, so there appears to be a check mechanism in the OS X updater that checks the boot.efi, if the answer is unexpected, the boot.efi is replaced, else it is left alone.
*which obviously does NOT have Tiamo's boot.efi.
I had quick look at the combo updater with Pacifist before I ran it, and it appears that only the /usr/stanalone/i386/boot.efi gets replaced on this update.
Although after running the update I did reboot to another external drive and replace both instances with Tiamo’s file.
I did notice though, that the file size of both instances (after the update) were different from Tiamo’s file, even though in theory only one instance was replaced .
I can’t help but wonder if the new update mechanism (the way the combo updater, did sort of a semi-warm-reboot without a full shutdown, to install the rest of the update) was the reason for the change of the standalone boot.efi.
I reckon we will find out on the next update, if it uses the same mechanism and has problems launching from an unrecognized standalone boot.efi.
Other than that everything is running great on my 1,1 with 10.9.2, and I’ve been dying to be the first one to say “Safari just feels snappier ! ”
It really doesn't, I just wanted to be the first.
- Jay
I should've checked this thread before i updated....
So I have a 1,1 with a GTX 570. After it updated throught software update it of course refused to boot back up. I was able to get it into windows. From windows I replaced the boot.efi in both directories and rebooted into mac. It still doesnt seem to boot. I've tried to get back into windows and now that doesnt seem to work or maybe i'm just not selecting the right drive. I cant see what i'm doing. I had a feeling this would happen when I sold my old card off.
Whats the cheapest card i can get that will give me a display? I'm not sure what else to do at this point. I cant even do target disk mode because i dont have any other firewire computers and I cant use thunderbolt because the mac pro doesnt have it.
edit: i managed to get myself back into windows for now. Going to recreate my steps. As far as I can tell i'm putting the boot.efi in the right place. I just hope windows isnt mucking it up. i'm using macdrive to do all of this work
edit 2: i figured out what i did wrong and i'm a complete retard lol
So I have a 1,1 with a GTX 570. After it updated throught software update it of course refused to boot back up. I was able to get it into windows. From windows I replaced the boot.efi in both directories and rebooted into mac. It still doesnt seem to boot. I've tried to get back into windows and now that doesnt seem to work or maybe i'm just not selecting the right drive. I cant see what i'm doing. I had a feeling this would happen when I sold my old card off.
Whats the cheapest card i can get that will give me a display? I'm not sure what else to do at this point. I cant even do target disk mode because i dont have any other firewire computers and I cant use thunderbolt because the mac pro doesnt have it.
edit: i managed to get myself back into windows for now. Going to recreate my steps. As far as I can tell i'm putting the boot.efi in the right place. I just hope windows isnt mucking it up. i'm using macdrive to do all of this work
edit 2: i figured out what i did wrong and i'm a complete retard lol
Last edited:
Messages persistently not working after 10.9.2 Upgrade
I reported on this in an earlier post. Here is some more detail:
I have upgraded five machines to 10.9.2, but my Mac Pro has run into a persistent problem with Messages.
On startup, I get a Message that an internal error has ocurred and asks me to relaunch. After that the window comes up and the acount window shows me logged in, but the history is not updated and new messages take forever to deliver or do not go through at all. They usually do not update on the local display.
The console log shows lot of failures like these:
- 2/27/14 6:33:44.954 PM imagent[371]: [Warning] __XPCIMDMessageStoreSendXPCMessage failed too many times...bailing!
I have set up another account and tried logging in from it, but it shows the same behavior.
The firewall is off, certificates seem to be fine. When I log out of Messages and back in, the other systems devices get all the nag messages about the system and numbers being added, so it is communicating with the server. But messages are not coming through.
I have cleared all preferences and caches, but the behavior does not change.
Multiple times, I have reverted the system to 10.9 by installing over it. Messages immediately works fine (same preferences etc.) Everything works great, but I'd rather not live with the SSL bug.
I have upgraded using both the Combo Updater and twice using the App Store upgrade from 10.9 and 10.9.1. The behavior stays the same.
The other four machines and my 4 iOS devices are all working as expected.
Does anybody have any ideas? My family and friends use Messages a lot, so I need it on my main machine.
Thanks,
-- Harald
I reported on this in an earlier post. Here is some more detail:
I have upgraded five machines to 10.9.2, but my Mac Pro has run into a persistent problem with Messages.
On startup, I get a Message that an internal error has ocurred and asks me to relaunch. After that the window comes up and the acount window shows me logged in, but the history is not updated and new messages take forever to deliver or do not go through at all. They usually do not update on the local display.
The console log shows lot of failures like these:
- 2/27/14 6:33:44.954 PM imagent[371]: [Warning] __XPCIMDMessageStoreSendXPCMessage failed too many times...bailing!
I have set up another account and tried logging in from it, but it shows the same behavior.
The firewall is off, certificates seem to be fine. When I log out of Messages and back in, the other systems devices get all the nag messages about the system and numbers being added, so it is communicating with the server. But messages are not coming through.
I have cleared all preferences and caches, but the behavior does not change.
Multiple times, I have reverted the system to 10.9 by installing over it. Messages immediately works fine (same preferences etc.) Everything works great, but I'd rather not live with the SSL bug.
I have upgraded using both the Combo Updater and twice using the App Store upgrade from 10.9 and 10.9.1. The behavior stays the same.
The other four machines and my 4 iOS devices are all working as expected.
Does anybody have any ideas? My family and friends use Messages a lot, so I need it on my main machine.
Thanks,
-- Harald
I should've checked this thread before i updated....
So I have a 1,1 with a GTX 570. After it updated throught software update it of course refused to boot back up. I was able to get it into windows. From windows I replaced the boot.efi in both directories and rebooted into mac. It still doesnt seem to boot. I've tried to get back into windows and now that doesnt seem to work or maybe i'm just not selecting the right drive. I cant see what i'm doing. I had a feeling this would happen when I sold my old card off.
Whats the cheapest card i can get that will give me a display? I'm not sure what else to do at this point. I cant even do target disk mode because i dont have any other firewire computers and I cant use thunderbolt because the mac pro doesnt have it.
edit: i managed to get myself back into windows for now. Going to recreate my steps. As far as I can tell i'm putting the boot.efi in the right place. I just hope windows isnt mucking it up. i'm using macdrive to do all of this work
Being as you haven't told us where you are replacing the boot.efi s we cannot tell if you are putting them in the right place - hint post 854, but forget the _92 lines
Tiamo's boot.efi is 462kb or very near whereas the Apple one is 505kb or thereabouts.
Cheapest card? Depends, but ones I know work are the Mac 2600xt and the Mac 5770 - another that may work is the Mac X1900XT - but that was hopelessly unreliable even when new - in my experience.
I've been meaning to get an Apple TB -> Firewire adaptor to see if Target Disk mode works across to the MP - but, I haven't so I cannot comment, sorry
Last edited:
I have seen the Apple HD-4870 on eBay for $89. It works all the way to back to Tiger and is of equivalent performance to the HD-5770 (but uses more power.) I found it to be very reliable.Being as you haven't told us where you are replacing the boot.efi s we cannot tell if you are putting them in the right place - hint post 854, but forget the _92 lines
Tiamo's boot.efi is 462kb or very near whereas the Apple one is 505kb or thereabouts.
Cheapest card? Depends, but ones I know work are the Mac 2600xt and the Mac 5770 - another that may work is the Mac X1900XT - but that was hopelessly unreliable even when new - in my experience.
I've been meaning to get an Apple TB -> Firewire adaptor to see if Target Disk mode works across to the MP - but, I haven't so I cannot comment, sorry