Huh? The Mac Pro has (broken) Yosemite and a black screen. I want to put Lion on the HDD so i can swap the system and boot the Mac Pro from Lion and fix the EFIs.
How can I use the Mac Pro to install Lion if I need Lion to boot it?
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.
Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
- Thread starter Mr. Zarniwoop
- Start date
- Sort by reaction score
Huh? The Mac Pro has (broken) Yosemite and a black screen. I want to put Lion on the HDD so i can swap the system and boot the Mac Pro from Lion and fix the EFIs.
How can I use the Mac Pro to install Lion if I need Lion to boot it?
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
What are you using to boot the Lion installer on the MacBook?
The Mac Pro will boot lion natively so you can just boot the Lion installer on the Mac Pro. Easiest option is to make a Lion install DVD. Then hold C at boot on the Mac Pro to boot from that disc.
What are you using to boot the Lion installer on the MacBook?
The Mac Pro will boot lion natively so you can just boot the Lion installer on the Mac Pro. Easiest option is to make a Lion install DVD. Then hold C at boot on the Mac Pro to boot from that disc.
That's where I struggle. I have a lion installer on my macbook and it won't install (not even on an external hdd) because it says the macbook is running a version too new (Yosemite) to install an old OSX. I don't know how to get around that.
You just made my day. Thank you so much.
And a huge thanks to Pike, Tobyg and all the awesome guys who make a great work for us!!!!
Sudo: command not found
I am trying to follow the instructions a few posts back for copying pikes boot.efi onto my 10.10.2 Yosemite SSD. Booted a retail Snowleopard dvd and started terminal. Changed directory (I'm assuming, doesn't change the prompt, but doesn't give me an error either) but both " sudo chef lags -nouchg boot.efi " and " sudo rm -rf boot.efi " give me "-bash: command not found" and return me to a " -bash-3.2# ". I should note, that I also have a working 10.9.5 install that I can boot from, but I got some errors about illegal operations the first time I tried.
I am trying to follow the instructions a few posts back for copying pikes boot.efi onto my 10.10.2 Yosemite SSD. Booted a retail Snowleopard dvd and started terminal. Changed directory (I'm assuming, doesn't change the prompt, but doesn't give me an error either) but both " sudo chef lags -nouchg boot.efi " and " sudo rm -rf boot.efi " give me "-bash: command not found" and return me to a " -bash-3.2# ". I should note, that I also have a working 10.9.5 install that I can boot from, but I got some errors about illegal operations the first time I tried.
I'm assuming "chef lags" is a typo because "chflags" the proper command. If "chef lags" is what you put in terminal then that is the problem.
Autocorrect not correct
I input the commands correctly. Please excuse the chef lags above. Lol.
I input the commands correctly. Please excuse the chef lags above. Lol.
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
I'm not sure if it matters or not but have you tried the path with proper capitalization?
/Volumes/Mac HD/System/Library/CoreServices
I'm not sure if it matters or not but have you tried the path with proper capitalization?
/Volumes/Mac HD/System/Library/CoreServices
Well, I finally managed to get my system started again.
It runs 10.10.2 and boots up normally with the replaced boot.efis, however when I do this to make sure I'm good for future updates:
1. Install the Piker script but DO NOT restart.
2. Delete the installed boot.efi.tiamo in the /usr/standalone/i386 folder
3. Duplicate the boot.efi file that is in that folder (command + D)
4. Change the name from "boot.efi copy" to boot.efi.Tiamo
5. Restart
...it will overwrite the efis again during restarting and gets stuck on black screen.
Am I missing something? I thought 1) installing the script will prevent the efis from being overwritten.
It runs 10.10.2 and boots up normally with the replaced boot.efis, however when I do this to make sure I'm good for future updates:
1. Install the Piker script but DO NOT restart.
2. Delete the installed boot.efi.tiamo in the /usr/standalone/i386 folder
3. Duplicate the boot.efi file that is in that folder (command + D)
4. Change the name from "boot.efi copy" to boot.efi.Tiamo
5. Restart
...it will overwrite the efis again during restarting and gets stuck on black screen.
Am I missing something? I thought 1) installing the script will prevent the efis from being overwritten.
For the life of me I don't know how people have so much trouble with this.
Last night I took my 1,1 from 10.10 to 10.10.2 with greatest of ease.
I ran the pikeryose thingy that blacksheep666 posted, rebooted, ran the updater in the app store and all was well.
It really is that simple.
Last night I took my 1,1 from 10.10 to 10.10.2 with greatest of ease.
I ran the pikeryose thingy that blacksheep666 posted, rebooted, ran the updater in the app store and all was well.
It really is that simple.
Well, I guess you were smart enough to run the pikeryosefix before you updated. Probably you read somewhere that you had to do that in order to install 10.10.2.
I - and a lot of people who are having problems - installed 10.10.2 before they read this thread. That makes it more difficult.
For example after a couple of hours I managed to replace the EFIs manually on the drive that had already updated to 10.10.2. I installed the pikeryosefix script so that it won't be a problem in the future, but when I restart to activate it, I always end up with broken EFIs again.
So now I'm scared to turn off my computer because rebooting will somehow cause the EFIs be overwritten with faulty ones again, even though I have installed the pikeryosefix and followed instructions to a T.Capitalization
Sorry for the delayed response. I will try soon. Dealing with a sick wife and a sick 10 month old. ( posted from my hiding spot. Aka the bathroom. Lol)
Sorry for the delayed response. I will try soon. Dealing with a sick wife and a sick 10 month old. ( posted from my hiding spot. Aka the bathroom. Lol)
Anyone willing to help me is greatly appreciated!
I am booting from 10.10.2 with manually replaced boot.efi. i installed pikeryosefix AFTER succesfully booting with manually replaced efis, so there won't be any future problems.
But now everytime I turn off my computer the efis are overwritten with faulty ones when I boot back up, causing a black screen.
To repeat: 10.10.2 works perfectly for me EXCEPT for the fact that I can't turn off the computer or else I'll lose my working efis again.
Help!
I am booting from 10.10.2 with manually replaced boot.efi. i installed pikeryosefix AFTER succesfully booting with manually replaced efis, so there won't be any future problems.
But now everytime I turn off my computer the efis are overwritten with faulty ones when I boot back up, causing a black screen.
To repeat: 10.10.2 works perfectly for me EXCEPT for the fact that I can't turn off the computer or else I'll lose my working efis again.
Help!
Why are you doing all this? Which script are you running?
If you ran the PikeYoseFix and rebooted, that's all that's needed.
I tried the TobyG first and that didn't work. I then managed to replace the efis manually which at least let me boot again in 10.10.2 and everything seemed alright. I then ran the PikeYoseFix so I won't have to replace the efis manually again in the future. But now when I reboot my computer the efis get overwritten anyway and i end up with a black screen again. Manually replacing the efis fixes that again, but as soon as I turn my computer off and on I end up with broken efis again.
Thank you for your help!
In the first post, you mentioned you altered what PikeYoseFix is copying, and now it's not clear.
I would clear the launch daemon out, and remove all traces of the script. And then if you still want the script installed, as it is great insurance, install it but don't screw with it.
The purpose of the script is to replace the boot.efi files right before every reboot. That is how it works and why it works. When you install 10.10.2 and it replaces the boot.efi file with a non working one and then it ask you to reboot. Right before you reboot the script puts back the working Pike boot.efi file. This way the system continues to boot.
He was messing with it because he installed the TobyG script instead of the PikeYoseFix as described in my post before 666Sheep had posted the PikeYoseFix.
PRAM reset
oh trouble
Running 10.10.0 on my Mac Pro 1.1 when i ran into an issue on reboot. Black Load screen with the apple logo gets stuck at around 50%, can be left for however long and still refuses to boot.
i have tried using safe mode, goes no where
i have tried using CMD+R to boot the recovery disk, holds at the same screen
i have used OPTION key, i can see the boot disk, and the recovery disk, as well as a windows partition. the windows partition boots with out any issues, but neither of the mac drives do.
what is the best way of further diagnosing this? i tried doing a verify disk / verify permissions from my mac mini (hooking the mac pro drive up thorough firewire). drive checked out fine.
what should i try next?
Running 10.10.0 on my Mac Pro 1.1 when i ran into an issue on reboot. Black Load screen with the apple logo gets stuck at around 50%, can be left for however long and still refuses to boot.
i have tried using safe mode, goes no where
i have tried using CMD+R to boot the recovery disk, holds at the same screen
i have used OPTION key, i can see the boot disk, and the recovery disk, as well as a windows partition. the windows partition boots with out any issues, but neither of the mac drives do.
what is the best way of further diagnosing this? i tried doing a verify disk / verify permissions from my mac mini (hooking the mac pro drive up thorough firewire). drive checked out fine.
what should i try next?
Well, I used the Hennesie method to update to Yosemite on my Mac Pro 1,1 back in November, and I then used the Piker method to change the boot.efi as recommended prior to the 10.10.2 software update. I did the 10.10.2 update. Everything went smoothly. I have been using the computer last week and all weekend. Until this morning. I awoke to find a black screen with a folder with a question mark in it. The computer was unable to recognize any boot disk. I was able to boot with my Snow Leopard disk. I am now trying to redo the Yosemite update. Any suggestions as to what happened so I can avoid this again in the future? Thanks, Steve
Thanks for the prompt reply!
here is where its been stuck:
Additionally, I ran a diagnostics through single user mode. Got message: "the volume Macintosh HD1 appears to be ok"
***** the volume was modified *****
Last edited: