Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

[chromedome45]

No Audio with Yosemite

So I managed to get Yosemite Beta 2 up and running using clover but have no audio. Suggestions? Something in config.plist? Or a kext?

 

[filmjames]

I don't normally reply to statements like this. I prefer to help whenever I post. But for you, I'll make an exception.

To simply answer your simple question... YES. People do have Yosemite working on a Mac Pro 1,1/2,1.

Now, if you want detailed instructions in how to do it yourself, READ THE THREAD. Because:
A) You might learn something. The geniuses who've made this work have gone through many trials and tribulations, so...
B) Stop asking for things to be repeated because you're too lazy to read.
C) Keeping these old machines running the latest OS requires time and patience. If you don't have enough of both of these (i.e. enough to read 19 pages), maybe it's best that you quit before you start.

So, I totally get this, but it'd be cooler to just have a guide handy too. I mean, links and other info are much easier to get from a little instruction page rather than digging through arguments and forum etiquette.

Hennessy wrote an awesome guide for Chameleon that'd be really cool looking right on the top post here.

I mean, it didn't work for me at all, but I'm sure that my case is special compared to most here. It is a least comforting to know exactly where my system stopped in the step by step instructions rather than wading through everyones trials seeing if this or that works.

 

[PeterHolbrook]

So, I totally get this, but it'd be cooler to just have a guide handy too.

The guides that several kind forum members have provided are still incomplete, as they may reflect particular hardware and even more particular configurations, not to speak of the provisional nature of the Chameleon and Clover versions currently available. Under such circumstances, trying to create a guide set in concrete right now would be foolish, as it would be short-lived and be useful to comparatively few readers; more likely than not, such guides would fail to work for many, creating unnecessary frustration.

When Yosemite GM does come out in a few weeks, expert forum members will know more, there'll probably be updated versions of both Chameleon and Clover that may overcome current problems and there may even be a Tiamo-like boot.efi for Yosemite, so the right time to compile a guide of Yosemite on an early Mac Pro will be then, not now. For now, I would suggest that you keep on reading, as we all usually learn from others.

 

[Hennesie2000]

The guides that several kind forum members have provided are still incomplete, as they may reflect particular hardware and even more particular configurations, not to speak of the provisional nature of the Chameleon and Clover versions currently available. Under such circumstances, trying to create a guide set in concrete right now would be foolish, as it would be short-lived and be useful to comparatively few readers; more likely than not, such guides would fail to work for many, creating unnecessary frustration.

When Yosemite GM does come out in a few weeks, expert forum members will know more, there'll probably be updated versions of both Chameleon and Clover that may overcome current problems and there may even be a Tiamo-like boot.efi for Yosemite, so the right time to compile a guide of Yosemite on an early Mac Pro will be then, not now. For now, I would suggest that you keep on reading, as we all usually learn from others.

The guide I made for Yosemite was only temporary to help get some other members running. It was just a modified version of my original Mavericks guide which is why I took the time since most of it was already written. The Mavericks guide is basically null and void now since Tiamo released his boot.efi.

I am using clover now instead of chameleon for Yosemite since it gets iMessage working and I was having trouble getting the newer versions of chameleon to boot Yosemite. My clover method is basically the same as my chameleon method but it involves creating a hybrid MBR since clover will not boot from a GPT like chameleon will.

 

[PeterHolbrook]

My previous post was not intended to be a criticism to your guide or anybody else's. On the contrary. I merely stressed the necessarily provisional nature of such guides, considering that the current versions of both Clover and Chameleon still have shortcomings that will probably be ironed out by the time the Yosemite GM comes out. In addition, by then there might be a Tiamo-like boot.efi that might make the use of Clover and Chameleon unnecessary. If my hunch is correct, then will be the time to prepare a guide that will be useful to ALL owners of early Mac Pros.

 

[Hennesie2000]

My previous post was not intended to be a criticism to your guide or anybody else's. On the contrary. I merely stressed the necessarily provisional nature of such guides, considering that the current versions of both Clover and Chameleon still have shortcomings that will probably be ironed out by the time the Yosemite GM comes out. In addition, by then there might be a Tiamo-like boot.efi that might make the use of Clover and Chameleon unnecessary. If my hunch is correct, then will be the time to prepare a guide that will be useful to ALL owners of early Mac Pros.

Oh I know, I was not taking offense. I was reiterating that it was just a temporary guide. I have even moved on from the guide which uses chameleon, to clover.

 

[filmjames]

My previous post was not intended to be a criticism to your guide or anybody else's. On the contrary. I merely stressed the necessarily provisional nature of such guides, considering that the current versions of both Clover and Chameleon still have shortcomings that will probably be ironed out by the time the Yosemite GM comes out. In addition, by then there might be a Tiamo-like boot.efi that might make the use of Clover and Chameleon unnecessary. If my hunch is correct, then will be the time to prepare a guide that will be useful to ALL owners of early Mac Pros.

I totally understand the shortcomings of guides at this stage of development, no worries. It just makes things easier when you know you've screwed up on step 7 rather than post 204 or whatnot.

Patience and study is the only way to learn from the screw ups right?

Funny how Hennesie moved to clover just as I get Chameleon working from his guide. Got to DP7 this time without any issues though, thanks!

 

[Hennesie2000]

I totally understand the shortcomings of guides at this stage of development, no worries. It just makes things easier when you know you've screwed up on step 7 rather than post 204 or whatnot.

Patience and study is the only way to learn from the screw ups right?

Funny how Hennesie moved to clover just as I get Chameleon working from his guide. Got to DP7 this time without any issues though, thanks!

Do you have iMessage working? That was my primary reason for moving to Clover. I could get it working in Chameleon but it involved booting once in Clover. Once winch posted how to get audio and the on board SATA ports working with Clover then it was an easy switch for me.

 

[filmjames]

Do you have iMessage working? That was my primary reason for moving to Clover. I could get it working in Chameleon but it involved booting once in Clover. Once winch posted how to get audio and the on board SATA ports working with Clover then it was an easy switch for me.

I get "An error occurred during activation. Try again." when I enter my password. I actually prefer to not use iMessage on my workstation so this isn't a deal breaker at all. I haven't tried using handoff.

 

[Hennesie2000]

I get "An error occurred during activation. Try again." when I enter my password. I actually prefer to not use iMessage on my workstation so this isn't a deal breaker at all. I haven't tried using handoff.

Yea, until a 10.10 compatible FileNVRAM module comes out, iMessage doesn't work with Chameleon until you boot once using Clover. However on each DP update it will stop working until you boot once using Clover again.

 

[ahmeier]

Mac Pro 1,1 firmware upgrade hack

I have Maverick running using Tiamo's boot loader (great after having to deal with slow Chameleon startup for years...). I am now playing with public beta Yosemite but so far have not been successful. I was wondering whether the 1,1 to 2,1 firmware hack was necessary to get this to work. My Boot ROM Version is MP11.005D.B00. Anybody successful with that version?

If 2,1 upgrade necessary, how do you actually do it? I looked through many threads but haven't found the "method" yet.

I am reasonably computer savvy, but not a true hacker.

Thanks, I really appreciate this thread which allowed me to learn a lot about my beloved Mac Pro 1,1

Andreas

 

[Hennesie2000]

I have Maverick running using Tiamo's boot loader (great after having to deal with slow Chameleon startup for years...). I am now playing with public beta Yosemite but so far have not been successful. I was wondering whether the 1,1 to 2,1 firmware hack was necessary to get this to work. My Boot ROM Version is MP11.005D.B00. Anybody successful with that version?

If 2,1 upgrade necessary, how do you actually do it? I looked through many threads but haven't found the "method" yet.

I am reasonably computer savvy, but not a true hacker.

Thanks, I really appreciate this thread which allowed me to learn a lot about my beloved Mac Pro 1,1

Andreas

The firmware upgrade is not necessary. It is only necessary to get an upgraded pair of processors like the x5365's to be recognized properly instead of showing "unkown" in about this Mac. However since you have the refurb MP11.005D.B00 firmware which was not released to the public it is newer and should already have support for the quad core 53xx processors.

 

[ahmeier]

The firmware upgrade is not necessary. It is only necessary to get an upgraded pair of processors like the x5365's to be recognized properly instead of showing "unkown" in about this Mac. However since you have the refurb MP11.005D.B00 firmware which was not released to the public it is newer and should already have support for the quad core 53xx processors.

thanks!

 

[schalliol]

Just curious, what cards are you ordering to try to get it to work properly? I have had some difficulty with handoff on my late 13 retina MBP and iPad/iPhone on its own up to DP10, so it might not be a machine specific issue.

 

[filmjames]

Yea, until a 10.10 compatible FileNVRAM module comes out, iMessage doesn't work with Chameleon until you boot once using Clover. However on each DP update it will stop working until you boot once using Clover again.

I'll give Clover a shot tonight and let you know the results.

My main MacPro has been running 10.10 like a champ with the 560Ti - it is actually much more stable than every 10.9 release I've had. Still have the occasional need to reboot, but no kernel panics or anything crazy. Finder crashes a little more but in 10.9 it'd hang forever at times.

I have two other MacPro 1,1 machines to put it on as well - one running a 5770 Mac card and the other with a Radeon HD 6570 (it was $40 and didnt require the power cable, don't judge). Any thoughts on cloning my current 10.10 system for the other machines rather than a fresh install?

 

[ahmeier]

USB port issues

I was able to get Yosemite running well using winch's most recent modification of clover. I run an old Apple Studio display with ADC connector as a second monitor through an ATI Radeon HD 5770 1024. This requires a ADC to Dvi adapter, then a DVI to thunderbolt adapter, and it works great. The one thing that does not work with this are the USB ports on the back of that monitor.

The startup message regarding this error is in the system log:

The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x3d000000)

It is not a big deal, but as it is an error I thought I share it with this group of experts.

Appreciate all of your help, this thread is really great!

 

[Hennesie2000]

I was able to get Yosemite running well using winch's most recent modification of clover. I run an old Apple Studio display with ADC connector as a second monitor through an ATI Radeon HD 5770 1024. This requires a ADC to Dvi adapter, then a DVI to thunderbolt adapter, and it works great. The one thing that does not work with this are the USB ports on the back of that monitor.

The startup message regarding this error is in the system log:

The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x3d000000)

It is not a big deal, but as it is an error I thought I share it with this group of experts.

Appreciate all of your help, this thread is really great!

Unplug everything except your keyboard and mouse and see if the error still exist.

 

[applereviewguy]

Hello, just wondering if you have released the script yet seeing as how we are on DP5 now. Thank you

Wow I totally forgot about this

Yes, I will release the script once the GM comes out.

 

[haralds]

I'll give Clover a shot tonight and let you know the results.

My main MacPro has been running 10.10 like a champ with the 560Ti - it is actually much more stable than every 10.9 release I've had. Still have the occasional need to reboot, but no kernel panics or anything crazy. Finder crashes a little more but in 10.9 it'd hang forever at times.

I have two other MacPro 1,1 machines to put it on as well - one running a 5770 Mac card and the other with a Radeon HD 6570 (it was $40 and didnt require the power cable, don't judge). Any thoughts on cloning my current 10.10 system for the other machines rather than a fresh install?

For me, CarbonCopy Cloner has been great for this purpose, I use it all the time. You will need the beta version for Yosemite.
It knows, how to handle the Recovery Partition.

 

[H2SO4]

For me, CarbonCopy Cloner has been great for this purpose, I use it all the time. You will need the beta version for Yosemite.
It knows, how to handle the Recovery Partition.

I’d say that the inbuilt Disk Utiltiy is even better. Strangely enough even the version with 10.6 handles the Recovery Partition properly.

 

[haralds]

I’d say that the inbuilt Disk Utiltiy is even better. Strangely enough even the version with 10.6 handles the Recovery Partition properly.

I have not used it for regular partitions - is it able to deal with size differences?

The nice part about CC is that it can be used for other use cases.

 

[Hennesie2000]

I’d say that the inbuilt Disk Utiltiy is even better. Strangely enough even the version with 10.6 handles the Recovery Partition properly.

I like to use CCC as well. It is especially handy when trying to clone to a smaller drive. Disk Utility will tell you there is not enough room even though the actual space used on the disk is far less than the space available on the disk you are trying to clone it to.

 

[H2SO4]

I like to use CCC as well. It is especially handy when trying to clone to a smaller drive. Disk Utility will tell you there is not enough room even though the actual space used on the disk is far less than the space available on the disk you are trying to clone it to.

Now that I think about it, yes you are correct.

 

[H2SO4]

Got the following today suddenly.

Anybody else had it?

 

[Hennesie2000]

Anybody else had it?

Yes, I posted about it on the previous page. I called apple care and they took care of it in a few minutes. You will need to log into appleid.apple.com and generate a temporary support pin. Then give them that 12 digit code. Then you should be able to login fine.

You will be asked for a serial number. Make sure you are using your real Mac Pro serial number.