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
That is one very large security update...
one other item I noticed, (colorsync) display calibrator does not appear to work with capitan, so calibrating the monitor is not possible as previously under 10.10.5 and earlier.
Last edited:
hello the image for capitan is here:
you need to go to page 56 of this forum for other installation instructions.
boot64 and other files are there
or install yosemite which is easier and just as good:
http://www.lincade.org/yosemite-and-the-macpro-1-1-2-1/
Last edited:
Hello Don,
I went through the whole process (I'm composing a new video tutorial for V14
Here's what I did:
So I think you must have messed up the Boot64 install (as you surmised).
- partitioned a drive into two equal volumes
- installed Lion on the second half volume, leaving the first half volume as my target for pikify
- Once El Capitan is installed I can destroy the second half partition and recover the space
- booted into Lion
- downloaded pikify V14
- ran pikify giving it my first Volume as the target
- it installed perfectly
- booted into El Capitan
- downloaded Boot64
- installed it (it should ask for your password, mine did)
- checked it was working (sudo /Library/Application\ Support/Boot64/ensureBoot.sh -g)
- open the Console
- select the system.log
- from a terminal: sudo touch /System/Library/CoreServices/boot.efi
- after a couple of seconds you should see a log entry in the Console from ensureBoot
- opened the App Store
- Checked for updates
- Installed the updates
- reboot
- all works okay
Hi rthpjm,
It worked! I did exactly the procedure you wrote in your previous post.
Yes, the Boot64 was messed up and a red light on one of the memory boards was lit. I turned the computer off and removed the memory board, re-seated the memory and plugged it back in.
I was trying to install 10.11.6 without being online and registering with Apple. As soon as I got online and registered, the update worked perfectly.
Thank you a bunch for your help.
Regards,
Don James
Henderson, Texas USA
Hello Don,
I went through the whole process (I'm composing a new video tutorial for V14
Here's what I did:
So I think you must have messed up the Boot64 install (as you surmised).
- partitioned a drive into two equal volumes
- installed Lion on the second half volume, leaving the first half volume as my target for pikify
- Once El Capitan is installed I can destroy the second half partition and recover the space
- booted into Lion
- downloaded pikify V14
- ran pikify giving it my first Volume as the target
- it installed perfectly
- booted into El Capitan
- downloaded Boot64
- installed it (it should ask for your password, mine did)
- checked it was working (sudo /Library/Application\ Support/Boot64/ensureBoot.sh -g)
- open the Console
- select the system.log
- from a terminal: sudo touch /System/Library/CoreServices/boot.efi
- after a couple of seconds you should see a log entry in the Console from ensureBoot
- opened the App Store
- Checked for updates
- Installed the updates
- reboot
- all works okay
Hi rthpjm,
It worked!
Yes, the Boot64 was messed up and a red light on one of the memory boards was lit. I turned the computer off and removed the memory board, re-seated the memory and plugged it back in.
I was trying to install 10.11.6 without being online and registering with Apple. As soon as I got online and registered, the update worked perfectly.
Thank you a bunch for your help.
Regards,
Don James
Henderson, Texas USA
on a slightly different theme.
I intend to upgrade ram with x2 8G or x4 8G DIMM's..
how would I install another x2 8G if my current configuration is the following in the attached pic?
I intend to upgrade ram with x2 8G or x4 8G DIMM's..
how would I install another x2 8G if my current configuration is the following in the attached pic?
On the inside of the side panel, there's a graphic and advised order. Or use Apple's support site, there's a document there.
Guys, I have a problem with running the Apple Hardware Test.
I am currently running a Mac Pro 2,1 (upgraded firmware) with a passive-cooled ATI Radeon 5750 that was ROM-tweaked to appear as a 5770. Bootscreen is available. The machine is sweet.
Unfortunately, I started experiencing some problems with the computer's inability to RESTART. It sleeps fine, starts up and shuts down just fine too. When I tell it to "restart" all I get is a black screen and the PSU won't switch-off. Looks like it cannot complete the command. I looked inside the case and always when that happens I get two diagnostic LEDs flashing: the CPU-A and CPU-B. Rare flashes. Computer unresponsive. Then I just kill it by holding the on/off switch until the shutdown. These LEDs never go on when the computer is being used. Just at an attempt to restart.
I know that there may probably be maaaany problems causing this situation. So I thought that the right way to start looking for the problem was to run the Apple Hardware Test. And this is were my actual problem starts: no matter what I do I cannot get the Mac Pro to boot off the Apple Hardware Test drive (be it a USB stick or even an internal SATA drive). I also have a MacBook Pro 5,2 (A1297 2,66 GHz 17”) that I managed to boot using a USB flash drive with a corresponding Apple Hardware Test on it with no problems! I tried my luck with it just to make sure that I am not making a mistake in the procedure of preparing the AHT bootable volume.
When I have my internal drive or USB stick containing a bootable volume of an AHT connected to the Mac Pro and switch it on (as I cannot RESTART) with the “D” button pressed, I only get an icon of a folder with a question mark and after a second the computer boots into El Capitan. Do you have an idea why I cannot get it to boot into the Apple Hardware Test? Is there some problem resulting from the "non-standard" configuration of this Mac Pro?
NOTE:
While choosing the correct version of AHT for my machine (using this guide: https://github.com/upekkha/AppleHardwareTest) I also discovered that my Terminal read-outs for the “model” and “board-id” are not matching, as they are respectively: “MacPro2,1” (as expected) and “Mac-F42C88C8” (witch matches Mac Pro 3,1). Being unsure which Apple Hardware Test disk image to use because of this ambiguity, I’ve tried 3 different ones (018-2769-A.dmg for 1,1; 018-2667-A.dmg for 2,1 and 018-3273-A.dmg for 3,1). All to no avail.
Please help!
I am currently running a Mac Pro 2,1 (upgraded firmware) with a passive-cooled ATI Radeon 5750 that was ROM-tweaked to appear as a 5770. Bootscreen is available. The machine is sweet.
Unfortunately, I started experiencing some problems with the computer's inability to RESTART. It sleeps fine, starts up and shuts down just fine too. When I tell it to "restart" all I get is a black screen and the PSU won't switch-off. Looks like it cannot complete the command. I looked inside the case and always when that happens I get two diagnostic LEDs flashing: the CPU-A and CPU-B. Rare flashes. Computer unresponsive. Then I just kill it by holding the on/off switch until the shutdown. These LEDs never go on when the computer is being used. Just at an attempt to restart.
I know that there may probably be maaaany problems causing this situation. So I thought that the right way to start looking for the problem was to run the Apple Hardware Test. And this is were my actual problem starts: no matter what I do I cannot get the Mac Pro to boot off the Apple Hardware Test drive (be it a USB stick or even an internal SATA drive). I also have a MacBook Pro 5,2 (A1297 2,66 GHz 17”) that I managed to boot using a USB flash drive with a corresponding Apple Hardware Test on it with no problems! I tried my luck with it just to make sure that I am not making a mistake in the procedure of preparing the AHT bootable volume.
When I have my internal drive or USB stick containing a bootable volume of an AHT connected to the Mac Pro and switch it on (as I cannot RESTART) with the “D” button pressed, I only get an icon of a folder with a question mark and after a second the computer boots into El Capitan. Do you have an idea why I cannot get it to boot into the Apple Hardware Test? Is there some problem resulting from the "non-standard" configuration of this Mac Pro?
NOTE:
While choosing the correct version of AHT for my machine (using this guide: https://github.com/upekkha/AppleHardwareTest) I also discovered that my Terminal read-outs for the “model” and “board-id” are not matching, as they are respectively: “MacPro2,1” (as expected) and “Mac-F42C88C8” (witch matches Mac Pro 3,1). Being unsure which Apple Hardware Test disk image to use because of this ambiguity, I’ve tried 3 different ones (018-2769-A.dmg for 1,1; 018-2667-A.dmg for 2,1 and 018-3273-A.dmg for 3,1). All to no avail.
Please help!
I don't know much about the AHT, but I can tell you why the terminal reports the board-ID as it does. The board-ID is a function call that passes through the modified boot.efi file. Pike has fixed the board-id to report the ID of a 3,1 (actually I thought he had added code to detect if the installer was running and only then report the board ID of the 3,1. But maybe it is hard coded now). It was one of the additions that Pike made to assist with installing Yosemite/El Capitan.
I would assume that the AHT for the 1,1 "should" be the correct image to use. It "should" simply boot up, I'm assuming it's a self contained image. If that's the case, you would not need to worry about the board-id, because the AHT is loaded, not the El Capitan installation with the modified boot.efi file.
So your issue may be that you cannot boot from the AHT. You mentioned a folder with a question mark. This is the symbol that the EFI firmware presents if it attempts to load an operating system from a disk (the AHT USB), but it can't figure out where the OS is located. This usually happens if the disk/volume is not "blessed". Blessing a disk/volume effectively stores a pointer to where to load the booter (boot.efi or in the case of the AHT it seems to be diags.efi) file.
Try plugging in your AHT USB stick in whilst booted into El Capitan, then query the blessed status. Let's assume your USB stick mounts as /Volumes/AHT (adjust to match what your USB is called)
From a Terminal, type
Code:
bless --info /Volumes/AHTIt should return some blessed folder, blessed file locations. If not, you need to try and bless the USB.
Try using the System Preferences > Startup Disk panel, you may be able to choose the AHT to boot.
If not it will need to be blessed from the terminal.
On the AHT, there will be a folder with a diags.efi file somewhere. Typically it's /Volumes/AHT/System/Library/CoreServices/.diagnostics/diags.efi
If you can find it, use the terminal again
Code:
bless --folder /Volumes/AHT/System/Library/CoreServices/.diagnostics --file /Volumes/AHT/System/Library/CoreServices/.diagnostics/diags.efiNow try your reboot into the AHT. Do NOT hold down the D key, immediately after the start chime, hold the ALT key.
You will enter the boot selector screen, select your USB device.
Last edited:
It happens to me from time to time (one in maybe 15-20 restarts?). Since the OS shuts down properly and it's only the computer that somehow can not power-cycle, I can't be really bothered.
Thank you so much! It worked!!!
Not sure what exactly did the trick though... I was sure that I was blessing the files and folders just correct before (not to say that the other computer booted from its AHT volume instantly) but it turns out that I must have been doing something wrong. Also, this time I tried the AHT for Mac Pro 1,1 exclusively. The computer booted from it, I run the test (no errors reported) - so it also tells all the other guys with similar setups: use the Apple Hardware for Mac Pro 1,1, even if you've flashed the computer with 2,1 firmware.
Now I am just left with inability to restart
But I will start a separate thread for that.@hwojtek - the LEDs flashing and no restart happens to me with a 100% probability - always.
@rthpjm - thanks a million!
Try these two things first:Thank you so much! It worked!!!
Not sure what exactly did the trick though... I was sure that I was blessing the files and folders just correct before (not to say that the other computer booted from its AHT volume instantly) but it turns out that I must have been doing something wrong. Also, this time I tried the AHT for Mac Pro 1,1 exclusively. The computer booted from it, I run the test (no errors reported) - so it also tells all the other guys with similar setups: use the Apple Hardware for Mac Pro 1,1, even if you've flashed the computer with 2,1 firmware.
Now I am just left with inability to restart
@hwojtek - the LEDs flashing and no restart happens to me with a 100% probability - always.
@rthpjm - thanks a million!
Reboot, at the chime hold down 4 keys:
Apple Alt P R
Wait for the next chime then release the keys
This is a parameter RAM (PRAM) reset. It should boot into El Capitan after the second chime. (Note, on my system I loose the boot screen during this process, but after a successful boot, the boot screens return subsequently. The PRAM seems to store the hardware path to the video card, which gets cleared with the reset, but is put back on boot).
If that doesn't help, try an SMC reset. Turn the machine off
Remove the power lead (absolutely no power)
Open the side panel
Look below disk bay 4 near the rear of the logic board (between the disk bay and the top of the memory cage), there's a small push switch (@jbarley posted a picture a few posts further on)
Hold the push switch in
Count slowly to 10
Release
Reassemble
Boot
You say it happens every time?
Try a verbose boot
Reboot, hold Apple V when you hear the chime. You will see the console output that's usually hidden during boot
Do some things on your Mac, then try the restart
You will probably see some shutdown console output as the machine starts to shutdown, see if that gives you any clue about where it is getting "stuck"
You might have a background process running that will not quit...,
Last edited:
No problem. I've been living with, working with, playing with, and fixing Macs for a very long timerthpjm, you're the man - the hardware button solved my no-restart situation.
So good there are guys like you among us
hello all. can you please upload a pic of this location. I cannot see such a thing on my 1.1.
i have tried the sms reset without the push button and do not know if it has worked.
i have weird fan behaviour in 10.10.5 and that might fix it. It seems less evident in capitan because i have not installed macs fan control on it.
I use mac fans control to monitor temps and set fans if required usually in the summer, accelerated fan speed is more noticeable because obviously higher ambient temperature and the internal temps of the mac rise as well.
I have a boot ssd and installed pc 5770. As well slots riser A, 1 and 2 and samsung 8G DIMMS correct spec RAM which runs hotter than other installed RAM.
i also use a widget istat pro last version is 4.9.2.
It shows cpu a and cpu b to be both usually in mid 20's degrees C.
in mac fan control the temps it reports for CORE cpu a and cpu b are in the 40-50 range, which seems excessive and may be responsible for the weird very sensitive fan behaviour.
Are they measuring the same thing: CORE and/or CPU A/B?
Or macs fan control installs something somewhere which oversensitises the behaviour.
ideas?
andrew
Sorry for the poor quality photo, but this is the button location as found in my MP1,1.
There appears to be a plastic shroud under the button.
is it quite delicate or
would you apply pressure to that with a pencil or finger?
Hello guys. I'm have a Mac Pro 1,1 which edited as 2,1 and running osx 10.10.5 without any problem. I installed it with Sfott pikes boot fix. Cpu is 2x4 cores of 2,66 intel xeon, 8gb ram & nvidia gtx 660(no boot screen. But still holding gt 7300 for new installs). Also got macbook 6,1 white(no firewire), running yosemite as well. I want to upgrade my mac pro to 10.11.6 from 10.10.5. Is it possible to safe upgrade? I dont want to reinstall all of my software(especially logic pro x). My osx harddrive is ssd so i can put it to my macbook(which i never tried). Any suggestion would be great. Thanks.
The easiest way, and the one I've tried many times - buy USB to SATA adapter for a few bucks and connect SSD to MacBook. Install ElCapitan from MacBook onto SSD (you must boot from MacBook's drive because of modded boot.efi files) and don't touch Disk Utility if you want your old files to stay in place.
After install, replace 3 boot.efi files (/usr/standalone/i386, /System/Library/CoreServices/ and /com.apple.recovery.boot/ after mounting Recovery partition) and put your SSD back into Mac Pro.
All done
After install, replace 3 boot.efi files (/usr/standalone/i386, /System/Library/CoreServices/ and /com.apple.recovery.boot/ after mounting Recovery partition) and put your SSD back into Mac Pro.
All done
or install another drive in the macpro, you have 4 slots remember... and install 10.11.x which i did. Read previous recent posts. I provided links and there is enough info to get the 10.11 image file and go from there.
when you boot into capitan, you can run the programmes you want even if they are on the yosemite drive.
@andew nz
Ty but I don't want to spend 1 more bay cause I already use all of them.
I already have a USB to Sata mounter. I don't even know how to install OsX to a usb ported HDD but I can try or do something like that. I hope it works. Thanks.
Ty but I don't want to spend 1 more bay cause I already use all of them.
The easiest way, and the one I've tried many times - buy USB to SATA adapter for a few bucks and connect SSD to MacBook. Install ElCapitan from MacBook onto SSD (you must boot from MacBook's drive because of modded boot.efi files) and don't touch Disk Utility if you want your old files to stay in place.
After install, replace 3 boot.efi files (/usr/standalone/i386, /System/Library/CoreServices/ and /com.apple.recovery.boot/ after mounting Recovery partition) and put your SSD back into Mac Pro.
All done
I already have a USB to Sata mounter. I don't even know how to install OsX to a usb ported HDD but I can try or do something like that. I hope it works. Thanks.