I have had something like this very sporadically for years (MP1,1/26GB/Radeon4870-512), under tiamo/Mavericks and even before. In my case, the only issue was that nothing was clickable. I could still do everything with the keyboard, such as saving open documents, quitting apps etc. Nevertheless, the only way out was always a hard reset. Never found out the reason. Recently upgraded to pikeralpha/ElCap, problem hasn't occurred so far.
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.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
I have had something like this very sporadically for years (MP1,1/26GB/Radeon4870-512), under tiamo/Mavericks and even before. In my case, the only issue was that nothing was clickable. I could still do everything with the keyboard, such as saving open documents, quitting apps etc. Nevertheless, the only way out was always a hard reset. Never found out the reason. Recently upgraded to pikeralpha/ElCap, problem hasn't occurred so far.
just wanted to add my 2 cents
was able to use target disk mode and a firewire 800 cable to a macbook pro and install that way (and also modify the boot.efi files). booted right up! I did the upgrades on the macbook pro booting my mac pro's HDD before trying to boot the mac pro natively.
was able to use target disk mode and a firewire 800 cable to a macbook pro and install that way (and also modify the boot.efi files). booted right up! I did the upgrades on the macbook pro booting my mac pro's HDD before trying to boot the mac pro natively.
And now .... did you installed the NEW 10.11.1 update ? If the answer is yes ... tell me how please. (I did exactly you did on mac pro 1.1 and EL CAPITAN works perfect) But now I want to do the update. Thank you.
I installed the 10.11.1 update while still in Target Disk Mode to my Mac Pro from my Macbook Pro (while booted to my Mac Pro's drive). you do this via a Firewire cable from your Mac Pro to your Macbook Pro, then reboot your Mac Pro while holding "T" on the keyboard until you see a Firewire logo... the Macbook Pro will now see the Mac Pro's drive(s) as if it is a giant hard drive enclosure, allowing you to install OS X to the drive(s) or boot via the drive(s) without removing them from your Mac Pro... I tried using a USB enclosure, but it kept failing on the first install reboot. Target Disk Mode worked 100% the first try (and Firewire 800 is faster than USB anyway).
I did all of my updates that way immediately after upgrading my Mac Pro's drive to El Cap. Then I just booted the Macbook Pro to its native drive (which is also running El Cap, but not 100% necessary) and did the following while the Mac Pro was still in Target Disk Mode:
first you need to be able to have all files visible on your Macbook Pro. mine already was, but in case you're wondering... in terminal:
defaults write com.apple.Finder AppleShowAllFiles YES
then re-launch Finder (alt+click finder in dock, relaunch)
open finder to the Mac Pro's drive
the first boot.efi is at: /System/Library/CoreServices/boot.efi
run this command to unlock it:
sudo chflags nouchg [drag and drop the boot.efi to terminal to get the exact path]
copy and paste Pike's boot.efi to the CoreServices folder on your Mac Pro drive, then re-lock the file (I've been told this isn't necessary, but whatever) in terminal:
sudo chflags uchg [same path]
next boot.efi is at: /usr/standalone/i386/boot.efi
this one you can just replace (it's already unlocked) -- copy and paste Pike's boot.efi to this folder, replace existing boot.efi
after I did this, I ejected the Mac Pro drive from my Macbook Pro, disconnected the Firewire cable, and rebooted the Mac Pro. it booted right up on first try.
I did all of my updates that way immediately after upgrading my Mac Pro's drive to El Cap. Then I just booted the Macbook Pro to its native drive (which is also running El Cap, but not 100% necessary) and did the following while the Mac Pro was still in Target Disk Mode:
first you need to be able to have all files visible on your Macbook Pro. mine already was, but in case you're wondering... in terminal:
defaults write com.apple.Finder AppleShowAllFiles YES
then re-launch Finder (alt+click finder in dock, relaunch)
open finder to the Mac Pro's drive
the first boot.efi is at: /System/Library/CoreServices/boot.efi
run this command to unlock it:
sudo chflags nouchg [drag and drop the boot.efi to terminal to get the exact path]
copy and paste Pike's boot.efi to the CoreServices folder on your Mac Pro drive, then re-lock the file (I've been told this isn't necessary, but whatever) in terminal:
sudo chflags uchg [same path]
next boot.efi is at: /usr/standalone/i386/boot.efi
this one you can just replace (it's already unlocked) -- copy and paste Pike's boot.efi to this folder, replace existing boot.efi
after I did this, I ejected the Mac Pro drive from my Macbook Pro, disconnected the Firewire cable, and rebooted the Mac Pro. it booted right up on first try.
Download the update from the app store and install it. It will overwrite the boot.efi files in System/Library/CoreServices and /usr/standalone/i386, so you will have to boot your Mac Pro off of a disk (or USB stick) with an earlier version of OS X, or off of the El Capitan recovery partition, and replace the Apple boot.efi files with the Pike versions (just as you did when you were originally installing El Capitan).
I just used this method and it works, thanks andsat!
I connected my Mac Pro cloned system drive in Target disk mode to my Mid 2011 MacBook Air using Thunderbolt-Firewire converter and installed El Cap then after install I changed all the boot.efi files. The only issues I had were on first boot, despite the option key choice, it went back to Yosemite partition but I chose the El Cap as the startup disk in sys prefs and it booted fine next time. Maybe I should have blessed the El Cap partition before restart. The other issue was a few preference panes (iCloud, Users & groups and Internet Accounts) wouldn't open until I ejected all the partitions with other OS versions on them. After that it worked a treat.
Thank to Pike, Tiamo and all the others involved in developing the boot.efi's, amazing work and much appreciated
P.S. FYI my system is a Mac Pro 1,1 flashed to 2,1, GeForce 8800 GT 1024 MB with 32Gb ram (all matched pairs with heatsinks)
Last edited:
Installed onto a MacPro 2.1 in Target Mode. WithPiker-Alpha bootloader.
Then upgraded to OS X 10.11 Server.
The Mac freeze then restart often. It seems It freeze each time it search update onto Internet.
If someone can help
Thanks
Then upgraded to OS X 10.11 Server.
The Mac freeze then restart often. It seems It freeze each time it search update onto Internet.
If someone can help
Thanks
It has ALREADY been said SEVERAL TIMES that SIP makes that IMPOSSIBLE. Pike is working on an alternative solution.
Last edited:
andsat thanks so much !!! of course also to Pike and everyone else too. It was driving me crazy that installation would get to about 75% and then it would quit. Only thing that worked was installing in Target Disk Mode . I removed my 512MB DIMMs, used different types of media, and nothing helped except this. On every other failed installation attempt I kept seeing the failed essentials.pkg error when trying to install from usb. I tried createinstallmedia as well as DiskmakerX to create the installer just incase but this didn't help. I also redownloaded the Capitan installer app from App Store a few times thinking it was corrupted. Until this method nothing worked. I followed andsat' instructions with no issue and like him replaced boot.efi in both locations from my MacBook before booting on my Mac Pro. I used a MacBook Pro running Mavericks for Target Disk Install and FireWire 400 cable to my Mac Pro 1,1. Thanks again guys
Kevin
. I removed my 512MB DIMMs, used different types of media, and nothing helped except this. On every other failed installation attempt I kept seeing the failed essentials.pkg error when trying to install from usb. I tried createinstallmedia as well as DiskmakerX to create the installer just incase but this didn't help. I also redownloaded the Capitan installer app from App Store a few times thinking it was corrupted. Until this method nothing worked. I followed andsat' instructions with no issue and like him replaced boot.efi in both locations from my MacBook before booting on my Mac Pro. I used a MacBook Pro running Mavericks for Target Disk Install and FireWire 400 cable to my Mac Pro 1,1. Thanks again guys Kevin
Hey folks, I'm running 10.11.0 on my MacPro 1.1 atm, thanks to Pike and all those great instructions in this thread.
I originally hooked up the internal drive from my MacPro to my Retina MBP and installed El Cap via USB to this drive.
My MacPro was originally running Yosemite when I got it a few months ago from Ebay, so I was able to boot to Yosemite and switch the required files from there.
Unfortunately, this Yosemite install no longer exists. Which leaves me with the conundrum of not being able to upgrade to 10.11.1, since I have no means to switch out the boot loader afterwards.
My MBP has no firewire ports, so TargetDiskMode is no option. Since I'm running a non-Apple Radeon HD5870 I also can't install Snow Leopard on a spare disk and switch the files out from there...the Snow Leopard install disc boots up, but I don't see anything.
Was thinking about picking up a cheap, working MacBook 1.1 from Ebay. There's a Firewire 400 port on this machine, which should allow me to access the MacPro's internal drive using TargetDiskMode, right?
I originally hooked up the internal drive from my MacPro to my Retina MBP and installed El Cap via USB to this drive.
My MacPro was originally running Yosemite when I got it a few months ago from Ebay, so I was able to boot to Yosemite and switch the required files from there.
Unfortunately, this Yosemite install no longer exists. Which leaves me with the conundrum of not being able to upgrade to 10.11.1, since I have no means to switch out the boot loader afterwards.
My MBP has no firewire ports, so TargetDiskMode is no option. Since I'm running a non-Apple Radeon HD5870 I also can't install Snow Leopard on a spare disk and switch the files out from there...the Snow Leopard install disc boots up, but I don't see anything.
Was thinking about picking up a cheap, working MacBook 1.1 from Ebay. There's a Firewire 400 port on this machine, which should allow me to access the MacPro's internal drive using TargetDiskMode, right?
You could use the pre-patched Piker-Alpha's bootable Yosemite installer, that can be restored to a USB flash drive using Disk Utility:
pre-patched Piker-Alpha bootable Yosemite installer
see:
https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-yosemite.1740775/
pre-patched Piker-Alpha bootable Yosemite installer
see:
https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-yosemite.1740775/
Thanks for the response Peter. I did as you said but no luck. It is working between my iPhone and iPad, but not with my MacPro. I've logged out of iCloud now numerous times on all devices. I can't get iMessage Text Message Forwarding to work either. The MacPro shows up on the phone but if you try to turn TMF on it starts Messages on the MacPro, but never gives you the code to enter into the phone. I've been talking with Apple Tech Support and they are supposed to give me another call back on Thursday.
I have the Wifi AC and Bluetooth Airport Card from MacVidCards which was working fine under Yosemite. It is clearly making some sort of connection as it will launch Messages on the MacPro when I try to turn on TMF from the phone. Also, Airdrop within finder shows both my iPhone and iPad and I can send a file either direction.
Any other suggestions would be appreciated.
If I were you, I'd get a blank HDD or SSD and install El Capitan from scratch, enter the relevant iCloud information and see it that solved your handoff issues. It should. Then, if that's settled, I'd move all my data and applications to the new disk. In any case, your problem isn't related to boot.efi as such.
Last edited:
You just need a thunderbolt to firewire adaptor from Apple, $25 or something !
My MacPro 1.1 that I was ready to replace a year ago has a second life with Yosemite and now El Cap. Thanks Pike and all the others for their work to make this possible. I have contributed to the link on this site:https: //github.com/Piker-Alpha/macosxbootloader
The El Cap method is not as slick as the Yosemite but every bit as effective. I followed the directions exactly and have had no problems. I used a MacBook Air 3.1 and an external HHD/SSD enclosure via USB and it was a breeze. Thanks again.
The El Cap method is not as slick as the Yosemite but every bit as effective. I followed the directions exactly and have had no problems. I used a MacBook Air 3.1 and an external HHD/SSD enclosure via USB and it was a breeze. Thanks again.
Attachments
Thank you.
It would be helpful if this information is posted in the first post of this thread. In that way, members won't ask the same questions again and again, nor will those who know be forced to yell.
Jesus, why didn't I think of that??? Sometimes the solution is right in front of your nose, just ordered the adapter and a FW800 cable, thank you!
Still I'm wondering...If I use this adapter to access the disk of my MacPro using TargetDiskMode from my MacBookPro running El Cap...won't Sytem Integrity Protection precent me from renaming the files?
I once tried disabling SIP on my MBP, had to turn it back on again because I couldn't boot El Capitan anymore afterwards.
Pike sorry about that, yours efi for Yosemite works fine. My problem is the new one. The latest one also 3.1 has the same behavior with my machine. What I discover today is that your old efi for Yosemite works fine with El Capitan. I am using it for 1 hour without crash and I am curious to tell me if there is a big change with your last version (3.1).
Thank you in advance and also for your work.
Nicholas
My Question is simple,
Is it right to use the old boot.efi for Yosemite instead of the new one?
And what is the difference?
And finally why doesn't work with my machine (the new one boot.efi 3.1) even in 10.10.5?
I think that you have to consider that as a specific bug in the new file. I believe that is helpful for the final release of the El Capitan boot.efi file.
Thank you in advance,
Nicholas
Last edited:
Nobody yelled at you. I simply pointed out the very unwelcome nature of your request. You really should know better. It so happens that, more likely than not, serious health problems of the main developer of this wonderful bootloader will keep him from giving the final touch to boot.efi. It is obvious SIP will keep a launch daemon from working.
SIP is not a problem, I installed El Cap and changed the boot.efi files using terminal from a MacBookAir running El Cap too! I think it only stops you from changing files on the active system you are booted from! The only issue I had was when I restarted the Mac Pro and used the option key to choose my El Cap boot disk it ignored me and went to my Yosemite partition. Once booted into Yosemite I chose the El Cap disk in Sys Preferences startup disk pane and restarted and all was well.
I have now cloned my El Cap test partition back onto my SSD and everything is awesome, good luck
Pike's busy, right now.
The new 'boot.efi' has changed, considerably, since the one for Yosemite was finalised (too many changes to tell, in a sentence).
You can use the older or newer boot.efi for Yosemite; no difference should be noticed . . . if you do, list them, please
I have v.3.1 booting into Mavericks 10.9.5, Yosemite 10.10.5 and El Capitan 10.11.1 . . . I even used the v.3.1 to run the Mountain Lion installer last night, and it ran just fine (in the installer)....
What does "doesn't work with my machine" mean? Would you provide more details?
Probably still many bugs to squash, but we can only provide help when specific and detailed questions are asked....
Regards, splifingate
Hello and thanks for your reply,Pike's busy, right now.
The new 'boot.efi' has changed, considerably, since the one for Yosemite was finalised (too many changes to tell, in a sentence).
You can use the older or newer boot.efi for Yosemite; no difference should be noticed . . . if you do, list them, please
I have v.3.1 booting into Mavericks 10.9.5, Yosemite 10.10.5 and El Capitan 10.11.1 . . . I even used the v.3.1 to run the Mountain Lion installer last night, and it ran just fine (in the installer)....
What does "doesn't work with my machine" mean? Would you provide more details?
Probably still many bugs to squash, but we can only provide help when specific and detailed questions are asked....
Regards, splifingate
As I wrote before, the new boot.efi 3.1 or 3.0 when I decided to upgrade from 10.10 I faced multiple system crash panics after 1 or two minutes on boot without any reason. My Mac Pro 1.1 is the same as others and I tried to have a clean install always. I recently discover that I can use the old one Pikes boot.efi the one for Yosemite and it woks just fine.
Please if it is possible to help, tell me what to check.
Thanks
Nicholas