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

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Reset pram

Oh, OK, it would have been nice had that been in the initial thread.

I did go through the annoying install again and it's fine now, it's just an annoyance and a time waster.

Could someone update that there please?

Also, I can't find usr/standalone/i386 at all on the old mac as a folder to put Pike's efi file into.

Has the name changed over time?

I guess repair permissions is simply done from disk utility as well, right?
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Oh, OK, it would have been nice had that been in the initial thread.

I did go through the annoying install again and it's fine now, it's just an annoyance and a time waster.

Could someone update that there please?

Also, I can't find usr/standalone/i386 at all on the old mac as a folder to put Pike's efi file into.

Has the name changed over time?

I guess repair permissions is simply done from disk utility as well, right?

Press command+shift+G the type /usr and press enter. These are very basic finder functions.
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Oh, OK, it would have been nice had that been in the initial thread.

I did go through the annoying install again and it's fine now, it's just an annoyance and a time waster.

Could someone update that there please?

Also, I can't find usr/standalone/i386 at all on the old mac as a folder to put Pike's efi file into.

Has the name changed over time?

I guess repair permissions is simply done from disk utility as well, right?

Oh, sorry about that, I forgot to show hidden files.

I'm so used to them always being displayed in Windows.
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Don't forget to swap out the boot.efi files before attempting to boot the MacPro1,1 on its own. And, don't for get to install the PikeYoseFix before attempting to update the OS.

So the Asus card doesn't work, but an ATI one does.

However, though I get a boot screen, I get an icon of a folder with a question mark on.

I did have two disks in the old mac pro when I did the installation from the appstore onto the target disk, and indeed, the initial setup did come up, but on the new mac, as I was away and it rebooted all by itself.

Now what?

Do I have to sit by it and make sure that it does not reboot all by itself and run initial setup on new mac hardware?

Can I do anything at this point so as to not need to duplicate anything?


Thank you z
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Press command+shift+G the type /usr and press enter. These are very basic finder functions.

Do I need to swap the cards and install pike's boot file before the first restart the installed attempts to make after rebooting once to start the installation process? (also swapping the video card of course)

Or do I let the installed reboot with the older mac still in target disk mode so that initial setup is run against the newer hardware after which I swap the boot files and graphics card?
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Reset pram

Apparently all I needed to do was select the newer Mac's HDD as the one the machine should use as a startup disk.

Could this be put in the initial thread please so that other people won't have to waste time either reinstalling the OS as I did or having to find this out all by themselves?


Thanks.
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Hi guys.

The "easy" solution simply does not work.

I've put my old mac in target disk mode, downloaded yosemite on the newer one, installed it specifying my old macs drive as the target, it installed, rebooted until I was actually able to boot the OS up on the newer mac and it went through all of it's setup stuff, it even let me browse files and so on so forth and start applications, but I can not put pike's boot file on it and repair permissions because the repair permissions button is greyed out as if my disk isn't even an OS startup disk.

What then is missing during the process, am I not supposed to run initial setup on while still connected to the newer mac over firewire?

Because leaving it connected until the OS is all up and running makes it only work if connected to that mac over firewire, but not in it's own older hardware at all.

Could someone PLEASE shed some more light on this for me, I really am trying to get this working for my charity and it's just not working due to steps being missed in the thread. (just like the one about selecting my newer Macs HDD as the startup disk after I disconnect the target disk that just got yosemite installed over 10.6.8)
 

charitytechsupport

macrumors newbie
Sep 27, 2015
29
0
Hi guys.

The "easy" solution simply does not work.

I've put my old mac in target disk mode, downloaded yosemite on the newer one, installed it specifying my old macs drive as the target, it installed, rebooted until I was actually able to boot the OS up on the newer mac and it went through all of it's setup stuff, it even let me browse files and so on so forth and start applications, but I can not put pike's boot file on it and repair permissions because the repair permissions button is greyed out as if my disk isn't even an OS startup disk.

What then is missing during the process, am I not supposed to run initial setup on while still connected to the newer mac over firewire?

Because leaving it connected until the OS is all up and running makes it only work if connected to that mac over firewire, but not in it's own older hardware at all.

Could someone PLEASE shed some more light on this for me, I really am trying to get this working for my charity and it's just not working due to steps being missed in the thread. (just like the one about selecting my newer Macs HDD as the startup disk after I disconnect the target disk that just got yosemite installed over 10.6.8)

Having said all of that, I must say that Yosemite is behaving quite confusingly.

It didn't see my target disk in the old mac as an OS disk so as to let me repair it's permissions, so I naturally thought something went wrong, since that would indicate that it is a data drive only, if it doesn't let me repair permissions that is.

However, upon bootup, it simply proceeded to let me boot it up just fine, which it didn't before, presumably because I had a second boot-up hdd in it, and it appeared to have never made my main had in the old one a bootable one.

However, what amazes me the most is that pike's boot.efi worked without even repairing permissions and simply booted after a mere copy paste into the two locations mentioned in the previous post.

So I am now actively running a permissions repair on it after it has simply booted up all by itself.

Is that all that is required then, to merely install the os from inside a newer mac onto an older one which is in target disk mode, let it reboot and all until it comes up with the newer os starting up from the old drive on the new hardware, shutting that down and replacing the boot.efi files in both locations after a second target disk mode setup?

Of course, apparently there have to be no other bootable os drives on the old mac. Perhaps disconnecting any other hdd from it will male it ultra-sure that it won't mess itself up.

Is it even worth repairing permissions afterwards since it boots up on the old mac just fine?


Of course I'll install the yosefix before we install any OS updates, especially upgrades like El Capitan.


Thanks!
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Having said all of that, I must say that Yosemite is behaving quite confusingly.

It didn't see my target disk in the old mac as an OS disk so as to let me repair it's permissions, so I naturally thought something went wrong, since that would indicate that it is a data drive only, if it doesn't let me repair permissions that is.

However, upon bootup, it simply proceeded to let me boot it up just fine, which it didn't before, presumably because I had a second boot-up hdd in it, and it appeared to have never made my main had in the old one a bootable one.

However, what amazes me the most is that pike's boot.efi worked without even repairing permissions and simply booted after a mere copy paste into the two locations mentioned in the previous post.

So I am now actively running a permissions repair on it after it has simply booted up all by itself.

Is that all that is required then, to merely install the os from inside a newer mac onto an older one which is in target disk mode, let it reboot and all until it comes up with the newer os starting up from the old drive on the new hardware, shutting that down and replacing the boot.efi files in both locations after a second target disk mode setup?

Of course, apparently there have to be no other bootable os drives on the old mac. Perhaps disconnecting any other hdd from it will male it ultra-sure that it won't mess itself up.

Is it even worth repairing permissions afterwards since it boots up on the old mac just fine?


Of course I'll install the yosefix before we install any OS updates, especially upgrades like El Capitan.


Thanks!

Do not update to El Capitan yet.
 
  • Like
Reactions: splifingate

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Apparently all I needed to do was select the newer Mac's HDD as the one the machine should use as a startup disk.

Could this be put in the initial thread please so that other people won't have to waste time either reinstalling the OS as I did or having to find this out all by themselves?


Thanks.

Resetting the PRAM would do the same thing as the Startup Disk selection is stored there.
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Yes, I know, I wasn't going to.

I've been closely watching that thread.

Btw, any idea if I could get that asus card to work?

Is there a driver I could install?

It would be great if I could get it to work!


Thanks!

That card is natively supported by OS X. Since it is a PC card the port mappings could be different so all ports may not work. Try another port on the card.
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
What do you mean when you say go back to the first post I dont see any other link in the original post https://forums.macrumors.com/threads/2... Can you please help me to find the rigth PikeYoseFix Patch to upgrade my Mac Pro ??? Thanks

What I mean is read more then 3 lines into the first post and there is a link for the PikeYoseFix.

vanna_zps27iyy1xi.jpg
 

Chooly

macrumors newbie
Oct 6, 2015
1
0
Hi everyone, I'm having an interesting problem and I was hoping anyone could offer any tips.
First thanks to everyone that's been actively supporting people in this thread, you guys are heroes.
I've got Yosemite running perfectly on my Mac Pro 1,1 thanks to OP's Guide, and I have installed Pike's Yosefix to keep my boot.efi from being overwritten.

The thing that's strange is Pike's Yosefix doesn't seem to be taking... and every morning when I boot up I am pushed to my second HDD's Lion install. Of course I'll fix it by overwriting the boot.efi files.
Haven't updated Yosemite and I've left the Lion install on my alternate HDD to troubleshoot.
Since this is happening every day I'm wondering if anyone knows about the problem or can suggest any fixes?

Sorry if this has been addressed in the 150+ pages of the thread, but I haven't scanned it all and searches haven't come up with any answers.

Cheers!
 

daav5

macrumors newbie
Oct 8, 2015
2
0
i installed Yosemite on a MacPro 1.1 with the boot method given on first thread
worked like a charm - after i sweated with SFOTT method

thanx to all guys
 

dannymk

macrumors newbie
Oct 23, 2013
2
0
Carnation, Wa
We stand on the shoulders of giants! Props to all who have contributed to the success of enabling El Cap to run on my early 2006 Mac Pro.

Partitioned the other half of my Yosemite drive, connected a firewire cable between my MBP and the MP, put it into Target Disk Mode and installed El Cap to the partition. Unlocked the boot.efi files, removed them, copied in the updated versions, changed the StartUp Disk and rebooted - BAM - this is freakin amazing!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.