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

jantoman

macrumors member
Mar 2, 2014
42
3
Italy
It booted to my prior OS (10.6.8). I went to System Preferences and attempted to select El Cap as the startup disk, but El Cap was not even there as an option
AFAIK, this is quite normal. I have the same configuration (HD with SL and SSD with newer OS, from Mavericks through El Capitan) and I've never been able to select from "Startup Disk" pane a boot disk with a non-supported OS. Always had to press "Alt" while booting, then confirm boot disk selection later.

the cursor froze over the El Cap HDD icon, and then 30 seconds later the Mac Pro boots into OS 10.6.8 again
It happened to me as well, when I was trying for the first time to install Mavericks on my 1,1. And yes, I believe it's something you can fix repairing permissions and blessing your drive from the Terminal.

Did you try to boot from Recovery Drive? It's the best way to fix permission, give it a try.
Then open the Terminal (I don't remember if you can do it from there or you have to reboot in SL) and paste:

sudo bless --folder /Volumes/ElCapDrive --file /Volumes/ElCapDrive/boot --setBoot

Replace ElCapDrive with the name of your boot disk. It's easier if the drive name doesn't have spaces in it: you can change it in the Info window and restore it later.
Insert the admin password and press Return. Your boot disk should be blessed.

Let us know if you get it working.
 

JOSECBA

macrumors member
Sep 1, 2015
33
4
Finally I got EL CAPITAN 10.11.1 working OK on my Mac Pro 1.1. Thank you all for your support and help, especially to the team of Pike R. Alpha !!!!

elcapitan2.png
 

stesoell

macrumors newbie
Nov 18, 2015
4
2
Hi all,

1st thank u guys for your efforts :)

Maybe someone can help me:

I've installed El Capitan 10.11.1 on an external drive via MBP (late 2013). Changed the boot.efi at /usr , /System and on the Recovery Partition with Pike's 3.1

After connecting the external HD to my Mac Pro 2.1 I can boot into El Capitans Recovery without problems. Here I've disabled the SIP.

In normal boot mode I can see shortly the Desktop (background image, dock..) When the upper menu bar pops up an immediately freeze will occur and the system restarts ...

Maybe someone knows about the phenomenon and could help me. Thank u guys.
 

javirnat

macrumors newbie
Jun 14, 2015
14
13
Valldemossa (Baleares Spain)
Still having trouble and can't get El Capitan to show up in System Preferences/startup disk. I installed El Cap from a Macbook Pro on to a HDD in the Mac Pro 1,1 using target disk mode via a firewire cable. After installation, the MBP successfully booted from El Cap. I completed the account set up, and then used the latest boot_grey.efi, and placed it in the three required places (changing name to boot.efi) in all three locations (Core Services, 1386, and Recovery). I ejected the El Cap drive from the MBP, powered off the Mac Pro from target mode, and rebooted the Mac Pro. It booted to my prior OS (10.6.8). I went to System Preferences and attempted to select El Cap as the startup disk, but El Cap was not even there as an option. I restarted, reset the PRAM, and held down the Option key after the second set of chimes and got the "El Cap" drive to show up, along with the Recovery Drive, and the HDD for my original OS (10.6.8). I clicked on the ElCap HDD image, the cursor froze over the El Cap HDD icon, and then 30 seconds later the Mac Pro boots into OS 10.6.8 again without any action on my part. This is my third attempt and I'm successful at replacing the boot.efi files, but can't get the Mac Pro to boot, or even see El Cap as an option in the Startup Disk. Very frustrating after reading how easy it has been for everyone else.

1) Am I missing something or doing something wrong?

2) I have read other posts about fixing permissions. Is this necessary with the most recent bootloader?

3) I have read others talking about the need to bless a folder. Is this a necessary step? If so, what bless command should I use in Terminal?

4) I have read that others used the Hennesie2000 guide, but it seems like that applied only to the previous versions. Are all those steps necessary?

5) Since I"m trying to upgrade from 10.6.8 to El Cap is that too big of a leap. Would it have been easier had I already done the bootloader trick with Mavericks or Yosemite?

6) Should I try from a bootable USB drive instead?

Would greatly appreciate any help, as I would love to resurrect my Mac Pro.

Thanks and Cheers,

Jeff

Below is the response I get after entering "bless --info" in Terminal:

Last login: Tue Nov 17 22:43:02 on console
Mias-MacBook-Pro:~ mamamia$ bless --info
finderinfo[0]: 58 => Blessed System Folder is /System/Library/CoreServices
finderinfo[1]: 653468 => Blessed System File is /System/Library/CoreServices/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 58 => OS X blessed folder is /System/Library/CoreServices
64-bit VSDB volume id: 0xE50B4EB0B9580C0D
Mias-MacBook-Pro:~ mamamia$
------------------------------------------------------------------------------------------------------------------

If you already change the 2 bot efi files (system-librery-coreservice , and in , system-usr standalone ) on El Capitan drive , restart your machine in (from) 10.6.8 and then go to applications utilities-disck and repare permissions in the driver were you have installed El capitan . After that you may boot with it ( El capitan drive ) select it from your system preferences startup disk and when it was done click on restart . The Mac Pro these time must restart well with the new system.
I hope this can help you.
Sorry for my english.
 

chackett

macrumors member
Feb 12, 2015
47
7
Wallingford, CT
Boot Champ is not supported on El Capitan, Do you think that asking Bootcamp to start in OS X has messed with the boot.efi files?
I tried replacing them again incase they were messed up but no luck..
I routinely use this method of switching back and forth from El Capitan to Windows 10, since I don't usually use the flashed ROMs on my R9 280X cards. It works fine, and it also worked well with Windows 7 and Yosemite. Using the control panels/preference panes to set your startup disk is not the problem. Unfortunately I'm not sure what is.
 

mykbro

macrumors newbie
Oct 28, 2015
3
0
The race is on.

Who's the first to get OS X version 10.11 El Capitan booting perfectly on a 2006/2007 Mac Pro (1,1/2,1)?

The techniques to boot Yosemite on unsupported Mac Pros may work. There are also a few more newer native boot loaders around: Pike's own clang fork and Andy Vandijck's andyvand fork.

UPDATE: Only one day later, 666sheep did it first!

The preferred approach that can be used to boot OS X 10.11 El Capitan Developer Betas on unsupported Map Pro models is a new El Capitan build of the Piker-Alpha macosxbootloader that is still in development:

This method, a fork of boot.efi boot loader that thunks EFI64 calls from the 64-bit OS X kernel to the EFI32 firmware.
The simplest install on a 2006/2007 Mac Pro is to use a second El Capitan-supported Mac and install El Capitan to the 2006/2007 Mac Pro's drive. This may be done either by attaching the 2006/2007 Mac Pro's drive as an external drive by placing the 2006/2007 Mac Pro in target disk mode or otherwise mounting the 2006/2007 Mac Pro's drive to an El Capitan-supported Mac.

Then, after installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi and repair permissions. That drive should now be bootable on a 2006/2007 Mac Pro, although sometimes it still may need to be blessed in the 2006/2007 Mac Pro.

Alternatively, adding rootless=0 to com.apple.Boot.plist allows replacing the boot.efi in-place.
 

mykbro

macrumors newbie
Oct 28, 2015
3
0
I got it all working with putting the MacPro in target mode and replacing the boot.efi file. Everything is working except when i choose restart I get stuck in some power cycle loop and never gets back up and running. If I shut down and power button on it's fine. Any ideas?
 

donjames

macrumors member
Feb 20, 2015
89
7
Henderson, Texas
Hi all,

1st thank u guys for your efforts :)

Maybe someone can help me:

I've installed El Capitan 10.11.1 on an external drive via MBP (late 2013). Changed the boot.efi at /usr , /System and on the Recovery Partition with Pike's 3.1

After connecting the external HD to my Mac Pro 2.1 I can boot into El Capitans Recovery without problems. Here I've disabled the SIP.

In normal boot mode I can see shortly the Desktop (background image, dock..) When the upper menu bar pops up an immediately freeze will occur and the system restarts ...

Maybe someone knows about the phenomenon and could help me. Thank u guys.


Hi,

I used this guy's script and was able to install El Capitan on my Macpro 1,1:
https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-33#post-22222642

When I first tried to install El Capitan, I had only 6 GB of ram in my computer. The installer, that I had created, would run for about 4 minutes and then the computer would reboot without finishing the install. I increased the ram to 12 GB and the El Capitan install ran perfectly. I made the installer on my Macpro 1,1. I created the installer on a hard drive and on an 8 GB usb drive. I successfully installed El Capitan from both.

I read a post by another guy who said that he could not install El Capitan with 8 GB of ram, but was able to do an install with 32 GB of ram.

Let me know if this helps.

Regards,

donjames
 

OldMachineFan

macrumors newbie
Nov 15, 2015
5
2
AFAIK, this is quite normal. I have the same configuration (HD with SL and SSD with newer OS, from Mavericks through El Capitan) and I've never been able to select from "Startup Disk" pane a boot disk with a non-supported OS. Always had to press "Alt" while booting, then confirm boot disk selection later.


It happened to me as well, when I was trying for the first time to install Mavericks on my 1,1. And yes, I believe it's something you can fix repairing permissions and blessing your drive from the Terminal.

Did you try to boot from Recovery Drive? It's the best way to fix permission, give it a try.
Then open the Terminal (I don't remember if you can do it from there or you have to reboot in SL) and paste:

sudo bless --folder /Volumes/ElCapDrive --file /Volumes/ElCapDrive/boot --setBoot

Replace ElCapDrive with the name of your boot disk. It's easier if the drive name doesn't have spaces in it: you can change it in the Info window and restore it later.
Insert the admin password and press Return. Your boot disk should be blessed.

Let us know if you get it working.

Rejoice, rejoice, and again I say rejoice! Jantoman, thanks so much for your advice, I got El Cap working on my Mac Pro. I first tried to boot the Mac Pro from the Recovery drive, clicked on it, and got the same issue... it booted to Mac OS 10.6.8. Next, I tried repairing permissions with Disk Utility on the Mac Pro while booted from 10.6.8, and both the verify and repair disk permissions options were greyed out, so I was not able to do anything.

I then put the Mac Pro in target disk mode via firewire cable, booted my Mac Book Pro, launched Terminal, and blessed the folder using the commands you provided. I dragged all my Mac Pro HDDs to the trash on the MBP pro, and powered off the Mac Pro (taking it out of target disk mode). Next, I booted the Mac Pro while holding down alt (option), and I got a different choice. Previously, I saw the name for "ElCap" which is what I named the HDD I installed El Cap on to. This time, the same hard drive (named ElCap) was titled "boot.EFI." I selected the boot.efi hard drive icon, and voila, the Mac Pro booted in El Cap. After this boot, I now saw my El Cap drive as an option in the system preferences for a startup disk. In other words, the only thing I did new was use the bless commands that Jantoman provided. Thank you all for your help, and thanks for the hard work of all those who developed and tested this! I hate the new tall Mac Pro Donut, and am thrilled to resurrect a proper metal tower! Whatever happened to manly computers and internal expansion? Thanks also to Javirnat for your suggestions. In case anyone has trouble, this was the outcome I saw in Terminal after using the Bless commands.

Here is the bless command and results:


Mias-MacBook-Pro:~ mamamia$ sudo bless --folder/Volumes/ElCap --file /Volumes/ElCap/boot --setBoot

bless: unrecognized option `--folder/Volumes/ElCap'

Usage: bless [options]

bless --help


bless --folder directory [--file file]

[--bootinfo [file]] [--bootefi [file]]

[--setBoot] [--openfolder directory] [--verbose]


bless --mount directory [--file file] [--setBoot] [--verbose]


bless --device device [--setBoot] [--verbose]


bless --netboot --server url [--verbose]


bless --info [directory] [--getBoot] [--plist] [--verbose] [--version]


Here is the bless info command and results:


Mias-MacBook-Pro:~ mamamia$ bless -- info

No volume specified

Mias-MacBook-Pro:~ mamamia$ password

-bash: password: command not found

Mias-MacBook-Pro:~ mamamia$ bless info

No volume specified

Mias-MacBook-Pro:~ mamamia$ bless --info

finderinfo[0]: 2 => Blessed System Folder is /Volumes/ElCap/

finderinfo[1]: 0 => No Blessed System File

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 2 => OS X blessed folder is /Volumes/ElCap/

64-bit VSDB volume id: 0xA05658FF0F26CA17

Mias-MacBook-Pro:~ mamamia$

Cheers and thanks to all!

Jeff
 

Attachments

  • photo.JPG
    photo.JPG
    116.7 KB · Views: 387
Last edited:

luvdahack

macrumors newbie
Mar 25, 2015
5
2
North Texas
Rejoice, rejoice, and again I say rejoice! Jantoman, thanks so much for your advice, I got El Cap working on my Mac Pro. I first tried to boot the Mac Pro from the Recovery drive, clicked on it, and got the same issue... it booted to Mac OS 10.6.8. Next, I tried repairing permissions with Disk Utility on the Mac Pro while booted from 10.6.8, and both the verify and repair disk permissions options were greyed out, so I was not able to do anything.

I then put the Mac Pro in target disk mode via firewire cable, booted my Mac Book Pro, launched Terminal, and blessed the folder using the commands you provided. I dragged all my Mac Pro HDDs to the trash on the MBP pro, and powered off the Mac Pro (taking it out of target disk mode). Next, I booted the Mac Pro while holding down alt (option), and I got a different choice. Previously, I saw the name for "ElCap" which is what I named the HDD I installed El Cap on to. This time, the same hard drive (named ElCap) was titled "boot.EFI." I selected the boot.efi hard drive icon, and voila, the Mac Pro booted in El Cap. After this boot, I now saw my El Cap drive as an option in the system preferences for a startup disk. In other words, the only thing I did new was use the bless commands that Jantoman provided. Thank you all for your help, and thanks for the hard work of all those who developed and tested this! I hate the new tall Mac Pro Donut, and am thrilled to resurrect a proper metal tower! Whatever happened to manly computers and internal expansion? Thanks also to Javirnat for your suggestions. In case anyone has trouble, this was the outcome I saw in Terminal after using the Bless commands.

Here is the bless command and results:


Mias-MacBook-Pro:~ mamamia$ sudo bless --folder/Volumes/ElCap --file /Volumes/ElCap/boot --setBoot

bless: unrecognized option `--folder/Volumes/ElCap'

Usage: bless [options]

bless --help


bless --folder directory [--file file]

[--bootinfo [file]] [--bootefi [file]]

[--setBoot] [--openfolder directory] [--verbose]


bless --mount directory [--file file] [--setBoot] [--verbose]


bless --device device [--setBoot] [--verbose]


bless --netboot --server url [--verbose]


bless --info [directory] [--getBoot] [--plist] [--verbose] [--version]


Here is the bless info command and results:


Mias-MacBook-Pro:~ mamamia$ bless -- info

No volume specified

Mias-MacBook-Pro:~ mamamia$ cymia

-bash: cymia: command not found

Mias-MacBook-Pro:~ mamamia$ bless info

No volume specified

Mias-MacBook-Pro:~ mamamia$ bless --info

finderinfo[0]: 2 => Blessed System Folder is /Volumes/ElCap/

finderinfo[1]: 0 => No Blessed System File

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 2 => OS X blessed folder is /Volumes/ElCap/

64-bit VSDB volume id: 0xA05658FF0F26CA17

Mias-MacBook-Pro:~ mamamia$

Cheers and thanks to all!

Jeff
 

luvdahack

macrumors newbie
Mar 25, 2015
5
2
North Texas
------------------------------------------------------------------------
for unlock you need do this:
1- Open Terminal
(/Aplicaciones/Utilidades)
2- Write this , follow of an space :
sudo chflags -R nouchg (here put or type an space).
3- Move the lock file from were is to the terminal window.
4- Push intro.
5- Terminal ask for your password , put it, and push intro.
Thats all and enjoy.
Some time ago I had the same problem and I do this and all is ok now.
Tell my if don´t work for you , but I´m 99% that this method works well for everybody.
sorry for my very bad english .


Your English is totally sufficient. Soy un perrro, entiendo bastante pero no puedo hablar nada. I used your directions to replace the boot efi on the Recovery Disk, did not need to boot out of El Cap, just used diskutil list command and then found the locked boot ef, dropped it in Terminal and authenticated and it worked! Replaced with Pikers boot efi. Mil gracias. NP
 
  • Like
Reactions: JOSECBA

OldMachineFan

macrumors newbie
Nov 15, 2015
5
2
I did not have an easy time with this. Spending hours reading through all 50+ pages of this thread caused me some confusion, because advice developed along with the versions, so that I was hanging on to older methods in my mind while reading about the new. Frankly, I got them all mixed up. I made a Word Doc for myself in case I need to redo this in the future. Everyone's scenario might vary, but I'm pasting what worked for me (Word file was too big to upload) in case it saves someone else from the 16+ hours I spent trying to get this to work for me. This is my small contribution in hopes that it will save others from the errors I made. There is a lot of detail there that many may not need, but it's there regardless. I would not have been able to succeed without the help on this forum. THANK YOU ALL!

Jeff


1) Downloaded El Capitan OSX from App store from MacBook Pro running OS X 10.7.5

2) Started the 2006 Mac Pro1,1 running OS 10.6.8, opened System Preferences, then Startup Disk, and selected “Target Disk Mode,” and restarted Mac Pro.

3) Connected Mac Book Pro (MBP) to the Mac Pro via firewire, and my HDDs in the Mac Pro were visible on the MBP desktop.

4) Used the MBP to erase the new hard drive (HDD) in the Mac Pro (ElCap), and formatted as Mac OS Extended (Journaled).

5) Installed El Capitan OS from the installer on the MBP on to the El Cap HDD in the Mac Pro while in Target Disk mode via firewire.

6) The installation took about 30 minutes, and then the MBP rebooted from the El Cap drive, and I completed the intro and account setup for the El Capitan OS.

7) I restarted the MBP, which booted to its native OS 10.7.5.

8) I opened Terminal from the MBP, and did the following to unlock the boot.efi files to enable replacement by Pike’s boot.efi.

a) defaults write com.apple.finder AppleShowAllFiles YES (and hit return)

b) Then re-launch Finder (alt+click finder in dock, relaunch)

c) The first boot.efi is at: /System/Library/CoreServices/boot.efi


Run this command to unlock it:


sudo chflags nouchg drag and drop the boot.efi to terminal to get the exact path


d) Hit enter

e) If prompted for your password, enter it in terminal, and then press enter


9) I downloaded Pike’s boot_grey.efi from here:

http://piker-alpha.github.io/macosxbootloader/


10) Now that the boot.efi from the official install /System/Library/CoreServices/boot.efi was unlocked, I moved that boot.efi to the trash in the MBP.


11) I then placed Pike’s boot_grey.efi in the /System/Library/CoreServices folder where the original used to be. I then renamed the newly placed boot_grey.efi to boot.efi


12) The next boot.efi is at: /usr/standalone/i386/boot.efi


13) I deleted the boot.efi file that was placed in the i386 folder by the official El Capitan OS installation by moving it to the trash.


14) I placed Pike’s boot_grey.efi file in the /usr/standalone/i386/ folder where the original used to be. I then renamed the newly placed boot_grey.efi to boot.efi


15) Next, I launched Disk Utility from the MBP, and did the following to replace boot.efi file in the RecoveryHD


16) In Disk Utility, I selected “show every partition” from the debug menu.


17) I then clicked on the “RecoveryHD” subdrive under the ElCap drive (which is the HDD where I installed El Capitan OS on in my Mac Pro).


18) Next, I clicked mount so that the files in RecoveryHD were visible


19) I then opened the folder entitled com.apple.recovery.boot


20) I moved the original boot.efi from inside the com.apple.recovery.boot folder to the trash.


21) I then placed Pike’s boot_grey.efi file in the com.apple.recovery.boot folder where the original used to be. I then renamed the newly placed boot_grey.efi to boot.efi


22) I then clicked on RecoveryHD within Disk Utility again, and then clicked unmount as I no longer needed to see that drive or it’s files.


23) Now, all three original boot.efi files were replaced with Pike’s boot_grey.efi and were renamed to boot.efi


24) Next, I needed to bless the system folder. I completed this in Step #25 below.


25) In terminal on the MBP I blessed the El Capitan OS system folder (note: my HDD name was ElCap) for my Mac Pro by typing in the following:


sudo bless --folder/Volumes/ElCap --file /Volumes/ElCap/boot --setBoot


I then hit Enter


26) I think I was prompted for my password, entered it, and then hit enter again. If not, it did it all just by me hitting Enter after completing Step #25 above. Below is what the input and output in terminal looked like. I only typed in what’s in bold below, and then hit enter, and the remainder of text is terminal’s response:


Mias-MacBook-Pro:~ mamamia$ sudo bless --folder/Volumes/ElCap --file /Volumes/ElCap/boot --setBoot

bless: unrecognized option `--folder/Volumes/ElCap'

Usage: bless [options]

bless --help


bless --folder directory [--file file]

[--bootinfo [file]] [--bootefi [file]]

[--setBoot] [--openfolder directory] [--verbose]


bless --mount directory [--file file] [--setBoot] [--verbose]


bless --device device [--setBoot] [--verbose]


bless --netboot --server url [--verbose]


bless --info [directory] [--getBoot] [--plist] [--verbose] [--version]


27) Next, I wanted to find out what folder was blessed on my ElCap drive, and entered the following command within Terminal:


bless – info


I believe I was prompted for my password, entered it, and then hit enter.


Below is what the terminal input/output looked like for this command. Where password is in bold, was my actual password. I only typed in bless –info and hit enter, and my real password was spit out by terminal in bold, but I changed it to password here


Mias-MacBook-Pro:~ mamamia$ bless -- info

No volume specified

Mias-MacBook-Pro:~ mamamia$ password

-bash: password: command not found

Mias-MacBook-Pro:~ mamamia$ bless info

No volume specified

Mias-MacBook-Pro:~ mamamia$ bless --info

finderinfo[0]: 2 => Blessed System Folder is /Volumes/ElCap/

finderinfo[1]: 0 => No Blessed System File

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 2 => OS X blessed folder is /Volumes/ElCap/

64-bit VSDB volume id: 0xA05658FF0F26CA17


28) At this point the System Folder in my ElCap HDD in the Mac Pro was blessed.


29) On the MBP, I then dragged all the HDD icons for HDDs within the Mac Pro to the trash.


30) I powered off the Mac Pro to take it out of Target Disk mode.


31) I started the Mac Pro, while holding down the alt (option) key, and saw three HDD icons to choose as startup system folders:


a) Western Digital (the original drive I have running OS 10.6.8)


b) boot.EFI (the drive upon which I installed the El Capitan OS)


c) RecoveryHD (the RecoveryHD that was part of the El Capitan OS install)


32) During previous failed attempts to get this working (when I did not correctly bless the El Cap HDD), the ElCap HDD would show as ElCap during after booting the Mac Pro while holding the Alt key.


33) Now, after correctly blessing the system folder in the El Capitan OS on my ElCap drive, the ElCap drive was listed as boot.EFI during startup.


34) I was advised in some posts to try and boot from RecoveryHD first, but decided to select boot.EFI (HDD choice in #31(b) above).


35) To my great pleasure and amazement, the Mac Pro successfully booted into the El Capitan OS.


36) Once I was fully booted, I went to System Preferences, selected the Startup Disk for El Capitan, and the machine rebooted to the El Capitan OS after this step without me having to hold the alt key and select it.


37) During previous attempts (when the folder wasn’t correctly blessed) I would select the ElCap HDD icon, the cursor would freeze, and then my Mac Pro would boot into 10.6.8. Also, I could never find the El Cap OS as a choice in Startup Disk.


38) I have read other posts where folks were able to complete this process without blessing the folder, or at least they did not say they did so. For me, blessing the El Capitan OS folder was the thing I was missing that when correctly executed, enabled my success.
 

Mystere65

macrumors member
Nov 2, 2015
79
49
Firenze (Italy)
I used a simple procedure, thanks to the user 3096, which has made available an image of El Capitan already ready, once restored on the EFI partition and replaced everything works beautifully.
 

macpro11yosemite

macrumors newbie
Oct 8, 2015
3
0
Yes, I installed one for Mavericks and it was working fine in El Capitan, but I've replaced it with a 6850 because I need a card with driver for Windows 10.
So the ATI Radeon HD 4870 512MB will NOT work with windows 10?? I really want 10 to be able to dualboot with el cap.
 

javirnat

macrumors newbie
Jun 14, 2015
14
13
Valldemossa (Baleares Spain)
Your English is totally sufficient. Soy un perrro, entiendo bastante pero no puedo hablar nada. I used your directions to replace the boot efi on the Recovery Disk, did not need to boot out of El Cap, just used diskutil list command and then found the locked boot ef, dropped it in Terminal and authenticated and it worked! Replaced with Pikers boot efi. Mil gracias. NP
--------------------------------------
Thank you mate.
 

macpro11yosemite

macrumors newbie
Oct 8, 2015
3
0
I wasn't successful installing the legacy drivers. I didn't invest to much time into it, maybe it's possible.
Thanks! One more question. Is the ATI Radeon HD 4870 512MB fast in El Capitan? Its only 512Mb, but it's very affordable. I might be able to afford the 1GB version, if the 512 is not fast enough.
I do alot of video and photography work, so I need pretty fast hardware in my Mac Pro 1,1.
Thank you,
Matthew
 

leoiv

macrumors newbie
Oct 13, 2015
15
6
Italy
Thanks! One more question. Is the ATI Radeon HD 4870 512MB fast in El Capitan? Its only 512Mb, but it's very affordable. I might be able to afford the 1GB version, if the 512 is not fast enough.
I do alot of video and photography work, so I need pretty fast hardware in my Mac Pro 1,1.
Thank you,
Matthew

Don't know about the 512 MB version, but i own the 1GB one, and it works like a charm.
 

Techchallenged1

macrumors newbie
Nov 14, 2015
9
1
There is a EBC ROM for 6870 that shows correct identifier, but it will not give you boot screen.
Thanks for the rom info. bummed about the boot screen. May have to invest in a Elcapitan compliant daughter card for boot screen. Probably a 8800gt or 5770 as my 7300gt won't play nice with Elcapitan when loaded.
 
Last edited:

profinite

macrumors regular
May 1, 2009
107
33
Thanks to many good people at this site and particularly in this marvelous thread, I have upgraded my 2006 Mac Pro that I have had for 9 years so that it could run Yosemite then El Capitan.

Today, I am happy to report that this remarkable MacPro1,1 (flushed to 2,1) recognizes 64GB (8 x 8GB) or memory:

OS_X_El_Capitan.jpg


64GB_RAM.jpg
 

dcloud45

macrumors member
Oct 5, 2015
52
0
Hey guys I had been running el cap since day 1 . Boots up ok , but am having problems with some applications not launching, one of them is safari, notes , avg, calendar , any ideas what's going on?
 

profinite

macrumors regular
May 1, 2009
107
33
Can I ask where you bought those DIMMs and how much you paid for them?

On eBay, here are the DIMM's I purchased for $199.

Caution:
The type of DIMM that works in 2006 Mac Pro is PC2-5300F 2Rx4 FB-DIMM ECC.
(1) The F after 5300 (or FB in FB-DIMM) means that the module is Fully Buffered.
(2) DO NOT get PC2-5300P DIMM’s. These parity modules are incompatible with MacPro1,1; both physically and electrically.

On eBay, use a search string like "64GB (8x8GB) PC2-5300F FB-DIMM”. I just did, and $176 is the lowest price at which you can get 64GB right at this moment.
Here are the search results.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.