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

Success! Question re: installing from "technically" supported Mac

Hi there,

Huge thanks first off to Tiamo, and also to all the knowledgeable folks helping out with the less savvy of us.

Just updated my Mac Pro 1,1 (12 GB Ram //ATI 2600 XT 256 MB) to 10.9 and ran the App Store update to 10.9.1

Seems like everything except sleep is working, and likely that's a GPU issue.

I used the "shortcut" method of using my other Mac Pro (a 3,1) to install a fresh copy of 10.9 (using an UNMODIFIED efi USB key) onto a spare Hard Drive and then replaced the two efi files while the drive was still in my 2008 3,1 Mac Pro.

After replacing the two efi files I simply moved the Hard Drive from my 2008 3,1 into my 2006 1,1. Booted into 10.9 successfully!

I've reread this thread 3 times in hopes of answering my two questions below, but could not determine a definitive answer.

1) For people with another Mac that is "officially supported" to run 10.9, would it be easier to simply install 10.9 onto a bare hard drive (assuming access to a "Toaster" like this:http://eshop.macsales.com/shop/NewerTech/Voyager/Hard_Drive_Dock),then change the two efi files and place the hard drive back into their 1,1 or 2,1?

2) Lastly, and please forgive the newbosity of this question:
When I boot my 1,1 I get a gray screen but no Apple logo, then a black screen with lots of what looks to my like code, and then boot into the desktop. I am using an official Apple Branded 2600 XT so it should have proper EFI.

Is the black screen with code I see prior to the dekstop booting merely Tiamo's EFI in action? Just curious about this, any insight is much appreciated.
 
stmp said:
Hi there,

Huge thanks first off to Tiamo, and also to all the knowledgeable folks helping out with the less savvy of us.

Just updated my Mac Pro 1,1 (12 GB Ram //ATI 2600 XT 256 MB) to 10.9 and ran the App Store update to 10.9.1

Seems like everything except sleep is working, and likely that's a GPU issue.

I used the "shortcut" method of using my other Mac Pro (a 3,1) to install a fresh copy of 10.9 (using an UNMODIFIED efi USB key) onto a spare Hard Drive and then replaced the two efi files while the drive was still in my 2008 3,1 Mac Pro.

After replacing the two efi files I simply moved the Hard Drive from my 2008 3,1 into my 2006 1,1. Booted into 10.9 successfully!

I've reread this thread 3 times in hopes of answering my two questions below, but could not determine a definitive answer.

1) For people with another Mac that is "officially supported" to run 10.9, would it be easier to simply install 10.9 onto a bare hard drive (assuming access to a "Toaster" like this:http://eshop.macsales.com/shop/NewerTech/Voyager/Hard_Drive_Dock),then change the two efi files and place the hard drive back into their 1,1 or 2,1?

2) Lastly, and please forgive the newbosity of this question:
When I boot my 1,1 I get a gray screen but no Apple logo, then a black screen with lots of what looks to my like code, and then boot into the desktop. I am using an official Apple Branded 2600 XT so it should have proper EFI.

Is the black screen with code I see prior to the dekstop booting merely Tiamo's EFI in action? Just curious about this, any insight is much appreciated.
Click to expand...

Two quick answers:
1) the method you described should be ok, but remember to insert also the board id
2) the code you see when you boot it's the verbose screen (you can boot in verbose mode on every mac holding command+V), it displays all the tasks of the system.
 
Sko said:
I remember there was a firmware update for AirPort in Mac Pro to support 802.11n. Did you apply it back then? Check supported PHY-modes in System Profiler.
Click to expand...

I now solved the issue partially. I copied the old IO80211Family.kext from my old 10.6.8 installation (located under /System/Library/Extensions) and inserted it with Kext Wizard (KW) under 10.9.1. After repairing the permissions with KW and a reboot my network card was available again (The BT is still missing but I can live with that).

Now I am facing another issue with my WiFi. As it seems there exists a known issue with WPA2 and 10.9. I can see my network but I am not able to connect to it. Doesn't matter if I use a fixed IP setup or DHCP. If I disable my encryption!!!! it works. However, this is not an acceptable solution. Any clues how to proceed?

Thx!
cheers,
eyseman
 
What's the deal with not changing the board ID? I recently installed Mavericks using TDM and swapped the boot.efi's.

I haven't changed anything else, machine seems to be running fine.
 
haralds said:
The error msg is:
Your Apple ID " >>> " can't be used to set up iMessage at this time.

...

Customer code: ...-...-...
Click to expand...

iMessage didn't/doesn't work for me either for some reason. It did under Chameleon, must admit I've gone back to 10.8 because of the iPhone sync issue). Stragely enough both BacktoMyMac and Find my Mac do.
I've got a bootbable 10.9 on another disk that I may start up from time to time when the point releases are out to see how the changes affect things.
 
Last edited:
resale said:
I followed the instructions by tiamo to the letter, I reboot to my usb and get this:
Image
Any advice on how to actually start/finish would be greatly appreciated.
I'm doing this on a Mac Pro 1,1 flashed to 2,1, 16gb ram and Apple 5770.
Click to expand...

hey there!

i am getting the same problem as him and i have no idea what to do! i followed everything very closely! help please!
 
Thank you so much tiamo! This fix is amazing!!! I can't believe how easy it was to implement and how well Mavericks is working on my Mac Pro 1,1.

I have a question that I'm hoping someone might be able to help me with. I've been running Mavericks via this fix (as well as a Chameleon fix before this) and wanted to download and play Bioshock Infinite. After downloading the game via the App Store (using both boot methods), I've tried to open the app but it crashes before opening every time. I've triple checked my specs with the game requirements and can't find any reason it wouldn't be able to run on my system. I've had no problems running all of my other programs (the full Adobe suite, iLife apps, etc.) but for some reason Bioshock Infinite won't run.

Has anyone else had success running Bioshock Infinite on their Mac Pro 1,1? Or is there anyone that may know why it wouldn't run when booting into Mavericks using tiamo's boot files on a Mac Pro 1,1?

----------
Adam.Lewin said:
hey there!

i am getting the same problem as him and i have no idea what to do! i followed everything very closely! help please!
Click to expand...

I had the same issue and read through the thread and found the bit about needing to format the USB drive under the Partition tab as GUID. Basically you just need to erase the USB drive and then create a single partition GUID partition on the drive then you can put all of the Mavericks install files on that new partition and reboot to it. Hope that helps!
 
miasis said:
----------

[/COLOR]

I had the same issue and read through the thread and found the bit about needing to format the USB drive under the Partition tab as GUID. Basically you just need to erase the USB drive and then create a single partition GUID partition on the drive then you can put all of the Mavericks install files on that new partition and reboot to it. Hope that helps!
Click to expand...

Yeah ive done that and i even did it again and followed someones detailed step by step instructions on how to do it haha! ive been trying for 3 days straight now and i dont know what to do. is there any other fix. ill try and do the whole process again and by then i hope it works or someone has suggested something else for me haha! this is Painful haha!

----------
hwojtek said:
Remove all hard disks except the boot drive from the Mac, install OS.
If you have no additional disks, try zapping PRAM.
Click to expand...

how do you zap the PRAM and what is that. sorry im a noob haha

i have also removed all my harddrives and left the boot drive and the usb in and i still get the message saying Still waiting for root device
 
Last edited:
I'm having trouble with this. For some reason i cant change the Installable machine.plist because it's read-only and i've tried chmod 755
 
Adam.Lewin said:
how do you zap the PRAM and what is that. sorry im a noob haha
i have also removed all my harddrives and left the boot drive and the usb in and i still get the message saying Still waiting for root device
Click to expand...
Tough luck :/ To zap PRAM you need to start your computer, press and hold down Command+Option+P+R keys before you hear the familiar startup chime. Keep them pressed until you hear the second chime (which will occur after your monitor flickers, because the computer actually restarts).
If this doesn't work I am running out of options - the disk removal trick did it for me (I had a failing non-boot hard drive which died a couple of days later), zapping PRAM might or might not be OK for you...
One more thing - if you have a spare internal drive, you may want to try to extract the installer to an internal drive instead of the USB and start the installation up from internal.
 
For those having Trouble installing Mavericks on a unsupported Mac.

HERE IS A COMPLETE GUIDE TO INSTALL MAVERICKS ON MACPRO’S 1,1 AND 2,1 USING TIAMO'S BOOT.EFI

First off its super simple.

** I strongly recommend upgrading CPU’s and graphics card.
- Cpu upgrade: Intel Xeon 5365
- Apple ATI Radeon HD 5770 Graphics Card
- Rack up the RAM!


For Mavericks cpu upgrade may not be necessary, but the graphics card is a MUST.

First Create Installer.

These instructions are pretty straight forward with photos, so I won’t waste time on this..

http://www.tips-and-tricks-in-mavericks.com/how-to-create-an-os-x-mavericks-install-drive/

Replacing boot.efi and inputing the board ID.

Some of you are having issues here and I will tell you how to simply do this procedure.

<< Modify the OSinstall.MKPG >>>

1 - Download and KEEP the “Flat Package Editor” Here --> View attachment Flat Package Editor.app.zip
2 - Download and unzip the boot.efi provided by the angel Tiamo. Here --> View attachment boot.efi.zip
3 - In the installer, navigate to System —> installation —> Packages Folder and located OSInstall.MPKG (Make sure it is the mpkg extension and NOT the pkg extension.)

4. Open OSinstall.mpkg with flat package editor. (should be in right click menu)

5. Drag Distribution file to desktop and open with text edit. (Keep Flat package editor open)

6. Slowly scroll and look for a area that has a list of “Platform Support Values” with board ID’s

7. Get your board ID.
Open Terminal and type ioreg -p IODeviceTree -r -n / -d 1
your board ID should look like this: Mac-F222BEC8 with a different number of corse. Copy that value.

8. Now, enter your board ID in the distribution file in the “Platformsupportvalues.” Be aware of how the IDs are inputed with a quote and comma. Click save.

Board ID.jpg


9. Now go back into flat package editor and delete the distribution file there, then drag the one you modified and saved on your desktop into the flat package editor. Make sure it looks like the previous with the distribution file and the resources fo.. then click save.


<< Modify the “InstallableMachines.plist” file.>>

1. With Xcode (the easiest method) or with text edit, open the Installable Machines.plist file in the same folder as the OSinstall.mkpg (System —> installation —> Packages Folder of the installer)

2. Add your board ID to the “ SupportedBoardIds” Section. If in text edit, make sure to follow the same format with the “<string>”

3. you want to do the same exact thing to the file called “PlatformSupport.plist located in System —> Library —-> Core Services folder.

Core Services.jpg

In this file you want to add your board ID and also your Model ID (for example “MacPro 2,1”) Following the same format as the file, when done, save and also save a duplicate on the desktop.

4. In the same Core services folder, click on the com.apple.recovery.boot folder and replace the Platformsupport.plst with the new one you just saved..



<< Replacing the boot.efi file >>

1. Still in Core Services folder (System —> Library —-> Core Services) you need to unlock the boot.efi tile.

2. In terminal type “sudo chflags nouchg” with no quotes and add ONE SPACE. Then drag the locked boot.efi file into terminal and press enter. enter password if needed.

3. Now copy Tiamo’s boot.efi file to the core services folder and click replace.

4. Now navigate to the root folder (main folder of your installer) and show hidden files.


5 in terminal type “defaults write com.apple.finder AppleShowAllFiles TRUE” without the quotes.

6. In the root of the installer navigate to the hidden folder “usr—> standalone -
—> i386” and replace the boot.efi file with Tiamo’s boot.efi file. (this one doesn’t need to be unlocked)

7. Hide hidden files: In terminal type “defaults write com.apple.finder AppleShowAllFiles FALSE” without quotes and you’re done.

8. Install Mavericks as normal and enjoy.

<< FINISHED! >>

I recommend downloading TechTool for Mavericks and creating an edrive or creating another small working partition that goes untouched in cause the boot.efi file gets replaced by updates. I haven’t had that happen since i updated but its nice to have just in case.

If the updates modify the boot.efi file, boot to the TechTool edrive or other working partition and replace the 2 boot.efi files again in the Mavericks OS. (system —> Library —> Core services)
and unhide hidden files and replace in “usr—> standalone—> i386”


This method is confirmed and working for the mountain lion installer as well..
The only difference is the show and hide files terminal command is different in mountain lion and below. (the F in finder is uppercase)

defaults write com.apple.Finder AppleShowAllFiles TRUE

defaults write com.apple.Finder AppleShowAllFiles FALSE

Thanks to Tiamo for creating this boot.efi file. We have 64bit machines, and we should be able to use the full capacity of what our machines can offer.

My MacPro 1,1 now converted to 2,1 is still running just as fast as computers today and there is no need after all the money we spent upgrading these machines to trash them "just because" of a firmware update. I buy and purchase everything apple, and have for years, but I'm not spending another 3,000 and 2,000 plus for upgrades, "just because", if my machine is doing what modern machines can do today.

Results.jpg
 
Last edited:
Jakimo said:
Tonight I grabbed an HD5770 locally for $40, made for Windows. Zero flash needed! Works beautifully, very glad for you guys. The simple boot.efi copies / board-id edits have worked out very well.

There goes my excuse to buy Darth Vader's helmet! Yeesh.. :)
Click to expand...

This is interesting in that you were able to use a PC HD5770 without flashing it for the Mac? What does it report in the system report?

Thanks!
 
Rough Edge said:
HERE IS A COMPLETE GUIDE TO INSTALL MAVERICKS ON MACPRO’S 1,1 AND 2,1 (AND ANY OTHER UNSUPPORTED MAC) USING TIAMO'S BOOT.EFI

First off its super simple.

** I strongly recommend upgrading CPU’s and graphics card.
- Cpu upgrade: Intel Xeon 5365
- Apple ATI Radeon HD 5770 Graphics Card

I'm not sure how necessary the CPU upgrade is for Mavericks, but I can say that the graphics card is a MUST.

First Create Installer.

These instructions are pretty straight forward with photos, so I won’t waste time on this..

http://www.tips-and-tricks-in-mavericks.com/how-to-create-an-os-x-mavericks-install-drive/

Replacing boot.efi and inputing the board ID.

Some of you are having issues here and I will tell you how to simply do this procedure.

<< Modify the OSinstall.MKPG >>>

1 - Download and KEEP the “Flat Package Editor” Here --> View attachment 454977
2 - Download and unzip the boot.efi provided by the angel Tiamo. Here --> View attachment 454978
3 - In the installer, navigate to System —> installation —> Packages Folder and located OSInstall.MPKG (Make sure it is the mpkg extension and NOT the pkg extension.)

4. Open OSinstall.mpkg with flat package editor. (should be in right click menu)

5. Drag Distribution file to desktop and open with text edit. (Keep Flat package editor open)

6. Slowly scroll and look for a area that has a list of “Platform Support Values” with board ID’s

7. Get your board ID.
Open Terminal and type ioreg -p IODeviceTree -r -n / -d 1
your board ID should look like this: Mac-F222BEC8 with a different number of corse. Copy that value.

8. Now, enter your board ID in the distribution file in the “Platformsupportvalues.” Be aware of how the IDs are inputed with a quote and comma. Click save. Example --> View attachment 454980


9. Now go back into flat package editor and delete the distribution file there, then drag the one you modified and saved on your desktop into the flat package editor. Make sure it looks like the previous with the distribution file and the resources fo.. then click save.


<< Modify the “InstallableMachines.plist” file.>>

1. With Xcode (the easiest method) or with text edit, open the Installable Machines.plist file in the same folder as the OSinstall.mkpg (System —> installation —> Packages Folder of the installer)

2. Add your board ID to the “ SupportedBoardIds” Section. If in text edit, make sure to follow the same format with the “<string>”

3. you want to do the same exact thing to the file called “PlatformSupport.plist located in System —> Library —-> Core Services folder.
Example --> View attachment 454979
In this file you want to add your board ID and also your Model ID (for example “MacPro 2,1”) Following the same format as the file, when done, save and also save a duplicate on the desktop.

4. In the same Core services folder, click on the com.apple.recovery.boot folder and replace the Platformsupport.plst with the new one you just saved..



<< Replacing the boot.efi file >>

1. Still in Core Services folder (System —> Library —-> Core Services) you need to unlock the boot.efi tile.

2. In terminal type “sudo chflags nouchg” with no quotes and add ONE SPACE. Then drag the locked boot.efi file into terminal and press enter. enter password if needed.

3. Now copy Tiamo’s boot.efi file to the core services folder and click replace.

4. Now navigate to the root folder (main folder of your installer) and show hidden files.


5 in terminal type “defaults write com.apple.finder AppleShowAllFiles TRUE” without the quotes.

6. In the root of the installer navigate to the hidden folder “usr—> standalone -
—> i386” and replace the boot.efi file with Tiamo’s boot.efi file. (this one doesn’t need to be unlocked)

7. Hide hidden files: In terminal type “defaults write com.apple.finder AppleShowAllFiles FALSE” without quotes and you’re done.

8. Install Mavericks as normal and enjoy.

I recommend downloading TechTool for Mavericks and creating an edrive or creating another small working partition that goes untouched in cause the boot.efi file gets replaced by updates. I haven’t had that happen since i updated but its nice to have just in case.

If the updates modify the boot.efi file, boot to the TechTool edrive or other working partition and replace the 2 boot.efi files again in the Mavericks OS. (system —> Library —> Core services)
and unhide hidden files and replace in “usr—> standalone—> i386”


This method is confirmed and working for the mountain lion installer as well..
The only difference is the show and hide files terminal command is different in mountain lion and below. (the F in finder is uppercase)

defaults write com.apple.Finder AppleShowAllFiles TRUE

defaults write com.apple.Finder AppleShowAllFiles FALSE

Thanks to Tiamo for creating this boot.efi file. We have 64bit machines, and we should be able to use the full capacity of what our machines can offer.

My MacPro 1,1 now converted to 2,1 is still running just as fast as computers today and there is no need after all the money we spent upgrading these machines to trash them "just because" of a firmware update. I buy and purchase everything apple, and have for years, but I'm not spending another 3,000 and 2,000 plus for upgrades, "just because", if my machine is doing what modern machines can do today.

Results --> View attachment 454981
Click to expand...

Thank you so much!
 
Chung123 said:
This is interesting in that you were able to use a PC HD5770 without flashing it for the Mac? What does it report in the system report?

Thanks!
Click to expand...

I also used a PC HD5770 (asus eah5770) without flashing, in system profiler there was ati 5000.
Now I'm waiting for the power cable (and i'm using a nvidia 8500gt and a 8400gs), the test was done with my mac pro open, with an external psu from another pc.
When the card will be installed definitively I would try to flash it in order to add the correct identification and maybe the boot screen, anyone tried to flash it?
 
Rough Edge said:
HERE IS A COMPLETE GUIDE TO INSTALL MAVERICKS ON MACPRO’S 1,1 AND 2,1 (AND ANY OTHER UNSUPPORTED MAC) USING TIAMO'S BOOT.EFI
Click to expand...
That's a nice writeup, however the statement "ANY OTHER UNSUPPORTED MAC" is misleading. There are computers (white MacBooks C2D, iMacs 17 and 20" etc) which are perfectly capable of running Mavericks CPU-wise, but their graphics cards do not allow Mavericks to start at all.

Rough Edge said:
** I strongly recommend upgrading CPU’s and graphics card.
- Cpu upgrade: Intel Xeon 5365
- Apple ATI Radeon HD 5770 Graphics Card
Click to expand...

CPU - not needed. Even the simplest 2x dual core Xeon Mac Pro flies in Mavericks. GPU - a 4870, while considered a minimum, is still a decent card unless you go for GPU-heavy rendering tasks. But for the system alone - it's really cheap, fast and easy to flash. What Mavericks needs but you have not mentioned is RAM. The more the better. If 32 GB in a 1,1 or 2,1 are not a stretch too far - get it.

TiberioG said:
I also used a PC HD5770 (asus eah5770) without flashing, in system profiler there was ati 5000.
When the card will be installed definitively I would try to flash it in order to add the correct identification and maybe the boot screen, anyone tried to flash it?
Click to expand...
LOL, everybody thought it's a stock PC card that suddenly started to work correctly with boot screens and identification. :) So no, nothing unusual here, the card just works. Regarding flashing - tons of info in here, check out posts by Netkas, Groths, Rominator, Blacksheep.
 
hwojtek said:
That's a nice writeup, however the statement "ANY OTHER UNSUPPORTED MAC" is misleading. There are computers (white MacBooks C2D, iMacs 17 and 20" etc) which are perfectly capable of running Mavericks CPU-wise, but their graphics cards do not allow Mavericks to start at all.



CPU - not needed. Even the simplest 2x dual core Xeon Mac Pro flies in Mavericks. GPU - a 4870, while considered a minimum, is still a decent card unless you go for GPU-heavy rendering tasks. But for the system alone - it's really cheap, fast and easy to flash. What Mavericks needs but you have not mentioned is RAM. The more the better. If 32 GB in a 1,1 or 2,1 are not a stretch too far - get it.


LOL, everybody thought it's a stock PC card that suddenly started to work correctly with boot screens and identification. :) So no, nothing unusual here, the card just works. Regarding flashing - tons of info in here, check out posts by Netkas, Groths, Rominator, Blacksheep.
Click to expand...


I'm sure you'll appreciate my edit.. LOL
 
I've been using this hack from day one, works flawlessly. Small question, I kinda do not like Mavericks comparing to 10.8.5, it just feels a bit sluggish.

Is it possible to use this boot.efi on 10.8.5 ??? Has anyone tried it?
 
. I buy and purchase everything apple, and have for years, but I'm not spending another 3,000 and 2,000 plus for upgrades, "just because", if my machine is doing what modern machines can do today.
Click to expand...

I agree i was going to spend $3000-$4000 on a new mac pro, but this hack has saved me a lot of money. I won't need a new computer for at least 3-4 Years. By that time the New Mac Pro will be faster and better and apple will finally release the 4K Display.
 
mnlth0 said:
I've been using this hack from day one, works flawlessly. Small question, I kinda do not like Mavericks comparing to 10.8.5, it just feels a bit sluggish.

Is it possible to use this boot.efi on 10.8.5 ??? Has anyone tried it?
Click to expand...

Yep. Possible.

However I wonder what you mean by sluggish - If it's a GPU issue (in case your not on a Mac Pro/XServe) you will experience the same sluggish-ness.
There is only a fix available for the ATI X1600 GPU. Else you'll have to use MLPF to get proper graphics.
 
mnlth0 said:
I've been using this hack from day one, works flawlessly. Small question, I kinda do not like Mavericks comparing to 10.8.5, it just feels a bit sluggish.

Is it possible to use this boot.efi on 10.8.5 ??? Has anyone tried it?
Click to expand...


Yes it is, I tried it...works fine.

Theres a few reasons why you can be experiencing the sluggishness (that is if you have a mac pro and the required graphics card)

I noticed that Mavericks Indexes quite a a lot in the first few days which causes a bit of sluggishness... Give it a few days and it should behave like normal...Also take into consideration if you have Time machine set up an if its rewriting large backups and also keep in mind mac os x defragmenting in the background... Mac OS X auto defragments since 10.4.. After a few days things should be crisp and smooth again..

Some issues that I notice, but from what I hear others with newer Macs have the same issues with Mavericks, is a longer boot time then usual. I also notice that when downloading large files things become sluggish too which i never experienced before and I'm on a clean install on a newish drive..

Upgrading to an SSD would solve a lot too but, I do think a lot of it has to do with Mavericks not being perfect yet... We are still only on 10.9.1. and well see what bugs get ironed out with the next update.

Check the app store and read the recent reviews for Mavericks. A lot of people with 2012 and 2013 new machines are experiencing issues as well with poor performance.. My buddy just bought the new retina macbook pro and we did a side by side test opening apps... Mine (Hacked Mac Pro 2,1) opened up Logic Pro faster, opened up iPhoto the same time, and his won on opening up iTunes.. Also His boot time was only 12 secs thanks to the SSD.Mine was 30 secs. But he still has weird graphic issues with apps, which i notice on a lot of machines, so i think its more an OS thing.. the 10.9.2 update is focusing on graphic drivers..

To everyone using this hack on a Mac Pro, whats your boot time with mavericks?

Mine is 30-35 secs on a 7200 data.
 
Last edited:
tiamo said:
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
Click to expand...
Hi tiamo,
Any chance you can provide a compiled one for efi64 also (Not for MacPro2,1)?
Thanks!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back