Hello guys, i have an old mac pro 1.1 running yosemite with "old" pike boot.efi and pike yosefix, is it safe to update it (not a fresh install) from this version to el capitan using rthpjm script v14 ? do i have to disable yosfix before ? also i have installed my system on a fusion drive made with an ssd and a 3tb drive and unfortunately i can't back it up on an other drive as they are smaller... thanks for your future advices got 12gb ram and a 512mb 4870 apple video card
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
Hello jacquesd,
It will be safer to uninstall yosfix first. I believe yosfix contains older copies of the boot.efi files (although I may be wrong, I have not looked closely at the contents). There were changes to the Pike versions of the efi files between Yos and El Capitan.
After that, you should be good to go.
Once installed, add either CapitanPikeFix or Boot64
[doublepost=1491205412][/doublepost]
I (like you) am currently running a modified ATI 5770 with boot screens. I do have an NVidia 680 which I swap to occasionally.
I'm not a graphics speed geek, however I think you will be okay with pretty much any card from ATI or NVidia that isn't the most recent. E.g. NVidia 9xx series.
I'm unsure about the 10xx series because I haven't been following the online discussions.
I did have a debate with a couple of fellow forum members about the impact of the MacPro 1,1 / 2,1 PCI busses. We sort of came to the conclusion it will have a small impact but not as much as you might think. I mention this because at some point there will be a price/performance trade off. I'm not sure where that is with cMP, you might need to do some research.
There were some discussions about the merits of 2.5G vs. 5.0G speeds (again I am unsure of what this is referring to. I have a suspicion it is internal transfer speed on the card, which in PCs can be software controlled, but for Macs it is often hard wired with a resistor addition)
EDIT:
I just had a read through the Wikipedia article on PCIe. PCIe version 1.1 has a maximum stated transfer speed of 2.5 gigatransactions per second (GT).
PCIe version 2 has 5GT.
On a 16-lane bus connection this seems to equate to 4GB/s for version 1.1, or 8Gb/s on version 2.
PCIe 3 is faster: 8GT/s or approx 15.75Gb/s
PCIe 4 is not out yet (expected 2017) is 2x v3.
These are the maximum performance figures for the busses. You must then take into account the protocols/languages/optimisations and then take a look at the performance characteristics of the graphics cards. One of the many discussions I had with the graphics card forum members brought me to understand that even a PCIe 1.1 bus is capable of saturating "most" graphics cards...
Last edited:
I have a question about a possible transition from my 1.1 to a genuine 5.1... In a few days I may inherit this mighty mid-2012 Mac Pro from work, as we are going to update our studio... Anyways... So I'm wondering: if I clone my 10.11.6 installation to a new SSD and replace the modified boot.efi with the original "Apple version", *and* get rid of the Capitanpikefix script, would this cloned system work in the 5.1?
The 5.1 is running Sierra at the moment, but I don't want to reinstall everything, so if possible I plan to just intall this SSD in the 5.1, and then probably go from 10.11.6 to Sierra once I have it up and running.
The 5.1 is running Sierra at the moment, but I don't want to reinstall everything, so if possible I plan to just intall this SSD in the 5.1, and then probably go from 10.11.6 to Sierra once I have it up and running.
I'd probably just use migration assistant on the 5,1 to bring everything over from the 1,1.
I did it with El Capitan to bring my Lion install over. And it installed everything and copied everything. It was just the same as if I'd updated Lion to El Capitan.
Seems like the simplest solution.
Hi Morpheo
In theory, yes, that will work.
Having said that, I will +1 for @flyinmac answer. I also like to use the Migtation Assistant.
I guess your choice depends on whether the mid-2012 has an SSD in it already
I'm using GTX 660 with Mac Pro & I really love the performance. But I need the bootscreen.. Is it possible to use both GTX660 & GT7300 on El Capitan without any problem, glitche, etc. And I don't want the system to switch between graphic cards which is frustrating. I just want the system use the main GTX 660.
If it's not possible, anyone recommend me any cheap card for second Graphic card for boot? Thanks.
If it's not possible, anyone recommend me any cheap card for second Graphic card for boot? Thanks.
No, I'll use the one that's currently in my 1.1/2.1.
Would you mind reminding me where thecapitanpikefix script is located? I'll look for it but I don't remember... Tx.
[doublepost=1491513548][/doublepost]
Indeed, although I will use the same disk, the 5.1 doesn't have SSD at the moment and I don't want to use a regular HD...
Sorry, I meant where it is located once it has been installed, I need to delete it on the disc that is going inside the 5.1.
If updating to El Capitan using this method, will the original NVIDIA 7300 GT graphics card still work? I recently got a 1,1 for free with no HD and 8GB of RAM. I found an old HD and put Lion (10.7) on it and got it running on that OS.
Before I invest in some RAM chips to get it up to 12GB or more for the El Cap install, I want to make sure it will work with that graphics card.
EDIT: There are 2 other graphics cards with the machine. Neither appears to be recognized when looking at the PCI section of the system profiler in 10.7. So I might be able to get them working under El Cap?
Last edited:
It will boot and work, just not very well.
You will want a better video card for anything useful.
Thanks! I opened up the Mac Pro and one card was a Radeon 3470 - appears to have been pulled from a Dell... seems like it wouldn't even be as good as the factory-installed card. The other card has a sticker on it that says HD Flex 6450 - with 1GB VRAM. I wonder if it will be recognized if I update to El Cap...
Thanks. Turns out I didn't have it in my Launch Daemons - I guess that's because I enabled SIP a while ago and forgot about it (as Security Updates don't touch the boot.efi), so the script got deleted.
...so... drum roll... It worked!
...I'm writing this from my "new" 5.1, I had to download the El Capitan installer to get my hands on the original boot.efi (I had an older installer but since I was running 10.11.6 I wanted the correct file not an older one - so I downloaded the 10.11.6 installer). Then put the SSD in the 5.1 and everything was there (of course!) except a couple of authorizations, no biggie.My wife will now use my 2.1 and I guess she'll like it! ...As for my new Mac Pro, it flies and work like a charm!...
I don't have any lag on mine. It's faster and smoother than all of the other non-pro 2014 and older iMacs, MacBook Pro's, and mini's that I've used (which are aggravatingly slow by comparison).
My system has the nVidia 8800+ in it though (specs in the footer below).
So, unless it's your video cards, there's no reason I could see for it to be lagging.
Mine is smooth and fast. The only thing I wait for is video rendering tasks (which you expect to take a bit anyway when you're encoding 2 or 3 hours of video).
But, if it helps, my system is just as fast and smooth with El Capitan as it was with Snow Leopard.
Thanks for the reply. This same set up was blazing through Mavericks a month ago.
I've checked a few areas to see if graphics have full acceleration and I'm getting mixed results. I can't get my menu bar/dock to appear transparent and there's lag when I move windows around.
What are some ways to ensure I'm taking full advantage of my GPU?
If you have just installed El Cap Spotlight may be indexing everything and hogging resources - have a look in Activity Monitor to see what is running.
Have you the latest drivers for the GPU - I think Nvidia drivers had to be downloaded manually but this is only based on a vague memory that that was necessary.
Have you the latest drivers for the GPU - I think Nvidia drivers had to be downloaded manually but this is only based on a vague memory that that was necessary.
The first thing I always check, is to see if the video card's manufacturer has any new drivers available for the card. I don't think I've ever relied on Apple's drivers. So that is where I'd check first.
This was my first guess but it's been running for a couple weeks now and Spotlight isn't using hardly any resources. Chrome is usually the only thing hogging resources which is a usual suspect with multiple tabs open.
So these dual HD 6770's that I have are actually PC cards but I updated the kexts and got them to work. Like I said, in Mavericks, didn't have any lag issues and to my understanding El Capitan is more stable on fronts that Mavericks lacked so there shouldn't be any issue with these cards.
It feels like when you first set up a Windows machine and haven't installed a gfx driver; Everything runs fine but the video has lag and things just aren't smooth. That's why I feel like it's just a gfx issue.
When you say check the manufacturer for drivers how would I do that? Aren't the graphics drivers part of the OS?
Hello camacho,
Only NVidia ship independent graphics drivers. ATI drivers are from Apple (and NVidia too, but you can choose the driver set from NVidia).
If it was all running fine previously, then it should be okay with El Capitan. My system spontaneously started to exhibit lag last year. It turned out that my system HDD was failing. I replaced the HDD and everything went back to normal. You might consider checking your HDDs.
If you have a second HDD in the system, try building another MacOSX on that disk, I suggest El Capitan so that you can narrow the issue. You mentioned fixing kexts. Initially do not change any kexts. Then try your kext mods.
There should not be any need to mess with the kexts.
So should these HD 6770s work in El Capitan without messing with the kexts? The only reason I modified the kexts is because I couldn't get my gpu's to display anything without doing so.
I have an Apple 8800 GT that I use for installs in case my 6770s don't show up initially, so I could try another hard drive but the one I'm using doesn't show any errors when I check it.
I just don't understand why everything was smooth in Mavericks but is sluggish since El Capitan.
Hi Camacho,
One word, SIP, (or in full, three words, System Integrity Protection). Apple has put a lot of effort into protecting the core operating system files from being (maliciously) modified. Unfortunately for those of us extending the life of our classic MacPros, this also means that modifications you previously made to get things working before SIP arrived will not work.
You may need to modify the kext so that it contains the ID for your card to operate. Unfortunately that will break the digital signature for the file, and MacOSX will refuse to load it with SIP active. This probably means that when the system boots, your graphics card will load with just the software renderer enabled, and hence the poor performance.
So try the following:
Boot from the Recovery HD (if you used pikify to build your El Capitan volume, the Recovery HD will be available. If you used a different method, the Recovery HD probably won't boot)
- Reboot
- When you hear the startup chime hold the Alt key down (assuming you can see the boot screens with your 8800)
- From the boot selector screen choose the Recovery HD
- (An alternative is to hold down Apple R keys, also referred to as Command R when you hear the chime)
- When that boots, open a terminal from the Utilities menu
- Issue the command
Code:
csrutil disableThis will disable SIP entirely.
In the Recovery HD terminal, also type
Code:
nvram boot-args=kext-dev-mode=1EDIT: I checked, and SIP supersedes the boot-args. ref: https://developer.apple.com/library..._Guide/KernelExtensions/KernelExtensions.html
Then reboot back into your El Capitan Volume.
See if you get your expected performance with your modified kexts in place.
You may be able to use the ioreg command using the terminal
Code:
ioregThis will produce a lot of lines of output. Look through them, you will find a section for the PCI bus, and then the gfx cards attached. On my system I have a single 5770
Code:
| | | +-o PXS1@0 <class IOPCIDevice, id 0x1000001a9, registered, matched, active, busy 0 (4421 ms), retain 22>
| | | | +-o AMD5000Controller@1 <class AMD5000Controller, id 0x100000372, registered, matched, active, busy 0 (4 ms), retain 5>
| | | | +-o ATY,Vervet@0 <class AtiFbStub, id 0x100000378, registered, matched, active, busy 0 (12 ms), retain 8>
| | | | | +-o ATY_Vervet <class AMDFramebuffer, id 0x10000037c, registered, matched, active, busy 0 (6 ms), retain 18>Here you can see that the PXS1@0 node is my gfx card, and that it has matched the AMD5000Controller kext, and further matched to the vervet personality.
I think you should be looking for the AMD6000Controller kext?....
You can also use the kextstat command
Code:
kextstat | grep -i amdOn my system I get
Code:
87 2 0xffffff7f82b66000 0x125000 0x125000 com.apple.kext.AMDSupport (1.4.2) FF769178-12FD-3CB4-BBD7-B2FA5A99C45C <86 85 12 11 7 5 4 3 1>
88 0 0xffffff7f83276000 0x5f1000 0x5f1000 com.apple.kext.AMD5000Controller (1.4.2) 1CE0058A-3411-3A16-9CEB-410D96963BC2 <87 85 12 11 5 4 3 1>
100 0 0xffffff7f82d13000 0x45b000 0x45b000 com.apple.AMDRadeonX3000 (1.4.2) F423B9AE-BBF7-3AFD-B114-1743B87EDC29 <99 85 12 7 5 4 3 1>
106 0 0xffffff7f83241000 0x22000 0x22000 com.apple.kext.AMDFramebuffer (1.4.2) 8BC41ECB-68F3-3579-9D12-5D03AA7BBEA0 <87 85 12 11 7 5 4 3 1>If you have Xcode installed, there is a graphical browser called the IORegistryExplorer, it's usually located at Applications > Utilities > Xcode Tools > IORegistryExplorer
(You may need to "add" the tools from within Xcode)
Last edited:
Thanks I appreciate the thorough response.
So I got to Recovery with my 8800 (both 6770's removed) and disabled SIP. Shutdown and replaced the 6770's. Didn't notice any change. Tried with one 6770 in the x16 slot and may have noticed a slight increase in performance but still not as smooth as it were with Mavericks.
I checked ioreg and got this:
Code:
| | | +-o PXS1@0 <class IOPCIDevice, id 0x1000001a8, registered, match$
| | | | +-o AMD5000Controller@1 <class AMD5000Controller, id 0x1000006$
| | | | +-o ATY,ATY,RadeonFramebuffer@0 <class AtiFbStub, id 0x1000006$
| | | | | +-o ATY_ATY,RadeonFramebuffer <class AMDFramebuffer, id 0x10$
| | | | | +-o AppleMCCSControlModule <class AppleMCCSControlModule, $
| | | | | | +-o AppleMCCSParameterHandler <class AppleMCCSParameterH$
| | | | | +-o AppleUpstreamUserClientDriver <class AppleUpstreamUser$
| | | | | +-o AMDNDRVService <class AtiAppServices, id 0x100000652, $
| | | | | +-o IOFramebufferI2CInterface <class IOFramebufferI2CInter$
| | | | | +-o display0 <class IODisplayConnect, id 0x100000654, regi$
| | | | | | +-o AppleDisplay <class AppleDisplay, id 0x100000656, re$
| | | | | +-o IOFramebufferUserClient <class IOFramebufferUserClient$
| | | | | +-o IOFramebufferSharedUserClient <class IOFramebufferShar$
| | | | +-o ATY,ATY,RadeonFramebuffer@1 <class AtiFbStub, id 0x1000006$
| | | | | +-o ATY_ATY,RadeonFramebuffer <class AMDFramebuffer, id 0x10$
| | | | | +-o AppleMCCSControlModule <class AppleMCCSControlModule, $
| | | | | | +-o AppleMCCSParameterHandler <class AppleMCCSParameterH$
| | | | | +-o AppleUpstreamUserClientDriver <class AppleUpstreamUser$
| | | | | +-o AMDNDRVService <class AtiAppServices, id 0x100000658, $
| | | | | +-o IOFramebufferI2CInterface <class IOFramebufferI2CInter$
| | | | | +-o display0 <class IODisplayConnect, id 0x10000065a, regi$
| | | | | | +-o AppleDisplay <class AppleDisplay, id 0x10000065c, re$
| | | | | +-o IOFramebufferUserClient <class IOFramebufferUserClient$
| | | | | +-o IOFramebufferSharedUserClient <class IOFramebufferShar$
| | | | +-o ATY,ATY,RadeonFramebuffer@2 <class AtiFbStub, id 0x1000006$
| | | | | +-o ATY_ATY,RadeonFramebuffer <class AMDFramebuffer, id 0x10$
| | | | | +-o AppleMCCSControlModule <class AppleMCCSControlModule, $
| | | | | | +-o AppleMCCSParameterHandler <class AppleMCCSParameterH$
| | | | | +-o AppleUpstreamUserClientDriver <class AppleUpstreamUser$
| | | | | +-o AMDNDRVService <class AtiAppServices, id 0x10000065e, $
| | | | | +-o IOFramebufferI2CInterface <class IOFramebufferI2CInter$
| | | | | +-o IOFramebufferUserClient <class IOFramebufferUserClient$
| | | | +-o ATY,ATY,RadeonFramebuffer@3 <class AtiFbStub, id 0x1000006$
| | | | | +-o ATY_ATY,RadeonFramebuffer <class AMDFramebuffer, id 0x10$
| | | | | +-o AppleMCCSControlModule <class AppleMCCSControlModule, $
| | | | | | +-o AppleMCCSParameterHandler <class AppleMCCSParameterH$
| | | | | +-o AppleUpstreamUserClientDriver <class AppleUpstreamUser$
| | | | | +-o AMDNDRVService <class AtiAppServices, id 0x100000660, $
| | | | | +-o IOFramebufferI2CInterface <class IOFramebufferI2CInter$
| | | | | +-o IOFramebufferUserClient <class IOFramebufferUserClient$
| | | | +-o AMDSupport <class AMDSupport, id 0x10000060e, registered, $
| | | | +-o AMDJuniperGraphicsAccelerator <class AMDJuniperGraphicsAcc$
| | | | +-o AMDRadeonX3000_AMDAccel2DContext <class AMDRadeonX3000_A$
| | | | +-o AMDRadeonX3000_AMDAccel2DContext <class AMDRadeonX3000_A$
| | | | +-o AMDRadeonX3000_AMDAccel2DContext <class AMDRadeonX3000_A$
| | | | +-o AMDRadeonX3000_AMDAccel2DContext <class AMDRadeonX3000_A$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x100000674, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x100000675, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x100000676, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x100000677, !r$
| | | | +-o AMDRadeonX3000_AMDAccelDevice <class AMDRadeonX3000_AMDA$
| | | | +-o AMDRadeonX3000_AMDAccelSharedUserClient <class AMDRadeon$
| | | | +-o AMDR8xxGLContext <class AMDR8xxGLContext, id 0x10000067d$
| | | | +-o AMDRadeonX3000_AMDAccelDevice <class AMDRadeonX3000_AMDA$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x1000006c9, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x1000006ca, !r$
| | | | +-o AMDRadeonX3000_AMDAccelDevice <class AMDRadeonX3000_AMDA$
| | | | +-o AMDRadeonX3000_AMDAccelSharedUserClient <class AMDRadeon$
| | | | +-o AMDR8xxGLContext <class AMDR8xxGLContext, id 0x1000006e5$
| | | | +-o AMDRadeonX3000_AMDAccelDevice <class AMDRadeonX3000_AMDA$
| | | | +-o AMDRadeonX3000_AMDAccelSharedUserClient <class AMDRadeon$
| | | | +-o AMDR8xxGLContext <class AMDR8xxGLContext, id 0x100000726$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x10000076b, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x10000076c, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x10000076d, !r$
| | | | +-o AMDR8xxSurface <class AMDR8xxSurface, id 0x10000076e, !r$
| | | | +-o AMDR8xxGLContext <class AMDR8xxGLContext, id 0x10000078c$Does this all look okay?
I got the modified kexts from osx86. I thought I read somewhere that with the newer OS X versions, many PC cards worked with no modifications but I couldn't get anything to work without modding the kexts for my gfx cards.
Am I correct in thinking that all you're doing when you edit kext is telling your Mac that the card you're using is in fact one that it supports? Hence why I'm showing the correct gpu ram size, resolution, etc. with the nuances of it labeled as "ATI Radeon HD 5000" and I don't get a boot screen.
Thank you very much, for helping me out with installing El Capitan onto a 1TB SSD drive. It works well with small but noticeable speed increase.
I now have my 6TB System El Capitan HDD drive corrupted. It would not boot at all. However, I can access it from SSD drive and my data looks good. Looks like only the system is hurt. It was also backed up with a Time Machine every hour. I am not sure if the system on the time machine is corrupt, too. I tried to reinstall the El Capitan using the Recovery disk. But it also does not work. It looks like working a few seconds but it does not reinstall the system and the result is the same. My last hope is to reinstall the El Capitan downloaded from the purchased section of the App Store, which I already downloaded the Install OS X El Capitan.app and placed it into the applications folder. Then I saw rthpjm's amazing work on Pikify3.1 v14. Therefore, my questions please are:
1. If I do not erase my corrupted 6TB System disk and starting from my 1TB SSD System disk, which is running El Capitan can I use the new Pikify3.1 v14 and reinstall El Capitan onto my 6TB system hard disk, please? Will this keep my data on the 6TB system disk intact?
2. Or, shall I try to reinstall the El Capitan onto my 6TB system disk using the Install OS X El Capitan.app on the 1TB SSD System disk and then manually replace the boot.efi files, please? Will this keep my data intact, too? Will this be preferred way over using the Pikify 3.1 v14?
Thank you very much for all your kind help.
I now have my 6TB System El Capitan HDD drive corrupted. It would not boot at all. However, I can access it from SSD drive and my data looks good. Looks like only the system is hurt. It was also backed up with a Time Machine every hour. I am not sure if the system on the time machine is corrupt, too. I tried to reinstall the El Capitan using the Recovery disk. But it also does not work. It looks like working a few seconds but it does not reinstall the system and the result is the same. My last hope is to reinstall the El Capitan downloaded from the purchased section of the App Store, which I already downloaded the Install OS X El Capitan.app and placed it into the applications folder. Then I saw rthpjm's amazing work on Pikify3.1 v14. Therefore, my questions please are:
1. If I do not erase my corrupted 6TB System disk and starting from my 1TB SSD System disk, which is running El Capitan can I use the new Pikify3.1 v14 and reinstall El Capitan onto my 6TB system hard disk, please? Will this keep my data on the 6TB system disk intact?
2. Or, shall I try to reinstall the El Capitan onto my 6TB system disk using the Install OS X El Capitan.app on the 1TB SSD System disk and then manually replace the boot.efi files, please? Will this keep my data intact, too? Will this be preferred way over using the Pikify 3.1 v14?
Thank you very much for all your kind help.