as far as I can tell, commit e66ce41f2abed460b57afe88ef625566d458fd91 behaves exactly the same as the version before this one.
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
as far as I can tell, commit e66ce41f2abed460b57afe88ef625566d458fd91 behaves exactly the same as the version before this one.
El Captain is running fine with the instructions from the first post. The only problem is copying boot.efi to /usr/standalone/i386
I could copy boot.efi to /System/Library/CoreServices/ and El Captain is running already
Apart from rootless, it is obvious you haven't studied Hennesie's guide. Do so now.
I figured it might have been a problem, but I had already installed it after it came to my mind. In any case, however, thank you for pointing that out and confirming my doubt. The only thing I was "hoping" for, was that the boot stage would not have the protection, but I guess it'd be stupid on my behalf to think so. So, for the time being, I guess the way to go would be to update from my MBP and then put the drive back in.
Hi every one, I need help ; I was unable to go further than the screen installation of el Capitan GM_Candidat:
my keyboard is not recognized and my touchpad so. I have put the last efi.boot.:
I have a white macbook 2,1 of 2007 no Pro.
thanks advance.
my keyboard is not recognized and my touchpad so. I have put the last efi.boot.:
I have a white macbook 2,1 of 2007 no Pro.
thanks advance.
Attachments
This is a general request to hackintosh users or people booting El Capitan on an old Mac Pro using Clover. Please, read https://pikeralpha.wordpress.com/2015/09/23/another-one-bites-the-dust/comment-page-1/
It appears Pike needs confirmation that csrutil disable works when these machines are booted with Clover.
It appears Pike needs confirmation that csrutil disable works when these machines are booted with Clover.
How To do to disable csrutil on macbbok 2,1 of 2007 Pleased ? thanks advance.
I don't know if your machine supports El Capitan or it doesn't. I will assume, just as a hypothesis, that it does. To disable SIP (not carutil as you say), you simply boot to the El Capitan Recovery HD, open Terminal, enter "csrutil disable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. When it does reboot to the regular El Capitan partition, SIP will be disabled. To re-enable it, simply boot to the Recovery HD again, open Terminal, ente "csrutil enable" (without the quotation marks), and, if successful (it should be, if it is a supported Mac), it will ask you to reboot your computer. Do it and, when it reboots to the regular El Capitan partition, SIP will be enabled.
Edit: Sorry, I hadn't paid due attention to the fact that you were quoting my mention of Pike's request about Clover. If you are booting El Capitan on your presumably unsupported Macbook via Clover, your input would be useful to Pike, but I don't know how you can access the Recovery HD from Clover (supposing there is one). You should probably ask people that use Clover on a regular basis. The farthest I went with such bootloaders was with a version of Chameleon that booted Mavericks.
Last edited:
I'm not installed clover. I have just unsupported macbook 2,1.
Attachments
You'll note that this thread is specifically about Mac Pros. There is a separate thread about El Cap on other Macs. The USB issue is well established there.
People with Mac Pros don't have the USB issue so we will be unable to help.
People with Mac Pros don't have the USB issue so we will be unable to help.
ok thanks but I try efi.boot from https://forums.macrumors.com/threads/os-x-el-capitan-beta-on-unsupported-macs.1889851 but I have a kernel panic.
I wanted to thank Peter for this post! I may be a little late to the game so to speak but I got El Capitan installed and working on my 2007 MacPro 1,1 (firmware updated to 2,1) this evening using the procedure above. I have to say having my Mid 2012 rMBP to install El Capitan made doing this so much easier. Once my 500GB SSD was formatted and new OS installed, all I had to do is plug in the drive to one of my bays and start the computer up. Yeah... it was just that easy. Thanks again Peter and to everyone else who was involved for making all of this possible!
Last edited:
@Macdctr
You are welcome. Just remember that Pike's Yosemite boot.efi, although capable of booting El Capitan on an old Mac Pro, is not entirely compatible with it. The one he's been developing these past weeks especially for El Capitan should work much better on the new operating system. It's ALMOST there, but it can't disable SIP yet when booted to the Recovery HD. Another foreseeable problem is that, when SIP is in place, your custom-made boot.efi may be inadvertently replaced by Apple's stock 64-bit version when an update to El Capitan is downloaded. In my note you quoted above, I neglected to mention the so-called PikeYoseFix daemon. Although that has worked flawlessly since before Yosemite (there was a previous version for Tiamo's boot.efi for Mavericks), it won't work on El Capitan, unless you disable SIP first. Good luck and just be careful with system updates.
You are welcome. Just remember that Pike's Yosemite boot.efi, although capable of booting El Capitan on an old Mac Pro, is not entirely compatible with it. The one he's been developing these past weeks especially for El Capitan should work much better on the new operating system. It's ALMOST there, but it can't disable SIP yet when booted to the Recovery HD. Another foreseeable problem is that, when SIP is in place, your custom-made boot.efi may be inadvertently replaced by Apple's stock 64-bit version when an update to El Capitan is downloaded. In my note you quoted above, I neglected to mention the so-called PikeYoseFix daemon. Although that has worked flawlessly since before Yosemite (there was a previous version for Tiamo's boot.efi for Mavericks), it won't work on El Capitan, unless you disable SIP first. Good luck and just be careful with system updates.
as far as I can tell, commit 0f76ac85bee944287f7a01866a5f71cb13c7d0bc behaves the same as the version before. " ioreg -lw0 -p IODeviceTree | grep system-id" gives value "00000000000000000000000000000000". El Capitan boots flawless if NVRAM empty. csrutil disable fails. csrutil status -> enabled (Apple Internal).
I was thinking until a "fix" is in place so we can disable SIP, I can put my SSD into an external enclosure and connect to my rMBP for updates then reinstall the modified boot.efi files again....more work but at least I can continue updating the software in this manner until there's a more permanent fix to this issue
Sure thing. That should be feasible.I was thinking until a "fix" is in place so we can disable SIP, I can put my SSD into an external enclosure and connect to my rMBP for updates then reinstall the modified boot.efi files again....more work but at least I can continue updating the software in this manner until there's a more permanent fix to this issue
00c99705773ef2247cf8514b11f1fca3ea6806bb: system boots normal, all tests conducted give the same results as before.
8cfc32ec09d0abecafe90766984a6c448514cf70: "ioreg -lw0 -p IODeviceTree | grep system-id" now gives a value (won't post this in public). "platform-uuid" still absent in NVRAM. "Hardware UUID" reported in System Profiler looks invalid to me (differs from the one displayed in Yosemite & Lion).
Commit a556a2e555bf773886ec312da7af2e3d58ee5946: system boots normal, all tests conducted give the same results as before.