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

Sevenfeet · Jul 18, 2018

rthpjm said:
If your recovery HD partition is working okay, simply reboot, wait until your hear the chime, then hold down Apple-R that should get you to the Recovery partition without the need for EFI visuals....

I don't think I have a working recovery partition. This machine was created beginning from a Lion partition which this machine still has as a fall back. If you try booting to "Commend-R", the machine will still boot to the drive that is selected in the Startup system preference, which in this case is the El Cap partition.

andrew nz · Jul 19, 2018

rthpjm said:
Hello everyone,

So I'm back home from working away, and I've tested with a spare partition. I installed a fresh copy of 10.11.6. Updated everything except Security Update 2018-001. To make sure I was as close to a typical starting point as possible I downloaded Security Update 2017-005 from the Apple > Support > Downloads web site pages, and applied that.

<edit>

Last disclaimer - this really is a hack. The kernel is now out of step with the kexts and possibly other Apps. We really are on the ragged edge now. I don't believe we NEED Security Update 2018-001, however, this approach gives us all of the rest of the update, just reverting the kernel. If you are at all concerned, don't perform the update, hide it in the App Store....

[doublepost=1531985679][/doublepost]hello

is the latest pikify app 1.9 the solution to the 2018.01 sec update?

rthpjm · Jul 19, 2018

andrew nz said:
[doublepost=1531985679][/doublepost]hello

is the latest pikify app 1.9 the solution to the 2018.01 sec update?

Nope.

I’ve done nothing to automate any of the kernel replacement. I think I was the first person to confirm replacing the kernel is possible, and supplied the steps. What I did here was motivated by the desire to help those people who bricked their machines to get them back without the anxiety of performing an OSX re-install.

For me personally, I prefer to stay with El Capitan 10.11.6 with Security Update 2017-005. It is the last Apple tested combination. For me, it’s too much of a risk to blindly install the 2018-00x updates. The 001 version introduced the incompatible kernel in the first case. Apple will not (and should not) consider backwards compatibility for our MacPro 1,1s or 2,1s.

What will happen when Apple releases a Security Update that introduces one or more incompatible kernel extensions and/or incompatible applications? Somebody (who will not be me!) will need to diagnose which are the incompatible files and then test if a downgrade will make the machine stable again. At this point you get into 1-n branching effects. Let’s say a kext becomes incompatible, if it is downgraded it might restore some functionality, but if there are other apps or libraries that were expecting certain responses, then these might become unstable after the downgrade. Ultimately, at some point in the future, the branching effect might mean that nearly 100% of the most recent updates would need to be rolled back...

Some people might argue that we’ve been modifying our Mac Pros for years without issue. Actually, all we’ve been doing is modifying the Pre-OS environment (boot.efi). The Mac OS X operating system has been untouched (kernel, kernel extensions, apps, and supporting files), until Security Update 2018-001.

Now, I can admire the courage of other users who carry on by downgrading the kernel and report back “works great for me”. I’m personally not going to do that, I’m more than happy to stay put at 10.11.6 + 2017-005 + supported app updates. Therefore, I’m disinclined to add downgrading the kernel to my toolsets.

Others have “filled the gap”... Contributor @alphascorp has posted an automation tool a few post back from here. For those wishing to go down this route, I wish you all the luck in the world. It’s simply not my choice.

My MacPro will be replaced in a years time (when Apple release the next machine). I’ll keep my cMP around, I’m going to turn it into a virtual machine host. I run lots of copies of Linux both professionally and as a hobby. The cMP will excel as a Proxmox VM host.

jbarley · Jul 19, 2018

rthpjm...
appreciate all your hard work
...

Luhunga · Jul 19, 2018

Hello Larsvonhier, I´ve read your reply to the security update 2018-004 and have done all the steps you suggested, even the ´touch /System/Library/Extensions' command as suggested by kaosnews but still no luck. Did I miss something or are there other ways to get the update working. Thanks in advance for your help!!!

Larsvonhier said:
Just a quick note to report that up to now, all El. Cap Security Updates can be installed on Mac Pro 1,1 and 2,1.
Currently Apple seeds out the (beta) of 2018-004 - what a great support period for such a dated OS!
The only thing to remember is to make a copy of the kernel file in /System/Library/Kernels/ and have a working bootable clone on a second drive before updating! Have a graphics card at hand that's capable of showing boot screen.

Procedure:
Let the security update install, reboot if needed, let the installer finish and see if you can boot. Normally, the updated kernel will panic and you get a reboot loop.
Boot from the clone drive now and copy back the old kernel file (see above for location) to the sec. updated volume. Use a tool like batchmod to set the kernel file attributes back to root, wheel.
Not sure if needed in all cases, but I do the next step in addition every time to make sure system is "clean": Run macOS disk utility and repair the boot volume that the sec. update is on. (This will also update "boot support drives", and imho this might copy the correct kernel onto them also).
Edit: kaosnews tried this also, and still entered the boot-loop, but fixed it by issueing 'touch /System/Library/Extensions' via terminal on the El Capitan partion. You might need to do this with the sudo prefix for correct permissions.

The system can now be booted again from the updated volume.

Nota bene: The security updates contain app updates, sometimes extension updates and changes to various frameworks in addition to the modified kernels. It´s doubtful that fixes for spectre, meltdown and other processor architecture related bugs will have full effect with the previous kernel, but the updated other components can at least be used.
We have two Mac Pro 2,1 running as servers 24/7 in my office and have not seen any stability issues so far (and I did all sec. updates that Apple released consecutively). After updating, I saw one additional reboot that I tend to attribute to the network filter "little snitch".
Currently, system build is now 15G22008 (2018-004 beta 3 as mentioned above) on both machines.
Additional note: In the meantime, dev beta 4 (15G22010) came out and after a week, Apple finalized it for public use under the same build number and it still works as described here.

Perhaps someone with deeper insight can provide info on what exactly the updates contain? (Apple´s info is not too detailed, as usual).

Larsvonhier · Jul 20, 2018

Luhunga said:
Hello Larsvonhier, I´ve read your reply to the security update 2018-004 and have done all the steps you suggested, even the ´touch /System/Library/Extensions' command as suggested by kaosnews but still no luck. Did I miss something or are there other ways to get the update working. Thanks in advance for your help!!!

Could you take a screenshot in verbose mode (with your Phone i.e.) to show where you´re stuck?
If touch does not work, try some kext tool (kext wizard i.e.) to set the flags right to root/wheel. BatchMod is another great tool for this.

Luhunga · Jul 20, 2018

Larsvonhier said:
Could you take a screenshot in verbose mode (with your Phone i.e.) to show where you´re stuck?
If touch does not work, try some kext tool (kext wizard i.e.) to set the flags right to root/wheel. BatchMod is another great tool for this.

...that´s as far as it gets, then the loop starts.

Batch68 · Jul 20, 2018

Any ideas where I may have gone wrong? I've uploaded a screenshot.

Hello out there...

I'm in the throws of selling my upgraded Mac Pro 1,1 which has been running El Capitan 10.11.6 without a glitch since Jan 2017, and I'm trying to install EC again on another SSD currently running Snow Leopard.

I'm using the same Install OS X El Capitan, copied to Snow Leopard Apps folder, + Pikefy v3.1. In terminal, everything is fine up to the point of dropping the installer, when I get the line: '...it is not a directory' and I can't get any further. Not sure if this may be a SIP issue?

rthpjm said:
==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

rthpjm said:
Even Newer:
The Pikify App.

Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

10.6 Snow Leopard

10.7 Lion

10.11 El Capitan

If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:

Reboot and hold the ALT key down, select the Pike Installer

Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

Code:

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD [your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

Larsvonhier · Jul 20, 2018

Luhunga said:
...that´s as far as it gets, then the loop starts.

That´s not what happens when file attributes or kernel cache is not set/rebuilt right. Must be something else. Do you see the line "updating boot support partitions" when you run the macOS disk util. on your boot drive (as destination)?
If nothing helps, I´d suggest to do a clean install on some (external?) drive and update & recopy kernel as described.
Never seen this sequence of events like on your screen capture following the security update (until 2018-004)!

Batch68 · Jul 20, 2018

rthpjm said:
Even Newer:
The Pikify App.

Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

10.6 Snow Leopard

10.7 Lion

10.11 El Capitan

If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:

Reboot and hold the ALT key down, select the Pike Installer

Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

Code:

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD [your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

I have spotted my error when in terminal, still a bit noob on that.

I've been able to complete the first stage, up to restart. But on reboot i just get the apple, and then the computer goes into repeated reboots. I tried alt key and booting into OS but the same thing happens.

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

rthpjm said:
Even Newer:
The Pikify App.

Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

10.6 Snow Leopard

10.7 Lion

10.11 El Capitan

If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:

Reboot and hold the ALT key down, select the Pike Installer

Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

Code:

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD [your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

I have spotted my error when in terminal, still a bit noob on that.

I've been able to complete the first stage, up to restart. But on reboot i just get the apple, and then the computer goes into repeated reboots. I tried alt key and booting into OS but the same thing happens.

Luhunga · Jul 20, 2018

Larsvonhier said:
Could you take a screenshot in verbose mode (with your Phone i.e.) to show where you´re stuck?
If touch does not work, try some kext tool (kext wizard i.e.) to set the flags right to root/wheel. BatchMod is another great tool for this.

...ok, all is fine now. I´ve used the kernel you´ve uploaded and also the command line from inspector42 - touch /Volumes/YourNormalBootDrive/System/Library/Extensions. Works like a charm. Many Thanks!!!

Batch68 · Jul 20, 2018

rthpjm said:
Even Newer:
The Pikify App.

Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

10.6 Snow Leopard

10.7 Lion

10.11 El Capitan

If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:

Reboot and hold the ALT key down, select the Pike Installer

Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

Code:

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD [your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

rthpjm · Jul 20, 2018

jbarley said:
Boy! are you out-of date..
sorry couldn't resist...

fixed it

EpilepticGerbil · Jul 20, 2018

rthpjm said:
fixed it

umm, any tips?

I've just made a backup of my El Cap install and now ready to throw caution to the wind. Couldn't get Pacifist to install the new kernel, all it wanted to know was where my OS X was. Does SIP have to be disabled? Think I really need the "How to Update EL Capitan with New Kernel and System Update 2018-004" manual. Trying to find particulars in this 3 year old (and counting) thread is challenging enough.

jbarley · Jul 20, 2018

rthpjm said:
fixed it

ditto!

aristocat · Jul 21, 2018

Hi All, I just got my hands on 2 2006xserves and a xserve raid and trying to get them to work.

I've installed lion in one of them.

Hardware for the 2006 xserves have been upgraded to dual 3.0 with 32GB of Ram. Graphics card have been changed to the GT120 pulled from another Mac Pro.

I also swop the dvd rom out from one of them and replaced it with a 1tb hdd.

I downloaded the pikify app and also the El Capitan from the App Store.

I run the pikify app and the preparation was a breeze. (Big Thank You)

I rebooted the 2006 xserve however was only greeted with an apple logo on a white screen with a scrollbar that does not move. (for the past 10 hours)

Thereafter I put the 2006 xserve into target disk mode booting through my Mac mini 2010, the scrollbar moves but until the end still no El Capitan.

I rebooted the 2006 xserve and there is was again the apple logo white screen and the non moving progress bar.

Any ideas where I have gone wrong?

Batch68 · Jul 21, 2018

rthpjm said:
Even Newer:
The Pikify App.

Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

10.6 Snow Leopard

10.7 Lion

10.11 El Capitan

If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:

Reboot and hold the ALT key down, select the Pike Installer

Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

Code:

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD [your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...

++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

aristocat · Jul 21, 2018

Well, I managed to get it up and running but stuck at osx El Capitan is already installed on this computer......

I'm sorry if I seem kind of noob because I am.

Thanks in advance if anyone could help to overcome this.

Batch68 · Jul 21, 2018

I'm getting a boot loop on my MacPro 1,1 when installing Pikey's V14 El Capitan on second HD running Snow Leopard.

I've been running EC 10.11.6 for some time now on my main drive without any glitches, installed from USB stick, but I'm selling the computer so need a clean install so I can reuse the main drive on another computer.

Initially I tried installing from the original USB stick but it stalled after progress bar completed. I ran it a couple of times for over two days each time...

I've used the 'Install OS X El Capitan' from first install, copied into new HD, but after following the video instructions, which is excellent, I get as far as the final installation stage but the apple appears with no progress bar, and the computer goes into reboot cycle. I've run Alt and booted into OS - same result.

Any thoughts on where I might be going wrong would be welcomed?

rthpjm · Jul 21, 2018

aristocat said:
Well, I managed to get it up and running but stuck at osx El Capitan is already installed on this computer......

I'm sorry if I seem kind of noob because I am.

Thanks in advance if anyone could help to overcome this.

Try a PRAM reset.
Reboot again
After you hear the chime hold Apple and R. It should enter the Recovery HD. Choose the disk to boot (Startup Disk) from the Apple menu
[doublepost=1532201585][/doublepost]

Batch68 said:
I'm getting a boot loop on my MacPro 1,1 when installing Pikey's V14 El Capitan on second HD running Snow Leopard.

I've been running EC 10.11.6 for some time now on my main drive without any glitches, installed from USB stick, but I'm selling the computer so need a clean install so I can reuse the main drive on another computer.

Initially I tried installing from the original USB stick but it stalled after progress bar completed. I ran it a couple of times for over two days each time...

I've used the 'Install OS X El Capitan' from first install, copied into new HD, but after following the video instructions, which is excellent, I get as far as the final installation stage but the apple appears with no progress bar, and the computer goes into reboot cycle. I've run Alt and booted into OS - same result.

Any thoughts on where I might be going wrong would be welcomed?

How much RAM do you have?
How many RAM modules?
What size is each module?

Batch68 · Jul 21, 2018

rthpjm said:
Try a PRAM reset.
Reboot again
After you hear the chime hold Apple and R. It should enter the Recovery HD. Choose the disk to boot (Startup Disk) from the Apple menu
[doublepost=1532201585][/doublepost]
How much RAM do you have?
How many RAM modules?
What size is each module?

28 GB, 8 modules, 6x4GB & 2x2GB.

Akshunhiro · Jul 21, 2018

Thanks so much rthpjm! I picked up a 2006 Mac Pro 2 days ago and already have it running El Capitan. I couldn't find a vanilla install so used a GM release but couldn't boot after updating to 10.11.1 so switched back to Lion and replaced the boot.efi and then installed Boot64

Currently doing a backup with carbon copy cloner and will try 10.11.6
It's a 1,1 with flashed EFI and SMC, only 11GB of RAM (have ordered a 32GB kit) still rocking original 7300GT so GPU upgrade is next! Will probably get a pair of 5365's as well.
[doublepost=1532224533][/doublepost]Update to 10.11.6 completed no problem. Security update 2018-004 now hidden (may attempt after another backup).
Any recommendations for budget cards? Was looking at 5770/5870. Metal is not a requirement.

rthpjm · Jul 21, 2018

Batch68 said:
28 GB, 8 modules, 6x4GB & 2x2GB.

Try the PRAM reset....
Oh but if you do that you’ll need to re-bless the installer location.
You can do that manually (search for “bless” in this thread), or use my latest v1.9 app...
[doublepost=1532242574][/doublepost]

Akshunhiro said:
Thanks so much rthpjm! I picked up a 2006 Mac Pro 2 days ago and already have it running El Capitan. I couldn't find a vanilla install so used a GM release but couldn't boot after updating to 10.11.1 so switched back to Lion and replaced the boot.efi and then installed Boot64 Currently doing a backup with carbon copy cloner and will try 10.11.6
It's a 1,1 with flashed EFI and SMC, only 11GB of RAM (have ordered a 32GB kit) still rocking original 7300GT so GPU upgrade is next! Will probably get a pair of 5365's as well.
[doublepost=1532224533][/doublepost]Update to 10.11.6 completed no problem. Security update 2018-004 now hidden (may attempt after another backup).
Any recommendations for budget cards? Was looking at 5770/5870. Metal is not a requirement.

Post #1 of this thread has a section recommending gfx cards. Personally I have an XFX branded 5770 that is flashed with a patched EFI Byte Code (EBC) extension in the card firmware, this gives me boot screens and a really good match with the kernel drivers. If I want (or need) metal or better performance, I also have a GTX 680 I simply swap to. My 680 is not patched and therefore does not show the boot screens.
..

Traace · Jul 22, 2018

I just bought a Mac Pro 1,1. Its my first Mac ever.

- (Someone) provided me a working preinstalled el capitan 10.11.6 dmg with recovery and boot.efi mod.

- But that old OSX Tiger coudn't extract dmg files from newer osx versions because they turned on compression.
- I connected the HDD to a external SATA reader, plug it into my Win10 PC and transfered the .dmg via TransMac.
- Then flashed a ATi HD 5870 with a proper EFI Bios to get bootscreens.
- Installed newest security update, replaced kernel with working 2017-005, rebuild kernel cache via recovery and touch
- RAM & CPU Upgrade
- Installed rEFInd manual way and created a bless script for it
- Triple-Booting: OSX 10.11, Windows 10 Spring Build (MBR+AHCI), Ubuntu 18.04
- Profit!

Maybe Apple will maintain Sec. updates a bit longer than usual, consider El Cap. is latest OS many oldies can run

Mac Pro 1,1: 100$
ATi HD 5870: 20$
32GB FB-DIMM: 20$
2x X5355 (Matching Pair!) @ 2,66Ghz: 30$
--------------------
170$

Time & Money....All just a illusion.

rthpjm · Jul 22, 2018

Akshunhiro said:
I couldn't find a vanilla install so used a GM release

If you can install Lion, then you have the App Store application.

If you have an Apple ID, then you can login.

If you have previously downloaded a copy of Install OS X El Capitan, then you can get another copy from the Purchases tab. Remember, to remove/delete any other/older copies first otherwise the App Store will not allow you to download. The App Store appears to search the Spotlight database, if it finds a match it assumes you’ve already got a copy and stops silently.

Alternatively, there’s a link in post #1390 to an Apple Support page that has an App Store link on it specifically for people upgrading. Same goes with other copies, remove/delete them first otherwise it will not download.

Remember, Spotlight’s index covers all visible volumes. Therefore if you have any older copies of Install OS X El Capitan on any mounted volume you will not be able to download a fresh copy.
HINT, use Disk Utility to unmount all Volumes except the Lion volume whilst you try to download your fresh copy.

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

macrumors regular

macrumors regular

macrumors 6502a

macrumors 601

macrumors newbie

macrumors 68000

macrumors newbie

Attachments

macrumors newbie

Attachments

macrumors 68000

macrumors newbie

macrumors newbie

macrumors newbie

macrumors 6502a

macrumors newbie

macrumors 601

macrumors newbie

macrumors newbie

macrumors newbie

Attachments

macrumors newbie

macrumors 6502a

macrumors newbie

macrumors newbie

macrumors 6502a

macrumors regular

macrumors 6502a

Our Staff