Mac Pro 2,1 and OS X Mavericks

[mzb]

Now all work great on 10.9.2 ! , Thanks
But my geForce 8800GT are no more detected by the Mac Pro.
Is it normal?

No, I'm running an 8800GT with no problems. (Mac Pro 1,1 & 10.9.2)

----------

Got my MacPro1,1 back up on Mavericks 10.9.2 using the Tiamo method via oemden's SFOTT scripted installation.

One thing though -- I have 16GB installed and it's only reporting 8GB. The RAM is quality, Apple-compliant DIMMs, and I didn't have a problem with them under 10.9.1 (via Chameleon).

Any ideas as to a) why it's showing this, b) if it's an actual problem or if I can ignore it, and c) how to fix it?

Have you tried sliding out the trays and re-seating all the RAM sticks? My Mac Pro 1,1 would occasionally seem to lose half its RAM but that always fixed it. It actually hasn't happened since Mavericks, but that's probably just a coincidence. Similarly, it might just be a coincidence that yours acted up after the Mavericks install.

 

[Robert Davies]

Have you tried sliding out the trays and re-seating all the RAM sticks? My Mac Pro 1,1 would occasionally seem to lose half its RAM but that always fixed it. It actually hasn't happened since Mavericks, but that's probably just a coincidence. Similarly, it might just be a coincidence that yours acted up after the Mavericks install.

As a backup to this, I recently replaced my RAM risers for just this reason - 16gb of memory only showing as 8gb. For a while the reseating of the trays would cure it, but in the end the final cure was getting another set of risers (S/H) off ebay for very little money.

-Rob

 

[Awediohead]

Huge thanks, especially to Tiamo and also oemden for making things so much easier for the likes of myself who've needed a fair amount of "hand-holding" crossing this particular road! Thanks also to everyone who's contributed to this thread and made it possible to breath a few more years life into my Mac Pro 1,1 with official Apple HD 5770 gfx card.

Though I initially did a clean 10.9.2 install into a small partition to test things, just last night I used a clone of my late 2011 MacBook Pro 10.9.2 install to create a full (all my apps, music and docs) installation on the Mac Pro.

I followed these steps from howjteck (many thanks!) post #726

Yes. The most failsafe procedure would be:
1. Open iTunes and deauthorize your current computer. Close iTunes.
2. Clone your HD using CCC, SuperDuper or similar.
3. After the clone has been made, replace the boot.efi files on the clone.
4. Boot up the Mac Pro with the clone, re-authorize iTunes in the MacBook.
5. Authorize your Mac Pro in iTunes, set up iCloud/iMessages.
6. Apply 10.9.1 to the Mac Pro (does not matter if it is already running 10.9.1 or not. Apply it again if unsure).
7. (on the Mac Pro) run the Disk Utility, fix permissions.


Bit puzzled as to Step 6 - apart from my having used 10.9.2, how do I and why would I want to reapply 10.9.2 to the existing install? Is it about loading drivers and extensions specific to the Mac Pro?

If so, will it mean I have to replace the Boot EFI files again and therefore do the update (somehow?) from another startup volume?

Thanks again!

P.S. This was also very helpful (sorry I've lost where the post was to properly acknowledge my thanks to the poster)

Luckily, if you do run into problems with a file that cannot be edited, either in the Terminal or in the Finder, you can unlock it by performing the following steps using the Terminal:
1. Open the Terminal.
2. Type the following command, followed by a single space (do not press enter yet).


sudo chflags nouchg

3. Drag the locked file from the Finder to the Terminal window to complete its full folder path.
4. Press Enter to run the command, supplying your password when prompted.
When run, this command will undo the lock flag for the file, regardless of whether you own the file.

 

[666sheep]

6. Apply 10.9.1 to the Mac Pro (does not matter if it is already running 10.9.1 or not. Apply it again if unsure).
7. (on the Mac Pro) run the Disk Utility, fix permissions.[/I]


Bit puzzled as to Step 6 - apart from my having used 10.9.2, how do I and why would I want to reapply 10.9.2 to the existing install? Is it about loading drivers and extensions specific to the Mac Pro?

You can easily omit 6 and 7. These steps are pointless.

Luckily, if you do run into problems with a file that cannot be edited, either in the Terminal or in the Finder, you can unlock it by performing the following steps using the Terminal:
1. Open the Terminal.
2. Type the following command, followed by a single space (do not press enter yet).


sudo chflags nouchg

3. Drag the locked file from the Finder to the Terminal window to complete its full folder path.
4. Press Enter to run the command, supplying your password when prompted.
When run, this command will undo the lock flag for the file, regardless of whether you own the file

Another unnecessary step. Just "sudo rm -rf" it and done.

 

[Awediohead]

Thanks 666sheep for the clarification.

Is there anything in moving a clone from MacBook Pro to Mac Pro that IS worth doing? Anything I need to reset/put back/ reconfigure?

For example an obviously needed change is to change the network access name in the Sharing preference pane. This is so VERY easy I'm just wondering if there's not some "under the hood" stuff I need to know about too?

Anything to help things run more smoothly?

thanks again

 

[Robert Davies]

Nothing I can think of - the install's the same these days whether it's on a MacBook Air or a Mac Pro - all the same stuff gets installed whether the machine needs it or not.

 

[Awediohead]

Nothing I can think of - the install's the same these days whether it's on a MacBook Air or a Mac Pro - all the same stuff gets installed whether the machine needs it or not.

Thanks for the reassurance Robert
Out of interest I ran repair permissions and it did need to repair permissions for the usr/standalone/i386/boot.efi

User differs on “usr/standalone/i386/boot.efi”; should be 0; user is 501.Group differs on “usr/standalone/i386/boot.efi”; should be 0; group is 20.Permissions differ on “usr/standalone/i386/boot.efi”; should be -rw-r--r-- ; they are -rwxr-xr-x .Repaired “usr/standalone/i386/boot.efi”

no idea if that's helpful to anyone

 

[LoLL31]

Thank you so much! I will do some reading up on it so I understand it a bit more before trying it, and will report back results.

Did you set yours up in this way?

Nope, did it manually.
But i launched scripts on my mac and they ran fine.
Of course you must have the modded boot.efi installed as /usr/standalone/i386/boot.efi.tiamo to run ,-) (or change path to $(dirname $0) if file is copied in same folder as the script)

 

[haralds]

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...

I have a mirrored partition for my boot system. The boot system is a 960GB SSD mirrored to a conventional disk partition. This one was still upgraded to 10.9.2 with the failing Messages. When I upgraded that to the (undisclosable) seed 10.9.x Release, Messages immediately popped back up working! However, an upgrade of the boot partition in use (the SSD) from 10.9 to 10.9.x results in its Messages failing.
I simply cloned the working 10.9.x backup to the SSD, which restored a functioning Messages.
Some other info:
- I had previoulsy restored the whole ~/Library folder from the working clone.This includes not just prefs, but also keychains (in case of certifcate errors somewho not caught in looking), and caches. This had not solved the problem.
- Since the issue persisted across multiple installs, corrupted binaries were not likely an issue.

This leads me to believe that the OS keeps some other security token in another location that was somehow corrupted. But going through a diff on a running platform is way too tedious. Hopefully, this will not break again...

ps Yes, Apple slapped my fingers for mentioning the seed in another location despite the fact that I disclosed no info on its details except its existence...

 

[makaveli559m]

Thanks 666sheep for the clarification.

Is there anything in moving a clone from MacBook Pro to Mac Pro that IS worth doing? Anything I need to reset/put back/ reconfigure?

For example an obviously needed change is to change the network access name in the Sharing preference pane. This is so VERY easy I'm just wondering if there's not some "under the hood" stuff I need to know about too?

Anything to help things run more smoothly?

thanks again

I didn't have no issues except maybe with some I had on my MacBook Pro for the switchable graphics and fans. All I had to do was delete them, everything worked great out of the copy :O I was surprised because my MacBook Pro is a 2010 model and my Mac Pro is a 2007.

 

[!Xabbu]

Works on MBP2,2 too ;-)

Out of interest i tried to make this work on my MBP2.2 and i can confirm it does !!!

Great work from all involved into this !
Only audio doesn't work yet ( applehda.kext needs to be patched ).

 

[Rastafabi]

Out of interest i tried to make this work on my MBP2.2 and i can confirm it does !!!

Great work from all involved into this !
Only audio doesn't work yet ( applehda.kext needs to be patched ).

Well… It's know, that Mavericks runs on ANY 32bit EFI Mac with 64bit CPU, which does NOT mean, that it's working. And no, it does not in your case as you don't have OpenGL acceleration. Which means that you cannot even watch a higher quality YouTube video. Also several system animations are horribly slow (it takes several seconds to open Launchpad).

Working? No, I don't think so, unless you want to use it as a server.

EDIT: Watch your screenshot. It reports 5MB of usable graphics ram. I already got it to show 256mb (BTO machine), but still you won't have acceleration so it's useless.

 

[gavinstubbs09]

I'm having horrible luck getting 10.9.2 working, all I get on reboot is a flashing folder so something in MV went corrupt. Tried the basic repair disk permissions, safe mode, reinstall 10.9.1 then try some ways around the update, no luck at all getting it to boot

 

[!Xabbu]

Well… It's know, that Mavericks runs on ANY 32bit EFI Mac with 64bit CPU, which does NOT mean, that it's working. And no, it does not in your case as you don't have OpenGL acceleration. Which means that you cannot even watch a higher quality YouTube video. Also several system animations are horribly slow (it takes several seconds to open Launchpad).

Working? No, I don't think so, unless you want to use it as a server.

EDIT: Watch your screenshot. It reports 5MB of usable graphics ram. I already got it to show 256mb (BTO machine), but still you won't have acceleration so it's useless.

I just wanted to find out if Mavericks could be installed on my MBP , nothing more. I know it's not perfect and yes you're right the graphics are not the best...anyway

 

[hwojtek]

I followed these steps from howjteck (many thanks!) post #726
(cut!)
6. Apply 10.9.1 to the Mac Pro (does not matter if it is already running 10.9.1 or not. Apply it again if unsure).
Bit puzzled as to Step 6 - apart from my having used 10.9.2, how do I and why would I want to reapply 10.9.2 to the existing install? Is it about loading drivers and extensions specific to the Mac Pro?

You're welcome. Yes, it's about applying the proper drivers, just in case. I tend to play it (triple) safe, although as 666sheep noted - this is kinda redundant. And as you've correctly pointed out, this procedure won't work with 10.9.2, since the boot.efi would be replaced again.
I personally just put the Pro into FW target mode and replace the files by hand.

 

[the bug]

So, has anyone sucessfully gotten the recovery partition working on a system that is using the Tiamo boot.efi file ?

I have a recovery partition and it supports "Find my Mac" and all that, but I can't boot from it.

I've tried replacing the boot.efi in the "com.apple.recovery.boot" directory without any success, and I've also tried replacing the "BaseSystem.dmg" with a modified version from the installer that should boot my machine with no luck.

I am still able to use my USB installer to do most functions, but it would be nice to get the recovery partition to do what it is there for.
Otherwise it seems like a lot of wasted disk space just to get "Find my Mac" working.

Anyone messed around with this ?

- Jay

 

[JoSch]

So, has anyone sucessfully gotten the recovery partition working on a system that is using the Tiamo boot.efi file ?

I have a recovery partition and it supports "Find my Mac" and all that, but I can't boot from it.

I've tried replacing the boot.efi in the "com.apple.recovery.boot" directory without any success, and I've also tried replacing the "BaseSystem.dmg" with a modified version from the installer that should boot my machine with no luck.

I replaced the boot.efi and nothing more was needed.
Perhaps you haven't really replaced the boot.efi on the recovery volume, because it's secured like the ones on your MacosX volume.
You should check whether you really changed boot.efi.

 

[ratedgforgraeme]

I'd like to thank Tiamo, Rastafabi, and everybody else on this forum for all the help they've provided. You guys are truly amazing. I really appreciate everything. I've gone through every page to try to find an answer to this, but I can not. If anyone could offer some advice, I'd really appreciate it. If not, no worries!

I downloaded the 10.9.1 install on my work MBP Retina.

-I successfully (? or appears I successfully) made the installer usb key with the correct model and board id.

-I have a Mac Pro 1,1 with swapped 2 x X5350 (2.66 quad core) and an Apple 5770 Graphics card. I've done the firmware flash/upgrade to 2,1.

- I have a Bootcamp drive in the machine, a lion drive, a 500GB drive for storage, and my drive I intended to install mavericks on. I also have a 64GB SSD that I used as a boot drive for snow leopard that I intended to use a a boot drive for Mavericks.

-I used the Mavericks installer to successfully install Mavericks. I rebooted into lion and swapped the PlatformSupport.plist.
-I restarted holding down option and selected my new 10.9.1 Mavericks drive.
-The first boot caused a kernel panic.
-I restarted again, resetting the PRAM, and it booted up into Mavericks.
-Occasionally when restarting I get several panics and then it boots into Mavericks after 2 or 3 reboots.
-My soundcard, bluetooth devices, and airport card all appear to be working. Sleep is also functioning.
-I have 12GB 6x2GB of ram only reading as 6GB.

My issue is when I go and try to set the startup disk in the system preferences I get a "Bless tool was unable to set current disk" message. Does anyone have any input on this? When I get home I'm going to try resetting the SMC and also checking out this page

I also tried cloning the Mavericks Drive without my user folder with CCC to my SSD to make a boot drive. Trying to select this as the startup disk gives me the same message about the bless tool. Rebooting holding down [Option] allows me to boot from the cloned drive, but it takes substantially longer than when I was using it as a boot drive for snow leopard. I notice when I do this, it takes about a minute to boot. The fans kick on, there is a bright white apple startup screen, the fans kick off, then it goes to a slightly darker apple startup screen and it boots off my ssd. Is this because of the new boot.efi?

Please forgive my ignorance. I'm pretty good at tinkering and following instructions but I'm at a place where I need some help. Do the sporatic kernel panics indicate that I may have botched the initial installation process. Thanks again for all the help and assistance you've provided so far!

 

[the bug]

I replaced the boot.efi and nothing more was needed.
Perhaps you haven't really replaced the boot.efi on the recovery volume, because it's secured like the ones on your MacosX volume.
You should check whether you really changed boot.efi.

DOH !
You are right, tried changing permissions and overwriting original boot.efi with terminal again but it didn't get replaced.
I thought "sudo chflags nouchg" would let me overwrite it, but apparently not for some reason.

I finally used FileBuddy to unlock and delete the file from the Finder, then copied Tiamo's magical file to the recovery partition, and it works WooHoo !!

Thanks again.

- Jay

----------

My issue is when I go and try to set the startup disk in the system preferences I get a "Bless tool was unable to set current disk" message. Does anyone have any input on this? When I get home I'm going to try resetting the SMC and also checking out

Yes I had the same thing happen to me, at first I was inadvertently using the wrong boot.efi file.

You must use this one :
https://forums.macrumors.com/attachment.php?attachmentid=449107&d=1385430562
and not the one that is included with the HackerWayne package that pre-dates Tiamo's file.

Hopefully this helps.

- Jay

 

[ratedgforgraeme]

Yes I had the same thing happen to me, at first I was inadvertently using the wrong boot.efi file.

You must use this one :
https://forums.macrumors.com/attachment.php?attachmentid=449107&d=1385430562
and not the one that is included with the HackerWayne package that pre-dates Tiamo's file.

Hopefully this helps.

- Jay

I'll give this a try when I get home. The boot.efi I'm using is 461kb but it's a different date then the one you just linked me to, so It's definitely worth a try. Thanks Jay!

 

[the bug]

I'll give this a try when I get home. The boot.efi I'm using is 461kb but it's a different date then the one you just linked me to, so It's definitely worth a try. Thanks Jay!

I did some digging and found this link again.
When I had the problems blessing the start up drive it was because I accidentally used the boot.efi file from this package. :
https://forums.macrumors.com/posts/18357265/

It's not actually HackerWayne's work, as I mistakenly said earlier, I just remembered his name because I found it in a thread that he started.

This package is pretty nice, it has documentation and all the tools you need to make your own Mavericks installer and prep your system for the upgrade.

The only thing to remember is to replace the boot.efi that comes with this package, because even though you can boot from it and it seems to run fine, this boot.efi doesn't support certian EFI services like "bless".

Hopefully all you have to do is swap out your files with Tiamo's.
Good luck.

- Jay

 

[F.A.D.]

HELP! I get a folder with a question mark after updating to 10.9.2 with the macprofix

HELP! The update to 10.9.2 did not work and I have important files on there that I can't access :-(

I installed the TiamoMacPro fix on my Mac Pro 1.1 running 10.9.1 I rebooted and rebooted again to see that the EFI files are freshly replaced.

I then installed the 10.9.2 update. I now get a folder with a question mark when booting and nothing else happens. I rebooted several times but I just get the folder with the question mark.

When I hold option while booting up I get the four individual drives from my RAID-0 instead of the one RAID-0 that I get normally. There is no recovery partition showing up.

I know its maybe stupid from me to update because I have important files on there but it sounded pretty safe.

How can I access these files again (especially because it is showing the individual drives of the RAID instead of one drive symbol for the RAID-0). Is there something I can boot from to see those files and copy them somewhere like an external hard disk? Any gel on that is very much appreciated!!!!

Thank you all in advance!

Best regards,

David

 

[PeterHolbrook]

HELP! The update to 10.9.2 did not work

On the contrary, it seems to have worked all right, since it replaced boot.efi, as it was intended to do, thereby erasing Taimo's version and rendering your computer unbootable. I suggest that you boot your computer using an older OS X install DVD (such as Snow Leopard) and then, from the relevant menu, open Terminal, navigate to the relevant folders in your Mavericks disk, and manually restore Tiamo's version of boot.efi.

 

[F.A.D.]

On the contrary, it seems to have worked all right, since it replaced boot.efi, as it was intended to do, thereby erasing Taimo's version and rendering your computer unbootable. I suggest that you boot your computer using an older OS X install DVD (such as Snow Leopard) and then, from the relevant menu, open Terminal, navigate to the relevant folders in your Mavericks disk, and manually restore Tiamo's version of boot.efi.

Yeah the update itself worked but not TiamosMacProFix because it should have replaced the files :-(

Sadly I have no idea how to replace files via the Terminal. There is also the problem that I have a RAID-0 consisting of four SSD's so to access the data I cannot pull out a drive bay.

I just booted with the original SFOTT stick and tried to make an image from the boot drive onto an external disk to access the data that is important but after 6 hours it seemed to hung up... :-(

I installed two Blu-Ray drives and therefore connected a SATA cable to the two hidden SATA ports on the main board behind the front fan. I try to connect an old SATA HDD to one of them and try to install Lion on it and replace the boot EFI files from there. We will see if that works *fingerscrossed*

Thanks for your help!

 

[ratedgforgraeme]

I did some digging and found this link again.
When I had the problems blessing the start up drive it was because I accidentally used the boot.efi file from this package. :
https://forums.macrumors.com/posts/18357265/
...
Hopefully all you have to do is swap out your files with Tiamo's.
Good luck.

- Jay

This was exactly my problem! I changed it, everything boots perfectly, quickly, and every time without any issue. Thank you so much for the help!

I also setup the boot.efi Daemon, and restarted twice, confirmed it was getting copied, and proceeded to successfully update via the app store to 10.9.2.

This is so amazing. Thanks again to everyone involved.

Take care