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
I joined this forum so I could thank Mr. Pike and his colleagues for their fantastic work - I have El Capitan running on my Mac Pro 1,1!
I installed it on an external drive from a Mac Air running El Capitan and then replaced the two boot.efi files. It booted up on the Mac Pro with two minor issues, both of which have been highlighted in other posts:
1. Some of the memory is not recognised - I recall some posts that suggested solutions, but haven't been able to find them again.
2. Messages and FaceTime don't work generating a code and the instruction to contact Apple support. I did this, and was told that in El Capitan these services require a Bluetooth card that supports Handoff. In the Yosemite thread it's suggested this is a software not hardware issue, and that Apple can resolve it on their servers. If so either Apple support are wrong, or there has been a change between Yosemite and El Capitan in the way Messages and FaceTime are supported.
Does anyone know the correct answer?
I installed it on an external drive from a Mac Air running El Capitan and then replaced the two boot.efi files. It booted up on the Mac Pro with two minor issues, both of which have been highlighted in other posts:
1. Some of the memory is not recognised - I recall some posts that suggested solutions, but haven't been able to find them again.
2. Messages and FaceTime don't work generating a code and the instruction to contact Apple support. I did this, and was told that in El Capitan these services require a Bluetooth card that supports Handoff. In the Yosemite thread it's suggested this is a software not hardware issue, and that Apple can resolve it on their servers. If so either Apple support are wrong, or there has been a change between Yosemite and El Capitan in the way Messages and FaceTime are supported.
Does anyone know the correct answer?
Last edited:
Thank you for responding. I tried everything in this post previously to no avail. When I use the terminal script "defaults write com.apple.DiskUtility DUDebugMenuEnabled 1" and then go into Disk Utility, the Recovery HD is not visible.
When I try to: 3. Replace the boot.efi found in com.apple.recovery.boot with Pike's new version.
Unlock the file by right click - get info - unlock
Overwrite the original boot.efi , and re-lock it.
this unlocks the info box, but does not unlock the boot.efi, and I am not able to replace it. I get the message "The operation can’t be completed because the item “boot.efi” is locked".
I used another method of mounting the Recovery HD posted by Pike, but I am not able to unlock the boot.efi to remove it. I found a method listed by Hennessie 2000 in his instructions for the Yosemite patch on how to unlock the boot.efi in CoreServices, but I do not know how to adapt this to the recovery HD disk.
Thanks for your help.
Issue the following command in terminal and make note of the designation of the recovery partition's number-
diskutil list
Eg.
MacBook:~ ognerd$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *480.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 479.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
Then mount it via -
diskutil mount /dev/disk0s3
Eg.
MacBook:~ ognerd$ diskutil mount /dev/disk0s3
Volume Recovery HD on /dev/disk0s3 mounted
MacBook:~ ognerd$
The Recovery Partition should then be visible on your desktop.
Ok. You have the correct copies of boot.efi in place. Please try our latest nightly of boot.efi and see if that helps.
@helmer,
You too
Hi Pike,
I try your latest nightly.
The MD5 = 0f2b540ecdd35632b1eb258108584260
The SHA1 = d118a2379b112e965ba7952cd6efae494c2ab534
The Mac 1.1 does not boot on El Capitan, always a folder with question mark.
I place the disk on my Mac 5.1 and it boot normally on El Capitan.
Hi guys,
first, I want to thank you all, and esspecially Piker for the work you do, it's awsome!
Today I installed El Capitan on my MacPro 1,1 which was running Mavericks before. To install, I used a newer Macbook Pro with Firewire to install El Cap to the MacPro System disk. Than I replaced the boot.efi in the /usr/standalone/i386 and /System/Library/CoreServices/ directories and blessed the drive, booted up and it works!! Awsome so far. Problem is, that now I get rendom Kernel Panics after the mac has been up for some time, sometimes a few minutes, sometimes an hour...
I don't really understand what the crash reports tell me, but I compared them, and as far as I understand, the process that causes the errors has been a different one each time, and the error is cpu related.
There were no such errors running Mavericks via the SFOTT Install, so I don't think it's a "real" hardware issue. Maybe the old CPUs are not correctly supported by El Cap??
Another forum post suggested that the Kernel panic pointed to a memory problem. So I played around with my Memory modules. I have 2 2Gb DDR2 FB-DIMM 667MHz Modules, which were both installed on the top riser. Taking one of the modules out resulted in the mac crashing seconds after the boot and successfull login.
So now I put the modules back as they were, both on the top riser card and the old behaviour is back with the Mac crashing after some time, at least some Minutes I can use to troubleshoot...
I also found out that I can "trigger" the kernel panic by simply starting many random programs, so I guess it's caused when the CPU trys to access certain areas in the RAM...
I posted the kernel panic reports to gitHub: https://github.com/Piker-Alpha/macosxbootloader/issues/3?_pjax=#js-repo-pjax-container
The Machine is a MacPro 1,1
2 Dual-Core Intel Xeon 2,66GHz (the factory ones, didn't switch them)
2x2Gb DDR2 FB-DIMM 667MHz
ATI Radeon HD 5770 (flashed I suppose, as there is no Boot Screen displayed...)
It's not a production machine, so I'm happy with playing araound to get it to work somehow..
Thanks for any advise!!
first, I want to thank you all, and esspecially Piker for the work you do, it's awsome!
Today I installed El Capitan on my MacPro 1,1 which was running Mavericks before. To install, I used a newer Macbook Pro with Firewire to install El Cap to the MacPro System disk. Than I replaced the boot.efi in the /usr/standalone/i386 and /System/Library/CoreServices/ directories and blessed the drive, booted up and it works!! Awsome so far. Problem is, that now I get rendom Kernel Panics after the mac has been up for some time, sometimes a few minutes, sometimes an hour...
I don't really understand what the crash reports tell me, but I compared them, and as far as I understand, the process that causes the errors has been a different one each time, and the error is cpu related.
There were no such errors running Mavericks via the SFOTT Install, so I don't think it's a "real" hardware issue. Maybe the old CPUs are not correctly supported by El Cap??
Another forum post suggested that the Kernel panic pointed to a memory problem. So I played around with my Memory modules. I have 2 2Gb DDR2 FB-DIMM 667MHz Modules, which were both installed on the top riser. Taking one of the modules out resulted in the mac crashing seconds after the boot and successfull login.
So now I put the modules back as they were, both on the top riser card and the old behaviour is back with the Mac crashing after some time, at least some Minutes I can use to troubleshoot...
I also found out that I can "trigger" the kernel panic by simply starting many random programs, so I guess it's caused when the CPU trys to access certain areas in the RAM...
I posted the kernel panic reports to gitHub: https://github.com/Piker-Alpha/macosxbootloader/issues/3?_pjax=#js-repo-pjax-container
The Machine is a MacPro 1,1
2 Dual-Core Intel Xeon 2,66GHz (the factory ones, didn't switch them)
2x2Gb DDR2 FB-DIMM 667MHz
ATI Radeon HD 5770 (flashed I suppose, as there is no Boot Screen displayed...)
It's not a production machine, so I'm happy with playing araound to get it to work somehow..
Thanks for any advise!!
Many thanks Mr. Pike and his colleagues for their fantastic work. EI Captian worked on the first try on my Mac pro 1.1
PLEASE READ THIS:
If you do not have a folder with the name ".IABootFiles" on your El Capitan partition, then that is fine.
Either the installer will create it, if required, or createinstallmedia will do this. In no event shall you add it yourself.
After the installation process is done, then the folder will be removed.
If you do not have a folder with the name ".IABootFiles" on your El Capitan partition, then that is fine.
Either the installer will create it, if required, or createinstallmedia will do this. In no event shall you add it yourself.
After the installation process is done, then the folder will be removed.
Hi Pike,
do you refer to my kernel-panic-problem? I'm not home at the moment, so I can't look for that folder.
Where should I find it? In the root / of the System disk? If it's there, shall I delete it?
I used a MacBook Pro (2008 i think) with quite different HW than the MacPro for the install, can that be the cause of the kernel-panics?
Thank you.
Now about the memory problems. El Capitan is an improved version of Yosemite, and that worked for many Mac Pro owners, without a hitch, so your processors are not the problem. However. Mavericks and Yosemite were lazy... compared to El Capitan with its active memory compression, and ditto checks. In short. I think that your memory is acting up, or isn't properly fitted, or El Capitan has an issue that only you/a hand full of people run into. What do you think? I'd say go hunt for some new Ram modules. OWC is your friend.
Note: The first thing, after a PRAM reset, would be to boot with slide=0 so that the (prelinked)kernel and drivers won't be moved upwards in memory. Not working? Swap the modules. Not working. Call OWC.
Use diskutil list to list the volumes. Then find the recovery volume and mount it with diskutil mount /dev/diskXsX.
Ok, I think I still got an old dell server somewhere and the memory should fit into the MacPro, so I'll give that a try... What do you mean by boot with slide=0? Sorry I'm a noob ^^
I've tried to do an install usb key with the same guide I've used for Yosemite and the new boot.efi files. I can boot my computer on the key, but after a very long time with the black screen (several minutes), I'm obliged to stop my machine, since the installer is not launched.
If you tried the boot.efi from the repository known as v3.0 and the BaseSystem.dmg method, the boot.efi will not recognize the install and therefore not disable SIP and the boot will fail. Wait a bit until boot.efi v4.0 or try the
Edit: link removed.
Last edited:
With the last bit of advice from Sko, I was able to get my USB installer to work. Thank you very much, everyone, especially Pike R. Alpha, Sko and all those who mentioned success with a USB installer.
I followed instructions here:
http://www.brainbugs.net/running-os-x-el-capitan-on-original-mac-pro/
There are a few problems with the instructions that I had to resolve.
1. The brainbugs link to icloud for the howto on creation of a bootable thumb drive ("Guide for installing...") is now down. Luckily I had captured the PDF earlier.
2. For the patched boot.efi, I had to use the latest developer commit, as mentioned by Sko.
3. Some of the steps in the "Guide for installing..." were impossible because the Flat Package Editor is inaccessible to me. I found a workaround for those steps here. In sections 4.4 through 4.5 he describes using pkgutil instead of the flat package editor. I used pkgutil and the vi editor from the command line.
4. I'm not sure if this was crucial, but I found a reference that says you must enable ownership of the flash drive.
Thanks again, everyone! What a great community.
I followed instructions here:
http://www.brainbugs.net/running-os-x-el-capitan-on-original-mac-pro/
There are a few problems with the instructions that I had to resolve.
1. The brainbugs link to icloud for the howto on creation of a bootable thumb drive ("Guide for installing...") is now down. Luckily I had captured the PDF earlier.
2. For the patched boot.efi, I had to use the latest developer commit, as mentioned by Sko.
3. Some of the steps in the "Guide for installing..." were impossible because the Flat Package Editor is inaccessible to me. I found a workaround for those steps here. In sections 4.4 through 4.5 he describes using pkgutil instead of the flat package editor. I used pkgutil and the vi editor from the command line.
4. I'm not sure if this was crucial, but I found a reference that says you must enable ownership of the flash drive.
Thanks again, everyone! What a great community.
Last edited:
Check the boot.efi files again. I'll bet one is still original. Past modded boot.efi wouldn't boot in 64bit machines so I always used that as a test. When it stopped working in my 5,1 I knew it was ready for 1,1
I have a disk with yosemite installed through sfott method i've replaced the boot.efi on two directory as mentioned above
now i've create a bootable usb key with "el capitan usb" software. After this i've installed el capitan without problem.
sorry for my elementary english Mario
Last edited:
Those steps are obsolete as of boot.efi v3.0 as it mimics a Mac Pro 3,1. Once development of boot.efi is finished, I'm sure someone will compile a streamlined guide.
Background: Just upgraded my Mac Pro 1,1 to 10.11 using the Henessie2000 method and pikeralpha's grey boot.efi. Everything went surprisingly smoothly at first, then the machine produced several spontaneous strange crashes. (It had been absolutely rock solid up until mavericks/tiamo; I had skipped Yosemite.) Tried rebuilding kext cache ("sudo touch /System/Library/Extensions"), has been stable so far.
Graphics performance: The GPU is an ATI Radeon HD 4870 (512MB). I ran an Xbench test and found that the score on the Quartz Graphics test is dramatically down from about 300 to 108. (Everything else has remained stable.) Does this make sense? Is there anything I can do to restore the performance? (short of downgrading the OS... :/
thanks for ideas!
I'm writing with Safari on El Capitan installed via my usb key. Thank you
. I've done a first test on a special partition. The only problem I had is that I had to copy again the boot.efi file on the El Capitan partition, since my computer didn't boot after the installation. I guess they weren't copied during the install process. Could I have forgotten something on my usb key ? Tomorrow I'll make a test to upgrade Yosemite on my main partition with the MAS installer and the latest boot.efi.