I met these problems today. I wanted to use an 8800GTS flahed as 8800GT/EFI in a MacPro4,1 but in vain.
Also GT120 doesn't run in MacPro2,1 with Tiamo efi boot file.
So i stay with cards as it was...
Apple and EFI, tss tss..
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
I met these problems today. I wanted to use an 8800GTS flahed as 8800GT/EFI in a MacPro4,1 but in vain.
Also GT120 doesn't run in MacPro2,1 with Tiamo efi boot file.
So i stay with cards as it was...
Apple and EFI, tss tss..
I don't know, and I've not been worried by it since installing the app from here:
https://forums.macrumors.com/posts/18829695/
I'm not familiar with this, as I haven't been to the boards since I updated to 10.9.2 (the hard way) a little while back.
So what does this little app do? Does it run some little background service that ensures the modified boot.efi file is properly copied to the right locations prior to any reboot?
Also, my boot drive is a three-drive RAID 0, and another user had issues with this package file and his four-drive RAID, I think I will lay off installation of this package file for the moment...
Last edited:
HEEEEELPPP!! Can't boot after security update
I applied security update and now it doesn't boot on Mavericks. After a while it just boots on my Windows HD. I doesn't reboot on Mavericks selecting it from the bootcamp application on windows nor selecting Mavs HD at booting time on Mac!! (I reinstalled Tiamo's boot.efi files again like I did with 10.9.2, but still not working).
Anyone with some ideas??
Some more background. I did have this problem before with d*mn bootcamp. After success with 10.9 on my Mac Pro for some weeks, I restarted selecting my windows HD from startup disk panel on systems preference and after that I couldn't make it to reboot on Mavericks. I reinstalled mavericks, only used Paralles and all fine until today (I was also applying updates to windows that required a restart all done in parallels) and I applied security update.
Now I can't reboot on Mavericks and hopefully don't need to reinstall everything again!!!
I applied security update and now it doesn't boot on Mavericks. After a while it just boots on my Windows HD. I doesn't reboot on Mavericks selecting it from the bootcamp application on windows nor selecting Mavs HD at booting time on Mac!! (I reinstalled Tiamo's boot.efi files again like I did with 10.9.2, but still not working).
Anyone with some ideas??
Some more background. I did have this problem before with d*mn bootcamp. After success with 10.9 on my Mac Pro for some weeks, I restarted selecting my windows HD from startup disk panel on systems preference and after that I couldn't make it to reboot on Mavericks. I reinstalled mavericks, only used Paralles and all fine until today (I was also applying updates to windows that required a restart all done in parallels) and I applied security update.
Now I can't reboot on Mavericks and hopefully don't need to reinstall everything again!!!
I very much doubt the security update has anything to do with it. I suggest that you try resetting your PRAM and making sure your motherboard button battery is alive. You'll know it's alive if you can choose a boot device when you press Alt when you hear the chime at boot up. If no option is presented, your button battery might have died on you and made your Boot Camp partition your default one.
If that were to be the case, no matter what you do, your choice of default boot device won't stick. In that case, and supposing your HFSJ and NTFS partitions are in different physical disks, and if your Macintosh HD and your Windows disks are, let's say, in Bays 2 and 1, respectively, exchange them and see if that works while you get a new battery.
Same here, just installed the update, can confirm that the boot files have been overwritten and are now 64-bit (booted from my laptop on my Mac Pro's drive at the moment). Replacing the files once more, will update!
Also, date modified on the boot.efi file in System - Library - CoreServices now has a date modified date of today, so yeah...
Update: Replaced both files, all is right in the world again.
So, don't install the security update if you don't have another computer handy to replace the boot files!
Last edited:
I guess I'll ask the question again, why in heck is Apple making it so hard to update the early Mac Pros? It seems, they, on purpose wrote code specifically excluding the 1,1 and 2,1 for no good reason that I can think of. As users have proved by installing this mod, the hardware is certainly powerful enough and capable of running OS 10.9 without issue.
Lou
Thanks Peter, I agree sec update shouldn't be related to the booting problem, i was just hoping to see if somebody else may have experienced the same problem or there was a known issue with bootcamp-mavericks-pro 1,1.
Anyway, battery is alive, I'll search for PRAM reseting.
As DrNeroCF mentioned, i can confirm that my boot.efi files were updated by the security update. They are 505K instead of TIAMO's 461K and one of them dated today 1:12 AM. I couldn't replace boot.efi files correctly so after wasting some time on this I'm in a full time machine restore now ...
I'll retry the update tomorrow and share my results
Anyway, battery is alive, I'll search for PRAM reseting.
As DrNeroCF mentioned, i can confirm that my boot.efi files were updated by the security update. They are 505K instead of TIAMO's 461K and one of them dated today 1:12 AM. I couldn't replace boot.efi files correctly so after wasting some time on this I'm in a full time machine restore now ...
I'll retry the update tomorrow and share my results
There is a very good reason:
They want you to buy a new computer - and they don't want to support an old one.
Companies do what is in their best interest - not yours.
Happy to join the club!
Exact! So, we'll take care by ourself
First post here. Have read all posts from page 1, followed the instructions and i'm now happy to say my old MacPro is running very well with Mavericks 10.9.2 (13C1021). Just applied the last security update (5 minutes ago) and everything's fine. Thanks a lot to this wonderful Mac community, specially to Tiamo and tobyg for such a great job and support!
My kit : MacPro 1,1 (flashed to 2,1), 2 x 3 GHz Quad-Core (used from eBay), 22 Go memory (half Apple approved, half used pulled from server), Nvidia GeForce GT 640 2048 Mo.
Exact! So, we'll take care by ourself
First post here. Have read all posts from page 1, followed the instructions and i'm now happy to say my old MacPro is running very well with Mavericks 10.9.2 (13C1021). Just applied the last security update (5 minutes ago) and everything's fine. Thanks a lot to this wonderful Mac community, specially to Tiamo and tobyg for such a great job and support!
My kit : MacPro 1,1 (flashed to 2,1), 2 x 3 GHz Quad-Core (used from eBay), 22 Go memory (half Apple approved, half used pulled from server), Nvidia GeForce GT 640 2048 Mo.
Hi tobyg. Tell me, why is this important? I never bothered with any of that on my install.
I applied the Security Patch on my 10.9.2 machine, Everything still runs perfectly.
The Security Patch should not effect your machine boot.efi, The patch fixes security certificates like (SSL, and bug fixes,etc..) Has nothing to do with the Core OS.
The Security Patch should not effect your machine boot.efi, The patch fixes security certificates like (SSL, and bug fixes,etc..) Has nothing to do with the Core OS.
tobyg said:
You didn't bother to quote the entire line:
tobyg said:
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.
Anyone else with power saving issues? Not waking up properly.
Hello likeminded,
does anyone of you have problems with your 32bit Maveicks mac to wake up properly from energy save mode?
My Mac Pro 1.1 (flashed to 2.1) is always rebooting (and it is a longer reboot than the usual boot up) when waking him up (pressing spacebar f.e.). The energy save from the displays is working o.k.
I also did a fresh install with the newest release of mavericks as well as sfott but the problem still remains.
I also disabled the option that the power save mode from the hard disks is activated.
Best regards,
David
Hello likeminded,
does anyone of you have problems with your 32bit Maveicks mac to wake up properly from energy save mode?
My Mac Pro 1.1 (flashed to 2.1) is always rebooting (and it is a longer reboot than the usual boot up) when waking him up (pressing spacebar f.e.). The energy save from the displays is working o.k.
I also did a fresh install with the newest release of mavericks as well as sfott but the problem still remains.
I also disabled the option that the power save mode from the hard disks is activated.
Best regards,
David
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.
----------
Messages has been working fine on my system. It failed after the first install. Could not log in. I called Apple support, told them about the error msg. I related the support to Mavericks and NOT the hardware, which would be way out of warranty. I did not go into details on the custom configuration.
They were able to reset Messages on the server, but it took an escalation.
I just wanted to pop back in here and thank tiamo and the community who helped make running Mavericks on mac pro 1,1/2,1 a reality. A few years ago I was going to dump my mac pro 1,1 because it couldn't support ML. It was running ok on SL but it really needed a refresh. I didn't want to put any more money until a machine that couldn't support the latest OS but I really didn't want to purchase a new Mac either ($$$). I came here and found the thread about Mavericks and figured I'd give it a shot since I had already replaced the stock video card in the 1,1 with a Radeon 6870 a few years ago. Now a month later and I have Mavericks running smoothly on a new SSD I installed and also installed 16GB of RAM and swapped in two quad core Xeon CPUs to go with it. The actual installation of Mavericks was made simple by using the SFOTT tool so many thanks to the person who created that. Overall I couldn't be any happier with the machine. It's more than responsive enough in the OS and apps. Sure it's old by today's technology standards and won't compete with any modern machines from a benchmark standpoint, but who cares if the system does what you need it to do? So thanks again everybody and keep up the great work!