Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

mikeboss

macrumors 68000
Aug 13, 2009
1,546
867
switzerland
commit 5d3d273a7c49ccb5c63cf40b6100596a3ad79433: boots normal. started into Recovery HD (empty NVRAM). csrutil status is enabled. I then disabled SIP using csrutil disable. reboot into El Capitan. -> status disabled. reboot into Recovery HD: csrutil enable -> OK. reboot into El Capitan: csrutil status gives enabled (Apple Internal). value in NVRAM is "EAAAAA". oh, and what about the "Hardware UUID" reported in "System Information.app" being different than what is displayed in Yosemite and/or Lion, is this a non-issue?
 

dfritchie

macrumors regular
Jan 28, 2015
198
83
Installed, rebooted to kernel panic. Replaced com.apple.boot.plist and booted without panic. Thanks guys for all your hard work!
 

andyyau

macrumors member
Jul 17, 2012
88
111
Sorry to ask the simple questions. After using target disk to install:
1. How to make recovery partition bootable? Need to replace boot.efi in recovery?
2. For the main hard disk, what to do with the permissions after the two efi are replaced.

Thanks!
 

PowerMac G4 MDD

macrumors 68000
Jul 13, 2014
1,900
277
Hey guys, I wanted to report that I got El Cap running in my 1,1 last night.

I listened to this guy and got it running easily.

1. I had installed DP1 on a 4,1.
2. From a working Yose install on the 1,1 I accessed the El Cap disk and replaced the boot.efi files. (tricky but doable)
3. I used a text editor to add "rootless=0" in the apple.boot.plist in El Cap
4. I rebooted into El Capitan on the 1,1 !
5. I ran the pikeryosefix app.
6. I ran all of the updates right from Apple Store, right to DP7.

In retrospect I probably could have run the pikeryosefix in the 4,1 and saved myself some bother. I just posted in the Yosemite on 1,1 thread that the value of this app has been overlooked. If you think about it and use it at right time, you don't have to do the manual replace, just run the pikeryosefix app while on a El Cap capable machine. Reboot until it won't boot anymore, this means the 32 bit EFI is in. Move drive to 1,1 and enjoy.

The point is, I read these threads and see a lot of people have a lot of trouble. It is easy as pie if you REALLY think about what you are doing and why. Thanks to Tiamo, Piker, Hennessiee, and Blacksheep for their hard work. No other 2006 era Mac can so effortlessly run El Cap, in fact most can't at all. The cMP may end up being best Mac they built.

Thanks for this post; it's a bit more reassuring (and sorry that I am responding to an old message). I see tons of people with trouble, in spite of the simplistic-looking instructions, and it almost discouraged me from trying this--or, rather, intimated me. One question for you, though: I hadn't seen step #3 before... I just heard of replacing about two files in the El Cap disk; is step #3 something necessary? What does it do?

-Thanks (BTW, what are your specs and how does it run? I'm running Mountain Lion now, and, although I'd like to have a fully current Mac OSX for the first time in many years, I am afraid that a possible drop in performance could occur and annoy the heck outta me. I have an SSD in this thing now, so that definitely helps, but even then... I still can't see it being any lighter than Mountain Lion. My current GPU (HD Radeon 6450) is also not too good, as my main GPU (Radeon 5770) is currently 'out of commission.')
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
To everyone interested in this project:

It is foreseeable that, in the next few hours or days, Pike will begin including phase-3 improvements to his boot.efi. If it is OK with everybody, I'll go on compiling them for Mike's tests. Naturally, other people can also test them at their own risk.

In any case, people must be aware that such interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.

Please, notice that the upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, such versions ARE NOT FOR YOU!
 
Last edited:

nick85

macrumors newbie
Nov 27, 2011
28
0
Fantastic work,

is someone able to show once again the updated steps ( post 1 ) on how to install el capital on a mac pro 1.1/ 2.1 when using a mac that is able to install el capitan ( my second mac is a mac mini late 2009 )

When installing el capitan via the mac mini ( ssd in a usb connector to mac mini )
Where do I have to put the boot.efi file. I could read that there are more than 2 places to put the file ?

At the moment I am running OSX Yosemite on my mac pro 2.1 with chameleon boot loader.
So when el capital is installed via the mac mini I will put back the ssd in my mac pro.

While booting the mac pro (with alt key pressed) I then will have to choose the ssd with el capital installed on.

Sorry for my basic knowledge

I really would enjoy to keep my old mac pro alive

Thanks to everyone who makes this possible.

nick
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
@nick85
You could probably benefit from studying Hennesie2000's guide to installing Yosemite on old Mac Pros, but I would advise that you wait for a few hours. Pike might include something like a shell script to make the entire process easy as pie and as foolproof as possible. Look here: https://pikeralpha.wordpress.com/2015/09/27/how-to-replace-boot-efi-with-mine/

It isn't done yet, because, quite understandably, Pike had to take some pause, considering a large part of that adaptation was authored by his recently deceased sister. So, wait until tomorrow. It shouldn't take much longer.
 

wwanthony

macrumors member
Oct 24, 2013
85
5
Installed, rebooted to kernel panic. Replaced com.apple.boot.plist and booted without panic. Thanks guys for all your hard work!

Same problem for me. You replaced the com.apple.boot.plist with what? I don't have any issues with booting into the recovery partition and turning off SIP. But I get a panic when I try to boot into the regular partition.
 

nick85

macrumors newbie
Nov 27, 2011
28
0
@nick85
You could probably benefit from studying Hennesie2000's guide to installing Yosemite on old Mac Pros, but I would advise that you wait for a few hours. Pike might include something like a shell script to make the entire process easy as pie and as foolproof as possible. Look here: https://pikeralpha.wordpress.com/2015/09/27/how-to-replace-boot-efi-with-mine/

It isn't done yet, because, quite understandably, Pike had to take some pause, considering a large part of that adaptation was authored by his recently deceased sister. So, wait until tomorrow. It shouldn't take much longer.



Thank you PeterHolbrook,

i am really sorry, I didn't know about pikes recently deceased sister.

Thats something really important !

So Pike should take all the time for his family and the big loss


Best wishes to Pike and his family


nick
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Getting ready for -f kernel patch


To everyone interested in this project:


[P]eople must be aware that [this and other] interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.


Please, notice that the [enclosed and other] upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, [these] versions ARE NOT FOR YOU!
 

Attachments

  • boot 4fe6137845f7b734db6a2f52d79b7ad1f8cdf3f5.zip
    204.3 KB · Views: 203

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
Thanks for this post; it's a bit more reassuring (and sorry that I am responding to an old message). I see tons of people with trouble, in spite of the simplistic-looking instructions, and it almost discouraged me from trying this--or, rather, intimated me. One question for you, though: I hadn't seen step #3 before... I just heard of replacing about two files in the El Cap disk; is step #3 something necessary? What does it do?

-Thanks (BTW, what are your specs and how does it run? I'm running Mountain Lion now, and, although I'd like to have a fully current Mac OSX for the first time in many years, I am afraid that a possible drop in performance could occur and annoy the heck outta me. I have an SSD in this thing now, so that definitely helps, but even then... I still can't see it being any lighter than Mountain Lion. My current GPU (HD Radeon 6450) is also not too good, as my main GPU (Radeon 5770) is currently 'out of commission.')

If there is a chance that a simplified installer is coming I would wait for that.

I discovered on an earlier version that manually replacing the 2 files wasn't necessary if you had a 64 bit machine to run the install on. Simply running the pikeryosefix app did exactly what was needed. I imagine that they will create something similar, though it is a little tougher now with SIP in place. To turn it off you need to set something in NVRAM on the 1,1. They understand this better then I, but I imagine they have some good ideas.

What worked for me last night was running the whole install on a 2012 MB via USB Sata adapter, then booting into 10.10 on the MB and switching all 3 files out (2 in OS and 1 on Recovery partition)

I moved the drive to 1,1 and it booted right up, recovery worked, etc. May have been made easier by already having SIP off in NVRAM. But switching the 3 files out is much easier when you aren't using the El Cap install as boot disk.

One thing that I think many folks have a hard time wrapping their heads around is that a MP can have nearly an infinite number of boot drives. So the wise choice is to never EVER do this on your one and only OS disk. Any old spare HD you have can be used as a 10.9 or 10.10 basic install to work from. If you have an OS disk with lots of crucial licensed software you will be MUCH happier and safer if you back it up first. 1TB+ hard drives can be had for a song now.

Make your life easier and calmer by making a full restore image via disk utility, that way no matter what you can start back at your previous working install.

It runs great on my 2,1 with Dual 5365s and 18 Gigs of RAM. Using a PCIE SSD I am getting 700Mb/s read and writes, the machine flies, no indication it is from 2006. I started a thread in Mac Pro section as I noticed there wasn't one.

With a little forethought and planning there is no reason for this to be difficult or stressful. But having a full backup is key. Craigslist and EBay have used HDs for peanuts. You can even use old PATA/IDE ones in the optical bays. Don't need to be fast, you just need fallback options.
 

nick85

macrumors newbie
Nov 27, 2011
28
0
macvidcards: for using a pcie ssd do you need an adapter or does the pcie 1.1 slot for the graphics card (16 lanes)
give you that option. Could you please describe how to manage that ? (700 Mb/s read and write speed ...
i am getting around 250 with my samsung evo 850 ssd (500 Gig)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.