Mac Pro 2,1 and OS X Mavericks

[Dark Dragoon]

Do you have more information on this step:
4.insert your board-id into InstallableMachine.plist(please google it)

I think that's probably what I'm missing.

On mine, on the installation media I went into the folder:
System > Installation > Packages

Then opened the InstallableMachines.plist file in Xcode.
There should be SupportedBoardIds with a little drop down to the left, click on the drop down to expand the list.
You can then hover the mouse over SupportedBoardIds and press the (+) that appears.
This will create a new entry where you can enter your computers board ID (The same one you added to OSInstall.mpkg).
Once done save the file.

 

[apple_iBoy]

Do you have more information on this step:
4.insert your board-id into InstallableMachine.plist(please google it)

I think that's probably what I'm missing.

tobyg, please go into terminal and enter the following:

ioreg -p IODeviceTree -r -n / -d 1

​

After you hit return, scan the results and look for "board-id" = <"something">

What comes up for something on your machine?

 

[mikeboss]

But exactly how does one overwrite the boot.efi? And if an update were applied that overwrote this file, what would you boot into in order to restore the good copy?

Is there a way to protect that file so that updates can't touch it?

AFAIK there's no way to stop an Apple update from overwriting the boot.efi.

I guess you'll have to boot from another disk to replace the files again.

 

[tobyg]

On mine, on the installation media I went into the folder:
System > Installation > Packages

Then opened the InstallableMachines.plist file in Xcode.
There should be SupportedBoardIds with a little drop down to the left, click on the drop down to expand the list.
You can then hover the mouse over SupportedBoardIds and press the (+) that appears.
This will create a new entry where you can enter your computers board ID (The same one you added to OSInstall.mpkg).
Once done save the file.

On my Mavericks USB drive built using the createinstallmedia method, I have no System/Installation/Packages directory.

 

[Dark Dragoon]

On my Mavericks USB drive built using the createinstallmedia method, I have no System/Installation/Packages directory.

Ah I also tried using the createinstallmedia and it didn't work,
instead I used the older method which tiamo's instructions linked to.

 

[Fredd057]

Hi !

Thanks for your job tiamo ...

I have a problem ... kernel panic when i tried to boot from the usb drive for installation after having made all the steps of your method ...

I don't know what is my mistake.

I let you see the message i have when booting ...

When i tried to run installation from the previous system i've got a message "this installation disk is corrupted, pleas download a new version on the app store".

So i decided to reboot on the usb drive and i got this error ...

My mac pro is a 1.1 updated to 2.1 with a Radeon 5770 from the apple store ...

Any idea ?

Thanks !

 

[tobyg]

Ah I also tried using the createinstallmedia and it didn't work,
instead I used the older method which tiamo's instructions linked to.

I see the problem now. I tried modifying the BaseSystem.dmg and repackaging it in the InstallESD.dmg but then I'm left with "This copy of the install OSX Mavericks application can't be verified. It may have been corrupted or tampered with during downloading." There may be a way around this to ignore signatures or something, but the main site for this sort of information that I would go to, insanelymac, is down.

I'm getting these errors in the log during install:

pkgdmg is missing a footer
pkgdmg validation has failed

I'm not sure if it's failing on my InstallESD.dmg or the BaseSystem.dmg inside.

Either way, this may be difficult to deal with.

 

[splifingate]

[...]

===================
source code: http://code.google.com/p/macosxbootloader/
it is built with visual studio 2013 and nasm

Immense thanks to you, tiamo, for what you have done.

I dropped the graph version into my Chameleon->Mavericks on a Mac Pro 1,1, Blessed Mavericks, and all is more than I would hope to have expected.

I have dropped it, likewise, into my modified installer, but have not performed a re-install (another story, for another time).

Any clues as to how I might compile this myself (if permissible) in OSX, native?

Thanks again for your work(s) and time.

Regards...

 

[tiamo]

Any clues as to how I might compile this myself (if permissible) in OSX, native?

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

 

[donw35]

My Experience

I was given a dead Mac Pro 1.1, I started to work on it and I knew the video card was out, I loaded a fresh SL install and could hear the music at the beginning but no video, I have a GT240 video card so I tried Lion but no go, no video. I thought I would give this process a last ditch effort, I installed Mavericks from my MBP and replaced the Boot.efi per instructions. the first boot did not work, no video so I put in the known bad video card and booted with Command + V, Now I get a desktop and first setup process. Did all that, repaired permissions and shutdown and put back the GT240, rebooted and got a desktop.

Thanks for your efforts, this old MP1.1 might have some life left in her yet.

 

[Fredd057]

Hi Tiamo ... no advice about my Panic at boot with your boot.efi file ?

When i put again the original boot.efi the booting is normal ...

thanks !

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

 

[tiamo]

Hi Tiamo ... no advice about my Panic at boot with your boot.efi file ?

When i put again the original boot.efi the booting is normal ...

thanks !

your kernel version 1699 means 10.7.5, my bootloader does not support this version.

 

[ggoerl]

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.

consider yourself lucky being stuck with snow leopard, that's still the only OS I like and still use. Hoorah for rosetta support!

 

[Rastafabi]

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.

1.) Your not stuck. Apple officially supports running OS X Lion (which ships with a 32bit kernel) on this machine.

2.) Your not stuck at all. You ever had the chance to use a CSM bootloder (hackintosh boot loader which uses BIOS instead of EFI) to enable a 64bit kernel.

3.) Now it's even better! The only purpose of the EFI file released by tiamo IS to ENABLE a fully working 64bit kernel on a 32bit efi system (in fact OS X will even tell you that your running on 64bit EFI).

4.) You can buy any USB3 adapter and use this driver to run it. (Well, maybe not any but your chances are extremely good. - I have a totally rare chipset and its still fully working.)

 

[mikeboss]

4.) You can buy any USB3 adapter and use this driver to run it. (Well, maybe not any but your chances are extremely good. - I have a totally rare chipset and its still fully working.)

I got me an ORICO on e*ay for USD 17.80 shipping from hong-kong included. look for seller sales_dsehk and card ORICO Desktop PCI-E USB 3.0 x 2 Port Express Card [PFU3-2P]. NO additional driver needed. just plug&play. doesn't even need addtional power to be connected.

 

[Fredd057]

your kernel version 1699 means 10.7.5, my bootloader does not support this version.

Oh noo :-( ... but it's not possible to install an higher version that 10.7.5 on 1.1 mac pro modded on 2.1 ...

 

[mikeboss]

Oh noo :-( ... but it's not possible to install an higher version that 10.7.5 on 1.1 mac pro modded on 2.1 ...

the whole point of tiamo's boot.efi is to run Mavericks (OS X 10.9) on the MacPro1,1 and 2,1. Lion runs without any modification whatsoever.

 

[Rastafabi]

Oh noo :-( ... but it's not possible to install an higher version that 10.7.5 on 1.1 mac pro modded on 2.1 ...

It would be great if you would actually READ the thread… especially it it's only 3 pages. Than you would know how to install...

However… here you are.

 

[666sheep]

Tiamo, this is magic. Your bootloader finally allowed EFI'ed AMD 7950 and whole 7xxx series to work flawlessly in 1,1/2,1. This is what was missing in Chameleon method. Some of R9 series will work as well.
Bootscreen, dual display, full acceleration and no cold bug. So far tested with 10.9 only, later will check 10.8.

You're the man! Big thanks!

 

[Fredd057]

the whole point of tiamo's boot.efi is to run Mavericks (OS X 10.9) on the MacPro1,1 and 2,1. Lion runs without any modification whatsoever.

Ok ... so, in a first time i need to install Lion and then using Tiamo's solution to install Mavericks ?

Thanks !

 

[Dark Dragoon]

Ok ... so, in a first time i need to install Lion and then using Tiamo's solution to install Mavericks ?

Thanks !

Unless you have another Mac to create the installer, as in that case you can create the modified Mavericks installer using the other Mac.
Then use the modified Mavericks installer to install Mavericks on a the completely clean (normally) unsupported Mac.

If you don't have another Mac then it would be easiest to run a standard Lion install on the unsupported Mac to create the Mavericks installer.

EDIT: For example I created the modified Mavericks installer on my MacBook Pro then used the installer to install Mavericks on my completely clean Mac Pro 1,1 (2006).

 

[Fredd057]

Unless you have another Mac to create the installer, as in that case you can create the modified Mavericks installer using the other Mac.
Then use the modified Mavericks installer to install Mavericks on a the completely clean (normally) unsupported Mac.

If you don't have another Mac then it would be easiest to run a standard Lion install on the unsupported Mac to create the Mavericks installer.

EDIT: For example I created the modified Mavericks installer on my MacBook Pro then used the installer to install Mavericks on my completely clean Mac Pro 1,1 (2006).

Ok ! I have understanding ! I will try it ! Thanks !

 

[macpro2000]

I'm getting the error "The bless tool was unable to set the current boot disk" when I try to select the usb drive as startup, and doesn't show up when holding down alt/option upon reboot. Anyone have any ideas. I've followed this sucker to a tee!

 

[splifingate]

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

'a lot of work' for you probably transforms into 'not impossible, but...' for mere mortals such as I <s>

Is VS13 'Express' in a bootcamp VM sufficient, or is VS13 Pro in a native boot needed?

Anyway(s), thanks again for the good stuff. I'll let you get back to your regularly scheduled broadcasting....

 

[mikeboss]

the question from "apple_iBoy" got me thinking... what to do if a future update will overwrite the boot.efi? I made a fresh install of Mavericks to an SSD (while in the MacPro3,1) using my USB thumbdrive I created with the creatinstallmedia command. this will also create a Recovery Partition. I then replaced the boot.efi on the Recovery Partition. AFAIK the Recovery Partition will never be updated by an Apple update. so, if something happens to the precious boot.efi, I can boot to the Recovery Partition and replace the boot.efi on the system volume again.