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

Macschrauber

macrumors 6502a
Dec 27, 2015
619
264
Germany
To my experience (I just installed a freshly downloaded and installed El Cap 10.11.6 on a supported Mac) the Kernel is fine until avoiding the Security Updates.

Just replaced 2 boot.efi and platformsupport.plist and set it into a mp 1.1

Anyway I have an ancient 10.11.6 installation with security updates and replaced Kernel what runs without problems.
 
  • Like
Reactions: hwojtek

Rocketman83

macrumors member
May 29, 2015
60
7
Skaneateles, NY
To my experience (I just installed a freshly downloaded and installed El Cap 10.11.6 on a supported Mac) the Kernel is fine until avoiding the Security Updates.

Just replaced 2 boot.efi and platformsupport.plist and set it into a mp 1.1

Anyway I have an ancient 10.11.6 installation with security updates and replaced Kernel what runs without problems.
Is there a way to install 10.11.6 over my existing 10.11.3 but avoid the security update boot-loop? I don't have another Mac computer (supported or not) to work with.
 

Rocketman83

macrumors member
May 29, 2015
60
7
Skaneateles, NY
make a backup with ccc and try it with the backup
I know that's the smart way, but being impatient, I went ahead and tried to update without backing anything up, other than the kernel file.

I'm happy to report the update was successful, although the installer did pause indefinitely after awhile. I hit the power button to restart, and fortunately the machine booted OK into the desktop. "About This Mac" confirms I am indeed now running El Capitan 10.11.6. No kernel swapping required.

I then updated to iTunes 12.8.2, iTunes Device Support, and Remote Desktop Client 3.9.3. The 2018-004 Security Update was listed as an update there too, but I hid that from future update notifications.

Knock on wood, guys, looks like I'm back in business! Thanks to all who offered their very professional advice. Much appreciated.

Now I better get busy backing this system up... :)
 

Rocketman83

macrumors member
May 29, 2015
60
7
Skaneateles, NY
Would also like to add that updating to El Capitan 10.11.6 resolved an audio issue with my Mac. In version 10.11.3, I was hearing no sound from my external speakers. I am now.

I'm still running the Paragon HFS+ for Windows program. Before the 10.11.6 update, Windows Bootcamp was applying some generic name to my El Capitan drive. After the update, Windows identifies the drive with the correct name, Mac HD El Capitan.
 

hwojtek

macrumors 65816
Jan 26, 2008
1,179
266
Poznan, Poland
I know that's the smart way, but being impatient, I went ahead and tried to update without backing anything up, other than the kernel file.
Sure as hell you can :)
0. Temporarily rename your boot drive to a single word (just to foolproof the procedure), like from "Macintosh HD" to "Boot". I will use "Boot" in subsequent guide.
1. Get your (patched) USB El Capitan installer ready. I will call it "ElCapInstall"
2. Locate your current kernel on your hard drive → /System/Library/Kernels/kernel. Do the same with your current boot.efi.
3. Copy both files to the root of your (patched) USB installer
4. Assuming you have correct modifications in platformsupport.plist etc your 10.11.6 update should run smoothly
5. ...until reboot, when it will go into the reboot loop
6. Boot from the (patched) USB installer
7. Once you are in the main installer screen, select terminal from Utilities menu and copy the kernel from the USB installer back to it's location (cp /Volumes/ElCapInstall/kernel /Volumes/Boot/System/Library/Kernels/)
7a. Copy your boot.efi to the usual locations (cp /Volumes/ElCapInstall/boot.efi /Volumes/Boot/usr/standalone/i386; cp /Volumes/ElCapInstall/boot.efi /Volumes/Boot/System/Library/CoreServices/
8. touch the files just to make sure:
touch /Volumes/Boot/System/Library/Kernels/kernel
touch /Volumes/Boot/usr/standalone/i386/boot.efi
touch /Volumes/Boot/System/Library/CoreServices/boot.efi
9. Use "Select startup disk" from the Apple menu to point the computer to boot from your "Boot" drive and reboot.
10. Should be OK by now, your computer should display 10.11.6 in "About this Mac".
 
Last edited:

Rocketman83

macrumors member
May 29, 2015
60
7
Skaneateles, NY
Sure as hell you can :)
0. Temporarily rename your boot drive to a single word (just to foolproof the procedure), like from "Macintosh HD" to "Boot". I will use "Boot" in subsequent guide.
1. Get your (patched) USB El Capitan installer ready. I will call it "ElCapInstall"
2. Locate your current kernel on your hard drive → /System/Library/Kernels/kernel. Do the same with your current boot.efi.
3. Copy both files to the root of your (patched) USB installer
4. Assuming you have correct modifications in platformsupport.plist etc your 10.11.6 update should run smoothly
5. ...until reboot, when it will go into the reboot loop
6. Boot from the (patched) USB installer
7. Once you are in the main installer screen, select terminal from Utilities menu and copy the kernel from the USB installer back to it's location (cp /Volumes/ElCapInstall/kernel /Volumes/Boot/System/Library/Kernels/)
7a. Copy your boot.efi to the usual locations (cp /Volumes/ElCapInstall/boot.efi /Volumes/Boot/usr/standalone/i386; cp /Volumes/ElCapInstall/boot.efi /Volumes/Boot/System/Library/CoreServices/
8. touch the files just to make sure:
touch /Volumes/Boot/System/Library/Kernels/kernel
touch /Volumes/Boot/usr/standalone/i386/boot.efi
touch /Volumes/Boot/System/Library/CoreServices/boot.efi
9. Use "Select startup disk" from the Apple menu to point the computer to boot from your "Boot" drive and reboot.
10. Should be OK by now, your computer should display 10.11.6 in "About this Mac".
Thanks for the tip, hwojtek. Hopefully, I'll never have to swap out the kernel or reinstall the OS again, but I'll record your post for future reference.
 

Rocketman83

macrumors member
May 29, 2015
60
7
Skaneateles, NY
Yes but there are conflicting reports. I have a 2006 mac pro firmware upgraded to 2,1 AND HAVE IT RUNNING 10.10 ... now im not sure weather to go to 10.11 or not?
I have a 2007 Mac Pro 1,1 upgraded to 2,1. Stock CPU but upgraded video card (AMD Radeon HD 5770) and 32GB of RAM. No issues for me on my recent reinstall of El Capitan, although this was a clean installation on a blank SSD. Previously, I had El Cap installed over an existing Yosemite installation. That ran well too, although I did notice some intermittent problems with USB drives not being recognized when first connected. Knock on wood, that has not been an issue with my latest El Cap installation.