Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
I Think it should be the RAM which is under 12GB so i think i need the old boot.efi. (But can't find them anywhere, or don't know which one i should use for a Mac Pro 1,1 under 12GB of Ram)

I will start the Mac this afternoon in verbose mode an will see where it stops.

The RAM requirement only applies to the installation procedure. Once you complete the installation the OS can happily run with less RAM.
 

andijegg

macrumors newbie
Feb 28, 2016
11
0
The RAM requirement only applies to the installation procedure. Once you complete the installation the OS can happily run with less RAM.
This means, i can rund the Installation on my rMBP on a extern HD and can switch this HD after the installation into the Mac Pro 1,1.

This is exactly what i try over days. I give it another try this evening...
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
This means, i can rund the Installation on my rMBP on a extern HD and can switch this HD after the installation into the Mac Pro 1,1.

This is exactly what i try over days. I give it another try this evening...

Just a thought, but I would reset the PRAM and SMC just for the sake of doing it. I first
loaded 10.11(1-3) on an old drive to do the testing and by the time I did the final install
I had found that doing the PRAM reset did a lot for a smooth install. You might have to doo an OPtion boot to select the correct boot drive, but that is a lot easier than banging my head against the wall.
 

LordSpunky

macrumors newbie
Feb 22, 2016
8
0
I've just completed this. Fresh download of El Capitan from Mac Store, ran the v8 boot loader and installed directly on my Mac Pro. All done! However, I see what you mean about the old graphic card support. I knew I needed a new card but waiting for pay day.
 

macprobuffalo

macrumors member
Feb 27, 2015
52
9
Anyone else having issues with their optical drive?

When I insert a disc it doesn't show up in the finder. I have had this problem since I first went from Lion to Yosemite. Figured it just came with running an unsupported OS, wondering if that is actually true
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Anyone else having issues with their optical drive?

When I insert a disc it doesn't show up in the finder. I have had this problem since I first went from Lion to Yosemite. Figured it just came with running an unsupported OS, wondering if that is actually true

No, not for me. I still have the original Sony/Apple DVD/CD rewriter (A.K.A. SuperDrive) in bay 1 and a TSSTcorp Bluray drive in bay 2. Both work fine. The original DVD drive is still connected on the parallel ATA bus, whilst the Bluray drive is connected to one of the motherboard SATA interfaces.

It's more likely to be either bad media, or that your drive is perhaps reaching the end of its life. Reliability has improved with each generation, but these things are still susceptible to failure. The laser diodes in particular are known to deteriorate over a long period of usage.

If you have a compressed air canister, it might be worth attempting a clean before deciding to buy a replacement.

Also check the system.log file (using the Console app). Insert a problematic disk and see if you get any disk related log messages...

A final thought occurred to me... You say that you have been upgrading, so you may have some old extensions that might be interfering (it all depends on how you did your upgrades). Have you tried a reboot into safe mode? (Safe mode only loads Apple-supplied extensions I believe). Also, if you try a safe mode boot, be patient because I also think it triggers an disk check (fsck) which will take some time to complete depending on the size(s) of your disk(s).... I think you can still get to safe mode by holding down the shift key immediately after the startup chime....

See this Apple KB article
 
Last edited:

andijegg

macrumors newbie
Feb 28, 2016
11
0
Just a thought, but I would reset the PRAM and SMC just for the sake of doing it. I first
loaded 10.11(1-3) on an old drive to do the testing and by the time I did the final install
I had found that doing the PRAM reset did a lot for a smooth install. You might have to doo an OPtion boot to select the correct boot drive, but that is a lot easier than banging my head against the wall.
PRAM and SMC reset I've already done. But I give it a try again this evening. Yesterday I have not enough time for testing and installing.
 

cdmawolf

macrumors member
Feb 26, 2016
63
10
PRAM and SMC reset I've already done. But I give it a try again this evening. Yesterday I have not enough time for testing and installing.

Remember, we are forcing hardware/software/firmware to do things that they were never meant to do.
 

andijegg

macrumors newbie
Feb 28, 2016
11
0
Remember, we are forcing hardware/software/firmware to do things that they were never meant to do.
I know. But i had already a running El Capitan System on this Mac Pro, which I had constantly updated from Mavericks over Yosemite up to El Capitan with only chanting the boot.efi on a compatible System.
But I need the HD's for my new NAS and I thought, that I wouldn't be such a great thing to make a new clean working El Capitan drive for my mac pro again. So I'am a bit confused about the Problems which I have now setting up the System again.
 

JazzerAlto

macrumors newbie
Apr 8, 2015
12
2
I created the install media with the latest Pikefy and when I start booting the install disk, I get a kernel panic. Screen shot attached. Any suggestions?

Thanks
 

Attachments

  • IMG_1655.jpg
    IMG_1655.jpg
    331.4 KB · Views: 232

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
16GB, all 2GB DIMMS

The text in your screenshot seems to point towards a problem with a firewire device. Disconnect all your peripherals except mouse, kb, monitor. Especially disconnect the firewire devices....

If you built the installer on an external firewire disk. Use Disk Utility and run first aid on the whole disk as well as any and all partitions. Consider a complete reformat of the firewire disk (that you put the installer on)...
 

JazzerAlto

macrumors newbie
Apr 8, 2015
12
2
The text in your screenshot seems to point towards a problem with a firewire device. Disconnect all your peripherals except mouse, kb, monitor. Especially disconnect the firewire devices....

If you built the installer on an external firewire disk. Use Disk Utility and run first aid on the whole disk as well as any and all partitions. Consider a complete reformat of the firewire disk (that you put the installer on)...

Thanks for the suggestions, I will disconnect the firewire device (it's an audio device). I put the installer on a USB drive but looks like I need to rebuild it anyway with a newer version of the installer.
 

dme881

macrumors newbie
Mar 6, 2016
13
1
I installed via a Macbook Pro that supports El Craptain by default. Random kernel panic, RAM CRASHES EVERY 30min. 6GB of ram, Curcial and Hynix.

If I was at work all the time I spent tinkering with my old Mac Pro 1,1 - I could have bought a brand new Mac Pro! :) Just a heads up!
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
I installed via a Macbook Pro that supports El Craptain by default. Random kernel panic, RAM CRASHES EVERY 30min. 6GB of ram, Curcial and Hynix.

If I was at work all the time I spent tinkering with my old Mac Pro 1,1 - I could have bought a brand new Mac Pro! :) Just a heads up!

Do you have any 512MB DIMMS in your setup?

A number of users have reported numerous crashes and difficulties. Empirically it has been discovered that the combination of El Capitan, 32-bit-efi machines, and 512MB original DIMMs seems to be the common factor. Every user who has reported kernel panics has been advised to buy new larger capacity RAM DIMMs, and has subsequently reported back that their system has stabilised. The recommendation is to purchase 2GB or 4GB DIMMs in pairs, as many as you can afford. (Remove the 512MB DIMMS entirely).

Personally, I have 8 x 4GB DIMMs, some of which have Apple-style heat sinks, and some of which have the more typical flat heat spreaders. My MacPro 2,1(1,1) was rock solid at Yosemite, and has been rock solid under El Capitan.
 

kuglepen

macrumors newbie
Aug 11, 2012
27
0

I just installed El Cap following your recipe, and I did manage to install El Cap, but the automatic ‘Boot 64’ was not installed as described.

Further, the script commands after ### DONE PIKIFYING ### failed.
[doublepost=1457366497][/doublepost]Since I installed El Capitan I’ve run into the issue that if I put my Mac Pro to sleep at night, then it will wake up during the night and ramp up the fans to maximum.

I’ve have reset the SMC and PRAM successfully, but to no avail.
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
I just installed El Cap following your recipe, and I did manage to install El Cap, but the automatic ‘Boot 64’ was not installed as described.

Further, the script commands after ### DONE PIKIFYING ### failed.
[doublepost=1457366497][/doublepost]Since I installed El Capitan I’ve run into the issue that if I put my Mac Pro to sleep at night, then it will wake up during the night and ramp up the fans to maximum.

I’ve have reset the SMC and PRAM successfully, but to no avail.

One other user told me the commands after "Done Pikifying" have caused problems.

Don't worry about them, I added them to try and detect if the Mac is a 1,1 or a 1,2 MacPro AND has the suggested 12GB or more of RAM. If the RAM is low it just prints a warning. There's no other impact. If it is throwing any errors or warnings they can be safely ignored.

If you saved the error messages, or can remember them, please post them. I'll see if I can figure out what is causing the issues.

It obviously works okay on my MacPro 1,1 (2,1) without issue. There must be some differences between your machine(s) and mine. What version of Mac OS X were you using when you built the installer? It is most probably a version issue....

The fans do that some times. It's Mac OS X, but remember (before asking Apple about it) we are running a version of Mac OS X on unexpected hardware from Apple's perspective.... Take a look at your System Preferences > Energy settings, and maybe your sharing settings. MacOSX will periodically wake just long enough to announce its presence to the network, then go back to sleep. I can't remember which settings affect the behaviour, there are probably a few....
 

Djwayne190485

Suspended
Mar 7, 2016
8
0
The race is on.

Who's the first to get OS X version 10.11 El Capitan booting perfectly on a 2006/2007 Mac Pro (1,1/2,1)?

UPDATE: Only one day later, 666sheep did it first!

This first post has now been updated with recent summarized information.


Simply looking to download the Piker-Alpha macosxbootloader for El Capitan? Links:
________________________________________________________________

If you have OS X El Capitan up and running on your 2006/2007 Mac Pro with Pike's boot loader, you should consider disabling "Install OS X updates" and "Install system data files and security updates" in System Preferences > App Store so that OS X doesn't automatically install any future updates that may overwrite Pike's boot.efi.
________________________________________________________________

If you find Pike's boot loader valuable in keeping your 2006/2007 Mac up-to-date, please consider simply thanking him via a comment on his blog, as he's done a lot of work without asking for anything in return or benefiting from this project. Thanks Pike!


How can these Macs run El Capitan?

Apple does not support OS X El Capitan on the original 2006/2007 Mac Pro and 2006 Xserve. These 64-bit Mac Pros and Xserves have EFI32 firmware and can't natively boot OS X El Capitan "out-of-the-box", but are easily capable of running it with a different boot loader. Once a new boot loader is used to launch the native 64-bit El Capitan kernel, OS X 10.11 boots and works normally exactly as it does on a 2008 Mac Pro or newer with EFI64 firmware.


Background:

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.

The last version of OS X officially supported by Apple on the original 2006 Mac Pro MA356LL/A (MacPro1,1), 2007 Mac Pro (8-core) MA1186/A (MacPro2,1) and Xserve (Late 2006) MA409LL/A (Xserve1,1) models was OS X 10.7 Lion, and then only when booted with a 32-bit kernel due to their EFI32 firmware. However, these Macs were the most powerful and upgradable EFI32 models and have a 64-bit architecture, so the user community has been keeping them running with 64-bit kernels and newer OS X releases using a variety of methods.


The Piker-Alpha bootloader can be used to boot OS X 10.11 El Capitan on unsupported Mac Pro models:

This approach, using a fork of boot.efi boot loader that thunks EFI64 calls from the 64-bit OS X kernel to the EFI32 firmware.

Additional information about Pike's boot.efi is available at Pike's blog, Universum. There are two variations available, one with a legacy light grey background/dark grey Apple logo boot screen boot.efi that blends with the native EFI32 pre-boot screen (2008-2012 Mac Pro-style), and a new black background/white Apple logo boot screen boot.efi (2013 Mac Pro-style).

The simplest method to boot El Capitan on these Macs is the "pikify" createpikeinstallmedia script to create a pre-patched El Capitan installer with the El Capitan branch of the Piker-Alpha bootloader. This directly allows an El Capitan installer to run to be run to completion on a 2006/2007 Mac Pro.

Another alternative install on a 2006/2007 Mac Pro is to use a second El Capitan-supported Mac and install El Capitan to the 2006/2007 Mac Pro's drive. This may be done either by attaching the 2006/2007 Mac Pro's drive as an external drive by placing the 2006/2007 Mac Pro in target disk mode or otherwise mounting the 2006/2007 Mac Pro's drive to an El Capitan-supported Mac.

This alternative approach still requires installation of the Piker-Alpha bootloader before it can be successfully booted on a 2006/2007 Mac Pro. After installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi. That drive should now be bootable on a 2006/2007 Mac Pro, although sometimes it still may need to be blessed in the 2006/2007 Mac Pro.

Disabling System Integrity Protection (SIP) may be required to replace the boot.efi in-place.

Alternatively, there's also an approach in the boot.efi development thread to exclude these files from SIP, but it has shown mixed results.

While this method is preferred because it's a native EFI boot, there is real risk that installing future El Capitan updates could overwrite Pike's EFI32 boot.efi if Apple were to update the stock EFI64 boot.efi. This has already happened in the few previous OS X El Capitan updates. When this happens, the system would no longer be natively bootable on a 2006/2007 Mac Pro until it had Apple's stock boot.efi re-replaced with Pike's boot.efi again. A simple approach to help protect against this is CaptainPikeFix, a launch daemon that re-copies the EFI32 boot.efi to proper locations at shutdown, but this approach requires disabling SIP.


Support for Handoff in El Capitan to allow AirDrop, Continuity and Instant Hotspot with iOS devices:

The original Airport Extreme (802.11a/b/g/draft-n Wi-Fi) and Bluetooth 2.0+EDR options from Apple don't support Handoff. Several vendors, including MacVidCards, sell new add-on hardware kits to retrofit older Mac Pros with 802.11ac Wi-Fi and Bluetooth 4.0 LE that work in 2006/2007 Mac Pros to allow Handoff. There have been reports of needing to sign out of iCloud and then sign in again after replacing WiFi and Bluetooth hardware to enable Handoff.

There has been a report of an OEM Bluetooth 2.0+EDR card causing a conflict with USB devices. If you experience issues with the built-in USB ports under El Capitan, you may also consider removing or upgrading your Bluetooth card.

In El Capitan, both Phone Calling and SMS from OS X with an iPhone work with a 2006/2007 Mac Pro and are not dependent on OS X Handoff support.


Unsupported original legacy graphics cards vs. 64-bit-kernel-supported graphics cards vs. Metal-supported graphics cards:

El Capitan does not include 64-bit kernel extension device drivers for the original NVIDIA GeForce 7300 GT, ATI Radeon X1900 XT, and NVIDIA Quadro FX 4500 PCIe graphics cards that shipped with these Mac Pros, nor the ATI Radeon X1300 that shipped with the Xserve (Late 2006), so they do not work properly in El Capitan. These graphics cards display issues such as a very sluggish GUI with no QE/CI support, no framebuffer support (for DVD Player, Geekbench and other programs), graphics artifacts, mouse tearing, inability to change resolutions, bad refresh rates, and other system instabilities. If you need normal graphics support in El Capitan, you will need a newer PCIe graphics card, with popular options being the Apple ATI Radeon HD 5770 Graphics Upgrade Kit for Mac Pro, SAPPHIRE HD 7950 3GB GDDR5 MAC Edition, or many different options of stock and Mac-"flashed" PC cards.

Many, but not all, modern stock non-flashed PC graphics cards with AMD (for OpenCL/OpenGL support) or Nvidia chipsets (for CUDA/OpenCL/OpenGL support) work "plug and play" with El Capitan in 2006/2007 Mac Pros, although the display will remain off until after the OS X Desktop initializes. This means you won't see anything during the boot process.

Compatible properly-Mac-flashed PC cards offer two benefits over stock non-flashed PC cards: allowing a normal boot screen just like a Mac-specific graphics card, and better compatibility in OS X with the card's capabilities/performance/ports. Most, but not all, Mac-flashed ATI/AMD cards have EBC firmware that work in all PCIe-based 2006-2012 Mac Pro models with either EFI32 or EFI64. All newer Mac-flashed Nvidia cards have EFI64 firmware and will act like non-flashed PC cards with no boot screens in EFI32-based 2006/2007 Mac Pros, except for older Mac-flashed Nvidia GeForce 8800 GT/9800 GT/GT 120 cards with EFI32 firmware.

Lastly, El Capitan has added a new graphics API called Metal that allows for much faster access to graphics card hardware. Note that only the most recent AMD (HD 7xxx "Tahiti" or newer) or Nvidia chipset (GeForce 6xx "Kepler" or newer) graphics cards fully and properly support Metal in a 2006/2007 Mac Pro.
Note also that the 2006/2007 Mac Pro has PCIe 1.1 expansion slots, with the bottom double-wide slot capable of being configured to use a maximum 2.5 GT/s link speed when configured as a x16 lane graphics slot. El Capitan's Expansion Slot Utility, located in /System/Library/Core Services, supports the 2006-2007 Mac Pro to configure the number of lanes available in each slot. PCIe 2.0/3.0 cards that can run at 5.0 GT/s link speed in 2008-2012 Mac Pros can work in 2006/2007 Mac Pros, but only with a PCIe 1.1 maximum 2.5 GT/s link speed.

None of these options are officially supported in these Mac Pros by AMD, Apple, or Nvidia, but can work with the Piker-Alpha boot loader.


iMessage/FaceTime note:

Regardless of approach used, some users cannot initially login to iMessage or FaceTime using their Apple ID from their Mac Pro after installing El Capitan as a security precaution. When trying to login, they receive an iMessage Registration validation code. The solution is to contact Apple support, provide the Mac Pro's serial number, explain that El Capitan was installed and that iMessage isn't working and provide the validation code. Apple then unblocks the Mac Pro, allowing iMessage and FaceTime login immediately and in the future without other issues.
Hi i am new to os x and i have got a macbook 2,1model number A1181 and was wondering if you can help me get either el capitan or poss yosemite 10.10.5 on it plz i have gone through loads of forums and videos on youtube but everything i seem to do dont work and the os x thats on it is rubish to the 1 im running virtualy on my windows laptop
 

kuglepen

macrumors newbie
Aug 11, 2012
27
0
It obviously works okay on my MacPro 1,1 (2,1) without issue. There must be some differences between your machine(s) and mine. What version of Mac OS X were you using when you built the installer? It is most probably a version issue....

I ran the script on Yosemite (last version). Regrettably I don’t have the log anymore.
 

macimesser

macrumors newbie
Mar 7, 2016
1
0
I have upgrated my MacPro 2,1 from Snow to El Capitan. It works well. But, one more thing... Terminal freezes. Any idea?
 

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
Hi i am new to os x and i have got a macbook 2,1model number A1181 and was wondering if you can help me get either el capitan or poss yosemite 10.10.5
No way. This machine will not support anything past 10.8, no matter how you hack it. Getting 10.7 on it is relatively simple, 10.8 is a major surgery and any later system is just impossible.
 

andijegg

macrumors newbie
Feb 28, 2016
11
0
Thanks for your Help i get my Mac Pro 1,1 running El Capitan 10.11.3 at least by Setting it up via my rMBP and chanching the boot.efi by Hand.

But at least I have System crashes many Times, so it's no fun working with it. Before my changes with the HD's and the decision to set up the System again from the ground I had 10.11.1 running on the Mac Pro 1,1 and I had no System crashes at all. So I think it could be the 10.11.3 my Mac pro can't handle.

So I want set up the System again with the 10.11.1, but I can't find it anywhere to download. Does anyone here knew a Downloadlink that's working for the 10.11.1?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.