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

FlyLight said:
Do I just replace the relevant parts of the path with my own structure? in my case volumes/SSD/System... etc ?
Click to expand...

You might do that, but there's an easier, "implicit" blessing if you simply do this: System Preferences/Startup Disk and you select your Mavericks partition.
 
How to donate for this great job!?

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

How can I donate for this great work? My Mac Pro 2,1 (a 1,1 with Xeon 5355 upgrade and firmware update to 2,1) got useful again thanks to your work!
 
Mac Pro 1.1 upgrade issue

Been reading all these post and really do appreciate tiamo's contribution. This thread is the only one that has come close to working for me after a couple days of trying to upgrade my Mac Pro 1.1 from Lion to Mavericks. Tried some other methods and could not get past the "white screen"
This process actually boots and gets past the initial validation - which is the farthest I have gotten.
I have followed the instructions and replaced both "boot.efi" files on the boot USB. I have made the changes to the OSInstall.mpkg as indicated along with the Plist. Actually tried two things for the OSInstall.mpkg file - changing the board value to "true" as per the video but ended up using the actual board value.
So what happens,
1.- Maverick install starts and I can click on the "continue" button (could not get past this in other attempts)
2.- Get a "continue" bottom on next screen so computer eligibility can be verified with Apple.
4.- runs for a while with a "loading install information"
5.- Now I get "Could not find installation information for this machine - contact AppleCare"

From the sounds of the error msg, it would seem I missed something with the Board ID value - but that is a guess. I am at a loss of what to do or look at this stage.

System:
Mac Pro 1.1 (2006)
Processor (4x2.66 Ghz (upgraded this earlier last week)
13 Gig RAM (OK…. i never spent the $$ to match the other RAM chips)
Video ATI Radeom HD 5770 1024 MB (Apple card)

Appreciate any help. Really want this to get running so I can upgrade some apps I work with. Stuck on Mac OS 10.7.5 and apps are starting to not update as well.

Thanks,
Tom L
 
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.
Click to expand...

After follow all steps I can't reboot from USB stick. I can't select it as a startup disc. I get a message saying that bless tool cant establish the disc as a sturtup disc. There is a screen capture of that message from disc utility: http://cl.ly/image/2x0r1R201g0R

What am I doing wrong?

Thanks in advance.
 
aitor said:
So, if I repeat the process over an internal hard drive instead a USB stick, it must work. Is it correct?
Click to expand...

Ok, I tried an installation from an internal HD. The installer seems to work fine. Having two minutes left to finish I got an installation error (undefined). Here is the picture from screen: http://cl.ly/image/2u470X2b0M38

What can I do in this case?

Thank you very much.
 
It's a pity that message in Spanish is somewhat unspecific, so it's difficult to tell. When I first tried installing Mountain Lion via Chameleon, I remember one of the tweaked files, OSIntall.mpkg if I remember correctly, was badly edited by me. My second attempt was successful. Naturally, I have no way of knowing if this is your case. Buena suerte.
 
PeterHolbrook said:
It's a pity that message in Spanish is somewhat unspecific, so it's difficult to tell. When I first tried installing Mountain Lion via Chameleon, I remember one of the tweaked files, OSIntall.mpkg if I remember correctly, was badly edited by me. My second attempt was successful. Naturally, I have no way of knowing if this is your case. Buena suerte.
Click to expand...

Thank you for your answer, including some spanish words ;)

The mpkg installer was modidified by editing a file called "Distribution" inside mpkg. There, I've added my board ID. It can be seen at the following code (Mac-F4208DA9 is my board ID):

function isSupportedPlatform(){

if( isVirtualMachine() ){
return true;
}

var platformSupportValues=["Mac-F4208DA9","Mac-031B6874CF7F642A","Mac-F2268DC8","Mac-50619A408DB004DA","Mac-F2218EA9","Mac-F42D86A9","Mac-F22C8AC8","Mac-F22586C8","Mac-AFD8A9D944EA4843","Mac-F227BEC8","Mac-F226BEC8","Mac-7DF2A3B5E5D671ED","Mac-35C1E88140C3E6CF","Mac-942459F5819B171B","Mac-77EB7D7DAF985301","Mac-942B59F58194171B","Mac-2E6FAB96566FE58C","Mac-7BA5B2794B2CDB12","Mac-031AEE4D24BFF0B1","Mac-00BE6ED71E35EB86","Mac-4B7AC7E43945597E","Mac-F22C89C8","Mac-F221DCC8","Mac-F42388C8","Mac-F223BEC8","Mac-F4238CC8","Mac-F222BEC8","Mac-4BC72D62AD45599E","Mac-F2208EC8","Mac-66F35F19FE2A0D05","Mac-F4238BC8","Mac-F221BEC8","Mac-C08A6BB70A942AC2","Mac-8ED6AF5B48C039E1","Mac-F2238AC8","Mac-FC02E91DDD3FA6A4","Mac-6F01561E16C75D06","Mac-F22589C8","Mac-F22587A1","Mac-F22788AA","Mac-F42C86C8","Mac-942C5DF58193131B","Mac-F2238BAE","Mac-F22C86C8","Mac-F2268CC8","Mac-F2218FC8","Mac-742912EFDBEE19B3","Mac-27ADBB7B4CEE8E61","Mac-F65AE981FFA204ED","Mac-F42D89C8","Mac-F22587C8","Mac-F42D89A9","Mac-F2268AC8","Mac-F42C89C8","Mac-942452F5819B1C1B","Mac-F2218FA9","Mac-F42D88C8","Mac-94245B3640C91C81","Mac-F42D86C8","Mac-F2268EC8","Mac-F2268DAE","Mac-7DF21CB3ED6977E5","Mac-F42C88C8","Mac-94245A3940C91C80","Mac-F42386C8","Mac-C3EC7CD22292981F","Mac-942B5BF58194151B","Mac-F2218EC8"];
var boardID = system.ioregistry.fromPath('IOService:/')['board-id'];
Click to expand...
Is it correct?
 
aitor said:
Thank you for your answer, including some spanish words ;)

The mpkg installer was modidified by editing a file called "Distribution" inside mpkg. There, I've added my board ID. It can be seen at the following code (Mac-F4208DA9 is my board ID):


Is it correct?
Click to expand...

Check the following information:

1. Your Mac's board identifier must be added to the PlatformSupportValues, but beware, since platformSupportValues might not be the same as PlatformSupportValues. I don't know right now whether it needs to begin with upper case or it doesn't. If I recall correctly, Mac-F4208DC8 was the usual identifier for the Mac Pro 1,1 board.
2. In addition, if you are using Chameleon, your smbios.plist should include this:
<key>SMboardproduct</key>
<string>Mac-F4208DC8</string>

There were other factors to take into account. Although this procedure is for Mountain Lion, it can be adapted almost verbatim for Mavericks: http://www.jabbawok.net/?p=47
 
Hey guys... I just updated from 10.9.1 to 10.9.2. Computer booted to an old osx install on a different drive, as the boot.efi files were overwritten.

I then replaced the boot.efi files in both the usr and coreservices locations, and tried to boot back to the mavericks install... NOTHING.

I'm continuously forced back into my old lion install on a different drive.

What am I missing here? I thought that if I recopied the two boot.efi files back to where they were, the update install would work.

Any help with this would be highly appreciated.

---Trav
 
Ensure that one in CoreServices is replaced. Remember, Apple one is locked and replacing just using authentication (like usr one) does not work. Install tobyg's package after you'll fix this.
 
I just installed tobyg's package and tried again... still no dice. both of the boot.efi files are replaced... each of the locations has a 461 kb file,which is the correct size for tiamo's boot.efi.

I used the app store updater, was that a bad move? Even after the restart, I have the correct boot.efi files. I don't understand what's going wrong... according to the process, everything should be fine.

Any help with this would be appreciated.... I'm so sick of the update notifications.
 
This thing is not working...

Just did the whole thing again... installed tobyg's package and restarted twice. I verified the timestamp on both of the boot.efi files... they were created at the moment of restart.

Then I went and downloaded the osx 10.9.2 combo update and installed. No deal.

Here I sit... typing from the Lion install that my mac defaults to when it can't boot from a drive.

It doesn't make any sense. I'm really struggling here... anyone have a suggestion?
 
Did you install my package in Lion? It's not going to update the ones for your Mavericks drive while under Lion.

Did you go into System Preferences -> Startup Disk and pick your Mavericks drive?

Are you sure you're replacing the boot.efi files on the Mavericks drive?
 
tobyg said:
Did you install my package in Lion? It's not going to update the ones for your Mavericks drive while under Lion.

Did you go into System Preferences -> Startup Disk and pick your Mavericks drive?

Are you sure you're replacing the boot.efi files on the Mavericks drive?
Click to expand...

Yup... all of this was done in mavericks. I was reading through the thread and other people seem to be having problems with "Fusion" drives.

The 4TB drive that I'm trying to update is a Core Storage Volume, which I think is technically a fusion drive. I'm going to give the update a shot on a mavericks install that I have on a crappy 320 gb hard drive.

Basically, I have been planning to migrate away from this 320 gb drive to a 4tb, and THEN update mav. Now that I've gotten the data over... the update won't work.

Let's see what happens when I update the crappy little drive... I bet it works. I'll post in a few.
 
There were other posts in this thread about fixing the boot.efi on fusion and raid drives. The quick package I wrote was not tested on fusion/raid drives. And when people did try it, it didn't work.
 
tobyg said:
There were other posts in this thread about fixing the boot.efi on fusion and raid drives. The quick package I wrote was not tested on fusion/raid drives. And when people did try it, it didn't work.
Click to expand...

no problem with fusion drive. Each disks is as following :
0: GUID_partition_scheme *500.1 GB disk2
1: EFI 209.7 MB disk2s1
2: Apple_CoreStorage 499.8 GB disk2s2
3: Apple_Boot Boot OS X 134.2 MB disk2s3

so you must mount and replace boot.efi on each Apple_Boot partitions of each drives used by fusion disk...
 
10.9.4

Hi,

Updated from "Software Update" to 10.9.4 with the boot efi script, without any problem.

:D
 
backup disk ... not working ...

hi,

just upgraded to 10.9.4 on my 1.1 Mac ... thxxx to tobyg's boot.efi script !!! ...
and I did a Carbon Copy Clone of my startup disk ...
BUT ... I cannot start from this backup-disk any more ... ???

anybody any idea why not ... thxxxx for help !!
... :)) Gerald
 
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