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

[Roland L]

Have a look at my post one page back, post #3139. The symptoms you describe are typical of there being a copy of El Capitan installer app already on your machine.

Thank you; was the first thing I tried. (And has worked repeatedly before.) However for some other reason it is not working now, even with all non-boot drives pulled and the Spotlight cache rebuilt on the boot volume.

It's going beyond the 'Download' button in the 'Purchased' tab, and taking me to a dialogue box inviting me to choose between download the installer or cancelling. The spinner starts after I elect to download.

When I go to the El Capitan page via an iTunes URL in Safari) again it's failing.

I had just installed last week's Security Update, so wonder whether that changed something?

 

[rthpjm]

Thank you; was the first thing I tried. (And has worked repeatedly before.) However for some other reason it is not working now, even with all non-boot drives pulled and the Spotlight cache rebuilt on the boot volume.

It's going beyond the 'Download' button in the 'Purchased' tab, and taking me to a dialogue box inviting me to choose between download the installer or cancelling. The spinner starts after I elect to download.

When I go to the El Capitan page via an iTunes URL in Safari) again it's failing.

I had just installed last week's Security Update, so wonder whether that changed something?

Maybe...

When you have disconnected everything, have you tried a Spotlight search for "Install"? Just to confirm that there isn't a copy lurking in a hidden corner (the Trash is a favourite hiding place)

If you have VMWare or Parallels on your machine, you could install a clean copy of Mac OS into a Virtual Machine, and try the download from there (I find it useful sometimes)...

 

[Roland L]

Maybe...

When you have disconnected everything, have you tried a Spotlight search for "Install"? Just to confirm that there isn't a copy lurking in a hidden corner (the Trash is a favourite hiding place)

If you have VMWare or Parallels on your machine, you could install a clean copy of Mac OS into a Virtual Machine, and try the download from there (I find it useful sometimes)...

Yes, quite sure there isn't a lurking copy. I'll try your other suggestion too.

Am concerned that either Apple have pulled the patched updates (as I think they have for Yosemite), or that they've changed the Machine ID check which Piker's amended boot.efi fixes.

 

[bootimous]

I appreciate your advice rthpjm..... Im an old pc guy getting into the mac pro world now.... I can use all the advice I can get!
Apple MacPro 1,1 2006 A1186 2x Intel Xeon Dual 2.66GHz 12GB RAM 2/1TB HD MA356LL/A
When you say "SPECIFIC" what else do I need to be aware of??

Thank you for your time!

 

[rthpjm]

I appreciate your advice rthpjm..... Im an old pc guy getting into the mac pro world now.... I can use all the advice I can get!
Apple MacPro 1,1 2006 A1186 2x Intel Xeon Dual 2.66GHz 12GB RAM 2/1TB HD MA356LL/A
When you say "SPECIFIC" what else do I need to be aware of??

Thank you for your time!

Just read, and then read some more.

Be aware, most stock PC graphics cards (but sometimes not the most recent releases) will work with MacOSX. There are two stages when booting a Mac, the boot sequence using the EFI firmware (analogous to a PC BIOS, indeed some modern PC motherboards are using EFI to boot now too), then MacOSX takes over. Stock PC graphics cards usually don't have an EFI section on their onboard firmware, this results in a blank screen during the initial boot phase. Once the OS takes over the drivers (kext in Mac terminology) are available and the display will turn on.

Original MacPros have a 32-bit version of EFI firmware (1,1 / 2,1), later MacPros have a 64-bit version of EFI. The EFI standard has an intermediate format called EFI Byte Code (EBC), this format is compatible with both 32-bit and 64-bit EFI platforms. For this reason, you will often need a card make and model for which the community has been able to adapt a 32-bit or EBC part for the firmware of the card. This part is added to the PC-style BIOS code on the card.

The addition of the EFI part gives the MacPro "boot screens". These are the early stages of display before the OS takes control.

 

[Sandleford]

Sorry I actually installed El Capitan but yeah there is no BT at all. I am checking the other threads. Also any solutions to the absence of airplay display mirroring options?

I had a thing where my card was crashing the system for some reason. I tried other cards and got the same thing. I lastly got the same card as you and still had the problem. I remembered at some point the bottom pcie slot stopped showing x16 lane width when it should have, so I picked up a logic board for 24$ and its all good now.

No that was the 4 core cpus, the logic board was closer to 40 but still cheap enough for me.

 

[Spleeny]

A minimum of 12GB seems to be required...

I just pikified my MP1.1 with 11

 

[basilt]

hi again ! I am back with feedback from 1st steps in installing ELCAP...

I got 14GB RAM on my 1.1 (2.1) mp, and downloaded pikify and macpostfactor. apps.

I am not sure if i have to run macpostfactor first and do something with it...

I have fresh OSX Lion, i copied OSX Installer in apps folder. GET info says ver 1.7.44

I put a 8gb USB in, run the terminal commands script etc. and i got stuck at 'copying files....' message
in terminal.... After 15minutes the pikify DONE msg did not appear, so i ejected the usb, reformated and
decided to add a 16GB insted in usb port, partitioned GUID etc.

I run terminal again, and the script said 'It looks a copy of OSX installer .... already pikified'
Then asked if i wanted to 1. RESET the installer back to Apple or 2. Continue using pikifed ver.

As i interrupted the terminal process, I decided to go for 1.

After some minutes i saw the DONE pikifying, so i guess i am back to start from beginning !
What has happened, i got confused !!

Shall i run the pikify script from the beginning now and see if i get stuck again or finally see
the Done Pikify message and continue with install ?

The steps i performed are exactly as seen in video.

A solution is appreciated

 

[rthpjm]

hi again ! I am back with feedback from 1st steps in installing ELCAP...

I got 14GB RAM on my 1.1 (2.1) mp, and downloaded pikify and macpostfactor. apps.

I am not sure if i have to run macpostfactor first and do something with it...

I have fresh OSX Lion, i copied OSX Installer in apps folder. GET info says ver 1.7.44

I put a 8gb USB in, run the terminal commands script etc. and i got stuck at 'copying files....' message
in terminal.... After 15minutes the pikify DONE msg did not appear, so i ejected the usb, reformated and
decided to add a 16GB insted in usb port, partitioned GUID etc.

I run terminal again, and the script said 'It looks a copy of OSX installer .... already pikified'
Then asked if i wanted to 1. RESET the installer back to Apple or 2. Continue using pikifed ver.

As i interrupted the terminal process, I decided to go for 1.

After some minutes i saw the DONE pikifying, so i guess i am back to start from beginning !
What has happened, i got confused !!

Shall i run the pikify script from the beginning now and see if i get stuck again or finally see
the Done Pikify message and continue with install ?

The steps i performed are exactly as seen in video.

A solution is appreciated

You don't need macpostfactor, that is a different tool (which I believe is aimed at unsupported MacBooks. I believe it contains extra items required to get the laptops working, which the MacPros do not need. Indeed it may cause issues on a MacPro).

The createpikeinstallmedia script modifies the "Install Mac OS X El Capitan" app located in the Applications folder. Before modifying the app it saves the original data. This allows it to present the option to "reset" or "continue".

You did the right thing. Now that you have reset, you can run the script again.
Be patient. Wait for the Done Pikifying message.
The copying of 7Gb over USB2 takes some time.

If you are still encountering issues, copy and paste the transcript here and I'll be able to give you more help...
[doublepost=1485683115][/doublepost]

I just pikified my MP1.1 with 11 View attachment 686020

Hello Spleeny,

Here is a gentle warning: MacPros 1,1 and 2,1 running Yosemite or El Capitan with 512Mb memory sticks are well documented to be unstable. They often crash with kernel panics (kp).

We have had reports of some users achieving a successful install with 10Gb, but it is variable. I advise 12GB because we encourage the use of 2GB sticks. They must be pairs, so a pair of 2Gb = 4Gb

• 4Gb not enough, installer fails
• 8Gb not enough, installer fails
• 12Gb has never been reported as a problem, installer always works

We always advise users to remove the 512mb sticks entirely. In your case you have two 4Gb sticks already, you can simply remove the 512s, your system will happily run on 8gb (it's only the install method that needs approx 12Gb RAM).

My experience is that Yosemite and El Capitan run better with more RAM, if you can afford to buy some more 2GB or higher capacity memory sticks I would encourage you to do so.

 

[basilt]

If you are still encountering issues, copy and paste the transcript here and I'll be able to give you more help...

I am back again....
I run the script, and same screen came up with 1, 2 choices.
I chose C (continue) and after a while i saw the DONE pikify.
I ejected mini usb flash drive (16gb) and removed - plugged back in
then reboot and ALT key, chose the install osx.

My screen started showing some kind of flickering with various dashed pixeled lines on monitor,
i waited and i saw a loading bar, after that screen went gray, and after 30 min, is still gray.

Am i doing anything wrong, or do i have to wait longer ?
---Edit---
I restarted and thank god the usb boots ok, i tried a test install upto a point and seems it works.

QUESTIONS
1. Shall i partition my 250gb hdd in 2 parts and install ELCAP in 1, and what size you recomend.
2. Will it make a recovery partition on same hdd -can i delete it later on
3. After install what updates can i do to ElCap and how.
4. After install how can i change the bootscreen to i.e. black ?

cheers
[/QUOTE]

 

[rthpjm]

I am back again....
I run the script, and same screen came up with 1, 2 choices.
I chose C (continue) and after a while i saw the DONE pikify.
I ejected mini usb flash drive (16gb) and removed - plugged back in
then reboot and ALT key, chose the install osx.

My screen started showing some kind of flickering with various dashed pixeled lines on monitor,
i waited and i saw a loading bar, after that screen went gray, and after 30 min, is still gray.

Am i doing anything wrong, or do i have to wait longer ?
---Edit---
I restarted and thank god the usb boots ok, i tried a test install upto a point and seems it works.

QUESTIONS
1. Shall i partition my 250gb hdd in 2 parts and install ELCAP in 1, and what size you recomend.
2. Will it make a recovery partition on same hdd -can i delete it later on
3. After install what updates can i do to ElCap and how.
4. After install how can i change the bootscreen to i.e. black ?

cheers

[/QUOTE]
Hello basilt

What graphics card is installed in your MacPro?

 

[basilt]

Hello basilt

What graphics card is installed in your MacPro?[/QUOTE]
hello,

I have a Gigabyte AMD Radeon HD 7970 3GB (GV-R797OC-3GD) rev 2.1, pcie, EAN 0818313014306.
has 3 fans, on highest speed pcie slot. flashed ok by a friend here in macRumors.

maybe it does this as it might not have Lion drivers. Generally when i also drag your video window looks like
its flickering or the frame rate is low ? But not as bad as i meantioned in past post.

Shall i partition the hdd or not, what would you recommend

 

[rthpjm]

QUESTIONS
1. Shall i partition my 250gb hdd in 2 parts and install ELCAP in 1, and what size you recomend.
2. Will it make a recovery partition on same hdd -can i delete it later on
3. After install what updates can i do to ElCap and how.
4. After install how can i change the bootscreen to i.e. black ?

Hello basilt,

1. There is no need to partition. It is entirely your choice, if you want to partition, go ahead...
2. Yes. The Recovery HD is automatically created. It is not wise to delete it. The Recovery HD is useful, it does not take much space. Better to keep it.
3. If you downloaded your copy of Install OS X El Capitan app from the Mac App Store recently, then it will already be 10.11.6. Apple is now developing 10.12.x Sierra, so it's unlikely that El Capitan will receive much in the way of updates, and these are likely to be just Security Updates. As a general rule of thumb, Security Updates do not overwrite the boot.efi files. If you want some extra peace of mind, then go back to page 56, read post #1391. There are two utilities CapitanPikeFix, or my own Boot64, install one of them.
4. If you use my Boot64, it ships with both grey and black variant of the boot.efi file. You can run the included script to set the background colour for the next and subsequent boots. Read on from post #1391, I wrote a post with the commands in it....

 

[lestate66]

hi there!
First time I ever register on a forum.
I would like to know if the method you showed us to install successfully EL CAPITAN,works on a white macbook early 2008?
Thanks, hope I didn't miss something with the forum protocol!

 

[basilt]

hi rthpjm,

It worked ! thanks to your help, guides and software ! Also all other mR users who helped me.
I see i have 10.11.4 so i guess iam ok insofar. But... what about sierra,
do you thing i should run your Boot64 to be able to update in future or shall i leave it now
and wait to see if sierra is more stable and secure. I heard ElCap is the most secure version of osx insofar.

Next Q's:
1.Shall i uncheck the autoupdater anyway, even when i run your boot64 ?
2.Shall i delete the osx installer from my Lion now, or leave it there ? I will go back to 12gb ram now from 14.
3. I thought to install ElCap on the hdd that contains Lion, is this possible as the installer
lies in Lion's app folde? Any tips etc here ?
4. what firewall settings i put here ? auto, stealth, block all, or install little snitch and finish without fwall.

Going to see your terminal to switch off the animations... really crap feature in osx i think.

 

[rthpjm]

hi there!
First time I ever register on a forum.
I would like to know if the method you showed us to install successfully EL CAPITAN,works on a white macbook early 2008?
Thanks, hope I didn't miss something with the forum protocol!

This thread is intended for MacPro users. There is another thread for unsupported MacBooks/MacBook Pros. The laptops have extra hurdles due to the built-in graphics chipsets, and other non-removable/non-upgradable elements, USB and wifi appear to have caused trouble.

Look for this thread


[doublepost=1485894096][/doublepost]

hi rthpjm,

It worked ! thanks to your help, guides and software ! Also all other mR users who helped me.
I see i have 10.11.4 so i guess iam ok insofar. But... what about sierra,
do you thing i should run your Boot64 to be able to update in future or shall i leave it now
and wait to see if sierra is more stable and secure. I heard ElCap is the most secure version of osx insofar.

Next Q's:
1.Shall i uncheck the autoupdater anyway, even when i run your boot64 ?
2.Shall i delete the osx installer from my Lion now, or leave it there ? I will go back to 12gb ram now from 14.
3. I thought to install ElCap on the hdd that contains Lion, is this possible as the installer
lies in Lion's app folde? Any tips etc here ?
4. what firewall settings i put here ? auto, stealth, block all, or install little snitch and finish without fwall.

Going to see your terminal to switch off the animations... really crap feature in osx i think.

Hello basilt,

Thank you.

With regards to Sierra, I am sorry to disappoint you, but it looks like we will not be able to get Sierra running on the original MacPros. El Capitan appears to be as far as we go.

This is because software components of MacOS Sierra appear to require CPU features that simply are not available to original MacPro owners. It's a physical issue now.

Never-say-never, but at this time it is probably too difficult! It would require a lot of software remodelling within the EFI to emulate the missing CPU features. Even if that were possible, it would probably take a long time to debug and perfect, and will probably impact performance negatively.

If you want to go to Sierra, then you will need to consider buying a MacPro 5,1 or higher (I believe you can purchase a 4,1 and upgrade it to behave as a 5,1 -similar to the 1,1 to 2,1 upgrade path).

Personally, I've had 10+ years of excellent work out of my 1,1 original MacPro. It was one of the best purchases I ever made. The fact that it's still running well is astonishing. I'm likely to buy myself a new MacPro soon, but I'm holding out for the next upgrade. I'm a little reticent to pay good money for the current MacPro, with its 3 year old technology base. I was disappointed that Apple didn't bring out a revised MacPro in 2016.

 

[basilt]

Thanks again !

In my current condition i will keep elcap, as my only problem was web access actually ando some s/w updates like FCP etc. Tiger remains my favorite gui though, plain without too much anim...

What should i do to install ElCap on the second hdd containing my Lion ? Copy the installer from Lion to new hdd with ElCap and run pikify again ? Got stuck here.

By the way, there is no recovery partition made by installer i think, (no hdd letter visible) unless is hidden.

thanks again

 

[rthpjm]

Thanks again !

In my current condition i will keep elcap, as my only problem was web access actually ando some s/w updates like FCP etc. Tiger remains my favorite gui though, plain without too much anim...

What should i do to install ElCap on the second hdd containing my Lion ? Copy the installer from Lion to new hdd with ElCap and run pikify again ? Got stuck here.

By the way, there is no recovery partition made by installer i think, (no hdd letter visible) unless is hidden.

thanks again

Your Lion partition, again it's your choice. Some users keep a second OS partition for those "just-in-case-something-goes-wrong" situations. It is often handy to have a second bootable partition which you can use to fix whatever went wrong.

Which brings me to the Recovery HD. The Recovery HD is hidden from the running OS. You typically access the Recovery HD in those situations where "Whoops, something went wrong". You will reboot your MacPro and hold down the ALT key immediately after the start up chime. You can select the Recovery HD from the startup chooser. (You can also reboot and hold down the Apple-R keys immediately after the chime, see https://support.apple.com/en-gb/HT201314 ).

For me personally, this means I don't keep a Lion Partition at all. I just use El Capitan and the Recovery HD.

I don't understand why you want to copy the "Install OS X El Capitan" app to the El Capitan partition. It has done it's job... (you built an installer with it using the createpikeinstallmedia script, which "slipstreams" the modifications into the installer to make it compatible with original MacPros).

If your intention is to retain access to the Install OS X El Capitan app, here is what I would do:

1. Boot into your El Capitan partition
2. Open the Mac App Store app
3. navigate to the Purchased tab
4. (Enter your login/password if required)
5. Check the purchased list for the OS X El Capitan app installer - this obviously is the Apple unmodified version
6. Nothing else to do, stop because you can always re-download the Apple OS X El Capitan installer

If you can't locate the installer in the App Store

1. Boot into your Lion partition
2. Open a terminal, navigate to where the Pikify files are
3. Run the createpikeinstallmedia script again
4. Choose to reset
5. This will return the on-disk copy back to the unmodified Apple version
6. Use the Finder to drag and drop a copy of the Applications > Install OS X El Capitan app from your Lion partition to your El Capitan partition
7. Done

So now you have retained access to the Install OS X El Capitan app (just in case).

Now you can decide if you want to keep the Lion partition or not. Your choice...

 

[lestate66]

Thank you for the reply and the link.
I'm gonna look into it.

 

[macprobuffalo]

Hello,

I've been running el captain on my 1,1 for over a year and recently put a fusion drive in the optical bay (it works great btw), I wanted to update to the latest version of Pikify to fully support DIY fusion drives. I simply ran the installer package while booted into el captain. Everything seems fine- is that all I needed to do to update the Pikify patch?

Thanks

 

[rthpjm]

Hello,

I've been running el captain on my 1,1 for over a year and recently put a fusion drive in the optical bay (it works great btw), I wanted to update to the latest version of Pikify to fully support DIY fusion drives. I simply ran the installer package while booted into el captain. Everything seems fine- is that all I needed to do to update the Pikify patch?

Thanks

There seems to be some confusion here.
Pikify is a one-shot script to build an installer with added bits to support original MacPros (also called slipstreaming in the PC world).
Once you have built the installer, and then run it, you have Mac OS X El Capitan up and running, pikify has no effect from here on.

The 'support for fusion drives' refers to the pikify scripts understanding a fusion drive layout (and how apple puts them together). It is referring to the ability of the pikify script to locate the intended Mac OS disk/partitions, and where and how to label the Recovery HD partition. It is not intended as a reference to any Mac OS X El Capitan support of fusion drives - that's Apple's job

In short - no need to worry or do anything with pikify if you are already running El Capitan successfully.

 

[basilt]

I don't understand why you want to copy the "Install OS X El Capitan" app to the El Capitan partition. It has done it's job... (you built an installer with it using the createpikeinstallmedia script, which "slipstreams" the modifications into the installer to make it compatible with original MacPros).

The reason i want to keep the installer for elcap, is to allow me to re-install it on another internal hdd, without having to rely on osx lion. In other words, to use it as an apple installer that needs not to be pikified again to allow it to install.

I copied the installer in my elcap apps folder now, after pikify reset. Will i be able to run it again to install on another hdd, this way, or i can do this by booting to recovery OSX elcap partition and install on another hdd from its menus please ?

By the way, do you remember which post/ page has the commands to turn off animation windows etc in elcap please ? I still have not found that...

 

[Roland L]

Yes, quite sure there isn't a lurking copy. I'll try your other suggestion too.

Am concerned that either Apple have pulled the patched updates (as I think they have for Yosemite), or that they've changed the Machine ID check which Piker's amended boot.efi fixes.

Thanks again to rthpjm, who has confirmed in a VM the fully patched 10.11.6 does indeed remain on the MAS. I have seen this today on another Mac today too, and have been able to obtain a fresh copy.

Unfortunately I don't have an explanation for why the file could not be downloaded even with the 'Download' button visible. 100% sure there wasn't an errant copy of the installer lurking.

 

[rthpjm]

The reason i want to keep the installer for elcap, is to allow me to re-install it on another internal hdd, without having to rely on osx lion. In other words, to use it as an apple installer that needs not to be pikified again to allow it to install.

I copied the installer in my elcap apps folder now, after pikify reset. Will i be able to run it again to install on another hdd, this way, or i can do this by booting to recovery OSX elcap partition and install on another hdd from its menus please ?

By the way, do you remember which post/ page has the commands to turn off animation windows etc in elcap please ? I still have not found that...

Hello basilt,

In my experience, you cannot simply run the unmodified Apple copy of "Install OS X El Capitan" on an original MacPro (1,1 or 2,1). If you run this, the installer checks usually prevent installation. Pike did modify the EFI files to report the board-id of a MacPro 3,1 if it thinks you are running the installer, therefore El Capitan running the unmodified installer "might" work (I've never tried it). However, you will then need to manually fix the boot.efi files on the new installation.

Also, you cannot run the modified (pikified) copy of "Install OS X El Capitan" that the createpikeinstallmedia script leaves in /Applications. If you run this, the installer checks spot the modifications (the digital signature is broken due to the modifications).

If you ever want to install "again" on an original MacPro, for example to install El Capitan on a second drive/partition, then you have to use the same technique that you used for your original El Capitan install (or the other method). There are two main methods:

1. Connect your drive to a "supported" Mac, use that Mac to install El Capitan onto your drive, manually fix the two boot.efi files, (optionally manually fix the Recovery HD), disconnect/refit the drive to your original MacPro. Boot. (See page 1, post 1). The most common method of "connecting your drive" is to place your MacPro into Target Disk mode and use a FireWire cable to connect to the supported Mac. The other common method is to remove the HDD from the MacPro, connect it to the other Mac either directly (if it will fit), or using an external caddy (e.g. SATA-to-USB)
2. Use a pre-patched installer. For El Capitan, my pikify tool set is the most common (see page 56, post 1390).

If you want to re-use a pikified USB memory stick (after the first successful usage), then you will need to re-bless the USB partition. (Search this thread for "bless", look for posts from me numbered higher than 1390).

If you think you will be doing this frequently, you might want to consider using a small HDD partition in place of the USB memory stick. You will still need to re-bless the pikified installer partition after each successful use.
(I use the HDD partition approach because I regularly test the pikify script. Although V12 is very stable and most users have success when using it )

I have no idea what you are talking about for the "animations". Google....

 

[hwojtek]

I have no idea what you are talking about for the "animations". Google....

Enter the following commands in Terminal. Most of the will work after logging out and in again.

# opening and closing windows and popovers
defaults write -g NSAutomaticWindowAnimationsEnabled -bool false

# smooth scrolling
defaults write -g NSScrollAnimationEnabled -bool false

# showing and hiding sheets, resizing preference windows, zooming windows
# float 0 doesn't work
defaults write -g NSWindowResizeTime -float 0.001

# opening and closing Quick Look windows
defaults write -g QLPanelAnimationDuration -float 0

# rubberband scrolling (doesn't affect web views)
defaults write -g NSScrollViewRubberbanding -bool false

# resizing windows before and after showing the version browser
# also disabled by NSWindowResizeTime -float 0.001
defaults write -g NSDocumentRevisionsWindowTransformAnimation -bool false

# showing a toolbar or menu bar in full screen
defaults write -g NSToolbarFullScreenAnimationDuration -float 0

# scrolling column views
defaults write -g NSBrowserColumnAnimationSpeedMultiplier -float 0

# showing the Dock
defaults write com.apple.dock autohide-time-modifier -float 0
defaults write com.apple.dock autohide-delay -float 0

# showing and hiding Mission Control, command+numbers
defaults write com.apple.dock expose-animation-duration -float 0

# showing and hiding Launchpad
defaults write com.apple.dock springboard-show-duration -float 0
defaults write com.apple.dock springboard-hide-duration -float 0

# changing pages in Launchpad
defaults write com.apple.dock springboard-page-duration -float 0

# at least AnimateInfoPanes
defaults write com.apple.finder DisableAllAnimations -bool true

# sending messages and opening windows for replies
defaults write com.apple.Mail DisableSendAnimations -bool true
defaults write com.apple.Mail DisableReplyAnimations -bool true