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

bunts

macrumors member
Jun 18, 2009
75
5
UK
just for the record - for those who did successfully installed Yosemite on Mac Pro 1.1 - Do Not Upgrade to 10.10.3 - It will screw your installation with non working boot partition and recovery HD.

At lease that was my case..
Even when I tried to re-install again pre-patched installer with 10.10 over the upgraded and non working 10.10.3 it staked at the login screen.

I'm not sure that'll be the case for everyone. I have a Mac Pro 1,1 and all is fine.

I have to admit though 10.10.3 (supplemental update) was the first update that caused complications for me since first installing Yosemite on my Mac Pro 1,1, but it was the incompatible graphic driver that was causing my issue. Luckily I had my old 7300GT card to stick back in so I could see what I doing and update to the latest driver before swapping back to my PC graphics card.

Taught me to read these forums carefully before updating each time. I had been up until 10.10.3, but felt confident not to this time for some reason!
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Ok.. i just realize that. :D

Do you mean you've just realized that this thread, "[Resolved] 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite", is actually devoted to old Mac Pros? That's some reading comprehension you've exhibited. Just awesome.
 
Last edited:

sanrooney

macrumors newbie
Apr 29, 2015
5
0
Do you mean you've just realized that this thread, "[Resolved] 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite", is actually devoted to old Mac Pros? That's some reading comprehension you've exhibited. Just awesome.

hahaha.. Sorry im very new to mac.. i dont understand the difference between mac pro, macbook, mac, macbook pro.. thats why.. just now only i have google it and understand the terms... hihihi :cool:
 

xavx

macrumors newbie
Dec 26, 2013
6
0
Boot Loop

I created the image many many times, thinking that maybe i messed something up, however i always get the same result.

Computer will see the drive when pressing the Command button, after I select it, I get a black screen with the apple loogo, and that is it. The unit will never pass that point.

This is a MacBook Pro 2,2 and it it not much different then the 2,1 from what i can see.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
hahaha.. Sorry im very new to mac.. i dont understand the difference between mac pro, macbook, mac, macbook pro.. thats why.. just now only i have google it and understand the terms... hihihi :cool:

Perhaps the most obvious difference between a Mac Pro and any other Mac (including MacBook, MacBook Pro, iMac and Mac Mini) is that the latter's graphics card is in the main board itself, whereas it is an expansion card for the Mac Pro. That means that in order to have the latest available graphics card on a Mac Pro you just need to purchase an add-on PCI card (and have up-to-date drivers for it, of course) and plug it in, whereas on a MacBook Pro you would need to replace the entire main board, which would be next to impossible.
 

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
I created the image many many times, thinking that maybe i messed something up, however i always get the same result.

Computer will see the drive when pressing the Command button, after I select it, I get a black screen with the apple loogo, and that is it. The unit will never pass that point.

This is a MacBook Pro 2,2 and it it not much different then the 2,1 from what i can see.

Mac Pro is not the same as MacBook Pro so much of the advice in this thread will be of no help, particularly about graphics cards.

Also, many USB sticks won't boot correctly. If you really want to try, use a stick known to work or instead put it on a partition of a known bootable hard drive, USB or otherwise.
 

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
just for the record - for those who did successfully installed Yosemite on Mac Pro 1.1 - Do Not Upgrade to 10.10.3 - It will screw your installation with non working boot partition and recovery HD.

At lease that was my case..
Even when I tried to re-install again pre-patched installer with 10.10 over the upgraded and non working 10.10.3 it staked at the login screen.

Did you have the piker alpha yose fix installed?

I did and updated my 1,1 last weekend. I went to app store and hit "update all"

They all ran fine, it rebooted running 10.10.3 with no issues or errors.

It is CRUCIAL that you have that boot fixer that installs the boot.efi after every shut down.

This is on a 1,1 running 2,1 firmware with AMD 7950. I was then able to update Nvidia drivers and run a GTX970 with ease. If you pay attention to details, a 1,1 is easy to run Yosemite on.
 

sumer

macrumors regular
Mar 2, 2015
130
0
Toronto
Is it hosted anywhere else? The Mega file won't download for me even after registering.

it's best to use either firefox or chrome to download. You don't need to register but firefox will want you to install a plugin because the file is large.

Cheers
 

macprobuffalo

macrumors member
Feb 27, 2015
52
9
Is it normal to for the startup chime to ding twice when you turn on the computer?

I have no issues with the computer, it boots quickly. I assumed it was due to the hacked EFI to boot Yosemite but wanted to make sure

Setup:
PC flashed ati 5770
Xenon 5365 cpu's flashed to 2,1 firmware
Raid0 boot disk
24gb ram
 

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
Is it normal to for the startup chime to ding twice when you turn on the computer?

Nope. Is it two boots, like it starts to boot but then reboots for a second chime before successfully loading OS X, or two quick chimes?

I have no issues with the computer, it boots quickly. I assumed it was due to the hacked EFI to boot Yosemite but wanted to make sure

Piker's Bootloader isn't technically a hacked EFI, as it's a replacement 64-bit boot loader to allow using the native original Apple unmodified 32-bit EFI. It should boot the exact same way as the original boot loader.
 

Spiky

macrumors newbie
Apr 10, 2015
4
0
Used the Piker-Alpha loader and the PikeYoseFix my Mac pro 1.1 works awesome takes all updates (so far) I flashed a Nvidia 8800gt after that made a boot usb with Piker_alpha rebooted added the fix rebooted twice done!!!

Just so we are clear I used the pre patched Piker-Alpha on the middle of the first page of this thread and it worked as described.
 
Last edited:

sumer

macrumors regular
Mar 2, 2015
130
0
Toronto
Used the Piker-Alpha loader and the PikeYoseFix my Mac pro 1.1 works awesome takes all updates (so far) I flashed a Nvidia 8800gt after that made a boot usb with Piker_alpha rebooted added the fix rebooted twice done!!!

Just so we are clear I used the pre patched Piker-Alpha on the middle of the first page on this thread thread and it worked as described.

How easy is it to flash that card? I have one but don't know how to.
 

Spiky

macrumors newbie
Apr 10, 2015
4
0

sumer

macrumors regular
Mar 2, 2015
130
0
Toronto

macprobuffalo

macrumors member
Feb 27, 2015
52
9
Nope. Is it two boots, like it starts to boot but then reboots for a second chime before successfully loading OS X, or two quick chimes?



Piker's Bootloader isn't technically a hacked EFI, as it's a replacement 64-bit boot loader to allow using the native original Apple unmodified 32-bit EFI. It should boot the exact same way as the original boot loader.

Since I have a pc card I can't see whats going on but the pause between the chimes makes me think it's two separate boots
 

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
Since I have a pc card I can't see whats going on but the pause between the chimes makes me think it's two separate boots

Above you said it was a PC flashed 5770. If so, you just need a VGA display to see bootscreens.

Even better news is that right now over at Netkas we are working out DVI boot screens for 5770s. Already have them for 5870s.
 

humann

macrumors newbie
Mar 12, 2008
29
0
Los Angeles
Sorry to hijack the thread but my 1,1/2,1 has this issue (10.10.3 with the proper boot.efi, 4870, 16 GB RAM, homemade Fusion Drive, no trim). What do I do?

I'm not sure but I think most of the people here with the double boot thing here are booting from RAIDs or Fusion drives. I boot 10.10.3 on a 2,1 with an SSD RAID and it's always booted twice. my other single-drive boot disk does not. Doesn't bug me any more :)
 

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
Sorry to hijack the thread but my 1,1/2,1 has this issue (10.10.3 with the proper boot.efi, 4870, 16 GB RAM, homemade Fusion Drive, no trim). What do I do?
What's on the screen when the first boot gives up and reboots? How long is the first boot?

My only guess is that something is goofy with the partition set to be booted, where it first boots a different partition, gives up, and then somehow chooses the correct Yosemite partition to boot.
 

macprobuffalo

macrumors member
Feb 27, 2015
52
9
Above you said it was a PC flashed 5770. If so, you just need a VGA display to see bootscreens.

Even better news is that right now over at Netkas we are working out DVI boot screens for 5770s. Already have them for 5870s.

I'll definitely keep an eye on progress with that. I'm assuming it is done by a reflash? Or is it different drivers?

I'm not sure but I think most of the people here with the double boot thing here are booting from RAIDs or Fusion drives. I boot 10.10.3 on a 2,1 with an SSD RAID and it's always booted twice. my other single-drive boot disk does not. Doesn't bug me any more :)

Come to think of it the double chime started right around when I did the cpu upgrade and RAID boot disk. Perhaps the RAID is causing this.
 

Mr. Zarniwoop

macrumors 6502a
Original poster
Jun 9, 2005
751
139
What do I do?

Maybe try re-blessing your partition?
Code:
sudo bless --folder /Volumes/SSDname ---setBoot

Replace SSDname with your volume name. Surround the whole path with quotes if there are spaces. For example, if SSDname is "Macintosh HD" then:
Code:
sudo bless --folder "/Volumes/Macintosh HD" --setBoot
 
Last edited:

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
What's on the screen when the first boot gives up and reboots? How long is the first boot?
It's just like a regular boot - the Apple logo and the progress bar show up, the progress bar then grows to "almost" the place it usually slows down a bit (about 2-3 seconds), then the computer just restarts to a regular boot.

Come to think of it the double chime started right around when I did the cpu upgrade and RAID boot disk. Perhaps the RAID is causing this.

This might be the case, I think it might have started when I set up the FusionDrive.

Maybe try re-blessing your partition?
Code:
sudo bless --folder "/Volumes/Macintosh HD" --file "/Volumes/Macintosh HD/boot" --setBoot

Just did that, here's the dump from Terminal:
Code:
Last login: Sun May  3 23:18:58 on console
Wojteks-Mac-Pro:~ wojtek$ sudo bless --folder "/Volumes/Macintosh HD" --file "/Volumes/Macintosh HD/boot" --setBoot
Password:
Error while getting file ID of /Volumes/Macintosh HD/boot. Ignoring...
Wojteks-Mac-Pro:~ wojtek$

Checked on my other computers - I do not have a "boot" file in the root of my boot drives on neither of my 4 computers running Yosemite. What am I doing wrong?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.