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
Thanks for this.
The only thing I noticed after restarting is an erroneous report of the CPU die sensors - not sure it was related though, I just had to reset the smc and everything was back to normal.
I've been experiencing random reboots with my 2,1 and found here that the problem is with the memory management and the solution is to put all the RAM into one riser and not use the other (essentially forcing dual channel mode). This solution works for me right now, but I was thinking about future use of this machine.
In the thread I linked, the bug speculates that either the Northbridge chip or the logic board is at fault. Is there a soft/firmware update that can fix this? ... would finding a new board change the situation?
Right now it doesn't impact me much (I'm not close to 16GB of ram for one riser), but it would be nice getting quad channel access back not to mention the possibility maxing out the RAM.
Raid
In the thread I linked, the bug speculates that either the Northbridge chip or the logic board is at fault. Is there a soft/firmware update that can fix this? ... would finding a new board change the situation?
Right now it doesn't impact me much (I'm not close to 16GB of ram for one riser), but it would be nice getting quad channel access back not to mention the possibility maxing out the RAM.
Raid
Yep, I'm still running my machine on 6GB on one riser card.
I'm glad you found my other longwinded thread, I was trying to put as much info out there for the next guy as I could.
As you said, it is pure speculation on my part, but I'm leaning towards either the support circuitry for the Northbridge on the motherboard, or one/ possibly both bad riser cards.
I did try reverting back to a 1,1 (both SMC and firmware) and replacing the power supply, but had the same problem.
I wish I had another set of riser cards to try out, but I'm thinking that it is most likely on the motherboard itself.
If that is the case, it seems to be cheaper to just find another 1,1 or 2,1 complete machine, than to source a replacement motherboard.
Hopefully someone here can come up with an answer, I too would love to get more of my RAM back.
Cheers.
- Jay
I had a working install of Yosemite on a 2007 Mac Pro and installed this script and it no longer booted Yosemite. Erasing the boot efi file that was installed didn't help either. I had to erase the drive and do a clean install of Yosemite and after changing the boot efi files it booted correctly- after migrating my files from my backup it no longer boots Yosemite.
The latest clean install works but I can't restore my files from Time Machine (I tried to restore from a date previous to the script install).
There must be something in this script that's incompatible with my system. How do I remove the program completely? (I'm not sure where the script files are saved).
Any help would be appreciated.
That package just installs a boot.efi and a launch daemon. Nothing else. It should not have made your machine unable to boot.
When I rebooted with my test drive that had only a clean install of Yosemite plus the changed boot efi, I got an error message that said the mac had a kernel panic.
I'm not sure what went wrong- all I did was install the package and it would no longer reboot.
Thanks,
D
I'm not sure what went wrong- all I did was install the package and it would no longer reboot.
Thanks,
D
kernel panics, also
I'm also experiencing kernel panics since I installed the "PikeYoseFix.pkg". Everything was all kosher before when I just had the "black Pike" boot.efi installed.
I then installed the "PikeYoseFix.pkg" over it. Rebooted and fixed permissions. Machine sits for awhile. I come back to my machine and see it crashed/rebooted with a dialog box. Log says their was kernel panic.
specs
1,1 flashed to 2,1
5870 radeon
16gb ram
os 10.10.1
I'm also experiencing kernel panics since I installed the "PikeYoseFix.pkg". Everything was all kosher before when I just had the "black Pike" boot.efi installed.
I then installed the "PikeYoseFix.pkg" over it. Rebooted and fixed permissions. Machine sits for awhile. I come back to my machine and see it crashed/rebooted with a dialog box. Log says their was kernel panic.
specs
1,1 flashed to 2,1
5870 radeon
16gb ram
os 10.10.1
Post KP log using
Code:
tag. I never encountered KPs with black or grey version of PikeYoseFix. Changes in the script are very simple: boot.efi.tiamo renamed to boot.efi.pike, com.tiamo.macprofix.plist renamed to com.pike.yosefix.plist, boot.efi.tiamo replaced with boot.efi.pike in the package. Nothing more.
Do you have any special boot drive setup (fusion drive or RAID)?Well there certainly was a lot of information, but the layman solution is there too (even I could understand
). I'm not entirely convinced it's a logic board/chip/motherboard problem though. My conversion to Yosemite was quite recent and up till then the RAM was behaving in Snow Leopard just fine. That's what makes me think it's software related ... but then again not all 2,1 users are complaining about this issue. It's kind of frustrating when the only solution is to 'downgrade' the performance of the machine.Hi all,
I'm new to this forum and to osx as well (I'm from Linux world).
I'm trying to install Yosemite on a friend's Macbook 2.1.
I'm getting same error than Peloche, what can I do to fix it ?
Thanks for your help !
I hope that someone can find a software (or firmware) solution to this problem.
My problems didn't start here until a couple of months after upgrading to Yosemite.
I (sort of) ruled out software as a cause on my machine, when I booted off the original install disk to run Apple Hardware Test and had it spontaneously reboot a couple of times while running AHT.
I'm not sure what version of OS X that AHT is based on (even though it looks like OS 9), but I think my version from the 2006 installer disk must be 10.4 or earlier.
That's not to say that Yosemite doesn't do something to the 2,1 firmware though.
I would love to be wrong, as that would mean not replacing hardware.
Hopefully someone smarter that me can figure this out, I've already wasted a bunch of time on this, and don't have a clue.
- Jay
Oops, I almost forgot to mention what I was going to post in the first place ...
To anyone who had problems with Little Snitch 3.5 on a 1,1 or 2,1 Mac running Yosemite, version 3.5.1 is out.
It seems to fix the problems of messing up the boot cache, and not rebooting after install.
I just updated here with no problems.
http://www.obdev.at/products/littlesnitch/download.html
- Jay
To anyone who had problems with Little Snitch 3.5 on a 1,1 or 2,1 Mac running Yosemite, version 3.5.1 is out.
It seems to fix the problems of messing up the boot cache, and not rebooting after install.
I just updated here with no problems.
http://www.obdev.at/products/littlesnitch/download.html
- Jay
some guy from inmac.org also said that yosemite should be able to install to this machine, even this is efi32bit.
So there is no possible to get newer OSX than 10.6 to this machine?
I cant use any newer apps with this machine...
and I think osx would run better than some linux distro..
There is a big difference between EFI32 and a 32bit processor. These boot.efi mods still require a 64bit processor to run the OS. The MacBook Pro 1,1 is a EFI32 and a 32bit processor. The Mac Pro 1,1 is a EFI32 and a 64bit processor.
Mt. Lion, Mavericks and Yosemite are all 64bit only. You must have a 64bit processor to run them. The EFI32 can be circumvented using the Tiamo/Pike boot.efi or a bootloader but you can't get around not having a 64bit processor. Even if you did magically get it running you wouldn't have graphics support and it would be unusable.
So I've finally had a chance to install Yosemite on my flashed 2,1. I downloaded the pre-patched Piker bootloader and put it on a USB key. Unfortunately, when I select it as my startup disk (I have an nVidia GTX 560 Ti with no boot screens), I get the following error:
"The bless tool was unable to set the current boot disk."
Would I have to put my old 7300 GT card in so I have a boot screen and hold down command-R?
Thanks so much.
"The bless tool was unable to set the current boot disk."
Would I have to put my old 7300 GT card in so I have a boot screen and hold down command-R?
Thanks so much.
Something is not right with the usb boot drive then. I suspect that if you put the 7300gt in to see the boot screen that it will not show up as an option. Have you tried building an installer drive either using the guide or SFOTT?
Trying that out now. Fingers crossed!
*Edit* It worked! I followed the SFOTT video and that did it. Hooray! Now to see if CUDA works in Premiere...
*Edit 2* Got a kernel panic after about an hour or so. I copied it to PasteBin, but I have no idea how to read these things. Any thoughts? http://pastebin.com/BkitviSY
Last edited:
That kernel panic a appears to be graphics related. I wouldn't worry unless it happens continually.
Bug report
the SFOTT boot-loader works great on My Mac Pro 1.1 but the is a few things that have turned into issues not enough to down grade back to 10.9.5 but kind of annoying
>sound for the audio jack is not outputting sound but internal and line-out is working tried different kexts still cat fix issue but i was buying a sound card anyways so not really a big deal
>i have my machine in a SLI config and i have found anytime i have the SLI cable connected the GPU's out put nothing it pretty weird but that could be the web-drivers not sure never did it before
thats the only things I'v found so far but thanks for the boot-loader it works great
the SFOTT boot-loader works great on My Mac Pro 1.1 but the is a few things that have turned into issues not enough to down grade back to 10.9.5 but kind of annoying
>sound for the audio jack is not outputting sound but internal and line-out is working tried different kexts still cat fix issue but i was buying a sound card anyways so not really a big deal
>i have my machine in a SLI config and i have found anytime i have the SLI cable connected the GPU's out put nothing it pretty weird but that could be the web-drivers not sure never did it before
thats the only things I'v found so far but thanks for the boot-loader it works great
Are you saying the optical audio isn't working or the headphone port on the front?
Thanks. So far it hasn't happened again. I also made sure I'm running the latest nVidia drivers. I haven't had any kernel panics again, but I do get messages about graphic issues. Seems to happen while using Premiere CC 2014. I'll post the next one I get.
Are you using the modified plist hack to enable GPU acceleration? Also, Premiere doesn't use CUDA, it uses OpenCL. At least that's true for CS6.
I used the hack to enable it with my GTX 570 that had in my 2006 Mac Pro without issues and now use it in my Hackintosh and a GTX 970.