Dammit, turns out that was NOT the problem. Downloaded it through MEGA and exactly the same result. Well, if no other ideas arise I guess I should be creating my own installer?
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
Dammit, turns out that was NOT the problem. Downloaded it through MEGA and exactly the same result. Well, if no other ideas arise I guess I should be creating my own installer?
I updated my previous post with a link to the prepatched version from another source - can't vouch for this but it looks like several have used it.
Hope it helps.
Good to see you have it up and running. El Capitan next?
Last edited:
Let me enjoy the spoils of victory first... I guess I will do it later but it seems more difficult a process. I'd have to either get more RAM (I run on 10Gb and 2 of them are 512 modules) or run the installation from the laptop. I'll look into it.
Thanks again!
Thanks again!
Oh boy, sorry for being a PITA, but I seem to be in a bit of a problem.... After a successful installation and rebooting twice after installing PikeYoseFix, I went on and enabled TRIM via sudo forcetrim enable in Terminal. Now I have a beautiful black screen to stare at, the computer seems to be stuck in some kind of boot loop, it doesn't matter if I start it holding option because I don't get to the gray boot screen. It does seem to reach some kind of early stage, the scanner boots as it always does, except after a while it boots again and again.
Did it go wrong for me for some reason or did it go wrong for me because I've been an idiot and didn't read properly everything that I needed to read first?
More importantly, can I fix it?
Edit: after a bit of thinking I realised I can unplug the SSD and reboot again, I have Lion installed on another HD, am I correct in assuming that with the SSD out of equation the computer would reboot into Lion just as it used to do? From then on, is there anything I can do to fix the issue beyond formatting again the darned thing and installing Yosemite again?
Did it go wrong for me for some reason or did it go wrong for me because I've been an idiot and didn't read properly everything that I needed to read first?
More importantly, can I fix it?
Edit: after a bit of thinking I realised I can unplug the SSD and reboot again, I have Lion installed on another HD, am I correct in assuming that with the SSD out of equation the computer would reboot into Lion just as it used to do? From then on, is there anything I can do to fix the issue beyond formatting again the darned thing and installing Yosemite again?
Last edited:
Hi, sorry to hear about the problems. I enabled TRIM and it worked OK on a Crucial MX200 SSD - not sure if the type of drive makes a difference. I assume when you say you don't get grey boot screen it is because you have a non-flashed GPU and so cannot select the boot drive. If you have another drive in there with an earlier OS you could power down and pull the SSD and then it may automatically boot from the next drive it can find. Then again, it should do this anyway.
Did you try to update after installing PikeYoseFix? Can you connect to another Mac via Target Disk mode? This may allow you to check the boot.efi files have not been changed back to the Apple versions. I think the Apple versions are larger than the Piked versions - 300kb v 600kb (ish) they are with El Capitan.
Can you boot into recovery? Boot your computer up using Command+R
Did you try to update after installing PikeYoseFix? Can you connect to another Mac via Target Disk mode? This may allow you to check the boot.efi files have not been changed back to the Apple versions. I think the Apple versions are larger than the Piked versions - 300kb v 600kb (ish) they are with El Capitan.
Can you boot into recovery? Boot your computer up using Command+R
Last edited:
Oh man, do I feel embarrased now for wasting your time....
I did unplug the SSD and started the computer. Quute worryingly the exact thing happened, it would boot or so it seemed but no image on screen. The screen, by the way, WAS on, little blue light flashing as it usually does when on but no signal. Tried switching it off and on..... Let there be light, my old Lion desktop in all its glory.
Powered off, plugged the SSD (Samsung Evo 850 in my case), powered on, voilá..... Yosemite boots, image on screen, TRIM support enabled.
Feel mighty embarrassed right now. In any case, again, thanks.....
Talk about arriving late to the party (Mac Pro1,1 party) that is.
Just picked up this machine last week and after upgrading the memory and video card I spent a few days scouring the web and these forums mainly for info and how-to's.
Well here is my pride and joy as it sits today.
Thanks guys 'n' girls for all the helpful information on bringing this wonderful machine forward into this decade.
Runs very fast and silently with dual SSD's in it.
Edit: Yosemite is my operating system of choice, I'm aware that El-Cap will also work.
Just picked up this machine last week and after upgrading the memory and video card I spent a few days scouring the web and these forums mainly for info and how-to's.
Well here is my pride and joy as it sits today.
Thanks guys 'n' girls for all the helpful information on bringing this wonderful machine forward into this decade.
Runs very fast and silently with dual SSD's in it.
Edit: Yosemite is my operating system of choice, I'm aware that El-Cap will also work.
Hi All,
I just finished updating my Mac Pro (2006) 1,1 from Snow Leopard 10.6.8.
The machine is 2 Ghz, 19 GB Ram, 1.25 GB, Radeon 5770 system.
I installed 10.10.1 on it used the Hennessie guide and it works AWESOME! Thank you so much!
Pretty quickly the 10.10.5 update came from the update store. My question is this, will the Hennessie method hold up to updates from the App Store? Or will it screw up my system? I was considering making a partition of hd the patched 10.10.1 system is on and adding it as a backup. Will the update hold up?
I just finished updating my Mac Pro (2006) 1,1 from Snow Leopard 10.6.8.
The machine is 2 Ghz, 19 GB Ram, 1.25 GB, Radeon 5770 system.
I installed 10.10.1 on it used the Hennessie guide and it works AWESOME! Thank you so much!
Pretty quickly the 10.10.5 update came from the update store. My question is this, will the Hennessie method hold up to updates from the App Store? Or will it screw up my system? I was considering making a partition of hd the patched 10.10.1 system is on and adding it as a backup. Will the update hold up?
You need to install the PikeYoseFix script which will make it so you can update. There is a link to it in the first post.
Hi, all. I was wondering if anyone else has had problems in El Capitan with crashes/kernel panics. I've had El Capitan installed with Pikes boot loader for a while now, and it's mostly stable, but from time to time it will crash seemingly randomly.
I think I've sort of narrowed it down to hardware related thing. It does seem to randomly crash at times, but most of the times it crashes it seems to be related to accessing or stopping accessing a device. The first time it crashed was when I tried to make a video call with Skype and it tried to start the webcam. Most recently it crashed when I stopped playback from a USB video capture device.
It doesn't seem to be limited to any one interface either. It's happened with my iSight (firewire) as well as various USB devices. It's crashed a couple of times when unplugging USB devices. And at times, when transferring large quantities of files over the network to my Time Capsule, the network stack seems to occasionally crash. No network things work until I disable the interface and reenable it.
I always check the console after a crash, but nothing seems to be consistent. I think whatever is causing the crashes isn't actually getting logged.
My specs are:
Mac Pro1,1
2 x 2 GHz Dual-Core Intel Xeon
13 GB ram
ATI Radeon HD 5770 1024 MB
PCIe USB 3.0 card
I think I've sort of narrowed it down to hardware related thing. It does seem to randomly crash at times, but most of the times it crashes it seems to be related to accessing or stopping accessing a device. The first time it crashed was when I tried to make a video call with Skype and it tried to start the webcam. Most recently it crashed when I stopped playback from a USB video capture device.
It doesn't seem to be limited to any one interface either. It's happened with my iSight (firewire) as well as various USB devices. It's crashed a couple of times when unplugging USB devices. And at times, when transferring large quantities of files over the network to my Time Capsule, the network stack seems to occasionally crash. No network things work until I disable the interface and reenable it.
I always check the console after a crash, but nothing seems to be consistent. I think whatever is causing the crashes isn't actually getting logged.
My specs are:
Mac Pro1,1
2 x 2 GHz Dual-Core Intel Xeon
13 GB ram
ATI Radeon HD 5770 1024 MB
PCIe USB 3.0 card
I just got done installing the PikeYoseFix script. I rebooted once, logged all the way back in, and then rebooted again (per the instructions). Then upon the 2nd restart the machine got hung up in a boot loop?
That's the best way I can describe it. Before it even gets to the grey apple screen it keeps trying to spin up the SuperDrive repeatedly. Nothing was in the drive when I started... Could it be that the system is searching for my USB bootable that I created? Or is it another issue?
No luck here, its crashed three times in the last two weeks.
Any other suggestions?I guess it could still be RAM related if it happens across different apps and under different circumstances. Have you restarted with the side off - there are LEDs on the riser boards that can indicate bad RAM modules - when I had some dodgy RAM they stayed lit when booted. I didn't leave it long enough to check for crashing though. Does the system profiler report all of you RAM? Do you have a log showing where it crashed - others may be able to interpret this to help pinpoint the issue.No luck here, its crashed three times in the last two weeks.
I did have to replace a few dimms a while back, but as of right now, there's no red lights on the riser boards and it is correctly listing all of the ram. I've never been able to find anything in the logs that's been of any value, but perhaps I'm just not looking for the right thing. I'll be sure to include them next time it crashes.
Is your RAM in the correct position on the riser boards? Over on the El Cap thread, a guy recently had crashes caused by RAM being positioned incorrectly - the side panel has a diagram inside showing the layout for different configurations, as does the Apple website. It seems to be very important.