Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

Pike R. Alpha said:
Status Update:

The next update to boot.efi will include:

1.) Installer Detection (done/confirmed working).
- One copy of boot.efi can be used in all locations (disables SIP for installation folders).

2.) Kernel patcher (done/confirmed working).
- This allows kexts to load without a prelinkedkernel.

3.) SMBIOS board-id upgrade (work in progress/confirmed working).
- This changes the board-id of your MacPro[1,1/2,1] to that of a MacPro3,1
- Other unsupported Mac models can be added to the list.

The result is that you can download El Capitan from the App Store and launch the installer from the Application folder without the need to mod the DMG's.
Click to expand...


Pike ~

Thank you for all your hard work!!

You've kept an untold number of Mac Pros out of the trash heap!
 
  • Like
Reactions: leoiv
Pike R. Alpha said:
3.) SMBIOS board-id upgrade (work in progress/confirmed working).
- This changes the board-id of your MacPro[1,1/2,1] to that of a MacPro3,1
- Other unsupported Mac models can be added to the list.
Click to expand...

So as long as the OS will be running with this new boot-efi, the mac will be seen as a 3,1 - correct?
 
Pike R. Alpha said:
Status Update:

The next update to boot.efi will include:

1.) Installer Detection (done/confirmed working).
- One copy of boot.efi can be used in all locations (disables SIP for installation folders).

2.) Kernel patcher (done/confirmed working).
- This allows kexts to load without a prelinkedkernel.

3.) SMBIOS board-id upgrade (work in progress/confirmed working).
- This changes the board-id of your MacPro[1,1/2,1] to that of a MacPro3,1
- Other unsupported Mac models can be added to the list.

The result is that you can download El Capitan from the App Store and launch the installer from the Application folder without the need to mod the DMG's.
Click to expand...


Pike~

Just to clarify:

The procedure will be to replace the boot.efi files in the usual three locations (i386, CoseServices, Recovery HD) with your new (yet to be released) modified boot.efi. You then start the El Cap installer from the Application folder and all's well??

...and subsequent updates??

Thanks, again!!
 
sweetspud said:
Pike~

Just to clarify:

The procedure will be to replace the boot.efi files in the usual three locations (i386, CoseServices, Recovery HD) with your new (yet to be released) modified boot.efi. You then start the El Cap installer from the Application folder and all's well??

...and subsequent updates??

Thanks, again!!
Click to expand...

No, he means that let's say you're on Lion or Mavericks or Yosemite, you open App Store and you see the El Capitan available. You press Install (means upgrade) and you're good to go. The reason will be that App Store and previous OS will "think" you're on a Mac Pro 3,1 instead of 1,1/2,1 (unsupported).

This is what I think Pike meant.
 
  • Like
Reactions: leoiv
VAGDesign said:
No, he means that let's say you're on Lion or Mavericks or Yosemite, you open App Store and you see the El Capitan available. You press Install (means upgrade) and you're good to go. The reason will be that App Store and previous OS will "think" you're on a Mac Pro 3,1 instead of 1,1/2,1 (unsupported).

This is what I think Pike meant.
Click to expand...
Correct.

Note: The new LaunchDaemon – also soon to be released – will take care of /.IABootFiles/boot.efi and /OS X Install Data/boot.efi so you can also reboot straight away and start with the actual installation process. After this you'll need to replace the boot.efi file in the usual locations. For this procedure we don't have a great solution, but a script should help to ease the pain a little.
 
  • Like
Reactions: sweetspud, VAGDesign and leoiv
Pike R. Alpha said:
Status Update:

The next update to boot.efi will include:

1.) Installer Detection (done/confirmed working).
- One copy of boot.efi can be used in all locations (disables SIP for installation folders).

2.) Kernel patcher (done/confirmed working).
- This allows kexts to load without a prelinkedkernel.

3.) SMBIOS board-id upgrade (work in progress/confirmed working).
- This changes the board-id of your MacPro[1,1/2,1] to that of a MacPro3,1
- Other unsupported Mac models can be added to the list.

The result is that you can download El Capitan from the App Store and launch the installer from the Application folder without the need to mod the DMG's.
Click to expand...

So Pike unlike the old Yosemite procedure we just add the new boot.efi to the current OS X (Yosemite in my case) and download from the app store as normal? If so that's beyond amazing!!! Cheers!!!
 
A sincere thank you for the great work and for giving a new Yosemite life to my and my brother-in-law's Mac Pro 1,1.
Will we need the good old "PikeYoseFix.pkg" in an updated form ("PikeElCapFix")?
 
Last edited:
xabierot said:
I follow the instructions on post ·585, on an external HD.
El Capitan boots fine and all seems to work. Then I make a carbon copy clone on the Macintosh HD (I have Yosemite on other partition) but when boots occurs that:

IMG_4078.JPG

Any help ? I tried boot.efi attached on post @585 and from http://piker-alpha.github.io/macosxbootloader/
I have a MacPro 1,1 with ATI Radeon HD 5770 1024 MB
Thanks in advance

(Sorry about my english)
Click to expand...

I get exactly the same KP on my machine (same setup as above). Tried all the boot.efi versions available, can anyone explain what the problem is?
 
[Quote = "Pike R. Alpha, poste: 22076639, membre: 995725"] Exact.


Bonsoir Pike r.alpha
Je ne suis pas sur le bon commentaire Mais je Voulais savoir si vous aviez Une solution Pour aller (prendre) JUSQU'A 10,6 Sur un PowerPC G5 puissance merci.
Les excuses de Djé Presente Membres de commentaire aux cette pertinente Cordialement
 
Last edited:
Louis Vox said:
I get exactly the same KP on my machine (same setup as above). Tried all the boot.efi versions available, can anyone explain what the problem is?
Click to expand...
It can't find the prelinkedkernel, and the version that you are using does not have the kernel patching routine that I have written to overcome this issue. New update will soon be made available.

Here's a verbose/debug version to try: boot 0e193cd3c15a599cfab687bbdab4bdded2e2fad4.zip

Nobody else should use this version!
 
Last edited:
wolf1734 said:
[Quote = "Pike R. Alpha, poste: 22076639, membre: 995725"] Exact.


Bonsoir Pike r.alpha
Je ne suis pas sur le bon commentaire Mais je Voulais savoir si vous aviez Une solution Pour aller (prendre) JUSQU'A 10,6 Sur un PowerPC G5 puissance merci.
Les excuses de Djé Presente Membres de commentaire aux cette pertinente Cordialement
Click to expand...
No.
 
leoiv said:
A sincere thank you for the great work and for giving a new Yosemite life to my and my brother-in-law's Mac Pro 1,1.
Will we need the good old "PikeYoseFix.pkg" in an updated form ("PikeElCapFix")?
Click to expand...
Yes, but it can only restore boot.efi for the first installation phase. After that you'll have to do it manually. That is until we've figured out how to solve this issue.
 
  • Like
Reactions: leoiv
Many thanks once again to Pike R. Alpha for breathing more life into these older Mac Pro's. Did a clean install on a new SSD drive from a compatible MacBook Pro with a firewire enclosure. Replaced all three boot.efi's, connected to Mac Pro and changed Startup Drives, booted up and used the Migration Utility to swap everything over from my Yosemite install. Had to remove a Sonnet USB 2.0 card and a USB3.0 card. One of them was causing a boot problem. Will do some more experiments to see which one or both.

Order a flashed AMD Sapphire Radeon 7970 from MacVidCards, just got it today. Popped it in and it's golden. Glad I can continue to use this wonderful machine for awhile longer.
 
  • Like
Reactions: leoiv
Rustynova said:
Many thanks once again to Pike R. Alpha for breathing more life into these older Mac Pro's. Did a clean install on a new SSD drive from a compatible MacBook Pro with a firewire enclosure. Replaced all three boot.efi's, connected to Mac Pro and changed Startup Drives, booted up and used the Migration Utility to swap everything over from my Yosemite install. Had to remove a Sonnet USB 2.0 card and a USB3.0 card. One of them was causing a boot problem. Will do some more experiments to see which one or both.

Order a flashed AMD Sapphire Radeon 7970 from MacVidCards, just got it today. Popped it in and it's golden. Glad I can continue to use this wonderful machine for awhile longer.
Click to expand...
Thank you Sir.

One note. We're not done yet. I want the installation process to be super smooth / supported Mac like, but since there is zero documentation from Apple about SIP... I had to figure it all out myself and 200 hours later (really) we're almost there.

And if everything goes as planned, then by Friday, or early Saturday, the new release should put a smile on everyones face.
 
  • Like
Reactions: leoiv, orangez and VAGDesign
Can anyone remind me the 3 locations where I have to replace the boot.efi, I've lost my bookmark for it and I've trawled through pages of the thread and can't find it :/
 
Pike R. Alpha said:
You need to mount it. First use: diskutil list and look for the Apple_Boot Recovery HD (usually
disk0s3) and then enter: diskutil mount disk0s3 (where the 0 matches the drive number in your setup).
Click to expand...
Got it, thanks. Replaced all three boot.efi files, assume it's a case of restarting and then hitting 'get' in app store?
 
For those of us already running 10.11 due to your great boot.efi work do we need to change it or can we remain on the current efi files
 
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