Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Another post from me, yay!

After busting my brains creating a functional bootable usb, I have decided to just use one of my Mac pro internal drives to boot from and voila it works. At this second I'm creating a fresh install of mavericks onto my fusion drive. Hopefully there are some speed improvenents.

I'll keep you all posted.

SL
 
This happened to me and I did *not* apply any updates since 10.9.2. They worked fine for months and just didn't work one day.

This is not related to any updates. I have been using Mavericks using Chameleon/Tiamo with every update since it came out last year and never had a problem with iMessage. As I said before it is an issue with Apples authentication server. I have also been using Yosemite since DP1 was released and never had any issues with iMessage. Both Mavericks and Yosemite gave me that error the same day when they had both been working the day before.
 
Another post from me, yay!

After busting my brains creating a functional bootable usb, I have decided to just use one of my Mac pro internal drives to boot from and voila it works. At this second I'm creating a fresh install of mavericks onto my fusion drive. Hopefully there are some speed improvenents.

I'll keep you all posted.

SL

Glad you got it to work!

In case it helps others, if you were having problems making a bootable USB drive, one common confusion is that they need to be partitioned as GUID. Commonly, USB drives are partitioned as MBR which works fine for data, as long as you're not trying to use them to boot on a Mac.
 
Glad you got it to work!

In case it helps others, if you were having problems making a bootable USB drive, one common confusion is that they need to be partitioned as GUID. Commonly, USB drives are partitioned as MBR which works fine for data, as long as you're not trying to use them to boot on a Mac.

Yes, finally got it to work. Believe me, I have tried every partition from GUID down to MBR and it was a no go. I really think my MP2,1 was disabling usb support. After experimenting with Fusion and Raid I came into a conclusion to merge the two. I Raided my SSD and created a Fusion Drive with my Raid SSD with a 1 TB HDD. So far so good and a very good improvement with speed according to Blackmagic Disk. Only issue is that I can't figure out how to create a Recovery HD 10.9. But I'm sure I'll find an answer somewhere in this forum. :)

SL:cool:
 
Then on 1.1 tiamo maveric 10.9.4 , upload from applestore from 10.9.4 to 10.9.5 , need or not need make tiamo instal again?
I lose the 64 efi?
 
iMessages all active again. Gave them a call and all good. Didn't ask me for a s/n

I too have contacted Apple because my Imessage needed authentication. They ask for my SN and I told them that I have a Mac pro2 1 and after a few seconds my imessage was up and running.
 
Success ! but now getting KP when upgrading RAM

After reading so many success stories I thought I'd take the plunge and add my experience with you guys.

My base build prior to the challenge was a macpro1,1 with 2 x 3GHz Dual Core Xeon running on 250GB Sata HDD with 10.6.8, Geforce 7300GT, 4GB Ram (8x512MB).

Now have successfully upgraded to MacPro2,1 with 2 x 2.66Ghz Quad Core Xeon running on a Samsung Evo 840 250GB SSD 10.9.5, 250GB Sata HDD 10.6.8, XFX ATI HD6870 Black Edition, 4GB Ram (8x512MB)

Now trying to get my ram upgrade working without success - it's 6 x 2GB Kingston Ram (KTA-MP667AK2/4G) which boots into 10.6.8 fine no problems but does not all work in 10.9.5 - just getting KP every single time I boot with the attached KP errors.

Since trying to play around with the different ram configurations the most amount of ram that works with 10.9.5 is 7GB which is 2 x 2GB and 6 x 512MB Ram.

Not sure if anyone has come across this before but I'm at a lost to why it works fine in OSX 10.6.8 and not mavericks!

Have not reset the PRAM so will do this later today when I get back from work!
 

Attachments

  • IMG_4723.JPG
    IMG_4723.JPG
    82.1 KB · Views: 180
^It's not the Mavericks fault. Drivers didn't even get loaded. It's more like hardware issue (loose connection, cable or so, short-out etc). It doesn't look like RAM problem either. You'd get a different KP log in such case. Check all possible connections first.
 
^It's not the Mavericks fault. Drivers didn't even get loaded. It's more like hardware issue (loose connection, cable or so, short-out etc). It doesn't look like RAM problem either. You'd get a different KP log in such case. Check all possible connections first.

Thanks for the advice 666sheep - I'll recheck everything again - maybe it might be that I'm running my sata bluray drive and ssd through one molex to split sata power cable, or maybe running both geforce and ati display cards are causing the issue - not sure but I'll remove as much as possible before trying again.
 
Thanks for the advice 666sheep - I'll recheck everything again - maybe it might be that I'm running my sata bluray drive and ssd through one molex to split sata power cable, or maybe running both geforce and ati display cards are causing the issue - not sure but I'll remove as much as possible before trying again.

Well spent several hrs trying to get these ram working with my build without success, I've literarily taken everything back to my original base build without replacing the cpu's but still not able to install any more than 4gb ram - I'm leaning towards a faulty ram but I ask myself why does it boot in 10.6.8 fine even put in some 4gb Hp ram in there with the 12gb Kingston ram and it still picks up 16gb, even went and did a fresh install of 10.9.4 but same kp. Pram zapped it several times and it seems to boot into 10.9.5 with 2x2gb and 6x512mb but even with this the system was unstable I.e applications would hang, random reboots, fans going wild, etc... Now back with my 8x512mb original ram and system is working again - never had an issue before with ram behaving so badly...##
 
Eyesman, did you ever figure this out? Did reverting to an earlier system cure it?

I'm having what sounds like the same issue, except I can't tell if it started with 10.9.3 because I rarely switch things in the USB ports. I have done each delta update within a week or two of its release. (After waiting for the adventurers on this thread to confirm that it works!)

First noticed last week that a wired keyboard & mouse wasn't recognized. Then a thumb drive, then a portable hard drive. The only thing still running on USB is my Elgato TV tuner. I *think* I've recently unplugged and replugged it when I was re-routing some wires, but I'm not sure and not going to risk experimenting with it since that's my main use for the machine.

What else could affect USB ports? Restart hasn't helped; can't do PRAM reset because wired keyboard not recognized.

I managed to fix this in my machine. I had a Digidesign / Avid MBox 1 that was failing to load. It kept trying too, preventing anything else from working.

USB mouse light would go on, but mouse wouldn't move. Had to screenshare in, and looked at console. Found one item there in particular that was continually failing to load. For me, it was digidesign MBox (that I know isn't supported in Mountain Lion). Went through and manually deleted a whole bunch of files from based on Avid's KB: http://avid.force.com/pkb/articles/...id-Audio-Interface-Driver-Components-Mac-OS-X. Now it works :)

It also fixed a bug where if I went to Apple -> Restart, nothing would show.

Hope this helps.
 
Well spent several hrs trying to get these ram working with my build without success, I've literarily taken everything back to my original base build without replacing the cpu's but still not able to install any more than 4gb ram - I'm leaning towards a faulty ram but I ask myself why does it boot in 10.6.8 fine even put in some 4gb Hp ram in there with the 12gb Kingston ram and it still picks up 16gb, even went and did a fresh install of 10.9.4 but same kp. Pram zapped it several times and it seems to boot into 10.9.5 with 2x2gb and 6x512mb but even with this the system was unstable I.e applications would hang, random reboots, fans going wild, etc... Now back with my 8x512mb original ram and system is working again - never had an issue before with ram behaving so badly...##
Well it looks like I've found out the solution to this and was a school boy error. The boot.efi used was somehow restricted to a max 4gb replaced the two files and now able to boot with 16gb!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.