Awesome thanks for sharing this info. I'm tempted to upgrade before the end of the year
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
Awesome thanks for sharing this info. I'm tempted to upgrade before the end of the year
profinite said:
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.
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.
Last edited:
Cool, totally off topic yet in the spirit of upgrading...Question:
Do (you) anyone have significantly higher temperatures running dimms with "fin-less" heatsinks? (non-apple, non-ever-so-huge-black-audio-amp-grade-attached-w/el-cheapo-tape-ready-for-lift-off-houston)
Do (you) anyone have significantly higher temperatures running dimms with "fin-less" heatsinks? (non-apple, non-ever-so-huge-black-audio-amp-grade-attached-w/el-cheapo-tape-ready-for-lift-off-houston)
I have noticed it with internet dependent apps. My consp. theory is we are on the same bandwagon as windows in regards to "user privacy and security". I send my best regards to my cousins at the NSA anytime I log onto the web.
i did the same thing with ccc it worked but this what i got ? i don't see boot recovery.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Back up 999.9 GB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Untitled 499.8 GB disk1
Hello all. Just wiped a blank HD, installed El Cap on a USB stick and added the boot.efi's and cloned that to the HD.
Initially it did not recognise the system until I rebooted then I restarted again with the HD as the Start Up disk.
Wow, it works, lovely. Thank guys.
One question, I have a 10bit Eizo display but it's still displaying in 8 bit, anything I can do to help it recognise the 10 bit display?
Cheers in advance.
Initially it did not recognise the system until I rebooted then I restarted again with the HD as the Start Up disk.
Wow, it works, lovely. Thank guys.
One question, I have a 10bit Eizo display but it's still displaying in 8 bit, anything I can do to help it recognise the 10 bit display?
Cheers in advance.
Once you see your recovery HD on the list, you have to mount it. Say your identifier is disk0s3, then you need to type this in your terminal: diskutil mount disk0s3.
Once you're done, "eject" it to unmount, like any other drive.
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Back up 999.9 GB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Untitled 499.8 GB disk1
Did you use CCC? iirc CCC will ask if you want to build the Recovery HD or not when you clone an OS drive to another.
For those who need to create a Recovery partition:
http://musings.silvertooth.us/2014/07/recovery-partition-creator-3-8/
http://musings.silvertooth.us/2014/07/recovery-partition-creator-3-8/
On most portables, an El Capitan install will convert your hard drive or SSD into a core storage volume. A core storage volume is used for things like fusion drives and more importantly file vault encryption. When you have a core storage volume, holding the alt key will NOT give you boot options to select your main drive or recovery partition. Recovery is still there but not as a separate partition, you must hold the command-R key to access recovery.
It is possible to revert the core storage volume back to a normal volume if you haven't encrypted it yet.
Run these 2 commands in a terminal.
diskutil cs list
and then
diskutil coreStorage revert lvUUID
where lvUUID is the last lvUUID reported by the previous Terminal command.
Restart after you have run these commands in Terminal, and things should be back to normal..
thanks i went with a fool wipe, carbon copy cloner did not clone my recovery. thanks anyways.
The bless command sets volume bootability and startup disk options. In some circumstances these may be altered by volume manipulations and require resetting. It can make the difference in a volume being bootable or not.
With the introduction of El Capitan, Apple introduced an enhanced system security mechanism dubbed System Integrity Protection which effectively locked down certain system directories from unauthorized changes; not even the root account is allowed to make changes to the contents of those directories. Disabling SIP (which officially cannot be accomplished from a running system, ie. it must be done from the Recovery platform) affords the system security level of Yosemite. SIP is the reason that Pike R. Alpha had to develop an entirely new boot.efi for El Capitan, and why the PikeYosFix script that shielded users from system software update changes that reverted back to the original boot.efi, no longer works.