Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's not that hard a requirement to manage (12GB) but seems a bit odd when the OS requirement sure isn't 12GB.

Keep in mind that the minimum specs are minimum specs for significantly later processors with very different architectures - Front-side bus, faster ram, the list goes on.

By the time El Capitan was being tested, there was no such thing as a 512MB 667MHz dimm in the Apple Lineup. The installer actually USES 12GB and presumably some tasks will as well. I strongly recommend 16 or 32GB, specifically, 8 exactly matched modules. Again, it's ridiculously cheap on eBay.

The last thing to remember is that the cMP is an "enterprise class" workstation with server class processors and is therefore a bit finicky. Apple assumes that Mac Pros will be used by professionals for whom it makes perfect sense to pay for upgrades that save them precious time.
 
Hi,

Currently preparing to install El Cap on a white 13" Macbook mid 2007 (this one), I hope I got the right board ID, but I am struggling with the rather uncomprehensive 900+ posts ;)

Is there somewhere an updated how-to, like the one in post #19?
The whole bootbase.efi trouble got me puzzled, do I need it or not?..

Edit: I stumbled upon the fact that the GMA950 video card is not supported... so I guess I'm out of luck then. Any confirms on that?
 
Last edited:
Hi,

Currently preparing to install El Cap on a white 13" Macbook mid 2007 (this one), I hope I got the right board ID, but I am struggling with the rather uncomprehensive 900+ posts ;)

Is there somewhere an updated how-to, like the one in post #19?
The whole bootbase.efi trouble got me puzzled, do I need it or not?..

Edit: I stumbled upon the fact that the GMA950 video card is not supported... so I guess I'm out of luck then. Any confirms on that?

I can confirm that on the hackintosh side of the fence. A family members laptop couldnt go to any 64bit versions of osx due to the lack of a 64bit GMA950 kext/driver. Everything else worked fine, but the graphics werent accelerated which meant horrible (pretty much unusable) performance.
 
My basic machine profile is as follows -

Model Name:
Mac Pro
Model Type: 8-core
Model Identifier: MacPro2,1
Board Identifier: Mac-F42C88C8
Processor Name: Quad-Core Intel Xeon CPU X5365
Processor Model: Clovertown
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 8
Memory Size: 32 GB 667 MHz DDR2 FB-DIMM
Graphics Model: AMD Radeon HD 7950 3072 MB
Boot ROM Version: MP21.007F.B06
System SMC Version: 1.15f3

My primary El Capitan boot drive is a 1TB SSD in a PCIe slot, but I also boot from Yosemite or Mavericks partitions on a 1TB fusion drive, as well as Carbon Copy clones of the three on partitions of a 2TB spinner. I also have a 2TB spinner dedicated to TimeMachine, and another 2TB spinner for shared data.

16GB flash media created by CREATEINSTALLMEDIA and DISK MAKER X 5 both failed with an Essentials.pkg extraction error. I was only able to successfully install 10.11 on my MP 2,1 via Target Disk mode from a supported MBP 8,2.
[doublepost=1453116194][/doublepost]Hello OGNerd

You run AMD Radeon HD 7950 3072 MB in a MacPro2,1? With Bootscreen? I thought there is no 32 Bit EFI ROM for this Card...
 
[doublepost=1453116194][/doublepost]Hello OGNerd

You run AMD Radeon HD 7950 3072 MB in a MacPro2,1? With Bootscreen? I thought there is no 32 Bit EFI ROM for this Card...

Yes I do, and yes, with bootscreens. As I write, there is one currently available on eBay for $209 (US).
 
Yes I do, and yes, with bootscreens. As I write, there is one currently available on eBay for $209 (US).
I do as well.

If memory serves, the AMD Radeon 7950 HD is EBC (EFI byte code). So, it can be used in 32-bit or 64-bit cMPs.
 
Well folks, it's been very educational participating in this thread and getting El Capitan running on my 1,1. I'm a little sad to say that I'm moving to a pristine 2009 4,1. Of course, I also bought a W3690 processor for it and will be doing surgery in just a few days, so I'll certainly still be around the forums, I'll just be involved in different threads.

My 1,1->2,1 is available if anyone is interested. It's up on eBay atm but I'd be happier if someone from this pool of great people wanted it so that it can continue to run at it's full potential. PM me for all the details and/or to make me an offer. Specs are below. I upgraded the DVD burner to a brand-new LG just about a month ago and the only thing wrong is that the top front USB port is picky about what devices it likes to see. Sometimes fine, sometimes not; depending on the device and the phase of the moon or some other factor that I cannot track down. So let's just agree that it has 4 USB ports and it's otherwise perfect.

Huge thanks to Pike, rthjpm, Peter Holbrooke, MacVidCards/Rominator, MikeBoss, Splifinagate, 666Sheep and everyone else who participated and helped and used their brains to help all of us.

Cheers,

Matt
 
+1 here (actually it's branded R9/280X, but since the EFI part comes from a 7950 it's identified as such)

Just because I've done so much friggin' research and learned so much:

The EFI that is available from Netkas' site (http://forum.netkas.org/index.php/topic,5619.0.html) and others will work with almost any "Tahiti" chipset AMD card. Tahiti = HD 79xx, and R9 2xx(X). (Disclaimer) That's not an absolute guarantee as there are probably ~100 variations on the reference design, but all reports on dozens of cards say it works. Follow the instructions carefully using the rom from your exact card and you'll be fine. The BIOS switch on most variations of the card make it all but fool-proof. I was nervous about doing it, but it was far easier than many other things I've done with "Kate" (My cMP1,1). Again, I thank MacVidCards. ;)

Here are some fine points that will probably not have any impact in real-world use. They are somewhat relevant if you're shopping for used cards on eBay. For example, an R9 280X is theoretically worth a bit more than an R9 280 and the R9 2xx cards are probably newer that any HD 79xx cards:
  • R9 280 (no X) is a re-branded HD 7950 with a few very minor tweaks, as reported HERE
  • Similarly, the R9 280X is a re-branded HD 7970
  • The general consensus is that there is so little difference between 7950 and 7970 that it's not worth paying the premium for the 7970.*
  • Certain versions of the 7950 can match and even outperform certain versions of the 7970 when they're overclocked. (I can't find that reference in the hundreds of pages in my history, you can google it yourself or take my word for it)
*I bought both the 7950 and a 7970GHz edition Gigabyte branded cards. I like the 3 fan Windforce design and Gigabyte has the exact BIOS for every card they make on their site. I'll spare you the specs of the two cards and say that the 7950 is slightly overclocked vs. a reference 7950 and the GHz edition 7970 is the absolute high-end in terms of factory overclocked 7970's. Benchmarks aside, I can barely tell the difference. The 7970 cost me $50 more than the 7950. Is it better? Sure. Is it $50 better? Probably not.

Because I'm strange and like to research and experiment, I flashed the R9 280X bios onto my HD 7970 GHz editions. The clock speeds lowered to those on the Gigabyte website and the card performed flawlessly on both El Capitan and Windows 8.1. When I tried the same bios on the 7950, I got a BSOD on the Windows side. That was enough experimentation and I restored everything to factory settings.

One last note for Wojtek - If you care what Apple System Profiler says you can use Hexfiend (free) to change the string so that it reads R9 280, just open a copy (always be safe), search for HD 7950 (there are 2 instances) and replace it with R9 280X or anything you want, it's just a string that is passed.

-iMattux - Doing the research so you don't have to since 2001 (R) ;)
 
Last edited:
  • Like
Reactions: OGNerd and hwojtek
Well, it didn't go well (I reverted back to previous EFI bios), however I had finally time to document a small bootup glitch. I am not sure if it's the boot.efi or broken AMD drivers, but take a look at the lower left corner. 1,1 flashed to 2,1 with an R9/280x flashed to Apple 7950.
 
:):):):):):):):):):)
Thank U Guys
U RULE

Upgraded successfully from 10.11.1 to 10.11.3.

As easy as
install pike 3.1v7 in OS to upgrade
Start upgrade from Appstore
When rebooting, entering to my 2nd OS
Install Pike 3.1v7 again in Upgrading OS Partition
Reboot into Upgrading OS Partition
Finish installing

I cannot enter to rescue hd though. It appears as it didn't upgrade itself
Still on 10.11.2 (yeah, one false upgrade, it stayed there)


Keep up the good work fellas!!!!
Cheers from the bottom of the world!!!
(Chile)
(we all don't have enough money to get a new mac every year)
LOL

LOVE UUUUUUUU
:):):):):)
 
Well, it didn't go well (I reverted back to previous EFI bios), however I had finally time to document a small bootup glitch. I am not sure if it's the boot.efi or broken AMD drivers, but take a look at the lower left corner. 1,1 flashed to 2,1 with an R9/280x flashed to Apple 7950.
This (second boot stage logo issue) is usually the result of a frame buffer error (ports that don't match) which you can patch yourself, or someone need to patch the flash image for you.
 
  • Like
Reactions: hwojtek
Thanks, Pike. Hope you're OK?
And regarding the EFI ROM for the 280x... any volunteers? :) Or what should I look for in the .rom file?
 
Hello everyone...

FYI: I have successfully upgraded 2 x MacPro 2,1 (was 1,1) to 10.11.4. - with a slight catch.

10.11.4 installation replaces the boot.efi file(s).

My Test MacPro - standard HDD - OS installed, rebooted to recovery partition, and I subsequently rebooted it again to another copy of the OS on another HDD. There after I replaced the boot.efi files on the intended HDD, rebooted to this drive and all was well.

On my *Main* MacPro - this is where things didn't go so well. On this machine I have an SSD setup as a Fusion drive as the boot volume.
* download and install 10.11.4 - goes off to reboot
* reboot boots to old faithful OS 9 - and therefore a much older efi file (it show txt on the screen as it boots).
* use terminal, replace the boot.efi files as appropriate on the 10.11.4 fusion drive and reboot
* reboots back to OS 10.9.5 - so I double check the efi files and even redo the copies etc - nothing works.
* parameter RAM reset - then option key to choose boot volume - and it sill boots to OS 10.9.5.

* I decide that the only way forward is to break the fusion drive, but first I'll copy it to another HDD using carbon copy cloner.
* Then I boot the cloned drive - it boots successfully, completing the OS installation/upgrade.
* So then I think.... before I break the fusion drive... let me try booting to the fusion drive again after choosing it in system extension/startup.
* success - boot the fusion drive, complete the OS install. And done.


Long story. Sorry. Though it worth posting here for others.
I can always rely on the boot.efi that I'm using on 10.9.5 - but it is special in some way.

- David
 
Hello everyone...

FYI: I have successfully upgraded 2 x MacPro 2,1 (was 1,1) to 10.11.4. - with a slight catch.

10.11.4 installation replaces the boot.efi file(s).

My Test MacPro - standard HDD - OS installed, rebooted to recovery partition, and I subsequently rebooted it again to another copy of the OS on another HDD. There after I replaced the boot.efi files on the intended HDD, rebooted to this drive and all was well.

On my *Main* MacPro - this is where things didn't go so well. On this machine I have an SSD setup as a Fusion drive as the boot volume.
* download and install 10.11.4 - goes off to reboot
* reboot boots to old faithful OS 9 - and therefore a much older efi file (it show txt on the screen as it boots).
* use terminal, replace the boot.efi files as appropriate on the 10.11.4 fusion drive and reboot
* reboots back to OS 10.9.5 - so I double check the efi files and even redo the copies etc - nothing works.
* parameter RAM reset - then option key to choose boot volume - and it sill boots to OS 10.9.5.

* I decide that the only way forward is to break the fusion drive, but first I'll copy it to another HDD using carbon copy cloner.
* Then I boot the cloned drive - it boots successfully, completing the OS installation/upgrade.
* So then I think.... before I break the fusion drive... let me try booting to the fusion drive again after choosing it in system extension/startup.
* success - boot the fusion drive, complete the OS install. And done.


Long story. Sorry. Though it worth posting here for others.
I can always rely on the boot.efi that I'm using on 10.9.5 - but it is special in some way.

- David

So to make this a little easier I've ran across this before and here is the logic behind it. Install El Capitan initially on a regular HDD then Clone it over with a HDD Cloner to SSD works like a charm for me, just make sure to enable Trim.

This is why you had the issue initially because it was trying to boot some weird sequence on the "SSD" Portion. When you use an actually Physical Hard Drive Cloner it actually clones the "HDD Sector" and allows to boot. Had to do something similar to my
2006 Mavericks setup.

I may try these variations as I just bought 2 2006 models off eBay, with installing. El Capitan in mind. Probably would have had avoided it if I had done my research first but oh well. We will see how successful I am here in a week or so! Good Luck to all you guys on here. I'm hoping they don't come out with a. 10.11.5 and wipe us completely out.
 
FYI - I have installed 64 GB in what was originally a 1,1 updated to a 2,1. Everything works.

64GB_2_1.png


64GB_2_1_DIMM.png
 
Last edited:
  • Like
Reactions: hwojtek
FYI - I have installed 64 GB in what was originally a 1,1 updated to a 2,1. Everything works.

View attachment 626877

View attachment 626878

Sorry but how did you manage to update from 1.1 to 2.1 and to make it recognaize the graphic card. Can you please explain it to me.

Got the same machine and card, just 32gb of RAM in it. But do not recognaize the processor either (i upgrade them a few months ago)
 
Any luck with 10.11.5?
I'm getting write error permission when trying to replace boot.efi :mad:

EDIT:
remounted drive and it was possible to replace both files.

macpro2,1 (1,1), confirmed working 10.11.5 ;)
 
Last edited:
Any luck with 10.11.5?
I'm getting write error permission when trying to replace boot.efi :mad:

EDIT:
remounted drive and it was possible to replace both files.

macpro2,1 (1,1), confirmed working 10.11.5 ;)

It works on my 2,1 (1,1) setup.

Maybe you forgot that you have to issue 'chflags nouchg /System/Library/CoreServices/boot.efi' before replacing it with a fresh copy of 'boot.efi'. Make sure you issue 'chflags uchg /S/L/CS/boot.efi' once you copy 'boot.efi'.

EDIT:
My bad, I didn't see your edit.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.