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

Discussion in 'OS X El Capitan (10.11)' started by Mr. Zarniwoop, Jun 8, 2015.

  1. Morpheo macrumors 65816

    Morpheo

    Joined:
    Feb 26, 2014
    Location:
    Paris/Montreal
    #1326
    Awesome thanks for sharing this info. I'm tempted to upgrade before the end of the year ;)
     
  2. OGNerd macrumors member

    OGNerd

    Joined:
    Jun 1, 2015
    #1327
    Great, it appears that I've found at least one Christmas present from me to me. :)
     
  3. PeterHolbrook macrumors 6502a

    Joined:
    Sep 23, 2009
  4. Jacko Lantern, Nov 22, 2015
    Last edited: Nov 22, 2015

    Jacko Lantern macrumors newbie

    Jacko Lantern

    Joined:
    Oct 31, 2015
    Location:
    USA
    #1329
    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.
     
  5. Jacko Lantern macrumors newbie

    Jacko Lantern

    Joined:
    Oct 31, 2015
    Location:
    USA
    #1330
    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)
     
  6. Jacko Lantern macrumors newbie

    Jacko Lantern

    Joined:
    Oct 31, 2015
    Location:
    USA
    #1331
    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.
     
  7. JOSECBA macrumors member

    JOSECBA

    Joined:
    Sep 1, 2015
    #1332
    Hello, did you fix it ?
     
  8. JOSECBA macrumors member

    JOSECBA

    Joined:
    Sep 1, 2015
    #1333
    Mines values...

    Screen Shot 2015-11-22 at 6.19.03 PM.png
     
  9. jamgold macrumors member

    jamgold

    Joined:
    Feb 27, 2014
  10. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1335
    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
     
  11. macrumoursnumpty macrumors newbie

    Joined:
    Nov 23, 2015
    Location:
    London
    #1336
    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.
     
  12. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1337
    Can anyone tell me why I don't see my recovery partition, when the command is enter? Any help would be appreciated.
     
  13. Morpheo macrumors 65816

    Morpheo

    Joined:
    Feb 26, 2014
    Location:
    Paris/Montreal
    #1338
    Which command?
     
  14. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1339
    The, diskutil list,
     
  15. Morpheo macrumors 65816

    Morpheo

    Joined:
    Feb 26, 2014
    Location:
    Paris/Montreal
    #1340
    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.
     
  16. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1341
    That's the problem I don't see it on the list .
     
  17. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1342

    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
     
  18. Morpheo macrumors 65816

    Morpheo

    Joined:
    Feb 26, 2014
    Location:
    Paris/Montreal
    #1343

    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.
     
  19. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1344
    ok I see , I think I miss that part. I'll do it again once I get home. Thanks.
     
  20. leoiv macrumors newbie

    leoiv

    Joined:
    Oct 13, 2015
    Location:
    Italy
  21. OGNerd macrumors member

    OGNerd

    Joined:
    Jun 1, 2015
    #1346
    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..
     
  22. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1347
  23. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1348
    thanks i went with a fool wipe, carbon copy cloner did not clone my recovery. thanks anyways.
     
  24. dcloud45 macrumors member

    dcloud45

    Joined:
    Oct 5, 2015
    #1349
    i have some questions.
    what is blessing the file , what does it do?what happens if i don't ?
    second -why do we need to disable SIP? what happens if i don't ?
     
  25. OGNerd macrumors member

    OGNerd

    Joined:
    Jun 1, 2015
    #1350
    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.
     

Share This Page