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

[donjames]

Hallo everyone,
I have MacPro1,1 dualcore, running on Yosemite thanks to help from here last year. I would like to upgrade to Capitan. Where should I start? Is there a specific post here with a complete tutorial?

Looking forward to climbing El-Capitan

Thanks in advance.

Take a look at this one: https://forums.macrumors.com/thread...os-x-el-capitan.1890435/page-56#post-22335920

Regards,

donjames

 

[rthpjm]

Just got-around to finally running your script, and have now only completed the creation of the modified installer. Before I proceed, two stdout responses post-"### DONE PIKIFYING ###":

2015-12-29 18:26:22.430 system_profiler[1051:73438] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0
2015-12-29 18:26:22.432 system_profiler[1051:73438] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0

More feedback, as time permits...

Regards, splifingate

Hey splifingate

Those two system profiler lines are unusual, they don't occur on my Mac Pro 1,1 (flashed to 2,1). Don't worry about them though, I simply added a bit of code at the end to try and detect if this system is a Mac Pro 1,1 or 2,1 AND has the required 12GB of RAM or more (for the installation that inevitably comes next). It just outputs some text to warn if the RAM is less than 12GB...

 

[rthpjm]

you in Nottingham? I have assumed (probably incorrectly) "rth" is "Robin The Hood" If so, I am other end of the A52. Thanks again.

Good guess! I'm at the same end of the A52 as you. One of my hobbies is archery!

 

[Ant3000]

Good guess! I'm at the same end of the A52 as you. One of my hobbies is archery!

Small world!
App Store is offering El Capitan Recovery Update 1.0 - do you think this will this be safe to update with current Boot64 installed or will it stop the Recovery working? I could risk it as the current install is really a test until new SSD arrives.
Thanks for any advice.

 

[wolf1734]

Good evening rthpjm

The key not it is created malgres that in the terminal it stood out " done pikifying" and in the second line " bash 3.2 * " thus I do not know how to make. Of the help(assistant) squeezed(tightened) timely. Excuse my English.
Cordially

 

[wolf1734]

Running Apple's createinstallmedia tool...



./createpikeinstallmedia: line 84: /Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia: No such file or directory



Piking the .IABootFiles directory
cp: /Volumes/Install OS X El Capitan/.IABootFiles/boot.efi: No such file or directory
cp: /Volumes/Install OS X El Capitan/System/Library/CoreServices/boot.efi: No such file or directory
cp: /Volumes/Install OS X El Capitan/usr/standalone/i386/boot.efi: No such file or directory
mv: rename /Volumes/Install OS X El Capitan/.IABootFiles/PlatformSupport.plist to /Volumes/Install OS X El Capitan/.IABootFiles/PlatformSupport.plist.apple: No such file or directory
./createpikeinstallmedia: line 92: /Volumes/Install OS X El Capitan/.IABootFiles/PlatformSupport.plist: No such file or directory
cp: directory /Volumes/Install OS X El Capitan/System/Library/CoreServices does not exist



Open the InstallESD disk image
hdiutil: attach failed - No such file or directory



Piking the OSInstall collection
cp: directory /Volumes/OS X Install ESD/Packages does not exist
./createpikeinstallmedia: line 102: /Volumes/OS X Install ESD/Packages/OSInstall.collection: No such file or directory
cp: directory /Volumes/OS X Install ESD/Packages does not exist
mv: rename /Volumes/OS X Install ESD/Packages/InstallableMachines.plist to /Volumes/OS X Install ESD/Packages/InstallableMachines.plist.apple: No such file or directory
./createpikeinstallmedia: line 116: /Volumes/OS X Install ESD/Packages/InstallableMachines.plist: No such file or directory
rm: /Volumes/OS X Install ESD/Packages/InstallableMachines.plist.apple: No such file or directory



Copy the BaseSystem disk image to /tmp
building file list ...
rsync: link_stat "/Volumes/OS X Install ESD/BaseSystem.dmg" failed: No such file or directory (2)
0 files to consider

sent 29 bytes received 20 bytes 98.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(992) [sender=2.6.9]
rm: /Volumes/OS X Install ESD/BaseSystem.dmg: No such file or directory



Open the BaseSystem disk image
hdiutil: attach failed - No such file or directory



Piking the Base System

chflags: /Volumes/OS X Base System/System/Library/CoreServices/boot.efi: No such file or directory
cp: /Volumes/OS X Base System/System/Library/CoreServices/boot.efi: No such file or directory
cp: /Volumes/OS X Base System/System/Library/CoreServices/bootbase.efi: No such file or directory
cp: /Volumes/OS X Base System/usr/standalone/i386/boot.efi: No such file or directory



Adding the missing fonts...

./createpikeinstallmedia: line 134: cd: /Volumes/OS X Base System/System/Library/Fonts: No such file or directory



Close the BaseSystem disk image
hdiutil: detach failed - No such file or directory



Put the modified BaseSystem back into the InstallESD disk image



hdiutil: convert failed - No such file or directory
rm: /tmp/BaseSystem.dmg: No such file or directory
rm: /tmp/BaseSystem.dmg.shadow: No such file or directory



Close the InstallESD disk image
hdiutil: detach failed - No such file or directory



Put the modified InstallESD back into the Install OS X El Capitan volume



rm: /Volumes/Install OS X El Capitan/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg: No such file or directory
hdiutil: convert failed - No such file or directory
rm: /tmp/InstallESD.shadow: No such file or directory




######### DONE PIKIFYING ###########



bash-3.2 #


It gives me ca when I make the key usb
Thank you for the help(assistant)
cordially

 

[Ant3000]

Do you have the El Capitan installer in your applications folder?
Post 1390 has more detailed information?
If it helps, reply in French and I will ask my son to translate and repost.

 

[wolf1734]

bonsoir Ant3000
je te remercie
oui j'ai bien installerOSXElCapitan dans applications

 

[Ant3000]

bonsoir - mon fils est dehors à l'heure actuelle
I used Pikify 3.1 v7
Look at post 1569 for a clearer explanation - Regardez l'après 1569 pour une explication plus claire

 

[mossman1120]

I have written a "recover the Recovery HD" script. It shares much of its code with the original Pikify3.1 scripts.

Use this tool if you want to utilise the Recovery HD. It is especially useful if you have run the 10.11.2 update and found that the Recovery HD has been updated and you can no longer boot from it.

As always the ZIP file contains the script plus supporting files. These all need to be kept together in the same folder. The ZIP file should extract to a folder called rrhd. Inside that folder is the script itself, also called rrhd (along with the supporting files). Open a Terminal, become the super user, execute the script with the volume name of the disk you want to update.

E.G. assuming you unzipped the ZIP file in your Downloads folder, and assuming your El Capitan drive is mounted as /Volumes/El Capitan (change these to suit your situation)

cd ~/Downloads/rrhd
sudo -s
[your password]
./rrhd /Volumes/El\ Capitan

For those people that run multiple disks with versions of Mac OS X installed, this rrhd script will present the Recovery HD in the boot picker as 'Recovery HD (Your El Capitan disk name)'. It makes it easier to identify which Recovery HD belongs to which main OS disk!

I tried to run script provided but it fails when trying to run this command:

chflags nouchg /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi[CODE]

Is this revenge of the SIP Lord?

 

[macguyincali]

Hi @macguyincali

Boot into the Recovery HD and then issue this command from the terminal:

csrutil enable --without kext

I believe it is the SIP equivalent of the former NVRAM setting kext-dev-mode=1.
Disclaimer: I haven't tried it myself

Well, I haven't issued that command yet. With SIP disabled, I installed the Drobo SCSI initiator and restarted (required). Then installed updates and restarted. Then I re-enabled SIPS in Recovery Mode and the drobo started up! This was working fine until I restarted again and the Drobo wouldn't be recognized and I'd get the error above (invalid signature). Disabled SIPS again. Now it only appears to work when SIP is disabled. I get the following console entries:

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ATTOiSCSI.kext
​

This leads me to believe that with SIP off, it is allowing kexts to load appropriately, despite the invalid signature. Will the code you gave me above disable this function without leaving the rest of the system vulnerable? In the long term, I'd like to keep SIP mode on as it is another security function that protects my system. Will disabling the KEXT validation (or whatever your code does) be an issue? Just want to confirm that before I try it.

Also, I wonder if there is a way to make that KEXT have a valid signature somehow?

Thanks in advance for your help.

 

[macguyincali]

I went ahead and tried this command and got the following message:

csrutil: requesting an unsupported configuration. This is likely to break in the future and leave your machine in an unknown state.​

I'm not quite sure what that means, but it sounds ominous. What are the risks with issuing this command and "leaving the machine in an unknown state" so to speak?

Thanks!

 

[macguyincali]

As I spend more time with my new El Capitan system running mostly smoothly on a nearly 10 year old computer, I have found another minor issue: My internal, secondary optical blu-ray drive no longer is recognized. The DVD drive that came with the computer seems to work fine.

The aftermarket internal blu-ray (Pioneer BDR-205 installed in 2010) no longer functions. Doesn't appear under Disc Burning in System Profiler, though it DOES appear under SATA/SATA Express. It doesn't appear as an option when I click the eject button on menu bar. Previously, I was able to click Option-Eject to eject the secondary optical drive. I have no way of opening the drive other than the manual force method.

So, I'm wondering if there is a preference or setting I need to re-enable to get that drive back up and running. If anyone has thoughts... it would be much obliged.

- macguyincali

Incidentally, on the functional main DVD drive, the keyboard eject button is all wonky, doesn't do anything and just gives a dialogue You Inserted a blank DVD even if there is no disk in the drive (or the drive is open and empty). I can eject a disk normally by clicking the eject button in menu bar however.

 

[rthpjm]

I went ahead and tried this command and got the following message:

csrutil: requesting an unsupported configuration. This is likely to break in the future and leave your machine in an unknown state.​

I'm not quite sure what that means, but it sounds ominous. What are the risks with issuing this command and "leaving the machine in an unknown state" so to speak?

Thanks!

SIP also protects the system in a similar fashion to Gatekeeper. Kernel Extentions by their nature must be loaded very early in the boot sequence (before Gatekeeper would be active). SIP is baked into the kernel, therefore it has been extended to check for valid developer-signed kexts. With SIP fully enabled, any unsigned kexts will not load.

You must disable SIP, or enable SIP without kext checking in order to continue to use 3rd party unsigned kexts.

The correct solution is to contact the vendor and ask them to provide a SIP-compliant kext (properly signed). I'm surprised to hear that Drobo are having problems. I guess they license the iscsi tools.

I decided to use the --without kext command myself. The unsupported configuration warning is "normal", the --without switch is essentially undocumented, hence the warning.

 

[rthpjm]

I tried to run script provided but it fails when trying to run this command:

chflags nouchg /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi[CODE]

Is this revenge of the SIP Lord?

Hmmm, can you run the following then post the transcript?

diskutil list

It implies that the target disk does not have a Recovery HD, or that it did not mount with that name.

The RRHD script expects you to supply an OS disk, it then interrogates that volume to find the associated Recovery HD. It then mounts the Recovery HD to work on it.

Did you ever change the volume name of the Recovery HD? The script expects it to be called Recovery HD.
I guess I should modify the script to get the name of the Recovery partition (in case it has been renamed)!

 

[rthpjm]

./createpikeinstallmedia: line 84: /Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia: No such file or directory

Bonjour wolf1734,

Please use the Finder, go to the Applications folder, please confirm that you have a copy of the Apple application 'Install Mac OS X El Capitan'.


If the application 'Install Mac OS X El Capitan' is not there, please use the App Store application to download a copy.... (Or if you have a copy located elsewhere, please make a copy into the Applications folder)

Also, please return to post #1390 to download the latest version of the pikify3.1 tool. It is now at version 8 which includes better error checking...

 

[rthpjm]

I tried to run script provided but it fails when trying to run this command:

chflags nouchg /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi[CODE]

Is this revenge of the SIP Lord?

So I have amended the rrhd script to properly find the volume name of the associated recovery partition (stopped being a lazy programmer and did it properly!). You will find version 2 posted at #1607

 

[Ant3000]

So I have amended the rrhd script to properly find the volume name of the associated recovery partition (stopped being a lazy programmer and did it properly!). You will find version 2 posted at #1607

Thanks for this - just ran the Update 1 for Recovery Disk from the Mac App Store and as expected it stopped booting into Recovery being possible (defaulting to Yosemite on another drive) - I ran the script and it appears to have worked perfectly. I guess Recovery isn't essential and as iMattux suggests, it may actually be quicker to use the USB installer should the need arise.
New year resolution: to try to get my head around Terminal commands to feel like I have a bit more idea of what the commands do and the correct way to enter them. Until then, I am grateful to those who can show me how to proceed.
Happy New Year!

 

[Zelegorm]

Everything was ok since today . I did an update and now i have to replace the two Boot.efi files. I've tried to Boot into recovery mode but it Did not work. Is there another possibility to deactivate sip?

 

[rthpjm]

Everything was ok since today . I did an update and now i have to replace the two Boot.efi files. I've tried to Boot into recovery mode but it Did not work. Is there another possibility to deactivate sip?

If you have another partition with Mac OS X installed boot from that (or its Recovery). You could even use Windows if you have a boot camp partition (assuming you have the Apple HFS+ disk driver loaded in Windows).
If you still have the installer (USB memory?), boot off that, use the terminal
If you have access to another Mac, build an installer, or put your MacPro into target disk mode, connect it to the other Mac, make the changes

 

[iMattux]

I'm confused and frustrated by the continued requests to fix the Recovery HD. While I applaud rthpjm's efforts, I've got to point something out to everyone. If I sound snarky, well, I guess I'm being a bit snarky, but people:

If you're on this thread and you've upgraded your MacPro to El Capitan,

YOU HAVE NO USE FOR A RECOVERY DRIVE
​

Think about it for about 5 seconds. I'll wait... Still think you'd ever need to use a Recovery Drive?

Okay, let's review the facts:

1. @ ~50 lbs. (25Kg) your Mac Pro is not particularly portable...
2. Even if you do take it someplace away from your home or office, you have at least 4 internal drive bays...
3. You have already created a bootable installer, either on a partition on one of the internal drives (best option IMO) or a USB drive or an external drive. Again, unless you take the 50 lb. beast somewhere, your install media is either inside the box or in the same house or building.
4. In every situation I can think of, booting from your Pikified install media is the way to go because:

• You are root - you can do whatever you want or need to do from the terminal - SIP is a non-issue...
• If you need to reinstall, why would you do it from Recovery? First you're gonna wait for a ~8GB download, then you've got to Pikify one way or the other... Why not just boot from the media you used to get you where you are now?

I get that many, if not all, of the people on this thread are here because they either can't or don't want to spend a whole lot of money on their computers, but I can't believe that anyone can't afford to dedicate an 8GB partition (faster than USB for $0) to the install media for the foreseeable future.

If I'm missing some need for a Recovery Drive that the Install Media will not do as well, please correct me.

Cheers and Happy New Year!

​

 

[Zelegorm]

If you have another partition with Mac OS X installed boot from that (or its Recovery). You could even use Windows if you have a boot camp partition (assuming you have the Apple HFS+ disk driver loaded in Windows).
If you still have the installer (USB memory?), boot off that, use the terminal
If you have access to another Mac, build an installer, or put your MacPro into target disk mode, connect it to the other Mac, make the changes

Thank you very much. Target Mode was very useful!

 

[fabounio]

Hello first post here.
Just to say that i've successfully upgraded from yosemite to el capitan, using post 1390 instructions.
I created an install disk with pikily 3.1. i used an old 80 Gb data disk on a free hd bay inside MacPro.

Note: since 2006, i had never installed a new system on my mac, i did only upgrades, staring from 10.4.. !!!
this is his 6 th upgrade ! (i jumped over 10.8).
My mac has 12 Gb ram, radeon 5770 mac edition and Crucial SSD as system drive.
So i can confirm that upgrade from pikify install media, works to upgrade yosemite system. At least, it worked for me

ps : i have launched pikily from my Mac Pro , could i have been able to create media using another "supported" mac ?

 

[Ant3000]

I created the USB stick installer on a Macbook Pro running El Capitan - having downloaded all the necessary files directly to it - it worked perfectly.

 

[rthpjm]

could i have been able to create media using another "supported" mac ?

You can use any Mac to build the install media with pikify3.1.