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

robbier · Sep 1, 2017

chrisrm9208 said:
OK, the beat goes on....

Have thrown away the entire MP, as it descended on startup to the chime, followed by 10 seconds of blank screen, then shutdown. No response to any startup keys, nothing. So, to Ebay and another MP1,1 for very little money. This is running Lion (10.7) and the drive I want to install ElCap onto is the SSD. The Pikify app ('Install Piked OS X El Capitan') has been supplied with the requisite ElCap installer (10.11.3) in Applications, it's been run pointing at the newly-formatted SSD(which now *does* appear in Finder), and Boot64.v3 has then been run against the same SSD. No errors reported, but the reboot simply sits with a blank white screen and goes nowhere. I did leave it for 15 minutes in case it was going to do something amusing or religious but no.

Any ideas as to what I've missed out or done wrong?

Chris M

Hi Chris,
Have you tried holding the option key at startup and seeing if the SSD appears as a bootable option to select? If not, my only other suggestion would be to try a different installation method - I used another (supported) Mac to install an unmodified, app-store copy of El Capitan to an SSD and then I copied over the boot.efi file to the two directories mentioned in the first post of this thread, and it booted right up in the Mac Pro 2,1 after I held option at startup and selected the drive.

Robert

chrisrm9208 · Sep 1, 2017

robbier said:
Hi Chris,
Have you tried holding the option key at startup and seeing if the SSD appears as a bootable option to select? If not, my only other suggestion would be to try a different installation method - I used another (supported) Mac to install an unmodified, app-store copy of El Capitan to an SSD and then I copied over the boot.efi file to the two directories mentioned in the first post of this thread, and it booted right up in the Mac Pro 2,1 after I held option at startup and selected the drive.

Robert

Yes, the SSD appears in the list of drives as 'Piked etc.', but selecting it leaves me staring at a white screen until i lose interest. I guess I'll try your suggestion next, assuming I can pry She-WHo-Must-Be-Obeyed away from her Macbook...

thanks,

Chris M
[doublepost=1504283312][/doublepost]

chrisrm9208 said:
Yes, the SSD appears in the list of drives as 'Piked etc.', but selecting it leaves me staring at a white screen until i lose interest. I guess I'll try your suggestion next, assuming I can pry She-WHo-Must-Be-Obeyed away from her Macbook...

thanks,

Chris M

Just tried the script version of Pikify, as opposed to the app version, and nothing's changed except the title of the drive on the boot selection screen; that now has '(Pike)' as opposed to 'Piked' but nothing happens. I've tried on a HDD to see if the SSD was damaged and no, it still just hangs on booting. The MP doesn't have USB-C and the MacBook Air doesn't have Firewire, so I'm having an issue with the whole target mode thing...

Chris M

rthpjm · Sep 1, 2017

chrisrm9208 said:
OK, the beat goes on....

Have thrown away the entire MP, as it descended on startup to the chime, followed by 10 seconds of blank screen, then shutdown. No response to any startup keys, nothing. So, to Ebay and another MP1,1 for very little money. This is running Lion (10.7) and the drive I want to install ElCap onto is the SSD. The Pikify app ('Install Piked OS X El Capitan') has been supplied with the requisite ElCap installer (10.11.3) in Applications, it's been run pointing at the newly-formatted SSD(which now *does* appear in Finder), and Boot64.v3 has then been run against the same SSD. No errors reported, but the reboot simply sits with a blank white screen and goes nowhere. I did leave it for 15 minutes in case it was going to do something amusing or religious but no.

Any ideas as to what I've missed out or done wrong?

Chris M

Hi Chris,

Whilst I have been testing, the same symptoms have occurred on my system. I simply press the power button ( interestingly the machine switches off immediately). Then power on.

If it still does that, I switch off, then on again and hold the ALT key down when I hear the chime.
When the boot screen appears, I select the volume labelled (Piked) installer @ myVolume.

On other occasions, the reboot simply works. I've got no idea why it sometimes stalls

rthpjm · Sep 1, 2017

chrisrm9208 said:
Yes, the SSD appears in the list of drives as 'Piked etc.', but selecting it leaves me staring at a white screen until i lose interest. I guess I'll try your suggestion next, assuming I can pry She-WHo-Must-Be-Obeyed away from her Macbook...

thanks,

Chris M
[doublepost=1504283312][/doublepost]
Just tried the script version of Pikify, as opposed to the app version, and nothing's changed except the title of the drive on the boot selection screen; that now has '(Pike)' as opposed to 'Piked' but nothing happens. I've tried on a HDD to see if the SSD was damaged and no, it still just hangs on booting. The MP doesn't have USB-C and the MacBook Air doesn't have Firewire, so I'm having an issue with the whole target mode thing...

Chris M

Just a thought, do you have multiple monitors?
There have been instances where the system has booted, but for some reason the video is being sent to a phantom monitor. If you have a single monitor, try moving the cable to one of the other connectors...

chrisrm9208 · Sep 1, 2017

rthpjm said:
Just a thought, do you have multiple monitors?
There have been instances where the system has booted, but for some reason the video is being sent to a phantom monitor. If you have a single monitor, try moving the cable to one of the other connectors...

Nope, a single Apple Cinema display, nothing complex at all. The GPU is a FX4500, and there's 32Gb of RAM in it from the previous MP. I can't think of a good reason why it just sits and ignores the two drives which have been Pikified (SSD and HDD). Selecting each one at boot, neither does anything other than sit and stare back at me. I'm seriously considering abandoning this exercise, and buying a Mini to host the Win7 VM that I'm trying to run(Parallels needs a recent OS...).

However, this weekend I'll devote to trying to get this to run...

ta muchly,

Chris M

rthpjm · Sep 2, 2017

chrisrm9208 said:
Nope, a single Apple Cinema display, nothing complex at all. The GPU is a FX4500, and there's 32Gb of RAM in it from the previous MP. I can't think of a good reason why it just sits and ignores the two drives which have been Pikified (SSD and HDD). Selecting each one at boot, neither does anything other than sit and stare back at me. I'm seriously considering abandoning this exercise, and buying a Mini to host the Win7 VM that I'm trying to run(Parallels needs a recent OS...).

However, this weekend I'll devote to trying to get this to run...

ta muchly,

Chris M

Hi Chris,

Let me ask a few questions then, and I'll see if I can help further....

Q1. From an earlier post you say that you have two HDDs, one is spinning, and one is SSD. It sounds like the spinning HDD has 10.7 Lion on it. Is that correct?
Q2. Does the machine boot okay into Lion?
Q3. What data is on the HDD?
Q4. What data is on the SSD?
Q5. Is your FX4500 an Apple brand, or an OEM/PC brand?
Q6. Are you able to see the boot screens under normal circumstances?
Q7. When you reboot, what happens if you hold the ALT key immediately after you hear the chime?
Q8. When you reboot, what happens if you hold the Apple and V keys immediately after you hear the chime?
Q9. Have you tried a parameter RAM (PRAM) reset (chime, hold Apple ALT P R, wait until you hear a second chime, release)?
Q10. When you get to the point of "sitting there doing nothing", can you see the mouse pointer?
Q11. If you click the mouse/trackpad, then try moving the cursor, can you go to the extreme left, or the extreme right, does the cursor appear on screen and then disappear off one edge?

Suggestions:
S1. Have you tried switching ports on the GFX card? Most FX4500s have two DVI ports, and you say that you only have a single Cinema display, try moving the cable to the other port.
S2. Try using the pikify V14 script again, but do not reboot at the end. Then check the following for me please (change /Volumes/yourSSD to match the target disk - I assume you are trying to build on the SSD)
Check that there is a folder named OS X Install Data on your SSD
It should contain:

Code:

macpro:/Volumes/yourSSD root# cd OS\ X\ Install\ Data/
macpro:/Volumes/yourSSD/OS X Install Data root# ls -alh
total 11917920
drwxr-xr-x   8 root  admin   272B 31 Aug 15:12 .
drwxr-xr-x  31 root  wheel   1.1K 31 Aug 16:30 ..
-rw-r--r--@  1 root  admin   2.0K 31 Aug 15:12 .disk_label
-rw-r--r--@  1 root  admin   5.7G 31 Aug 15:12 InstallESD.dmg
-rw-r--r--@  1 root  admin   3.2K 29 Aug 02:53 PlatformSupport.plist
-rw-r--r--   1 root  admin   309K 29 Aug 02:53 boot.efi
-rw-r--r--   1 root  admin   402B 29 Aug 02:53 com.apple.Boot.plist
-rw-r--r--   1 root  wheel    21M 17 Sep  2015 prelinkedkernel

also run the commands

Code:

bless --info /Volumes/yourSSD
nvram -p
diskutil info /Volumes/yourSSD

Post the responses here and I'll review them

chrisrm9208 · Sep 2, 2017

rthpjm said:
Hi Chris,

Let me ask a few questions then, and I'll see if I can help further....

Q1. From an earlier post you say that you have two HDDs, one is spinning, and one is SSD. It sounds like the spinning HDD has 10.7 Lion on it. Is that correct?
Q2. Does the machine boot okay into Lion?
Q3. What data is on the HDD?
Q4. What data is on the SSD?
Q5. Is your FX4500 an Apple brand, or an OEM/PC brand?
Q6. Are you able to see the boot screens under normal circumstances?
Q7. When you reboot, what happens if you hold the ALT key immediately after you hear the chime?
Q8. When you reboot, what happens if you hold the Apple and V keys immediately after you hear the chime?
Q9. Have you tried a parameter RAM (PRAM) reset (chime, hold Apple ALT P R, wait until you hear a second chime, release)?
Q10. When you get to the point of "sitting there doing nothing", can you see the mouse pointer?
Q11. If you click the mouse/trackpad, then try moving the cursor, can you go to the extreme left, or the extreme right, does the cursor appear on screen and then disappear off one edge?

Suggestions:
S1. Have you tried switching ports on the GFX card? Most FX4500s have two DVI ports, and you say that you only have a single Cinema display, try moving the cable to the other port.
S2. Try using the pikify V14 script again, but do not reboot at the end. Then check the following for me please (change /Volumes/yourSSD to match the target disk - I assume you are trying to build on the SSD)
Check that there is a folder named OS X Install Data on your SSD
It should contain:

Code:

macpro:/Volumes/yourSSD root# cd OS\ X\ Install\ Data/ macpro:/Volumes/yourSSD/OS X Install Data root# ls -alh total 11917920 drwxr-xr-x 8 root admin 272B 31 Aug 15:12 . drwxr-xr-x 31 root wheel 1.1K 31 Aug 16:30 .. -rw-r--r--@ 1 root admin 2.0K 31 Aug 15:12 .disk_label -rw-r--r--@ 1 root admin 5.7G 31 Aug 15:12 InstallESD.dmg -rw-r--r--@ 1 root admin 3.2K 29 Aug 02:53 PlatformSupport.plist -rw-r--r-- 1 root admin 309K 29 Aug 02:53 boot.efi -rw-r--r-- 1 root admin 402B 29 Aug 02:53 com.apple.Boot.plist -rw-r--r-- 1 root wheel 21M 17 Sep 2015 prelinkedkernel

also run the commands

Code:

bless --info /Volumes/yourSSD nvram -p diskutil info /Volumes/yourSSD

Post the responses here and I'll review them

Q1. Yes, although I have D1(HDD/Lion), D2 (SSD/ElCap), D3 (HDD/ElCap)
Q2. Correct, Lion is OK and I'm using that now.
Q3. Backup and the results of Pikify
Q4. Nothing of any use bar the results of Pikify. It'll be a boot/system drive.
Q5. Apple
Q6. Yes, as fas as Lion is concerned in this MP
Q7. Boot selector for Lion, white screen for D2 and D3
Q8. A black screen, with a single underline character sitting about 2/3 way up the screen. This persisted until I lost interest/needed coffee.
Q9. SMC and PRAM reset done many, many times...
Q10. Nope
Q11. See Q10

Will try S1/S2 and comment,

Many thanks,

Chris M
[doublepost=1504350197][/doublepost]Haven't personalised this one yet, so still has odd directory structure...

S1 shows same picture as the other interface

Macs-Mac-Pro:ElCapitan macpromacpro$ cd OS\ X\ Install\ Data/
Macs-Mac-Pro:OS X Install Data macpromacpro$ ls -alh
total 12135968
drwxr-xr-x 8 root staff 272B 2 Sep 11:52 .
drwxrwxr-x 9 macpromacpro staff 374B 1 Sep 17:15 ..
-rw-r--r--@ 1 root staff 209B 2 Sep 11:52 .disk_label
-rw-r--r--@ 1 root staff 5.8G 2 Sep 11:52 InstallESD.dmg
-rw-r--r-- 1 macpromacpro staff 5.7K 2 Sep 11:50 PlatformSupport.plist
-rw-r--r--@ 1 macpromacpro staff 308K 2 Sep 11:50 boot.efi
-rw-r--r-- 1 macpromacpro staff 430B 2 Sep 11:50 com.apple.Boot.plist
-rw-r--r--@ 1 root wheel 21M 2 Sep 11:50 prelinkedkernel

Macs-Mac-Pro:OS X Install Data macpromacpro$ bless --info /Volumes/ElCapitan
finderinfo[0]: 140 => Blessed System Folder is /Volumes/ElCapitan/OS X Install Data
finderinfo[1]: 142 => Blessed System File is /Volumes/ElCapitan/OS X Install Data/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 140 => OS X blessed folder is /Volumes/ElCapitan/OS X Install Data
64-bit VSDB volume id: 0xDC84F39FC84D7E41

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>7DA53C16-61F6-4F5F-99E3-E3B0DE10E155</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict><dict><key>IOEFIBootOption</key><string>config=\OS X Install Data\com.apple.Boot</string></dict></array>
boot-gamma %10%06%00%00%1c%92%00%00%fdm%00%02n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8nknu%17%07%00%00%00%00%00%00%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7
boot-args
IdlePML4 %d0%0aO%01%80%ff%ff%ff
BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%7f%ff%04%00
security-mode none
prev-lang:kbd en:2
platform-uuid %00%00%00%00%00%00%10%00%80%00%00%17%f2%04@%f4
efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%b5E%c6'%fcS%b3D%a2%be%%c6jv%97@%02%02%04%04\%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00L%00O%00C%00K%00E%00D%00_%00M%00P%001%001%00_%000%000%005%00C%00_%000%008%00B%00.%00f%00d%00%00%00%7f%ff%04%00
fmm-computer-name Mac%e2%80%99s Mac Pro
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ac%df%0d%00%00%00%00%16<%a5}%f6a_O%99%e3%e3%b0%de%10%e1U%02%02%7f%ff%04%00
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00
SystemAudioVolume 8
EFIBluetoothDelay %b8%0b
csr-active-config %80%00%00%00

Macs-Mac-Pro:OS X Install Data macpromacpro$ diskutil info /Volumes/ElCapitan
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part of Whole: disk0
Device / Media Name: Yosemite

Volume Name: ElCapitan
Escaped with Unicode: ElCapitan

Mounted: Yes
Mount Point: /Volumes/ElCapitan
Escaped with Unicode: /Volumes/ElCapitan

File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 16384 KB at offset 0x37a000
Owners: Enabled

Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 4C38BE6E-237D-3C5A-8B62-AF8976D7CEA8

Total Size: 119.2 GB (119174365184 Bytes) (exactly 232762432 512-Byte-Blocks)
Volume Free Space: 112.7 GB (112735846400 Bytes) (exactly 220187200 512-Byte-Blocks)
Device Block Size: 512 Bytes

Read-Only Media: No
Read-Only Volume: No
Ejectable: No

Whole: No
Internal: Yes
Solid State: Yes
Device Location: "Bay 2"
[doublepost=1504351488][/doublepost]

chrisrm9208 said:
Q1. Yes, although I have D1(HDD/Lion), D2 (SSD/ElCap), D3 (HDD/ElCap)
Q2. Correct, Lion is OK and I'm using that now.
Q3. Backup and the results of Pikify
Q4. Nothing of any use bar the results of Pikify. It'll be a boot/system drive.
Q5. Apple
Q6. Yes, as fas as Lion is concerned in this MP
Q7. Boot selector for Lion, white screen for D2 and D3
Q8. A black screen, with a single underline character sitting about 2/3 way up the screen. This persisted until I lost interest/needed coffee.
Q9. SMC and PRAM reset done many, many times...
Q10. Nope
Q11. See Q10

Will try S1/S2 and comment,

Many thanks,

Chris M
[doublepost=1504350197][/doublepost]Haven't personalised this one yet, so still has odd directory structure...

S1 shows same picture as the other interface

Macs-Mac-Pro:ElCapitan macpromacpro$ cd OS\ X\ Install\ Data/
Macs-Mac-Pro:OS X Install Data macpromacpro$ ls -alh
total 12135968
drwxr-xr-x 8 root staff 272B 2 Sep 11:52 .
drwxrwxr-x 9 macpromacpro staff 374B 1 Sep 17:15 ..
-rw-r--r--@ 1 root staff 209B 2 Sep 11:52 .disk_label
-rw-r--r--@ 1 root staff 5.8G 2 Sep 11:52 InstallESD.dmg
-rw-r--r-- 1 macpromacpro staff 5.7K 2 Sep 11:50 PlatformSupport.plist
-rw-r--r--@ 1 macpromacpro staff 308K 2 Sep 11:50 boot.efi
-rw-r--r-- 1 macpromacpro staff 430B 2 Sep 11:50 com.apple.Boot.plist
-rw-r--r--@ 1 root wheel 21M 2 Sep 11:50 prelinkedkernel

Macs-Mac-Pro:OS X Install Data macpromacpro$ bless --info /Volumes/ElCapitan
finderinfo[0]: 140 => Blessed System Folder is /Volumes/ElCapitan/OS X Install Data
finderinfo[1]: 142 => Blessed System File is /Volumes/ElCapitan/OS X Install Data/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 140 => OS X blessed folder is /Volumes/ElCapitan/OS X Install Data
64-bit VSDB volume id: 0xDC84F39FC84D7E41

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>7DA53C16-61F6-4F5F-99E3-E3B0DE10E155</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict><dict><key>IOEFIBootOption</key><string>config=\OS X Install Data\com.apple.Boot</string></dict></array>
boot-gamma %10%06%00%00%1c%92%00%00%fdm%00%02n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8nknu%17%07%00%00%00%00%00%00%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7
boot-args
IdlePML4 %d0%0aO%01%80%ff%ff%ff
BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%7f%ff%04%00
security-mode none
prev-lang:kbd en:2
platform-uuid %00%00%00%00%00%00%10%00%80%00%00%17%f2%04@%f4
efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%b5E%c6'%fcS%b3D%a2%be%%c6jv%97@%02%02%04%04\%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00L%00O%00C%00K%00E%00D%00_%00M%00P%001%001%00_%000%000%005%00C%00_%000%008%00B%00.%00f%00d%00%00%00%7f%ff%04%00
fmm-computer-name Mac%e2%80%99s Mac Pro
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ac%df%0d%00%00%00%00%16<%a5}%f6a_O%99%e3%e3%b0%de%10%e1U%02%02%7f%ff%04%00
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00
SystemAudioVolume 8
EFIBluetoothDelay %b8%0b
csr-active-config %80%00%00%00

Macs-Mac-Pro:OS X Install Data macpromacpro$ diskutil info /Volumes/ElCapitan
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part of Whole: disk0
Device / Media Name: Yosemite

Volume Name: ElCapitan
Escaped with Unicode: ElCapitan

Mounted: Yes
Mount Point: /Volumes/ElCapitan
Escaped with Unicode: /Volumes/ElCapitan

File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 16384 KB at offset 0x37a000
Owners: Enabled

Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 4C38BE6E-237D-3C5A-8B62-AF8976D7CEA8

Total Size: 119.2 GB (119174365184 Bytes) (exactly 232762432 512-Byte-Blocks)
Volume Free Space: 112.7 GB (112735846400 Bytes) (exactly 220187200 512-Byte-Blocks)
Device Block Size: 512 Bytes

Read-Only Media: No
Read-Only Volume: No
Ejectable: No

Whole: No
Internal: Yes
Solid State: Yes
Device Location: "Bay 2"

And now here I am, buffoon that I am, with a working ElCap install and no real idea whether it was the port change or the blessing that did the job...

In fact, I still have the broken D2 install that I can experiment with; would that be of use?

An extremely grateful Chris M
[doublepost=1504352096][/doublepost]

chrisrm9208 said:
Q1. Yes, although I have D1(HDD/Lion), D2 (SSD/ElCap), D3 (HDD/ElCap)
Q2. Correct, Lion is OK and I'm using that now.
Q3. Backup and the results of Pikify
Q4. Nothing of any use bar the results of Pikify. It'll be a boot/system drive.
Q5. Apple
Q6. Yes, as fas as Lion is concerned in this MP
Q7. Boot selector for Lion, white screen for D2 and D3
Q8. A black screen, with a single underline character sitting about 2/3 way up the screen. This persisted until I lost interest/needed coffee.
Q9. SMC and PRAM reset done many, many times...
Q10. Nope
Q11. See Q10

Will try S1/S2 and comment,

Many thanks,

Chris M
[doublepost=1504350197][/doublepost]Haven't personalised this one yet, so still has odd directory structure...

S1 shows same picture as the other interface

Macs-Mac-Pro:ElCapitan macpromacpro$ cd OS\ X\ Install\ Data/
Macs-Mac-Pro:OS X Install Data macpromacpro$ ls -alh
total 12135968
drwxr-xr-x 8 root staff 272B 2 Sep 11:52 .
drwxrwxr-x 9 macpromacpro staff 374B 1 Sep 17:15 ..
-rw-r--r--@ 1 root staff 209B 2 Sep 11:52 .disk_label
-rw-r--r--@ 1 root staff 5.8G 2 Sep 11:52 InstallESD.dmg
-rw-r--r-- 1 macpromacpro staff 5.7K 2 Sep 11:50 PlatformSupport.plist
-rw-r--r--@ 1 macpromacpro staff 308K 2 Sep 11:50 boot.efi
-rw-r--r-- 1 macpromacpro staff 430B 2 Sep 11:50 com.apple.Boot.plist
-rw-r--r--@ 1 root wheel 21M 2 Sep 11:50 prelinkedkernel

Macs-Mac-Pro:OS X Install Data macpromacpro$ bless --info /Volumes/ElCapitan
finderinfo[0]: 140 => Blessed System Folder is /Volumes/ElCapitan/OS X Install Data
finderinfo[1]: 142 => Blessed System File is /Volumes/ElCapitan/OS X Install Data/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 140 => OS X blessed folder is /Volumes/ElCapitan/OS X Install Data
64-bit VSDB volume id: 0xDC84F39FC84D7E41

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>7DA53C16-61F6-4F5F-99E3-E3B0DE10E155</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict><dict><key>IOEFIBootOption</key><string>config=\OS X Install Data\com.apple.Boot</string></dict></array>
boot-gamma %10%06%00%00%1c%92%00%00%fdm%00%02n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8nknu%17%07%00%00%00%00%00%00%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7
boot-args
IdlePML4 %d0%0aO%01%80%ff%ff%ff
BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%7f%ff%04%00
security-mode none
prev-lang:kbd en:2
platform-uuid %00%00%00%00%00%00%10%00%80%00%00%17%f2%04@%f4
efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%b5E%c6'%fcS%b3D%a2%be%%c6jv%97@%02%02%04%04\%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00L%00O%00C%00K%00E%00D%00_%00M%00P%001%001%00_%000%000%005%00C%00_%000%008%00B%00.%00f%00d%00%00%00%7f%ff%04%00
fmm-computer-name Mac%e2%80%99s Mac Pro
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ac%df%0d%00%00%00%00%16<%a5}%f6a_O%99%e3%e3%b0%de%10%e1U%02%02%7f%ff%04%00
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00
SystemAudioVolume 8
EFIBluetoothDelay %b8%0b
csr-active-config %80%00%00%00

Macs-Mac-Pro:OS X Install Data macpromacpro$ diskutil info /Volumes/ElCapitan
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part of Whole: disk0
Device / Media Name: Yosemite

Volume Name: ElCapitan
Escaped with Unicode: ElCapitan

Mounted: Yes
Mount Point: /Volumes/ElCapitan
Escaped with Unicode: /Volumes/ElCapitan

File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 16384 KB at offset 0x37a000
Owners: Enabled

Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 4C38BE6E-237D-3C5A-8B62-AF8976D7CEA8

Total Size: 119.2 GB (119174365184 Bytes) (exactly 232762432 512-Byte-Blocks)
Volume Free Space: 112.7 GB (112735846400 Bytes) (exactly 220187200 512-Byte-Blocks)
Device Block Size: 512 Bytes

Read-Only Media: No
Read-Only Volume: No
Ejectable: No

Whole: No
Internal: Yes
Solid State: Yes
Device Location: "Bay 2"
[doublepost=1504351488][/doublepost]

And now here I am, buffoon that I am, with a working ElCap install and no real idea whether it was the port change or the blessing that did the job...

In fact, I still have the broken D2 install that I can experiment with; would that be of use?

An extremely grateful Chris M

Working but an oddity occurs. There's a password been set for this, and I don't recall being asked for a password on the ElCap install. There's the 'Use your Apple ID to log in' bit, but that's the only place where a password prompt was given. This means that, right now, i can't install anything like Boot64 as I can't open the thing. I think resetpassword may be the only way forward...
[doublepost=1504352338][/doublepost]

chrisrm9208 said:
Q1. Yes, although I have D1(HDD/Lion), D2 (SSD/ElCap), D3 (HDD/ElCap)
Q2. Correct, Lion is OK and I'm using that now.
Q3. Backup and the results of Pikify
Q4. Nothing of any use bar the results of Pikify. It'll be a boot/system drive.
Q5. Apple
Q6. Yes, as fas as Lion is concerned in this MP
Q7. Boot selector for Lion, white screen for D2 and D3
Q8. A black screen, with a single underline character sitting about 2/3 way up the screen. This persisted until I lost interest/needed coffee.
Q9. SMC and PRAM reset done many, many times...
Q10. Nope
Q11. See Q10

Will try S1/S2 and comment,

Many thanks,

Chris M
[doublepost=1504350197][/doublepost]Haven't personalised this one yet, so still has odd directory structure...

S1 shows same picture as the other interface

Macs-Mac-Pro:ElCapitan macpromacpro$ cd OS\ X\ Install\ Data/
Macs-Mac-Pro:OS X Install Data macpromacpro$ ls -alh
total 12135968
drwxr-xr-x 8 root staff 272B 2 Sep 11:52 .
drwxrwxr-x 9 macpromacpro staff 374B 1 Sep 17:15 ..
-rw-r--r--@ 1 root staff 209B 2 Sep 11:52 .disk_label
-rw-r--r--@ 1 root staff 5.8G 2 Sep 11:52 InstallESD.dmg
-rw-r--r-- 1 macpromacpro staff 5.7K 2 Sep 11:50 PlatformSupport.plist
-rw-r--r--@ 1 macpromacpro staff 308K 2 Sep 11:50 boot.efi
-rw-r--r-- 1 macpromacpro staff 430B 2 Sep 11:50 com.apple.Boot.plist
-rw-r--r--@ 1 root wheel 21M 2 Sep 11:50 prelinkedkernel

Macs-Mac-Pro:OS X Install Data macpromacpro$ bless --info /Volumes/ElCapitan
finderinfo[0]: 140 => Blessed System Folder is /Volumes/ElCapitan/OS X Install Data
finderinfo[1]: 142 => Blessed System File is /Volumes/ElCapitan/OS X Install Data/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 140 => OS X blessed folder is /Volumes/ElCapitan/OS X Install Data
64-bit VSDB volume id: 0xDC84F39FC84D7E41

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>7DA53C16-61F6-4F5F-99E3-E3B0DE10E155</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict><dict><key>IOEFIBootOption</key><string>config=\OS X Install Data\com.apple.Boot</string></dict></array>
boot-gamma %10%06%00%00%1c%92%00%00%fdm%00%02n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8nknu%17%07%00%00%00%00%00%00%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7
boot-args
IdlePML4 %d0%0aO%01%80%ff%ff%ff
BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%7f%ff%04%00
security-mode none
prev-lang:kbd en:2
platform-uuid %00%00%00%00%00%00%10%00%80%00%00%17%f2%04@%f4
efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%b5E%c6'%fcS%b3D%a2%be%%c6jv%97@%02%02%04%04\%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00L%00O%00C%00K%00E%00D%00_%00M%00P%001%001%00_%000%000%005%00C%00_%000%008%00B%00.%00f%00d%00%00%00%7f%ff%04%00
fmm-computer-name Mac%e2%80%99s Mac Pro
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ac%df%0d%00%00%00%00%16<%a5}%f6a_O%99%e3%e3%b0%de%10%e1U%02%02%7f%ff%04%00
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00
SystemAudioVolume 8
EFIBluetoothDelay %b8%0b
csr-active-config %80%00%00%00

Macs-Mac-Pro:OS X Install Data macpromacpro$ diskutil info /Volumes/ElCapitan
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part of Whole: disk0
Device / Media Name: Yosemite

Volume Name: ElCapitan
Escaped with Unicode: ElCapitan

Mounted: Yes
Mount Point: /Volumes/ElCapitan
Escaped with Unicode: /Volumes/ElCapitan

File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 16384 KB at offset 0x37a000
Owners: Enabled

Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 4C38BE6E-237D-3C5A-8B62-AF8976D7CEA8

Total Size: 119.2 GB (119174365184 Bytes) (exactly 232762432 512-Byte-Blocks)
Volume Free Space: 112.7 GB (112735846400 Bytes) (exactly 220187200 512-Byte-Blocks)
Device Block Size: 512 Bytes

Read-Only Media: No
Read-Only Volume: No
Ejectable: No

Whole: No
Internal: Yes
Solid State: Yes
Device Location: "Bay 2"
[doublepost=1504351488][/doublepost]

And now here I am, buffoon that I am, with a working ElCap install and no real idea whether it was the port change or the blessing that did the job...

In fact, I still have the broken D2 install that I can experiment with; would that be of use?

An extremely grateful Chris M
[doublepost=1504352096][/doublepost]

Working but an oddity occurs. There's a password been set for this, and I don't recall being asked for a password on the ElCap install. There's the 'Use your Apple ID to log in' bit, but that's the only place where a password prompt was given. This means that, right now, i can't install anything like Boot64 as I can't open the thing. I think resetpassword may be the only way forward...

<phew> ElCap is brighter than Lion... The Apple Clod password has the feature to replace itself and split the thing into two passwords, one for the Clod and one for the Mac. Boot64 now installed. As you were...

rthpjm · Sep 2, 2017

chrisrm9208 said:
Q1. Yes, although I have D1(HDD/Lion), D2 (SSD/ElCap), D3 (HDD/ElCap)
Q2. Correct, Lion is OK and I'm using that now.
Q3. Backup and the results of Pikify
Q4. Nothing of any use bar the results of Pikify. It'll be a boot/system drive.
Q5. Apple
Q6. Yes, as fas as Lion is concerned in this MP
Q7. Boot selector for Lion, white screen for D2 and D3
Q8. A black screen, with a single underline character sitting about 2/3 way up the screen. This persisted until I lost interest/needed coffee.
Q9. SMC and PRAM reset done many, many times...
Q10. Nope
Q11. See Q10

Will try S1/S2 and comment,

Many thanks,

Chris M
[doublepost=1504350197][/doublepost]Haven't personalised this one yet, so still has odd directory structure...

S1 shows same picture as the other interface

Macs-Mac-Pro:ElCapitan macpromacpro$ cd OS\ X\ Install\ Data/
Macs-Mac-Pro:OS X Install Data macpromacpro$ ls -alh
total 12135968
drwxr-xr-x 8 root staff 272B 2 Sep 11:52 .
drwxrwxr-x 9 macpromacpro staff 374B 1 Sep 17:15 ..
-rw-r--r--@ 1 root staff 209B 2 Sep 11:52 .disk_label
-rw-r--r--@ 1 root staff 5.8G 2 Sep 11:52 InstallESD.dmg
-rw-r--r-- 1 macpromacpro staff 5.7K 2 Sep 11:50 PlatformSupport.plist
-rw-r--r--@ 1 macpromacpro staff 308K 2 Sep 11:50 boot.efi
-rw-r--r-- 1 macpromacpro staff 430B 2 Sep 11:50 com.apple.Boot.plist
-rw-r--r--@ 1 root wheel 21M 2 Sep 11:50 prelinkedkernel

Macs-Mac-Pro:OS X Install Data macpromacpro$ bless --info /Volumes/ElCapitan
finderinfo[0]: 140 => Blessed System Folder is /Volumes/ElCapitan/OS X Install Data
finderinfo[1]: 142 => Blessed System File is /Volumes/ElCapitan/OS X Install Data/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 140 => OS X blessed folder is /Volumes/ElCapitan/OS X Install Data
64-bit VSDB volume id: 0xDC84F39FC84D7E41

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>7DA53C16-61F6-4F5F-99E3-E3B0DE10E155</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict><dict><key>IOEFIBootOption</key><string>config=\OS X Install Data\com.apple.Boot</string></dict></array>
boot-gamma %10%06%00%00%1c%92%00%00%fdm%00%02n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8nknu%17%07%00%00%00%00%00%00%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7
boot-args
IdlePML4 %d0%0aO%01%80%ff%ff%ff
BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%7f%ff%04%00
security-mode none
prev-lang:kbd en:2
platform-uuid %00%00%00%00%00%00%10%00%80%00%00%17%f2%04@%f4
efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%b5E%c6'%fcS%b3D%a2%be%%c6jv%97@%02%02%04%04\%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00L%00O%00C%00K%00E%00D%00_%00M%00P%001%001%00_%000%000%005%00C%00_%000%008%00B%00.%00f%00d%00%00%00%7f%ff%04%00
fmm-computer-name Mac%e2%80%99s Mac Pro
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ac%df%0d%00%00%00%00%16<%a5}%f6a_O%99%e3%e3%b0%de%10%e1U%02%02%7f%ff%04%00
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00
SystemAudioVolume 8
EFIBluetoothDelay %b8%0b
csr-active-config %80%00%00%00

Macs-Mac-Pro:OS X Install Data macpromacpro$ diskutil info /Volumes/ElCapitan
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part of Whole: disk0
Device / Media Name: Yosemite

Volume Name: ElCapitan
Escaped with Unicode: ElCapitan

Mounted: Yes
Mount Point: /Volumes/ElCapitan
Escaped with Unicode: /Volumes/ElCapitan

File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 16384 KB at offset 0x37a000
Owners: Enabled

Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 4C38BE6E-237D-3C5A-8B62-AF8976D7CEA8

Total Size: 119.2 GB (119174365184 Bytes) (exactly 232762432 512-Byte-Blocks)
Volume Free Space: 112.7 GB (112735846400 Bytes) (exactly 220187200 512-Byte-Blocks)
Device Block Size: 512 Bytes

Read-Only Media: No
Read-Only Volume: No
Ejectable: No

Whole: No
Internal: Yes
Solid State: Yes
Device Location: "Bay 2"
[doublepost=1504351488][/doublepost]

And now here I am, buffoon that I am, with a working ElCap install and no real idea whether it was the port change or the blessing that did the job...

In fact, I still have the broken D2 install that I can experiment with; would that be of use?

An extremely grateful Chris M
[doublepost=1504352096][/doublepost]

Working but an oddity occurs. There's a password been set for this, and I don't recall being asked for a password on the ElCap install. There's the 'Use your Apple ID to log in' bit, but that's the only place where a password prompt was given. This means that, right now, i can't install anything like Boot64 as I can't open the thing. I think resetpassword may be the only way forward...
[doublepost=1504352338][/doublepost]

<phew> ElCap is brighter than Lion... The Apple Clod password has the feature to replace itself and split the thing into two passwords, one for the Clod and one for the Mac. Boot64 now installed. As you were...

I'm glad it eventually worked for you.

chrisrm9208 · Sep 2, 2017

rthpjm said:
I'm glad it eventually worked for you.

I'm always struck by the difference between a talented amateur (me) and someone who actually knows what they're doing

Many thanks!

rthpjm · Sep 2, 2017

chrisrm9208 said:
I'm always struck by the difference between a talented amateur (me) and someone who actually knows what they're doing

Many thanks!

Hmmm....

It looks like your machine might have been queued up for a FIRMWARE upgrade...

chrisrm9208 said:
efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>27C645B5-53FC-44B3-A2BE-25C66A769740</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\LOCKED_MP11_005C_08B.fd</string></dict></array>%00

chrisrm9208 · Sep 2, 2017

Interesting; say more, please...

rthpjm · Sep 3, 2017

chrisrm9208 said:
Interesting; say more, please...

It's hard to say for sure. It could just be a residue of some other install, or it may be part of your install attempt.

Earlier you said

chrisrm9208 said:
has been supplied with the requisite ElCap installer (10.11.3) in Applications

Did you stick with that version as the source/donor installer?
I can have a dig into that version to see if it was bundled with an EFI updater, but it is more likely to be a Lion update that pulled in the EFI firmware update, because Apple stopped support of the classic MacPro after lion (they wouldn't ship an EFI update for an unsupported machine, I.e. After Lion).
Did you get any Lion updates on the previous machine and or this one, before you started down the El Capitan route?

The combination might explain the symptoms you experienced...
IF, your default display output path was going to a phantom monitor (other port believing it had a display connected even though there was no physical connection - it's been reported by others - seems to only affect Nvidia cards), AND there was an EFI firmware package to install, you might get to a point where the first machine was mid way through the firmware upgrade, but you could not see the progress bar. IF at this point you removed the power, you "might" have bricked the machine with an incomplete firmware update.
This is just an assumption for the first machine, I'm simply speculating.

On the second machine (where we know there was an efi update queued from the nvram dump), this may explain the "not booting". I've had firmware updates do this to my machine too, just sit there and do nothing. A reboot usually clears it.

I think you may have just been unlucky with the "phantom" display, because you couldn't see any progress bar on the first machine, and a little luckier on the second machine....

If you want to see if there are still residual files, then use diskutil (from a terminal) to mount disk1s1. This is the small EFI partition, and is where items like EFI code and/or updates are traditionally stored.
(Review the efi-apple-payload0 variable as I posted to see where I'm getting the values from)

Code:

diskutil mount disk1s1
ls /Volumes/EFI/EFI/APPLE

If there is a FIRMWARE folder present then it still thinks there should be an update.
If not, then the efi-apple-payload0 variable might just be residual, but may have been interfering...

Tidy up...

Code:

cd
diskutil unmount disk1s1

It looks like you can check your machine's boot rom version
Go to the Apple menu
Hold the ALT key (About this Mac should change to System Information - the ALT key is a shortcut)
The System Information window will open, it should have Hardware selected, look for the Boot ROM Version

My system is a MacPro 2006 (1,1) which I upgraded to a 2,1. My Boot ROM Version is MP21.007F.B06.

On your system I'm expecting that the string will be MP11.005C.08B (which I have derived from the efi-apple-payload0 NVRAM variable)...

rthpjm · Sep 4, 2017

rthpjm said:
It's hard to say for sure. It could just be a residue of some other install, or it may be part of your install attempt.

Earlier you said

Did you stick with that version as the source/donor installer?
I can have a dig into that version to see if it was bundled with an EFI updater, but it is more likely to be a Lion update that pulled in the EFI firmware update, because Apple stopped support of the classic MacPro after lion (they wouldn't ship an EFI update for an unsupported machine, I.e. After Lion).
Did you get any Lion updates on the previous machine and or this one, before you started down the El Capitan route?

The combination might explain the symptoms you experienced...
IF, your default display output path was going to a phantom monitor (other port believing it had a display connected even though there was no physical connection - it's been reported by others - seems to only affect Nvidia cards), AND there was an EFI firmware package to install, you might get to a point where the first machine was mid way through the firmware upgrade, but you could not see the progress bar. IF at this point you removed the power, you "might" have bricked the machine with an incomplete firmware update.
This is just an assumption for the first machine, I'm simply speculating.

On the second machine (where we know there was an efi update queued from the nvram dump), this may explain the "not booting". I've had firmware updates do this to my machine too, just sit there and do nothing. A reboot usually clears it.

I think you may have just been unlucky with the "phantom" display, because you couldn't see any progress bar on the first machine, and a little luckier on the second machine....

If you want to see if there are still residual files, then use diskutil (from a terminal) to mount disk1s1. This is the small EFI partition, and is where items like EFI code and/or updates are traditionally stored.
(Review the efi-apple-payload0 variable as I posted to see where I'm getting the values from)

Code:

diskutil mount disk1s1 ls /Volumes/EFI/EFI/APPLE

If there is a FIRMWARE folder present then it still thinks there should be an update.
If not, then the efi-apple-payload0 variable might just be residual, but may have been interfering...

Tidy up...

Code:

cd diskutil unmount disk1s1

It looks like you can check your machine's boot rom version
Go to the Apple menu
Hold the ALT key (About this Mac should change to System Information - the ALT key is a shortcut)
The System Information window will open, it should have Hardware selected, look for the Boot ROM Version

My system is a MacPro 2006 (1,1) which I upgraded to a 2,1. My Boot ROM Version is MP21.007F.B06.

On your system I'm expecting that the string will be MP11.005C.08B (which I have derived from the efi-apple-payload0 NVRAM variable)...

If there is a firmware update pending, you probably need to manually launch it now...
https://support.apple.com/kb/DL309?viewlocale=en_US&locale=en_US

Here is the up to date list of EFI and SMC firmware from Apple
https://support.apple.com/en-gb/HT201518

chrisrm9208 · Sep 5, 2017

Apologies for not replying promptly, have been poking Parallels re mouse handling...

I have the same Boot ROM version as you, mostly because I used Netka's upgrade tool (I, too, have MP2006). SMC is still left at 1.7f10, and there's nothing sitting on disk1s1 Volumes/EFI/EFI/APPLE except something called EXTENSIONS.

I'll take some time later on to poke the other HDD to se if I can get that to misbehave once more and comment here on it.

rthpjm · Sep 6, 2017

chrisrm9208 said:
Apologies for not replying promptly, have been poking Parallels re mouse handling...

I have the same Boot ROM version as you, mostly because I used Netka's upgrade tool (I, too, have MP2006). SMC is still left at 1.7f10, and there's nothing sitting on disk1s1 Volumes/EFI/EFI/APPLE except something called EXTENSIONS.

I'll take some time later on to poke the other HDD to se if I can get that to misbehave once more and comment here on it.

In that case, the NVRAM variable makes no sense, it must be "old", residue from a previous incarnation prior to your upgrade of the firmware to the 2,1 variant.
You could boot into the Recovery HD, open a Terminal from the Utilities menu, and use the nvram -d efi-apple-payload0 command to delete the entry.

A PRAM reset should also clear it I think...

echase · Sep 8, 2017

First off, big thanks to everyone here who is working to keep these workhorses running.

My MP 1,1 has been running pretty well in 10.9 for some time, but my Macbook pro gave up the ghost recently, so I want to pull the SSD which has El Cap, and patch it to run in the MP so I can have my user environment all setup, and can get back to work.

The MBP is nearly non-bootable, but works fine in target disk mode. So, I've replaced both boot.efi files with the latest from Pike's site, and it shows up when option-booting. HOWEVER, when I select the volume, it freezes for about 30 seconds, then boots off of another volume.

I've done:
bless --folder /volumes/drive/System/Library/Coreservices --file /volumes/drive/System/Library/Coreservices/boot.efi --setBoot

That didn't change anything. I can't boot into El Cap on any of my hardware now, so repairing permissions does not seem possible. Is there something else I can try?

For what it's worth the boot.efi files do NOT have the little terminal screen icon (like they do on my working 10.9 volume)

Here's bless --info:

finderinfo[0]: 3127991 => Blessed System Folder is /Volumes/MBPSSD/System/Library/CoreServices

finderinfo[1]: 27656424 => Blessed System File is /Volumes/MBPSSD/System/Library/CoreServices/boot.efi

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 3127991 => OS X blessed folder is /Volumes/MBPSSD/System/Library/CoreServices

64-bit VSDB volume id: 0x2090C1E17EAD1475

Ant3000 · Sep 8, 2017

My initial thought would be that the MBP version of El Cap will not run on the Mac Pro as it would be a custom install for the original machine and therefore not be compatible with the MP. I would suspect that you may need to reinstall El Cap with it attached to the MP either by Firewire or installed in a drive bay. As I understand it the architecture of these machines is quite different - as in that the MBP can run El Cap without the need for the boot.efi stuff.
I am sure others with more knowledge can advise further.

rthpjm · Sep 9, 2017

echase said:
First off, big thanks to everyone here who is working to keep these workhorses running.

My MP 1,1 has been running pretty well in 10.9 for some time, but my Macbook pro gave up the ghost recently, so I want to pull the SSD which has El Cap, and patch it to run in the MP so I can have my user environment all setup, and can get back to work.

The MBP is nearly non-bootable, but works fine in target disk mode. So, I've replaced both boot.efi files with the latest from Pike's site, and it shows up when option-booting. HOWEVER, when I select the volume, it freezes for about 30 seconds, then boots off of another volume.

I've done:
bless --folder /volumes/drive/System/Library/Coreservices --file /volumes/drive/System/Library/Coreservices/boot.efi --setBoot

That didn't change anything. I can't boot into El Cap on any of my hardware now, so repairing permissions does not seem possible. Is there something else I can try?

For what it's worth the boot.efi files do NOT have the little terminal screen icon (like they do on my working 10.9 volume)

Here's bless --info:

finderinfo[0]: 3127991 => Blessed System Folder is /Volumes/MBPSSD/System/Library/CoreServices

finderinfo[1]: 27656424 => Blessed System File is /Volumes/MBPSSD/System/Library/CoreServices/boot.efi

finderinfo[2]: 0 => Open-folder linked list empty

finderinfo[3]: 0 => No alternate OS blessed file/folder

finderinfo[4]: 0 => Unused field unset

finderinfo[5]: 3127991 => OS X blessed folder is /Volumes/MBPSSD/System/Library/CoreServices

64-bit VSDB volume id: 0x2090C1E17EAD1475

Check the file size of the boot.efi file at
/Volumes/MBPSSD/System/Library/CoreServices/boot.efi

The Apple version is around 600kb, the Pike version is just over 300kb

DukeBoy · Sep 9, 2017

Hi! Thanks very much for this hack! It has worked for me so far.

I have, however, run into a serious issue for me. I am setting up this computer as an audio workstation. I use some high end apps and plugins. One of these - Waves - is presenting an issue I can't resolve: When I open one of its plugins in a host application the screen for the plugin does not appear.

I have tried everything I can think of, but no luck so far. I do believe the issue has to do with your hack (I don't have this issue on my MacBook Pro running ElCapitan).

If possible, please advise me on a solution.

Thanks!

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
Current stable release is version 1.2

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; I suggest Lion 10.7 because that's what I've tested this version on!

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...

if you are using El Capitan to install another copy of El Capitan, and 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 ~~(hint: try holding the C key immediately after you hear the start up chime)... (hint 2: disable SIP before you start)~~
(hint: you will need to reboot, then hold down the ALT key to enter the boot chooser)

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 (hint: try holding the C key immediately after you hear the start up chime)...

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

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (pikifyApp-1-2.tar.zip) = 2ceb19954ddec82cc42275e4c7ea0ea8

rthpjm · Sep 12, 2017

DukeBoy said:
Hi! Thanks very much for this hack! It has worked for me so far.

I have, however, run into a serious issue for me. I am setting up this computer as an audio workstation. I use some high end apps and plugins. One of these - Waves - is presenting an issue I can't resolve: When I open one of its plugins in a host application the screen for the plugin does not appear.

I have tried everything I can think of, but no luck so far. I do believe the issue has to do with your hack (I don't have this issue on my MacBook Pro running ElCapitan).

If possible, please advise me on a solution.

Thanks!

It's not my hack. Many people have contributed to keeping these classic Mac Pros running. My efforts are simply around automating the method (providing an installer of installers)
It's unlikely to be an issue with the modifications. The mods simply allow the machine to boot. No other changes are made to the core OS.
It's most likely just an App issue.
Worst case? It could be that the App is using a function call that relies on a specific set of hardware features (CPU capabilities like SSE4) which these old Mac Pros simply don'y have.
Best case? It's just a missing window, possibly rendered off screen.

Can you answer these questions? (With your app running)

Click on the App icon in the Dock. Does the Menu bar show the Waves menus?
If you right click the Waves icon in the dock when it is running, does it say "Application not responding"?
If not, what happens if you goto the menus, click Window > Bring all to front?
At the bottom of the window menu there is usually a list of window names. Is there a window with a name the you cannot see? What happens if you click it?
Quit your app. Hold down the ALT key and start your app. Does the window appear?
Did you ever make it go full screen? Try holding down the CTRL key and then pressing the right arrow key. Is it on Desktop 2?
You should have a Mission Control icon in the dock, click it. Can you see your App window?
Try resetting/changing the display resolution: System Preferences -> Displays. This will often recover a missing window.
Have you tried deleting the App's preference file?

DukeBoy · Sep 12, 2017

rthpjm said:
It's not my hack. Many people have contributed to keeping these classic Mac Pros running. My efforts are simply around automating the method (providing an installer of installers)

It's unlikely to be an issue with the modifications. The mods simply allow the machine to boot. No other changes are made to the core OS.

It's most likely just an App issue.

Worst case? It could be that the App is using a function call that relies on a specific set of hardware features (CPU capabilities like SSE4) which these old Mac Pros simply don'y have.

Best case? It's just a missing window, possibly rendered off screen.

Can you answer these questions? (With your app running)

Click on the App icon in the Dock. Does the Menu bar show the Waves menus?

If you right click the Waves icon in the dock when it is running, does it say "Application not responding"?

If not, what happens if you goto the menus, click Window > Bring all to front?

At the bottom of the window menu there is usually a list of window names. Is there a window with a name the you cannot see? What happens if you click it?

Quit your app. Hold down the ALT key and start your app. Does the window appear?

Did you ever make it go full screen? Try holding down the CTRL key and then pressing the right arrow key. Is it on Desktop 2?

You should have a Mission Control icon in the dock, click it. Can you see your App window?

Try resetting/changing the display resolution: System Preferences -> Displays. This will often recover a missing window.

Have you tried deleting the App's preference file?

Thanks for the response! I did more research after posting this message. I found that there is a fairly common problem with audio plugin GUI's and El Capitan that causes a blank or missing GUI. I also had purchased an ATI Radeon 5770 card for my aging Mac Pro 1,1. Turns out the 5770 resolved the GUI problem! I apologize for the inconvenience. Thanks!

sdogalex · Sep 17, 2017

Not sure if anyone still uses this, but I accidentally purchased a gt9500 thinking it would work, but it doesn't. Is there any way to flash it to work on the mac pro?

Antirational · Sep 19, 2017

Hello,

Very nice. I found it today, that I can update my Mac Pro 1.1 to El Capitan.
I tried to create a USB Installer. But it did not work

I created on my MacBook Pro with pikify3.1.V14. Everything was good. But after the terminal said everything is fine the USB Stick did not change the name into OS X Install ...
What should I do? On the Post on page 56 I read, that V14 can create a USB Stick? But I think I did not unterstand correctly?!
I think there are other Versions, too. Because I have no System on the Mac Pro ;( I did not use the Mac a long time, because I have also a Mac Pro 5.1.
So my Question:
Can I create a USB Stick to install el capitan on my Mac Pro 1.1?

sdogalex · Sep 19, 2017

Antirational said:
Hello,

Very nice. I found it today, that I can update my Mac Pro 1.1 to El Capitan.
I tried to create a USB Installer. But it did not work I created on my MacBook Pro with pikify3.1.V14. Everything was good. But after the terminal said everything is fine the USB Stick did not change the name into OS X Install ...
What should I do? On the Post on page 56 I read, that V14 can create a USB Stick? But I think I did not unterstand correctly?!
I think there are other Versions, too. Because I have no System on the Mac Pro ;( I did not use the Mac a long time, because I have also a Mac Pro 5.1.
So my Question:
Can I create a USB Stick to install el capitan on my Mac Pro 1.1?

If you haven't already, try using the following steps found in this video:

I installed El Capitan using the method above and it works perfectly fine with a new GPU added to it.

Let me know if it works

Ant3000 · Sep 19, 2017

Antirational said:
Hello,

Very nice. I found it today, that I can update my Mac Pro 1.1 to El Capitan.
I tried to create a USB Installer. But it did not work I created on my MacBook Pro with pikify3.1.V14. Everything was good. But after the terminal said everything is fine the USB Stick did not change the name into OS X Install ...
What should I do? On the Post on page 56 I read, that V14 can create a USB Stick? But I think I did not unterstand correctly?!
I think there are other Versions, too. Because I have no System on the Mac Pro ;( I did not use the Mac a long time, because I have also a Mac Pro 5.1.
So my Question:
Can I create a USB Stick to install el capitan on my Mac Pro 1.1?

Short answer is yes but you need to have enough RAM installed and of the right size modules. That would be 12gb and no 512mb sticks - perhaps no 1gb sticks either. Have you followed the instructions regarding this as a lot of problems are caused by not understanding this.

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

macrumors member

macrumors member

macrumors 6502a

macrumors 6502a

macrumors member

macrumors 6502a

macrumors member

macrumors 6502a

macrumors member

macrumors 6502a

macrumors member

macrumors 6502a

macrumors 6502a

macrumors member

macrumors 6502a

macrumors newbie

macrumors 6502

macrumors 6502a

macrumors newbie

macrumors 6502a

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors 6502

Our Staff