Got a tip for us?
Let us know
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
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
Not sure what you mean by "Pacified".
Re-read post #3643 & 3645, then go ahead and install the updates.
From my experience, the security updates don't overwrite the boot.efi files so you are OK to update. There is no saying this will always be the case but it seems to have been OK so far. It is the point updates to the whole OS that can potentially cause an issue if precautions are not taken - if El Cap is up to date (10.11.6) then this is unlikely to be an issue unless Apple decide to update the OS - which they almost certainly will not do.
hey,im getting mixed messages about this, do i need a new graphics card im still running a 7300 gt? im getting a radeon 7950 soon but can i run it with out?
Hi all, I recently am having a problem with my pikified MacPro 1,1 with it rebooting when the progress bar gets to about a the 3/4 point. This just started happening the other day. I am able to boot using safe mode. I also have reinstalled using the pikify app and the behavior is the same. Do you guys have any idea of what is happening?
Yes all 2GB RAM modules show in system profiler. No red lights on the riser cards. I have reseated the modules too.
I assume you have the RAM in pairs in the correct slots and no 512s? What is the total RAM you have? Have you tried SMC reset and a PRAM reset? If all are OK could the drive be failing? If you have a spare drive you could install El Cap on that and see if the issue is still there. This would help to pinpoint the issue a bit more or at least rule out the HD. I assume you had it working OK for a while - were you on the latest version - 10.11.6 or did this happen after an update (not the security update)? This could have happened without you instigating it if it was set to auto update.
Last edited:
tried to cp boot.efi to /System/Library/CoreServices/ but not permitted, tried to disable sip by booting into recovery partition, but no terminal app...WTF? csrutil doesn't seem to exist either..
Try this and report back please.
Top menu bar...
Finder->Go->Go to Folder
This should take you to csrutil, it does for me.
I am having a similar issue. I have a 2006 Mac Pro 1,1 and had a working version of El Capitan (I believe it was 10.11.6) until a recent install of an Apple "security update." The CaptainPikeFix worked to keep the system functional through previous "security updates" from Apple, but perhaps not after this most recent one. Alas I too have a progress bar that "hangs" at the 3/4 point when trying to boot.
I checked my boot.efi and the correct (e.g., "Piked") versions are in both locations (/usr/standalone/i386 and /System/Library/Coreservices). I also checked to make sure that SIP was disabled, which it continues to be. Nonetheless, I replaced the boot.efi at both locations, without resolution. I have checked my memory modules and all memory slots are well seated and showing up in the system profiler (2gb each, 16gb total for the machine).
Did this most recent security update "break" the Pike fix? Is there something else I should do to restore the system?
I have my startup disk different that my data files, and I have access to all my data. I can currently boot the system up with a "piked" Yosemite startup disk and run diagnostics from there. The El Capitan Recovery Disk is also available by booting in recovery mode.
Appreciate any assistance from the community. (BTW -- this community rocks -- I have been able to keep my MacPro very functional for long past what I thought was possible)
Great thoughts! I did both a SMC and PRAM reset and I still have the "hang" on startup once the status bar hits ~3/4 progress. So alas no resolution yet.
I do have working Lion and Yosemite OS boots on the machine, so I will be using those boots. Looks like my ~12 years with this computer is coming to an end. I have been eyeing the new 27" iMac so I guess now I have an excuse.
Thank you again for all the contributions made to this forum.
You could try a fresh install onto a spare HD if you have one around. This would preserve your current set-up but may help to locate the issue. Perhaps sometimes a failing HD can cause this sort of issue as if it was working previously something has to have changed to cause the problem.
Looking back through the last couple of pages of this thread there does seem to be a couple of similar issues of the startup failing around the 3/4 mark so there may be some common cause not yet identified. RTHPJM may be able to offer more options as he has a much deeper knowledge of the workings of this than I have and we are indebted to him and others for keeping us afloat.
I keep my Mac Pro running as there would be a big change needed to update the software (i.e. pay Adobe to rent their products for ever) if I went for a new Mac and some apps I use a lot may not work at all. I know I will have to do this at some point, but I keep kicking it further down the road.
Good luck.
Looking back through the last couple of pages of this thread there does seem to be a couple of similar issues of the startup failing around the 3/4 mark so there may be some common cause not yet identified. RTHPJM may be able to offer more options as he has a much deeper knowledge of the workings of this than I have and we are indebted to him and others for keeping us afloat.
I keep my Mac Pro running as there would be a big change needed to update the software (i.e. pay Adobe to rent their products for ever) if I went for a new Mac and some apps I use a lot may not work at all. I know I will have to do this at some point, but I keep kicking it further down the road.
Good luck.
Another good thought. Will do and see if the issue resolves. I also agree that the recent trend towards "subscription" for the majority of new software releases is especially aggravating. Be well!
Attached is an image of the last lines of code available during startup in Verbose mode
After this code I get a grey screen background (I choose the "grey" version of the boot.efi). Then the screen goes black with no progress bar nor lines of code. It seems that it's the same as the 3/4 of the way "stuck" portion, just without a profess bar graphic.
Again I appreciate any insight here.
Ah, ha!
What graphics card do you have?
How many monitors do you have connected?
How many physical connectors does your gfx card have, and what type are they?
Try this....
Boot
Wait for the grey screen
Wait about 1 minute more
Then remove the video cable from the back of the machine
Count to ten
Plug the video cable back in
If that doesn’t work, and your card has at least two physical connectors of the type you are using (e.g. DVI), move the video cable to the other port....
It sounds like you have encountered the issue where MacOS believes there are two monitors connected. It is sending the primary desktop signal to the “phantom” display. What you’re probably seeing is the “second” monitor with a plain black background. Try scooting the mouse around, a long way left, a long way right. See if the cursor appears on your monitor....
Been running my 2,1 mac pro running El Cap since August, and I must say all seems to be running well. I swapped my graphics card to the 5770 and bumped my ram up to 32g. And my 5770 graphics card powers my 3 monitors, with just one 6 pin connector; I'm still surprised as heck about that too. I don't understand why Apple wouldn't support this hardware for El Cap. I clone my bootup every week or so just to make sure I have it backed up. Thanks all for the support and info here.
Gibby.
Gibby.
Hi everybody, just update from yosemite (tiamo flavor) to el capitan with the pikify app and will never thank enough pike and rthpjm for all their work! Just in case my hardware is 1.1 16gb 4870 radeon and a self made fusion drive, all went fluently at the exception of the beginning of the install where i choose my yosemite drive to install el capitan with pikify then after the kernel panic, reset pram reboot on yosemite then retry but choose a different drive with the app to install the system then after the reboot when the apple installer appeared i have selected my yosemite drive to upgrade and voilà 
thanks again i bought my 1.1 in 2007 and it still works great on el capitan
thanks again i bought my 1.1 in 2007 and it still works great on el capitan