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

[Ih8reno]

New one. Definitely. Or you won't be able to upgrade to 10.11.1 properly.

So once your new files are ready I do the same procedure as the first time? replace the efi files in the 3 locations. I pulled the drive and connected it externally with my macbook pro. Anything else we may need to know if we are currently running 10.11?

Oh and I can't thank you enough!

 

[darthgeekonius]

You mean 10.11.1 final right? I'm already running the beta version with the last .efi I'll update because you said so, I'm just a little confused I guess.

New one. Definitely. Or you won't be able to upgrade to 10.11.1 properly.

 

[Pike R. Alpha]

So once your new files are ready I do the same procedure as the first time? replace the efi files in the 3 locations. I pulled the drive and connected it externally with my macbook pro. Anything else we may need to know if we are currently running 10.11?

Oh and I can't thank you enough!

Thanks.

The cool thing is that you don't need to pull the drive out of your Mac Pro, and connect it to another supported Mac. You can simply install/upgrade OS X straight from the App Store. That is when the new Launch Daemon is released. The first reboot is then covered by the launch daemon, but after that you replace the copies of boot.efi as usual. I mean. As long as the Recovery HD stays as is, with my version of boot.efi, then you will always have a way to replace the copies of boot.efi on the boot drive.

Note: All future versions of my version of boot.efi will be released here: http://piker-alpha.github.io/macosxbootloader/

 

[Pike R. Alpha]

You mean 10.11.1 final right? I'm already running the beta version with the last .efi I'll update because you said so, I'm just a little confused I guess.

Don't be confused. We are still working on the last couple of changes, and we will announce the final release here, and then you can download it from: http://piker-alpha.github.io/macosxbootloader/

Edit: I wish it would go faster, but the delay is caused by the limited number of people who are actually testing my latest commits here:
https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-14

And we can, with all due respect, only use people there who really know what they are doing, because you may end up with an unsupported Mac that fails to boot. So. People who can handle this kind of issues, are invited to join me there.

 

[Louis Vox]

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:

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)

I tried this PeterHolbrook's boot.efi from post #112 on this page:

https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-5

Along with instructions to edit: com.apple.Boot.plist by splifingate post #790

It now works on my system although it is only in verbose mode.

 

[Pike R. Alpha]

I tried this PeterHolbrook's boot.efi from post #112 on this page:

https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-5

Along with instructions to edit: com.apple.Boot.plist by splifingate post #790

It now works on my system although it is only in verbose mode.

The com.apple.Boot.plist edits should no longer be required. Test/confirm please. Thanks!

Verbose mode is normal behaviour for test versions of boot.efi

 

[Louis Vox]

The com.apple.Boot.plist edits should no longer be required. Test/confirm please. Thanks!

Verbose mode is normal behaviour for test versions of boot.efi

Tried it without com.apple.Boot.plist at first, system halted, after edit booted okay. Will try again with original.

 

[OGNerd]

This has been an adventure.

I patiently waited and watched as Pike, et al developed a working fork of the macosbootloader for El Capitan, then installed it onto a new 1TB Samsung SSD 850 EVO. I initially only replaced the boot.efi file in /usr/standalone/i386 and /System/Library/CoreServices/. It ran wonderfully, and was noticeably more responsive than the Yosemite and Mavericks installations on a fusion drive in the system. Something went amiss replacing the boot.efi on the SSD's recovery partition, so I made a CCC clone of the El Cap installation, wiped the SSD and attempted re-installation of El Cap to rebuild the recovery partition. Seven re-installations in a row failed, either by claiming the installer app was damaged (2 were freshly downloaded from the App Store), or that it could not install something from the Essentials.pkg. Success finally came on the 8th attempt by booting from an USB El Captian Installer stick that I had built earlier.

I now have a MP 2,1 that tri-boots Mavericks, Yosemite, and El Capitan, with enough oomph to host a reasonably snappy Windows 10 VM.

Happy camper!

 

[estevet]

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.

Yes sir.. a lot of smiles on everyones faces.. Great work.. Great Thanks !! Moltes Gracies

 

[codeman7]

The com.apple.Boot.plist edits should no longer be required. Test/confirm please. Thanks!

Verbose mode is normal behaviour for test versions of boot.efi

I'm happy to hear about this new process! Does this mean I can place the test (or final) boot.efis into place on my Yosemite install, and then just install El Capitan to a new drive or even upgrade?

 

[Pike R. Alpha]

I'm happy to hear about this new process! Does this mean I can place the test (or final) boot.efis into place on my Yosemite install, and then just install El Capitan to a new drive or even upgrade?

That is the idea yes, but I have yet to get a confirmation that it actually works. That was also why I was hoping that more people would join us and test the new versions of boot.efi

 

[codeman7]

That is the idea yes, but I have yet to get a confirmation that it actually works. That was also why I was hoping that more people would join us and test the new versions of boot.efi

I'm happy to give it a shot on my machine. Will try tomorrow.

 

[sweetspud]

That is the idea yes, but I have yet to get a confirmation that it actually works. That was also why I was hoping that more people would join us and test the new versions of boot.efi

Pike~

Where do we get 'em??

Also, could you direct me to the posting with the recommended procedure?

Would be happy to give it a try - I just cloned my Yosemite 10.10.5...

Thanks!

 

[splifingate]

Where do we get 'em??

https://forums.macrumors.com/thread...os-x-el-capitan.1890435/page-35#post-22082420

 

[Louis Vox]

The com.apple.Boot.plist edits should no longer be required. Test/confirm please. Thanks!

Verbose mode is normal behaviour for test versions of boot.efi

Tested again with same result: system halted, replace edited com.apple.Boot.plist and booted okay. Should I try a different boot.efi version?

I realise the test versions are verbose, I was just pointing it out to another user.

 

[Pike R. Alpha]

Tested again with same result: system halted, replace edited com.apple.Boot.plist and booted okay. Should I try a different boot.efi version?

I realise the test versions are verbose, I was just pointing it out to another user.

Thanks. Just for the record. That was with the copy of boot.efi from post #112 correct?

Also. You get the KP during the installation or on regular boots? What build of OS X are you using?

 

[codeman7]

Thanks.

The cool thing is that you don't need to pull the drive out of your Mac Pro, and connect it to another supported Mac. You can simply install/upgrade OS X straight from the App Store. That is when the new Launch Daemon is released. The first reboot is then covered by the launch daemon, but after that you replace the copies of boot.efi as usual. I mean. As long as the Recovery HD stays as is, with my version of boot.efi, then you will always have a way to replace the copies of boot.efi on the boot drive.

Note: All future versions of my version of boot.efi will be released here: http://piker-alpha.github.io/macosxbootloader/

I added your newest (I think, from the other thread post 112) boot.fi to my Yosemite install, and it boots fine, but my mac is still listed as MacPro1,1, and I can't use the El Capitan installer.

 

[Louis Vox]

Thanks. Just for the record. That was with the copy of boot.efi from post #112 correct?

Also. You get the KP during the installation or on regular boots? What build of OS X are you using?

I've now updated to 10.11.1 (Public Beta 4) using boot.efi from #112 with no problems. I got KP with all previous versions of boot.efi. I have not yet tried any newer versions.

 

[Pike R. Alpha]

I added your newest (I think, from the other thread post 112) boot.fi to my Yosemite install, and it boots fine, but my mac is still listed as MacPro1,1, and I can't use the El Capitan installer.

Use boot.efi from https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-14#post-22089649

 

[codeman7]

Use boot.efi from https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-14#post-22089649

Ok, I just switched over to that version, but I'm still showing up as a MacPro1,1 without the ability to download El Capitan from the app store.

 

[Pike R. Alpha]

Ok, I just switched over to that version, but I'm still showing up as a MacPro1,1 without the ability to download El Capitan from the app store.

Model won't be changed. Board-id does. Confirmed by several people already. Check output of ioreg -lw0 | grep board-id (should list "Mac-F42C88C8").

 

[codeman7]

Model won't be changed. Board-id does. Confirmed by several people already. Check output of ioreg -lw0 | grep board-id (should list "Mac-F42C88C8").

Realized I'm having some weird behavior where I can't seem to replace the /System/Library/CoreServices/boot.efi, when booted from a secondary El Capitan partition and writing to the Yosemite partition. Not sure if El Capitan SIP functions on other system drives. I sort of brute force rm -rf'd the boot.efi there and was then able to replace it, but now the partition won't boot.

Is there a good way to do a clean install of El Capitan at this point, without a secondary machine? No good way to do this, I was previously installing to an external from a newer mac and then cloning that to the Mac Pro internal.

 

[helmer]

Hi everybody,
First of all, thank you for everything you are doing.
I have a Mac Pro 1.1, 24Gb of ram, ATI Radeon 5770, 1 256 Go SSD with Mac OS 10.6.8.
One 1To SSD which is a clone of my first SSD with 10.6.8.
I put on a Mac 5,1, made the update to El Capitan.
I put the disk on my Mac 1,1, start-up on 10.6.8, replace the 2 efi files.
The first time I had the same kernel panic as Louis Vox.
Then I replace the efi files with those of Pike #838.
When I reboot with Alt Key and select El Capitan, nothing happens for a few seconds then the Mac boot on 10.6.8, and no kernel panic.
Hope this can help ;-)

 

[Pike R. Alpha]

Realized I'm having some weird behavior where I can't seem to replace the /System/Library/CoreServices/boot.efi, when booted from a secondary El Capitan partition and writing to the Yosemite partition. Not sure if El Capitan SIP functions on other system drives. I sort of brute force rm -rf'd the boot.efi there and was then able to replace it, but now the partition won't boot.

Is there a good way to do a clean install of El Capitan at this point, without a secondary machine? No good way to do this, I was previously installing to an external from a newer mac and then cloning that to the Mac Pro internal.

SIP works for all installations of El Capitan, and SIP need to be disabled from the RecoveryHD with: csrutil disable The next reboot allows you to replace any file you want.

 

[Pike R. Alpha]

Hi everybody,
First of all, thank you for everything you are doing.
I have a Mac Pro 1.1, 24Gb of ram, ATI Radeon 5770, 1 256 Go SSD with Mac OS 10.6.8.
One 1To SSD which is a clone of my first SSD with 10.6.8.
I put on a Mac 5,1, made the update to El Capitan.
I put the disk on my Mac 1,1, start-up on 10.6.8, replace the 2 efi files.
The first time I had the same kernel panic as Louis Vox.
Then I replace the efi files with those of Pike #838.
When I reboot with Alt Key and select El Capitan, nothing happens for a few seconds then the Mac boot on 10.6.8, and no kernel panic.
Hope this can help ;-)

Thank you Helmer, for confirming that our workaround works, and the delay of a few second is caused by the booter having to load the kernel and all kexts. That takes some time.