Got a tip for us?
Let us know
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
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
Hi everyone, I've been running Yosemite for about 18 months on my Mac Pro 1,1. I want to find out if anyone has successfully upgraded (not new install) to El Capitan. The reason is that when i first successfully installed Yosemite I could not get my iCloud to work -- so Mail and other stuff was not working. Appreciate any direction on upgrading. Thanks!
I did, using exactly the same process as installing (as described in the beginning of the thread), but choosing to upgrade once the installer booted from USB (note - since I failed to find a good USB-stick, I am using an USB-SATA interface and a 2.5" hard disk, does not make any difference in the process, but I've found it much more robust. YMMV).
Actually, just to make it a bit harder I did it by CCC'ing my previous Fusion Drive setup to a 4TB magnetic disk, upgrading the system to El Capitan on this disk, creating a new Fusion Drive on my SSD/HDD combo from within El Capitan and CCC'ing back already upgraded system to the FD. The actual upgrade was about 40 minutes, as the rest of the 11 hours process was cloning the disks back and forth.
Actually, just to make it a bit harder I did it by CCC'ing my previous Fusion Drive setup to a 4TB magnetic disk, upgrading the system to El Capitan on this disk, creating a new Fusion Drive on my SSD/HDD combo from within El Capitan and CCC'ing back already upgraded system to the FD. The actual upgrade was about 40 minutes, as the rest of the 11 hours process was cloning the disks back and forth.
Thanks to Deepwinter in the Yosemite forum I now have the latest version of Yosemite running great on my 1,1. I now have 16gb of ram. I now want to upgrade to El Capitan. What is the best/easiest method for doing so? I have access to a MacBook Pro running El Capitan. The Yosemite load was so easy. Basically plug and play. No coding to do or anything.
Start by reading Post #1390 for the mechanics of it. Do not know about the upgrade process, but the full install works great!
I generated El Capitan install media using the pike utility and installed El Capitan on a Mac Pro 1,1 (new SSD, single partition). The Mac Pro has 10GB RAM and 8800GT graphics card. The install completed successfully and after restarting I see a startup screen with Apple logo and shortly afterward, see this:
Any ideas / recommendations?
Thank you!
Any ideas / recommendations?
Thank you!
I had already done that. Same problem. I forgot to mention right after I see the screen above, the screen goes blank/black (power save mode?), like there is no video signal from the Mac. The Mac is powered--but I can only hold the power button to power off and try again.
Last edited:
Do you possibly have (access to) another ElCap compatible graphics card? Maybe try to swap and boot with another card again? I think it's worth a shot. I am not sure if 8800 cuts the minimum specs for ElCap.
How do you get 10gig of ram? You are not using 512m dimms are you? If so try booting without them.
Are you sure you selected the correct Destination disk/partition? It started complaining about not enough disk space and then file does not exist. Just a thought as I am no expert on this software, just read the log files.
Last edited:
ok it was the hdd.I have succesfull installed.The HDD was damaged
Ummm...I am. One memory riser is populated with 4 x 512MB modules.
Why would that be a problem? For testing, I pulled that riser and tried booting with 8GB (4 x 2GB). Now I get slightly different results when trying to boot. I see the Apple logo and progress bar, then the kernel panic/trap (same message as before). But now the system automatically restarts. I briefly see, "Your computer restarted because of a problem", then the Apple logo / progress bar, and back to the kernel panic, then automatic restart... (loop). Same deal when trying to boot to safe mode.
I saw mention (in this thread?) that the piker install method "likes" lots of memory--a suggestion of 12GB min!? The install process never hiccuped. The kernel panic appeared only after the post-install reboot.
Any other ideas/suggestions?
The issue with 512mb modules is well documented in this thread - there are various theories on what the root cause is but the bottom line is they cause a problem. As memory is pretty cheap it makes sense to increase the RAM to the minimum spec for this installation (12gb) tried and tested by many. I have 32gb and the install went fine. (8 x 4gb).
Some have had problems from incomplete downloads or damaged installers - so it may be worth redownloading the files to be sure you are not trying to install from a broken installer - it rules it out at least.
Some have had problems from incomplete downloads or damaged installers - so it may be worth redownloading the files to be sure you are not trying to install from a broken installer - it rules it out at least.
My 10.11.3 install keeps changing the Pike boot.efi back to the Apple one every time I reboot. How can I stop this and keep the Pike boot.efi?
Did you install CapitanPikeFix, or Boot64? If so, it is possible that the copy of boot.efi used by these tools to replace the system files has somehow been replaced with the Apple one.
Check the file sizes of the following files:
(CapitanPikeFix)
Code:
ls -lh /usr/standalone/i386/boot.efi.capitan.pike(Boot64)
Code:
ls -lh /Library/Application\ Support/Boot64/boot.efi.black
ls -lh /Library/Application\ Support/Boot64/boot.efi.greyIn all cases the result should show a file size of around 300K. If one of them shows a file size of around 600k then it is an Apple original version, in which case replace it with a Pike version.
----
Also if you use Boot64, it's possible to set the tool to use the Apple boot.efi. Did you do that? You can check by issuing the command
Code:
defaults read -g uk.co.rthpjm.Boot64.defaultBootTypeIt should return grey or black. If it returns apple, there is your problem. To fix it, issue one of the following commands
Code:
#grey
/Library/Application\ Support/Boot64/ensureBoot.sh -g
#
#or
#black
/Library/Application\ Support/Boot64/ensureBoot.sh -b----
If you don't have CapitanPikeFix or Boot64 installed, or if you do but the replacement file has the correct size, and you've checked the defined preference if using Boot64, then you have something weird going on. Have you tried your own version of update-protection?
I'm about to carry this out. I've got the Mac, got the RAM. I'm just waiting for the right graphics card. (Can I try with my current graphics card).
I going to use my iMac to install to my Mac Pro HDD via a usb sata caddy and replace the boot files. But does anyone use OSX Server with this? That is my final aim.
I going to use my iMac to install to my Mac Pro HDD via a usb sata caddy and replace the boot files. But does anyone use OSX Server with this? That is my final aim.
I had OS 10.11.2 already running on my Mac Pro 1,1. It was my 24/7 Server for Pley an iTunes and data share etc. But the energy costs over the year was almost too high, so i decided to buy a Sinology NAS for my Plex Server on my ATV 4 and as data server. For the iTunes Server is just right when the Mac Pro wakes up by calling. I don't use the iTunes Server very often.
For the new NAS i had to switch HD's and the Mac Pro should get a brand new clean installation. The last times it was very easy to install Yosemite and El Capitan. So i decided to put El Capitan on a new smaler HD, that i can use the bigger HD's for the NAS, means, i erase the HD with the running El Capitan Partition.
As it seams, meanwhile it isn't as easy as before to get El Capitan running on my System. After installation the Mac Pro boot up to the Status bar an stuck on it at 3/4.
I tried it via Pike USB recovery and to Install the System via my rMBP an change the boot.efi manually. But both way's i get stuck at the same point.
My last running El Capitan i updated from a the running Yosemite HD of my Mac Pro on a rMBP and change the boot.fi manually. This works juste fine, but this Time i can't get the System running.
So what should I do now? My Mac Pro has not 12Gb of RAM and i don't want to buy more RAM. for my case the 8GB are enough.
Should i install Yosemite an upgrade? Or have I to use only the old boot.efi?
But where can I get the old ones? I haven't stored them anywhere...
Thank's for help!
For the new NAS i had to switch HD's and the Mac Pro should get a brand new clean installation. The last times it was very easy to install Yosemite and El Capitan. So i decided to put El Capitan on a new smaler HD, that i can use the bigger HD's for the NAS, means, i erase the HD with the running El Capitan Partition.
As it seams, meanwhile it isn't as easy as before to get El Capitan running on my System. After installation the Mac Pro boot up to the Status bar an stuck on it at 3/4.
I tried it via Pike USB recovery and to Install the System via my rMBP an change the boot.efi manually. But both way's i get stuck at the same point.
My last running El Capitan i updated from a the running Yosemite HD of my Mac Pro on a rMBP and change the boot.fi manually. This works juste fine, but this Time i can't get the System running.
So what should I do now? My Mac Pro has not 12Gb of RAM and i don't want to buy more RAM. for my case the 8GB are enough.
Should i install Yosemite an upgrade? Or have I to use only the old boot.efi?
But where can I get the old ones? I haven't stored them anywhere...
Thank's for help!
You say you can see the progress bar? If so try to boot in verbose mode by holding CMD V after the chime. You should see the boot text. See if there is anything obvious at the point it stops....
I Think it should be the RAM which is under 12GB so i think i need the old boot.efi. (But can't find them anywhere, or don't know which one i should use for a Mac Pro 1,1 under 12GB of Ram)
I will start the Mac this afternoon in verbose mode an will see where it stops.