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 post date
verbose mode is enabled for debug purpose
use this one if you prefer graph mode.
PS: system update may overwrite boot.efi, you should replace it after system update.
PS2: the bootloader is dedicated to 10.9, it DOSE NOT support 10.7's kernel, because 10.8+ kernel use a new version boot_arg. AND it will bypass drvier cache(mkext) in 10.8, because 10.9 does not use driver cache, please make sure kernel cache is always enabled if you want use it in 10.8. AND in 10.8 the bootloader will ALWAYS load 64bits kernel(the only one 10.9 has) even if you set arch=i386 in boot_args or press 32 on startup.
use this one if you prefer graph mode.
PS: system update may overwrite boot.efi, you should replace it after system update.
PS2: the bootloader is dedicated to 10.9, it DOSE NOT support 10.7's kernel, because 10.8+ kernel use a new version boot_arg. AND it will bypass drvier cache(mkext) in 10.8, because 10.9 does not use driver cache, please make sure kernel cache is always enabled if you want use it in 10.8. AND in 10.8 the bootloader will ALWAYS load 64bits kernel(the only one 10.9 has) even if you set arch=i386 in boot_args or press 32 on startup.
Last edited:
there is a homebrew bootloader for OS X 10.9
1. following those steps to make an install drive
http://www.tips-and-tricks-in-mavericks.com/how-to-create-an-os-x-mavericks-install-drive/
2. replace boot.efi
boot.efi can be found at System/Library/CoreServices/boot.efi and usr/standalone/i386/boot.efi
3.insert your board-id into OSInstall.mpkg(please google it)
4.insert your board-id into InstallableMachine.plist(please google it)
5.reboot from the usb drive.
===================
this is a native efi32 bootloader, instead of a CSM loader
it built a thunk between EFI64 and EFI32, forwarding EFI64 call from kernel to EFI32 firmware.
so those programs using EFI runtime services, such as bless, nvram will be run without any problem.
this is a full version bootloader, hibernation, filevault2 are also supported out of box.
===================
source code: http://code.google.com/p/macosxbootloader/
it is built with visual studio 2013 and nasm
1. following those steps to make an install drive
http://www.tips-and-tricks-in-mavericks.com/how-to-create-an-os-x-mavericks-install-drive/
2. replace boot.efi
boot.efi can be found at System/Library/CoreServices/boot.efi and usr/standalone/i386/boot.efi
3.insert your board-id into OSInstall.mpkg(please google it)
4.insert your board-id into InstallableMachine.plist(please google it)
5.reboot from the usb drive.
===================
this is a native efi32 bootloader, instead of a CSM loader
it built a thunk between EFI64 and EFI32, forwarding EFI64 call from kernel to EFI32 firmware.
so those programs using EFI runtime services, such as bless, nvram will be run without any problem.
this is a full version bootloader, hibernation, filevault2 are also supported out of box.
===================
source code: http://code.google.com/p/macosxbootloader/
it is built with visual studio 2013 and nasm
Attachments
Last edited:
I don't dispute a single word of that, but I'm not really arguing against your opinions. I'm just putting a different perspective from a different user (hence "what this says to me").
When I bought by Mac Pro in 2006, I was lucky enough to have been pretty much given a blank cheque by the company I worked for to go out and buy a machine to allow me to work from home. They also made it clear that it would be my machine and I'd be able to keep it if I ever left the firm. So, I pretty much went out and bought what was the best machine on the market at the time, reckoning that with upgradability and performance well ahead of the pack it would give me plenty of years of use before it became obsolete. Now, 7 years later, at the back end of 2013, I have a Mac which can still keep pace with what's required for the work I do.
That to me is exactly what I bought it for. I'm delighted that my old beast still manages to pull its weight, and come pretty close to what most PC users would get if they bought a fairly standard desktop machine today. And apart from having to do a little hackery to get the most recent OS onto it, it's been pretty plain sailing all the way.
When I bought by Mac Pro in 2006, I was lucky enough to have been pretty much given a blank cheque by the company I worked for to go out and buy a machine to allow me to work from home. They also made it clear that it would be my machine and I'd be able to keep it if I ever left the firm. So, I pretty much went out and bought what was the best machine on the market at the time, reckoning that with upgradability and performance well ahead of the pack it would give me plenty of years of use before it became obsolete. Now, 7 years later, at the back end of 2013, I have a Mac which can still keep pace with what's required for the work I do.
That to me is exactly what I bought it for. I'm delighted that my old beast still manages to pull its weight, and come pretty close to what most PC users would get if they bought a fairly standard desktop machine today. And apart from having to do a little hackery to get the most recent OS onto it, it's been pretty plain sailing all the way.
Hacking a Mac to run OS X, now that's funny, hey Mac 1 & 2 owners, welcome to hackintosh, of sorts.
Hi,
Will the MacBookPro 2,2 get full graphic acceleration with this method under 10.9?
Any kext to be copied required?
Thanks in advance!!
Will the MacBookPro 2,2 get full graphic acceleration with this method under 10.9?
Any kext to be copied required?
Thanks in advance!!
This is awesome!
Apple released EFI32 Mac Pro after going all 64-bit with PowerPC G5.
Until now, we had a few choices to work around this unacceptable engineering error, all with side effects.
Then, tiamo made it with an innovative approach, just like Apple should have done.
Many thanks for sharing this awesome work with the community, you rocks.
Apple released EFI32 Mac Pro after going all 64-bit with PowerPC G5.
Until now, we had a few choices to work around this unacceptable engineering error, all with side effects.
Then, tiamo made it with an innovative approach, just like Apple should have done.
Many thanks for sharing this awesome work with the community, you rocks.
Last edited:
build an EFI binary on windows is straightforward, because EFI uses the same format, the same calling conversion that M$'s native binary used.
and you CAN DEBUG this bootloader over COM/1394 with WinDbg! yes SOURCE level debugging(this is another story
)it is possible to build an EFI binary on *nix by using gnu-efi http://sourceforge.net/projects/gnu-efi/
if you want to build the bootloader with gnu-efi, you should remove all the SEH codes, and implement those instrict functions.
a lot of work...If the air is "worthy" of new OS then time to stop reinventing the wheel. Either use a 2.5" drive connected by SATA to USB to the Air or get whatever you need to put 1,1 into target disc mode and run it's HD from the Air.
Install the OS on the air to your drive.
Run the pikeryosefix app from blacksheep666 that contains your needed boot.efi and reboot until the air won't boot from the new install. When this happens it means that it is ready for 1,1.
Reboot from 1,1 and be amazed at all the time you wasted when you could have just snapped your Ruby Slippers together and been done with it.
hwojtek,
I want to thank you for sending the link for the boot.efi file. My machine (2006 Mac Pro 1,1 with Intel Xeon 5365 4 core processors; ATI Radeon 4770 w/1GB ram; 32 GB ram, is now running OS X Mountain Lion in 64 bit mode. Thanks also to Pike and Tiamo for doing what I could never do.
gr
I want to thank you for sending the link for the boot.efi file. My machine (2006 Mac Pro 1,1 with Intel Xeon 5365 4 core processors; ATI Radeon 4770 w/1GB ram; 32 GB ram, is now running OS X Mountain Lion in 64 bit mode. Thanks also to Pike and Tiamo for doing what I could never do.
gr
I had this issue as well. The thing that worked for me was, open Terminal and type: sudo bless (drag the drive from the finder to the Terminal window to insert the path of the drive here)
Then press enter and try setting your startup disk to the Mavericks drive
Hold down Option/Alt upon reboot. Select the Mavericks startup disk. Once you boot into Mavericks, go to System Preferences > Startup Disk and select your mavericks disk to start
Alternatively you can also install rEFInd (i suggest doing it from the Lion install, as it has the proper 32-bit kernel for the efi file)
I prefer the non verbose version. It's in the same thread a couple of posts down.
Sure, it doesn't run without the proper boot.efi but this is a minor issue.
Our old Mac Pro's aren't actually that fast anymore.
My parents got a new Mac Mini recently (maxed everything out, except the SSD), and it scored similar geek bench results to my 2008 Octo core with an 8800GT.
My parents got a new Mac Mini recently (maxed everything out, except the SSD), and it scored similar geek bench results to my 2008 Octo core with an 8800GT.
32-bit boot ROM is source of trouble
I have a Mac Pro 2,1 and I am stuck on Snow Leopard. The reason is that for a while Apple shipped the operating systems with both a 32-bit and a 64-bit version of the kernel. The Mac Pro 2,1 will never be able to run the 64-bit kernel because the EFFI32 boot rom just won't do it.
What I want to know though is where I can buy a USB3 adapter that will work in the Mac Pro 2,1.
I have a Mac Pro 2,1 and I am stuck on Snow Leopard. The reason is that for a while Apple shipped the operating systems with both a 32-bit and a 64-bit version of the kernel. The Mac Pro 2,1 will never be able to run the 64-bit kernel because the EFFI32 boot rom just won't do it.
What I want to know though is where I can buy a USB3 adapter that will work in the Mac Pro 2,1.
You would have to contact the third party manufactures and ask them about a USB3 and driver support for it.
What that says to me, is not that they're slow, but they they're still perfectly capable of running modern Operating Systems and applications at a very usable pace.
My 2006 Mac Pro 1,1 with upgraded processors gets over 10,000 on geekbench, which only a fraction under a 2012 15" Quad Ivy Bridge Macbook Pro Retina 2.3 Ghz. When your 7 year old machine is still able to run at that pace, it's comfortably good enough for prime time work.
Sure they're not miles ahead of the pack any more, but they're still in the same league as the modern machines most people use every day.
You can go to Lion with a 2,1 - which gives you access to many of the current apps - however being "stuck" with Snow Leopard is OK if it is running the programs (apps) that you need to run. If I did not have a ipad mini, phone, iMac and pro that I want to keep in sync and use the messages feature I might still be using Snow as my primary OS.
But were folks who need mainstream computational power the targeted users for the Mac Pro? Slow for whom is the more operative question.
Support for old system has little to do with "fast enough". It has to with:
i. dwindling number of those systems in active deployed use. system die over time and not all of them get repaired or passed down.
ii. parts availability dies off over time. Again leads to a general decrease in actually running deployed systems.
For example, the 3500/3600/5500 Xeons in 2009-2012 Mac Pros are being dropped from retail market this year. ( http://www.cpu-world.com/news_2012/2012031102_Intel_discontinues_Xeon_5500_series_processors.html http://www.cpu-world.com/news_2013/...ues_Xeon_3500_and_3600_server_processors.html ). Apple won't be able to buy them this time next year. Where parts are going to come from to keep these systems running is from old system boneyards. The Mac Pro 2008 ( and earlier) are already in this state.
Desupported hardware doesn't tend to get new software. That isn't an Apple thing. It is a general industry thing. "Fast enough" completely ignores support costs and development allocation issues. If Apple slapped megabuck charges for "extended support" perhaps, but they don't engage in that sort of business at all.