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

[ewheat]

Ok I am re-downloading and will let you know in a few hours if it works.

I used a new download of El Capitan to make a pikified USB installer. I am still getting the same error after approximately 3/4s of the way through the progress bar. When I try to boot in Verbose mode it glitches out and has white and black text scattered( I am assuming this is where it crashes).

Not sure if I mentioned before that i don't have the updated bluetooth/airport card installed yet.
It was my understanding that I don't need the updated Bluetooth and Airport card until I want the features related to it in Capitan? Or do you think this would cause problems with the install?
[doublepost=1462234334][/doublepost]Also, not sure if this is related but after I upgraded the CPUs and RAM, I am not able to restart. I can shutdown but if I try to restart it hangs and keeps hitting the CD drive. So things like resetting NVRAM don't seem to work.

I did install EL Cap to the ssd using my MBP and the older install file. It booted fine on MBP but I must have buggered up the manual editing/copying of the boot.efi files? Because it still would not boot when I put inside Mac Pro.

 

[Ant3000]

[QUOTE="I did install EL Cap to the ssd using my MBP and the older install file. It booted fine on MBP but I must have buggered up the manual editing/copying of the boot.efi files? Because it still would not boot when I put inside Mac Pro.[/QUOTE]

I have not installed this way but I think there is a way to check the boot.efi files have been changed by checking their size - the Apple files are different size to the 'Pikified' ones. I am sure the info is here somewhere. Try here...#1895

Not sure about the not restarting issue - if it started to happen after changing the CPUs and RAM they look to be likely candidates. Have you tried putting back the old RAM and testing - if it works add a new stick one at a time and retest. I had some bad RAM and it wouldn't boot at all and showed a red LED on the board (with side panel removed). Not sure if dodgy RAM can cause your problem, but this is easier to physically check than the CPUs.

 

[I_HaCKeD]

I'm using MacPro 1,1 with Mac version 5770 graphics 12G RAM 8 core upgrade.
I'm trying to install 10.11.4 from a USB stick created with the Pikify 3.1v8 to an SSD and the install continuously fails half way through the install.Here's a portion of the Log.On a previous clean install I tried to manually modify the boot.efi but it is locked and I can't unlock it even in the terminal.Any thought? Thanks.

May 2 20:44:19 Mac-Pro OSInstaller[480]: PackageKit: Using / as external payload root for package com.apple.pkg.BaseSystemResources
May 2 20:44:19 Mac-Pro OSInstaller[480]: PackageKit: Extracting file:///System/Installation/Packages/BaseSystemResources.pkg (destination=/Volumes/SSD/.OSInstallSandboxPath/Root, uid=0)
May 2 20:48:16 Mac-Pro OSInstaller[480]: PackageKit: Extracting file:///System/Installation/Packages/Essentials.pkg (destination=/Volumes/SSD/.OSInstallSandboxPath/Root, uid=0)
May 2 20:53:04 Mac-Pro OSInstaller[480]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo={NSUnderlyingError=0x7fe88405db40 {Error Domain=BOMCopierFatalError Code=1 "Block-compressed payload operation failed" UserInfo={destinationPath=/Volumes/SSD/.OSInstallSandboxPath/Root, offset=20445889, type=BOMCopierFatalError, sourcePath=/System/Installation/Packages/Essentials.pkg, NSLocalizedFailureReason=Block-compressed payload operation failed}}, NSFilePath=/Volumes/SSD/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.} {
NSFilePath = "/Volumes/SSD/.OSInstallSandboxPath/Root";
NSLocalizedDescription = "An error occurred while extracting files from the package \U201cEssentials.pkg\U201d.";
NSURL = "Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution";
NSUnderlyingError = "Error Domain=BOMCopierFatalError Code=1 \"Block-compressed payload operation failed\" UserInfo={destinationPath=/Volumes/SSD/.OSInstallSandboxPath/Root, offset=20445889, type=BOMCopierFatalError, sourcePath=/System/Installation/Packages/Essentials.pkg, NSLocalizedFailureReason=Block-compressed payload operation failed}";
PKInstallPackageIdentifier = "com.apple.pkg.Essentials";
}
May 2 20:53:04 Mac-Pro OSInstaller[480]: OSIInstallElement <OSIInstallElement: 0x7fe8846f6bd0> errored out:Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo={NSUnderlyingError=0x7fe88405db40 {Error Domain=BOMCopierFatalError Code=1 "Block-compressed payload operation failed" UserInfo={destinationPath=/Volumes/SSD/.OSInstallSandboxPath/Root, offset=20445889, type=BOMCopierFatalError, sourcePath=/System/Installation/Packages/Essentials.pkg, NSLocalizedFailureReason=Block-compressed payload operation failed}}, NSFilePath=/Volumes/SSD/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.}
May 2 20:53:04 Mac-Pro OSInstaller[480]: ------- Install Failed -------
May 2 20:53:04 Mac-Pro OSInstaller[480]: Operation: Install packages failed, Failure Reason: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo={NSUnderlyingError=0x7fe88405db40 {Error Domain=BOMCopierFatalError Code=1 "Block-compressed payload operation failed" UserInfo={destinationPath=/Volumes/SSD/.OSInstallSandboxPath/Root, offset=20445889, type=BOMCopierFatalError, sourcePath=/System/Installation/Packages/Essentials.pkg, NSLocalizedFailureReason=Block-compressed payload operation failed}}, NSFilePath=/Volumes/SSD/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.}
May 2 20:53:04 Mac-Pro OSInstaller[480]: ISAP: Abort progress UI called.
May 2 20:53:04 Mac-Pro OSInstaller[480]: ISAP: Done with phase “OS Installer”
May 2 20:53:04 Mac-Pro OSInstaller[480]: open on /Volumes/SSD/Library/LaunchDaemons/com.apple.installer.osmessagetracing.plist: No such file or directory
May 2 20:53:05 Mac-Pro OSInstaller[480]: Enabling system idle sleep.
May 2 20:54:57 Mac-Pro OSInstaller[480]: Could not find next pane.

 

[Ant3000]

You don't have any 512mb RAM in there do you?

 

[rthpjm]

May 2 20:53:04 Mac-Pro OSInstaller[480]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo={NSUnderlyingError=0x7fe88405db40 {Error Domain=BOMCopierFatalError Code=1 "Block-compressed payload operation failed" UserInfo=

That's what we normally see when the MacPro has less than 12Gb of RAM. Remove the side panel power up your machine and check that there are no red LEDs lit on the memory cards.
Try re-seating the memory sticks.
Confirm you have 12Gb or more memory being reported by Mac OS X.....

 

[creepyTowel]

In case you were wondering, I'm happy to report that the just-released public beta 4 of OS X 10.11.5 is a straightforward upgrade for us -- no boot.efi replacement, no re-enabling SIP. If you don't have an EFI graphics card BIOS there's the usual nerve-racking wait for something to appear on screen, but don't worry -- it will.

Peter.

 

[PowerMac G4 MDD]

About the iMessage sign-in fix, I called up Apple before about my 1,1, running Mountain Lion unsupported, and they were able to take the code I received and activate it. Since then, I put El Cap on the MP and had it run okay. However, I semi-recently got a 4,1 Mac Pro and went and stuck an old HDD (with Mtn. Lion, but w/o the iMessage fix already applied) into the 1,1. I went through the same process of giving Apple my customer code, but, this time, I still can't log-in to Messages with iMessage. I tried to have them activate it multiple times, but it's still not working. Any ideas? Pretty sure that that one time I got it working (by contacting Apple) was when it had Mountain Lion on it to begin with. Pretty sure I don't have to upgrade it to El Cap, right? It must be some freak issue...?

To clarify, I had Mtn. Lion on this MP at one point and was able to do the fix. It's on Mtn. Lion right now, but on an old backup that hasn't had the fix done to it yet.

 

[ewheat]

I pulled 4- 4GB sticks of RAM(16GB) and now my Mac Pro at least restarts. Didn't have any red lights though. Must have a bad stick in there. I ran AHT on the remaining RAM and it passed.

However, I am still failing the boot to install on Pikified USB at the same place. Right after it says "bluetooth controller missing." then the text goes haywire. What loads next after that? Could it be the problem?

I also tried to install Mavericks using the "create maverick install usb and modify osinstall.mpkg and replace 2 boot.efi" but that didn't work either. I put my old gpu back in (7300GT) and tried as well (makes sense). No success.

So, going back to the manual install, is there a special way to replace the boot.efi files? I just copied and replaced them in their respective locations.

Also if I didn't mention it before I am trying to do this from 10.6.8 if that makes a difference (but using a 9,1 MBP to create the installer usb's). I am thankful for the help from you guys and anymore suggestions would be appreciated!

 

[owbp]

@ewheat , Bluetooth Controller Missing should be associated with graphic card, but I'm not 100% sure.

Regarding Mavericks, i installed it last night on 50gb partition for a fallback, since i want to try 10.11.5 Beta
You should add you Board ID and Mac model in InstallableMachines.plist (same folder as OSInstall.mpkg), have you done that?

If you want to go with manual install, why don't you just buy USB3 to SATA adapter, or FireWire to SATA (assuming you still have access to MBP9,1) and install it that way?
After installation, don't make User account from MBP, but just boot back into 10.6.8, replace boot.efi files and put your HDD back to MP.
[doublepost=1462445521][/doublepost]

If you don't have an EFI graphics card BIOS there's the usual nerve-racking wait for something to appear on screen, but don't worry -- it will.

Even if you have EFI GPU there is still a few seconds of white screen between apple logo and login screen - longest seconds in ones life


P.S. Feeling good logging into Feedback Assistant on MP1,1 that runs OS X 10.11 better than friends few years old MBP and Mac Mini...

 

[coarist]

The method listed on the original 2005 post by Mr. Zarniwoop worked for me - OSX 10.11.4 can run on MacPro 2006 1,1. Original GeForce GT 7300 video card and ATi Radeon X1900 XT 5MB have minor glitches on Safari and sluggish LaunchPad otherwise function is normal.

 

[ManMor]

Hi ... please for help = I installed El Captan on my MacPro 2006 (change boot.efi method) and working good, but Mac does not want SLEEP (!). Do you know where is problem? Sorry when is "old topic" on this forum, but english not native languge for me and I have problem read all parts of this forum.... thanks for help.

 

[Ant3000]

Possibly SMC reset? Does it sleep if you try to make it sleep from the finder? Assume you have checked System Prefs > Energy saver and that never sleep isn't selected. Check for disk or network activity with Activity Monitor to check if something is running in the background.
[doublepost=1462491011][/doublepost]

I pulled 4- 4GB sticks of RAM(16GB) and now my Mac Pro at least restarts. Didn't have any red lights though. Must have a bad stick in there. I ran AHT on the remaining RAM and it passed.

However, I am still failing the boot to install on Pikified USB at the same place. Right after it says "bluetooth controller missing." then the text goes haywire. What loads next after that? Could it be the problem?

I also tried to install Mavericks using the "create maverick install usb and modify osinstall.mpkg and replace 2 boot.efi" but that didn't work either. I put my old gpu back in (7300GT) and tried as well (makes sense). No success.

So, going back to the manual install, is there a special way to replace the boot.efi files? I just copied and replaced them in their respective locations.

Also if I didn't mention it before I am trying to do this from 10.6.8 if that makes a difference (but using a 9,1 MBP to create the installer usb's). I am thankful for the help from you guys and anymore suggestions would be appreciated!

There is a pre patched Yosemite installer available to download which may be a step up from Mavericks and there is no messing with .efi files. This should install easily. I think link is on P1 of Yosemite thread. I have no ideas on the Bluetooth Controller error - a quick search seems to see the issue on Hackintosh set-ups but sorry I can't advise on a fix. Have you checked the graphics card is definitely compatible?

 

[ManMor]

- SMC reset haven't effect. And I checked Preferences and Activities to = nothing.

- In "Sleep mode" is dark monitor, but MAC PRO (sorry no MACBOOK) doesn't sleep.

- I know about "printing system restart", but it doesn't solution for my MAC.

 

[Ant3000]

Do you have any apps running in the background that may affect it? Maybe things like temp monitors or finder extensions? Can you make the computer sleep via the power button?

 

[ManMor]

Sorry - I have Mac Pro - no macbook - it was mistake. Sleep button haven't effect. And I don't know, what app can be problem...

I use this image

- maybe bad image (and actualisation doesn't solution). In OSX 10.8.4 sleep running OK.
[doublepost=1462558122][/doublepost]Do you know about diferent Yosemite/El Capitan image for "boot.efi" install method? I haven't next apple computer for "change disk with installation".

 

[Ant3000]

I installed by creating a USB installer following the instructions on here - not sure if this makes any difference to sleep, but I have not had a problem. Sleep issues have always been a thing Apple seem to be good at and I have had issues over the years with other versions of OSX. Does your Mac sleep and then immediately wake or just not even try?

 

[ManMor]

No reaction for a sleep (menu or button)... Can you send me image your install USB? Please... I haven't very much Mac skills...

 

[Ant3000]

No reaction for a sleep (menu or button)... Can you send me image your install USB? Please... I haven't very much Mac skills...

Hi, this is the link to the instructions to create the installer from a copy of El Capitan downloaded from the Mac App Store. #1390 - credit to rthpjm and Pike.
I downloaded this on another Mac and created the installer there. You DO need at least 12gb of RAM and NO 512mb chips to make it work this way. You can always install from another mac using Target Disk mode without the need for 12gb RAM and then change the boot.efi files.
If El Capitan seems to be running OK except for the sleep issue reinstalling may be unnecessary - others may be able to offer advice on how to fix. Have you reset the P-RAM by the way?

Have you worked through this...
https://support.apple.com/kb/PH21709?locale=en_US&viewlocale=en_US

 

[ManMor]

Restart PRAM - it was a first idea. I hava 12 GB Ram... El cap. app have from my dead macbook. ... and in my area i don't know about some "el capten" compatibile Mac. I'll try it - this instruction.

 

[ManMor]

New information - I tryed "pmset -g assertions" (new command for me) and this say:

Idle sleep preventers: IODisplayWrangler
System sleep preventers: .Display_boot

Do you know what is it?

 

[Ant3000]

No idea what it is but this may help...
https://discussions.apple.com/thread/7256162?start=0&tstart=0

https://discussions.apple.com/thread/7275550?start=0&tstart=0

 

[ManMor]

Jan-Mac-Pro:~ MACPRO$ pmset -g assertions
2016-05-07 02:28:06 +0200
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 0
PreventUserIdleDisplaySleep 0
InteractivePushServiceTask 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0
Listed by owning process:
pid 1622(AddressBookSourceSync): [0x00000cc70001048a] 00:00:16 PreventUserIdleSystemSleep named: "Address Book Source Sync"
Timeout will fire in 1784 secs Action=TimeoutActionTurnOff
(...)
Idle sleep preventers: IODisplayWrangler
System sleep preventers: .Display_boot

I try this manual: https://discussions.apple.com/thread/5565445?tstart=0

 

[ManMor]

Good, solution of "AddressBookSourceSync" is delete the addressbooksourcesync entirely from system//Library/frameworks/addressbook.app/versions/A. Now is pmset -g assertions clean. But steel can't sleep(!).

2016-05-07 04:35:03 +0200
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 0
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 0
NetworkClientActive 0
Kernel Assertions: 0x4=USB
id=500 level=255 0x4=USB mod=01.01.70 1:00 description=com.apple.usb.externaldevice.fd500000 owner=USB2.0 Hub
id=501 level=255 0x4=USB mod=01.01.70 1:00 description=com.apple.usb.externaldevice.fd200000 owner=USB2.0-CRW
id=502 level=255 0x4=USB mod=01.01.70 1:00 description=com.apple.usb.externaldevice.fd510000 owner=USB Receiver
id=503 level=255 0x4=USB mod=01.01.70 1:00 description=com.apple.usb.externaldevice.fd530000 owner=USB Optical Mouse
Idle sleep preventers: IODisplayWrangler
System sleep preventers: .Display_boot

 

[Ant3000]

Have you tried unplugging all devices Including mouse, keyboard external drives, printers and see if it will sleep then?

 

[ManMor]

Yes and nothing... I tryed reinstal El Capian today - nothing. But - and it is interesting - i used Parallels Desktop for install El Capitan on real external disk and it is functional method. You doesn't need another mac with El Capitan for it (!). Maybe it is a new method instalation for this forum.