Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

spin498

spin498

macrumors member
Nov 24, 2010
42
1
I move around
I have managed to get mine running in Safe Mode, prior to that it would loop at loading of the mouse driver and all I would get is a black screen with the cursor flashing in the top left corner every couple of seconds.

This what the crash report the system generated. I have a vague idea of what it's saying. Do I read it correctly that the last loaded kext is the issue? If so, if I delete that kext, will the system generate a new one or just stop trying to load it. I don't want to make the system worse.

*** Panic Report ***
panic(cpu 0 caller 0xffffff80147ce5fa): Kernel trap at 0xffffff8014745383, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000010, CR3: 0x000000000c808000, CR4: 0x0000000000002660
RAX: 0x0000000000000000, RBX: 0xffffff802801f000, RCX: 0x000000000000007e, RDX: 0x0000000000000000
RSP: 0xffffff911e9eabc0, RBP: 0xffffff911e9eafb0, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0xffffff911e9eacd0, R10: 0x00000000ffffffff, R11: 0xfffffffff0000000
R12: 0x0000000000000002, R13: 0x0000000000000023, R14: 0x0000000000000000, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff8014745383, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff911e9ea850 : 0xffffff80146dab12
0xffffff911e9ea8d0 : 0xffffff80147ce5fa
0xffffff911e9eaab0 : 0xffffff80147ec463
0xffffff911e9eaad0 : 0xffffff8014745383
0xffffff911e9eafb0 : 0xffffff8014744a06
0xffffff911e9eb010 : 0xffffff8014bd87be
0xffffff911e9eb040 : 0xffffff80148ff5f9
0xffffff911e9eb0c0 : 0xffffff80148ff256
0xffffff911e9eb100 : 0xffffff8014902804
0xffffff911e9eb130 : 0xffffff80148fe301
0xffffff911e9eb1c0 : 0xffffff8014b00cc5
0xffffff911e9eb2f0 : 0xffffff8014b297c7
0xffffff911e9eb4b0 : 0xffffff8014b15acf
0xffffff911e9ebbd0 : 0xffffff801492723e
0xffffff911e9ebc60 : 0xffffff80149165c4
0xffffff911e9ebd70 : 0xffffff801490cc40
0xffffff911e9ebf60 : 0xffffff8014c286a1
0xffffff911e9ebfb0 : 0xffffff80147ecc66

BSD process name corresponding to current thread: mds

Mac OS version:
15F34

Kernel version:
Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64
Kernel UUID: 7E7B0822-D2DE-3B39-A7A5-77B40A668BC6
Kernel slide: 0x0000000014400000
Kernel text base: 0xffffff8014600000
__HIB text base: 0xffffff8014500000
System model name: MacPro1,1 (Mac-F42C88C8)

System uptime in nanoseconds: 151940412056
last loaded kext at 44793706962: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f959fe000, size 69632)
loaded kexts:
com.Cycling74.driver.Soundflower 1.5.1
com.nvidia.NVDAStartupWeb 10.0.9
com.rim.driver.BlackBerryUSBDriverInt 0.0.74
com.apple.filesystems.msdosfs 1.10
com.apple.driver.AppleGraphicsDevicePolicy 3.12.7
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleHDAHardwareConfigDriver 274.9
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleHDA 274.9
com.apple.driver.AppleMCCSControl 1.2.13
com.apple.driver.pmtelemetry 1
com.apple.GeForce 10.1.0
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 4.4.5f3
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.CSRBluetoothHostControllerUSBTransport 4.4.5f3
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleLPC 3.1
com.apple.nvidia.NVDAStartup 10.1.0
com.apple.driver.AppleHV 1
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.iokit.SCSITaskUserClient 3.7.7
com.apple.iokit.IOAHCIBlockStorage 2.8.5
com.apple.driver.AppleIntel8254XEthernet 3.1.4b1
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.driver.AppleFWOHCI 5.5.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 38
com.apple.driver.AppleAHCIPort 3.1.8
com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1
com.apple.driver.usb.AppleUSBUHCIPCI 1.0.1
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleACPIButtons 4.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 4.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 163
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.driver.AppleGraphicsControl 3.12.8
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 274.9
com.apple.kext.OSvKernDSPLib 525
com.apple.driver.AppleSMBusController 1.0.14d1
com.apple.iokit.IOAcceleratorFamily2 205.10
com.apple.nvidia.driver.NVDAGK100Hal 10.1.0
com.apple.nvidia.driver.NVDAResman 10.1.0
com.apple.AppleGraphicsDeviceControl 3.12.8
com.apple.iokit.IOSurface 108.2.1
com.apple.iokit.IOSerialFamily 11
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.4.5f3
com.apple.iokit.IOBluetoothFamily 4.4.5f3
com.apple.driver.CoreCaptureResponder 1
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleHDAController 274.9
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 274.9
com.apple.iokit.IOAudioFamily 204.4
com.apple.vecLib.kext 1.2.0
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d7
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleHIDKeyboard 181
com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1
com.apple.driver.usb.AppleUSBHub 1.0.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.7
com.apple.iokit.IOBDStorageFamily 1.8
com.apple.iokit.IODVDStorageFamily 1.8
com.apple.iokit.IOCDStorageFamily 1.8
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOFireWireFamily 4.6.1
com.apple.iokit.IOATAPIProtocolTransport 3.5.0
com.apple.iokit.IOAHCIFamily 2.8.1
com.apple.driver.usb.AppleUSBUHCI 1.0.1
com.apple.driver.usb.AppleUSBEHCI 1.0.1
com.apple.iokit.IOATAFamily 2.5.3
com.apple.iokit.IONetworkingFamily 3.2
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 417.4
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.iokit.IOUSBMassStorageClass 4.0.2
com.apple.driver.AppleUSBComposite 900.4.1
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.iokit.IOUSBHostFamily 1.0.1
com.apple.driver.AppleUSBHostMergeProperties 1.0.1
com.apple.driver.AppleACPIPlatform 4.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
Model: MacPro1,1, BootROM MP11.005C.B08, 8 processors, 2.66 GHz, 8 GB, SMC 1.7f10
Graphics: NVIDIA Chip Model, NVIDIA Chip Model, PCIe, 2048 MB
Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser A/DIMM 3, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser A/DIMM 4, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser B/DIMM 3, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Memory Module: DIMM Riser B/DIMM 4, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, -
Bluetooth: Version 4.4.5f3 17904, 3 services, 26 devices, 0 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
Serial ATA Device: TOSHIBA MK2035GSS, 200.05 GB
Serial ATA Device: WDC WD5000AAKX-001CA0, 500.11 GB
Serial ATA Device: ST1000DM003-9YN162, 1 TB
Serial ATA Device: ST1000DM003-9YN162, 1 TB
Parallel ATA Device: OPTIARC DVD RW AD-7170A
USB Device: USB 2.0 Bus
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: USB2.0 Hub
USB Device: USB to ATA/ATAPI Bridge
USB Device: CSR8510 A10
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Optical Mouse
USB Device: USB Bus
USB Device: USB Bus
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
 
CT87

CT87

macrumors newbie
Jun 12, 2016
5
0
France
I am disappointed ... I do not know how ... it takes you I found an older version of Mac OSX 10.11 ?
 
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
spin498 said:
I have managed to get mine running in Safe Mode, prior to that it would loop at loading of the mouse driver and all I would get is a black screen with the cursor flashing in the top left corner every couple of seconds.

This what the crash report the system generated. I have a vague idea of what it's saying. Do I read it correctly that the last loaded kext is the issue? If so, if I delete that kext, will the system generate a new one or just stop trying to load it. I don't want to make the system worse.





BSD process name corresponding to current thread: mds


last loaded kext at 44793706962: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f959fe000, size 69632)
loaded kexts:
com.Cycling74.driver.Soundflower 1.5.1
com.nvidia.NVDAStartupWeb 10.0.9
com.rim.driver.BlackBerryUSBDriverInt 0.0.74
com.apple.filesystems.msdosfs 1.10
Click to expand...

There appears to be two potential issues. You have some third party kernel extensions loading (Nvidia, Soundflower, and BlackBerry). You could try restarting, when your hear the chime hold down the shift key, when you see the progress bar you can let go. This should start up in "safe mode". It might take longer to start than usually, it will sometimes runs a disk check....

The second alternative is a disk issue, the process that crashed looks to be the mds process (meta data server), it is the spotlight indexing process. Perhaps you could try starting from the Recovery partition, open the Disk Utility from the Utilities menu, and run first aid on all your disks.

The two could be related. The last loaded extension was the msdos extension, and then mds crashed. Do you have any disk partitions or external drives connected that are formatted as MSDOS (or Boot Camp)?
[doublepost=1465894805][/doublepost]
CT87 said:
I am disappointed ... I do not know how ... it takes you I found an older version of Mac OSX 10.11 ?
Click to expand...

Hello CT87,

Please search for, and delete all copies of "Install OS X El Capitan" app. Empty the Trash. Finally use the Mac App Store to download a fresh copy of the El Capitan installer...

Bonjour CT87,

S'il vous plaît rechercher et supprimer toutes les copies de l'application "Installer OS X El Capitan". Vider la poubelle. Enfin utiliser le Mac App Store pour télécharger une nouvelle copie de l'installateur El Capitan ...
 
spin498

spin498

macrumors member
Nov 24, 2010
42
1
I move around
rthpjm said:
There appears to be two potential issues. You have some third party kernel extensions loading (Nvidia, Soundflower, and BlackBerry). You could try restarting, when your hear the chime hold down the shift key, when you see the progress bar you can let go. This should start up in "safe mode". It might take longer to start than usually, it will sometimes runs a disk check....

The second alternative is a disk issue, the process that crashed looks to be the mds process (meta data server), it is the spotlight indexing process. Perhaps you could try starting from the Recovery partition, open the Disk Utility from the Utilities menu, and run first aid on all your disks.

The two could be related. The last loaded extension was the msdos extension, and then mds crashed. Do you have any disk partitions or external drives connected that are formatted as MSDOS (or Boot Camp)?
[doublepost=1465894805][/doublepost]
Click to expand...

I have a disc that I had loaded with music that is MSDOS from my Win 7 days. You suggest reformatting it to make it more OS X compatible?

I have an Nvidia graphics card, won't I need that extension. I forget why I have Soundflower and my BlackBerry died years ago. I will try to remove the latter two.
 
nounousomes

nounousomes

macrumors newbie
Jun 18, 2008
16
3
tu154 said:
First of all, in my first post here, I want to give a big thank you to Pike and all the people involved in testing of the boot.efi file that gave an extra live to my Mac Pro. What a great work you have done!. Thank you very much

I've been using the boot.efi since Yosemite and now on El Capitan and after reading a lot of posts I decide to share my experience with to objective to try to help or simply give my feedback.

In terms of hardware as I say I have a Mac Pro 1,1 2006 with a Nvidia PC Graphic Card Asus GeForce GT740 OC 2GB GDDR5 PCI-E. Since I have a pc card I cannot see the boot screen neither intaller or otherthings until the login window. The graphic card works with yosemite and el capitan native driver but is recomended to instal latest nvidia webdriver. I had some kernel panics that lead to 2 or 3 reboots before login wind. After that instal the webdriver and everything went good.

I do not have an extra mac that supports yousemite or el capitan and after several trials I found a diferent way to install the OSX with the Pike boot efi. I've done this to yousemite and after to el capitan but you can do it, probably in any machine or system.

1-I started to install the OSX in a virtual machine. I've used Vmware.

2-After this I created a account (like a normal osx install).

3-With disk utility I've done a OSX disk image. After disk image is done you should do a scan/check of the disk image with this utility. I think in yosemite is scan image for restore ( I am not in front of my mac sorry).

4-After this you shold copy the osx image file to your "normal" mac startup system (desktop for example)

5-Create a partition for your new OSX instalation;

6-Restore the osx image created on the virtual machine;

7-Replace the boot efi in their locations;

8-Repair the new disk partition with you current system disk utility.

9-Your new osx should appear now (also in previous step) on your startup disks; Select it and reboot.

Now you should see your login window.

The only thing is that I could not have the recovery Hd but in my case I can not use it. I think you can restore with carbon copy cloner for example.

Hope this can help someone.

Take care
Click to expand...


You mentioned, you did:

3-With disk utility I've done a OSX disk image.

How did you do this?
 
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
spin498 said:
I have a disc that I had loaded with music that is MSDOS from my Win 7 days. You suggest reformatting it to make it more OS X compatible?

I have an Nvidia graphics card, won't I need that extension. I forget why I have Soundflower and my BlackBerry died years ago. I will try to remove the latter two.
Click to expand...
Hello spin498,

If the MSDOS formatted disk is self contained, first try removing it from your system to see if it resolves your boot issue.

If you have an NVidia card, don't try removing it. I really just pointed out the third party kexts because those won't be enabled when safe-booted
 
OGNerd

OGNerd

macrumors regular
Jun 1, 2015
128
136
buzzworm said:
I tried with latest boot.efi. Kernel Panic. Didn't try verbose booting. Don't really have the time to mess around with it.
Click to expand...

I believe that it is going to take a tweak to Pike's boot.efi to run macOS Sierra. Pike's boot.efi is coded to present the Mac Pro 1,1 & 2,1 as a Mac Pro 3,1, and that model is not supported by Sierra (nor is the 4,1 for that matter). :(
 
J

jcathey

macrumors newbie
Jun 16, 2016
2
0
Obibob said:
...
Hardware UUID: 2B12FE1B-1090-593B-B740-2E45F371D1E4
...
Click to expand...

So I've Piked (et al.) two nice MacPro 1,1 machines that now have 2,1 firmware, 8x3GHz "Big Jim" SLAED CPU's, SSD's, gobs of RAM, and ATI HD4870's, and they're working beautifully, running 10.11.5, couldn't be happier.

... Except for Time Machine backups to our file server. Turns out both machines have exactly the same hardware UUID's, the one quoted above from #1013 in fact, and the UUID is used as part of the Time Machine database key, so they fight over the same backup set. Which is not appreciated!

All attempts to get them to have different UUID's have failed, I even went so far as to write a C program that did a find/replace on the entire SSD volume, replacing 40-odd occurrences. It worked fine, but it booted back up with this UUID anyway.

So, do the patched boot.efi files somehow force a particular UUID? Is there any way to get them to not do this? The machines do not have the same HW UUID's when running 10.6 or 10.7, for example.
 
Last edited:
A

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Same here, but maybe the small price we have to pay for the "fix". Maybe there is a way to edit the numbers or have another copy created by the good people who have enabled this fix to work, so that at least the ID's would be different on 2 Macs.
 
Eagalution

Eagalution

macrumors newbie
Jun 16, 2016
7
0
Hi
rthpjm
I did the magic with the help of your GREAT video. It went well and now I am using EL Capitan on my 2006 Macpro 1.1
All work well so far (I already use it a week), except of some problems, and I am wondering if you could give an advice;
1. Restart does not work! It get stuck and cant reboot. The only solution so far was to shot the computer and restart manualy.
2. Every time I start, I need to push the alt key and choose a drive to start from. If I just let it start as normal, it chooses another drive with an old system. (an old drive I still use with my music studio).
3. I was trying to fix the problem with my Tectool, but rebuilding the hierarchy went into error that could not be fixed. I had to restore all from time machine.

Thank you so much!!

PS. I was using version 8 of Piky
 
Last edited:
A

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Have you tried selecting the drive with El Cap as your startup disk in system preferences?
Have you tried resetting the SMC? Whatever you do, no need to "shot the computer" ;-)
 
Last edited:
Eagalution

Eagalution

macrumors newbie
Jun 16, 2016
7
0
Ant3000 said:
Have you tried selecting the drive with El Cap as your startup disk in system preferences?
Have you tried resetting the SMC? Whatever you do, no need to "shot the computer" ;-)
Click to expand...
Thank you Ant3000. This solved problem 2. Now it goes directly to El Capitan with no need for the Alk key!

Problem 1. and 3. still waiting to be resolved... :)
 
A

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Eagalution said:
Thank you Ant3000. This solved problem 2. Now it goes directly to El Capitan with no need for the Alk key!

Problem 1. and 3. still waiting to be resolved... :)
Click to expand...
Is the restart being stopped by an app running in the background? Open Activity monitor to check if anything is still running..
 
Eagalution

Eagalution

macrumors newbie
Jun 16, 2016
7
0
Ant3000 said:
Is the restart being stopped by an app running in the background? Open Activity monitor to check if anything is still running..
Click to expand...
When restarting it does shot down, but then it tries again and again to start. ( I can hear that sound of the computer wanting to start, as it would sound regularly when turning it on.
I guest it is not a major problem... I could live with it...
 
A

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Eagalution said:
When restarting it does shot down, but then it tries again and again to start. ( I can hear that sound of the computer wanting to start, as it would sound regularly when turning it on.
I guest it is not a major problem... I could live with it...
Click to expand...
Have you tried logging out of your account and then try a restart from the login window?
 
S

SignalFlow562

macrumors newbie
Apr 12, 2016
18
2
rthpjm said:
Some of the guys that were working with Pike split off into a new thread to concentrate on just the development and testing of Pike's frequent changes, "the developer thread". As these things go, the volunteers that were testing Pike's changes found that they needed to frequently wipe and re-install, me included, so I developed a bundle of scripts and items to ease the install of a new El Capitan. My innovation (if you want to call it that) was to find a way to patch the fresh install with Pike's efi files during the install. I called my bundle of scripts and items 'pikify3.1.zip'.

Since it is now well used and tested, I'll cross post here. The latest version pikify3.1.v8.zip will build install media with all the fixes in (but not including my Boot64 update protector, nor the equivalent pikeyosfix derivative CapitanPikeFix - see the next post). This version also excludes the boot.efi files from SIP-control (meaning SIP is running and protecting everything else, just not the boot.efi files).

So with pikify3.1 you will build an installer onto media, typically a USB memory stick, or a small disk partition.
You will then boot off the installer, to run the installation process. Once the installer finishes, you will have a working copy of El Capitan with no further need for changes. You can then choose to install the updated version of pikeyosfix now called CapitanPikeFix, or my Boot64 (both do pretty much the same thing), to allow you to run the Apple updates from either the App Store or from the DMG downloads.

READ ALL THE CAVEATS - memory, backup, fresh install, migration assistant, etc...

Use this if you have not yet installed El Capitan and you only have your Mac Pro available.

(If you have another "newer/compatible" machine available then you can attach your Mac Pro (disks) to this compatible Mac and install from there), otherwise....

This is the installer (starting point) if you only have your Mac Pro to work with...

-----------------------------------------------------------------------------------------------

ORIGINAL POST WAS AT POST #807 of the 'boot.efi developer's thread'

============= Edit =====================

It appears that MacPro1,1 and 2,1 need a lot of memory to achieve a successful install by this method. Others have kindly tested with varying configurations of RAM. See the later posts in the developers thread and my post at #855

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

============ end edit ====================

Hi @Inspector42, I'm glad you were able to use my script. I like your rsync idea!

Here is a new script and accompanying files. This one is based around Apple's createinstallmedia script.

The unique feature of this script is that it builds an installer which will pre-patch the resulting El Capitan volume. What this means is that the installer can be run, and then the reboot will work without any further modification. You have a working installation of El Capitan directly from the installer.

Download the zip file.
Unzip it.
You should have a folder named pikify3.1 (possibly with the version number pikify3.1.v2 etc)
In that folder should be a number of files, the script is createpikeinstallmedia. Keep all the files in one location. Some people have tried to use just the script on its own without the accompanying files and then come back for help because it didn't work. You can move the pikify3.1 folder wherever you please, just keep the contents of the folder together.

If you are not familiar with the Terminal and the command line, take a look at post #1569 it will probably help you.

Pre-requisites:
  • As per Peter's guide, you will need a volume that can be overwritten by the installer
    • This could be a USB memory stick
    • A small disk partition from one of your hard drives (not the disk that you intend to use for El Capitan)
      • You need to be able to boot from this volume
  • The installer volume needs to be at least 8GB
  • Your copy of 'Install OS X El Capitan.app' should be located in your /Applications folder
  • The pikify3.1 folder contains both the black and grey variants of the boot.efi file. When unzipped the boot.efi file is the grey one, if you want to change to the black background variant, simply copy the black one over the boot.efi before you start. e.g.
    Code: 
    cp -f boot_black_3_1.efi boot.efi
Usage:
  • Open a terminal window
  • Change directory to the pikify3.1 folder from the zip file. Let us assume that you downloaded the zip file to your Downloads folder and unzipped it there. (If you have put the pikify3.1 folder somewhere else, please alter the path to suit your location)
  • Change [InstallerVolumeName] to the name of the USB memory stick or your small disk partition. For example if you are using a USB memory stick and it shows on the desktop with the name Untitled, then replace [InstallerVolumeName] with Untitled so that the path reads /Volumes/Untitled
Code: 
cd ~/Downloads/pikify3.1
  • You need to run the script as the root user
Code: 
sudo -s
[your password]
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

  • OR
Code: 
sudo ./createpikeinstallmedia /Volumes/[InstallerVolumeName]
[your password]
  • OR (optionally switch to the black background variant before you start)
Code: 
sudo -s
[your password]
cp -f boot_black_3_1.efi boot.efi
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

Be patient, the script will take some time to run through to completion, especially if your installer volume is a USB memory stick!

Once the script completes it will print ### DONE PIKIFYING ### and you should have an installer volume named 'Install OS X El Capitan'

--------------------- EDIT -----------------------------------------------
Some users have reported that after building a pikify3.1 USB memory stick they cannot boot their MacPro from it. Typical symptoms are that when rebooting, holding the ALT key immediately after the chime, enter the boot selector, choose the USB memory stick to boot from, yet the system then boots to the main OS from the hard disk(s), or the screen is blank (possibly showing the folder with a question mark).

I have replicated this on my machine. Here is what works for me....

After you build your pikify3.1 USB memory stick, but before you attempt to boot from it, try ejecting it, physically unplug it, wait a few seconds, then re-plug it in allowing it to mount.

Doing this seems to work for me. I think the important thing is to physically remove (power down) the device. It's a good old fashioned hardware restart.

-------------------- end EDIT ------------------------------------------
  • Reboot your MacPro with the newly created install media (partition or USB stick) attached
  • Hold the ALT key down immediately after the startup chime to enter the boot chooser
  • Choose the Install OS X El Capitan volume
    • For those people with graphics cards that don't show the boot screens
      • If you are using a USB stick (and it's the only one attached), then get to the boot chooser as above then press the left-arrow key once, followed by the return/enter key. (Removable media generally shows up last in the horizontal list, pressing the left arrow key takes you from the automatic first entry and wraps the highlight round to the other end of the list, which is usually where the USB stick is presented).
      • If you're using a small disk partition, the get to the boot chooser as above then press the right-arrow key once, followed by the return/enter key). If you have just your main disk and the installer volume this should work. If you have more than just those two, experiment pressing the arrow key more than once until you find the installer volume!
      • OR, consider getting hold of a DVI-vga adaptor. You should be able to find one of your DVI ports that will send out a VGA signal (to a VGA connected monitor) and show you the boot screen.
  • Your machine should boot into the Installer, run the installer
    • You may need to click the Reboot button at the end of the install (for some reason, the 10 second countdown doesn't seem to automatically start)
  • Your machine should reboot into the new El Capitan Installation and begin the OS X setup procedure.
============== edit ===============
I made a video! I hope you like it...

I used my iPhone for the second half, apologies for the moire patterns.

I decided to start from my MacPro running 10.7.x Lion, since this is the last officially supported version.
The only difficulty for people is to get hold of a copy of Apple's "Install Mac OS X El Capitan" app. I recommend using a newer "supported" Mac and then copying it to the MacPro....

One of the steps in the video shows me formatting my hard disk drive, do not do this step if you have data on your hard disk (unless you have a backup and are prepared to wipe the drive)


============== end edit =============

I have only tested this script as a clean install onto an erased destination disk. I don't know if it will work for an upgrade. I have successfully updated a Yosemite clean install to El Capitan.
If you are upgrading I would suggest a clean install of El Capitan onto a spare disk, then use the Apple Migration Assistant to migrate your previous system and user files.
If you are brave and want to try an in-place upgrade, make sure you backup your current system first...

Detail:

I created an additional package (pikify.pkg) which handles the post-install modification of the boot.efi files on the destination volume. The script puts pikify.pkg into the InstallESD.dmg, along with OSInstall.collection.
OSInstall.collection overrides the default behaviour of the Installer Assistant, it calls the default OSInstall.mpkg and appends pikify.pkg to the install chain.

In effect I'm running the exact same installation as an unmodified Apple install with the addition of my pikify.pkg.

Because the default behaviour has been overridden, there are a few differences:
  • An unmodified Apple installer will open with the /System/Installation/CDIS/OS X Utilities.app
    • The modified installer goes straight into the Installer
  • An unmodified Apple installer will automatically reboot 10 seconds after the installation completes
    • The modified installer doesn't, you will have to click the Reboot button
I've included both versions (black and grey) of Pike's 3.1 boot.efi file. If you want to change the colour, overwrite the boot.efi file in the pikify3.1 folder with the coloured version of your choice. The zip file unpacks with the grey version in place.

Enjoy...

======================== UPDATE ================================

The original Apple BaseSystem.dmg appears to be missing a number of fonts. This causes the installer log file to fill up with thousands of unnecessary lines complaining about the missing fonts. I've updated the installer creation script to fix the missing fonts. It just makes the log file smaller and easier to read and follow.

See pikify3.1.v2.zip in the attachments...

==================== ANOTHER UPDATE =============================

I figured out how to set up El Capitan so that we can make it survive an Apple update. See my post at post #1391

I've modified the pikify3.1 set so that those changes are automatically applied.

I'll leave v2 here in case anyone is paranoid, and doesn't want the slight lowering of SIP's security blanket!

==================== Version 5 ===================================

V5 includes some mods to the SIP exclusion paths file

==================== Version 7 ===================================
(includes version 6, which added support for home-baked fusion drives)
V7 adds error checking and a bit of an explanation to start

==================== Version 8 ===================================
V8 adds a check to ensure there is a copy of the Apple Install OS X El Capitan application located in the Applications folder!

==================== Version 9 ===================================
All previous versions would first write the Install media, and then modify that content. If the Install media is a USB memory stick, all those operations are slow due to the USB bus speed.

V9 attempts to speed up the operations. It will modify the /Applications/Install OS X El Capitan.app on the hard disk first (faster), and then write the contents to the USB memory stick. There is only one write across the USB bus.

Plus, the modifications are left in place. The script will detect if the copy of Install Mac OS X El Capitan has already been modified, giving you the option to reset to the Apple version, or to continue. If you choose to continue it will skip the modifications (because they're already present) and simply write a new copy to your USB memory stick (or installer partition)

It should be quicker :)

==================== Version 10 ==================================
Version 10 adds a check to see if the InstallESD.dmg and/or the BaseSystem.dmg are already mounted, if so it tries to detach them.

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

MD5 (pikify3.1.v2.zip) = 80333eda8eecc3094f06d175bdba0a64
MD5 (pikify3.1.v9.zip) = b14e4489bf5c8c7177d570748adf30f5
Click to expand...
Just curious. Will the pikify patch work for 10.10?
 
S

SignalFlow562

macrumors newbie
Apr 12, 2016
18
2
rthpjm said:
Maybe,... But you would need to edit the script...
Click to expand...
I'm a serious noob when it comes to scripts and stuff. Is this something fairly easy to do?

I was able to get 10.11.5 on my 1.1 using your steps. It was pretty clear and easy to understand especially the video:)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom