2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[Ant3000]

So you have tried keyboard and mouse in all the USB ports and it's still the same?

Have you tried them attached to another Mac - this will help to pinpoint the problem.

 

[Mastropiero]

Nope but will do and get back to you.


edit: I left the computer on, two hours later both mice and keyboard work fine. The only explanation I can think of - bare with me if I say anything stupid - is: last thing I clicked prior to this problem starting was the spotlight magnifying glass because it was indexing and wanted to check. Today, during all my attempts to get the peripherals working, spotlight was still indexing.

Now it has stopped.... and I can type and click. I am in Lion right now and the problem is gone. If it arises again, I will check everything as instructed and report back.


Many thanks!

 

[rthpjm]

Intellimouse yes, but as I said, that one probably is FUBAR.

MM and Logitech work fine in Yosemite. Well, MM 2 works very basic in Yosemite but that's not the point.

Regarding checking prefs in Lion.... I can't get there, can't click anything. Oh, by the way, keyboard is gone too. I don't know if I could get to prefs via shortcuts but I tried fn keys and volume and such and they don't work either. It looks - in my illiterate opinion - USB related. It's odd though that keyboard is gone and mice are just half gone, ie they react to movement but not to clicks

Try an SMC reset (my footer/signature has a signpost)

 

[Mastropiero]

Try an SMC reset (my footer/signature has a signpost)

I would've but check my last reply, the problem sorted out by itself. Pikifying as I type.

 

[rthpjm]

I would've but check my last reply, the problem sorted out by itself. Pikifying as I type.

Yeah, I spotted that after my post went up.
Asynchronousness strikes again
[doublepost=1503605223][/doublepost]

I would've but check my last reply, the problem sorted out by itself. Pikifying as I type.

Well, the last few days (in my spare time) I've had a go at building a GUI for Pikify.
It's a bit rough around the edges, anyone want to give it a try?....

 

[Mastropiero]

Oh joy, while installing, my Intellimouse - still plugged- has come to life. Go figure.

 

[Adesz88]

How this perform under El Capitan in my Mac Pro 2,1?
Samsung 16GB (4X4GB) PC2-5300F DDR2-667MHZ ECC Fully Buffered FB-DIMM Server RAM
Is this worth to buying it?

 

[Mastropiero]

Hi guys, I just wanted to check in and let you know that my installation of El Capitan 10.11.6 is up and running. I have just installed boot64 as well, I hope I won't have to trouble you too much again.


Big thanks for the great work and help, you guys are fantastic.

 

[izzy0242mr]

Just installed El Cap 10.11.6 on my 2006 Mac Pro (x2 3.0 GHz Xeon chips, 32 GB RAM, Radeon HD 4870 Mac GPU) using Pike's v14 script, but the sound is greyed out. I've selected "internal speakers" in sysPrefs but it still has no audio output. Any fixes?

ALSO: My computer only registers 28 GB RAM instead of 32, any clues why that might be? It was detecting all 32 GB a few minutes ago when I was on Lion. All 8 sticks are detected, but 2 of my 4GB sicks are registering as 2GB sticks.

Also, my firmware is 1,1 if that makes a difference.

 

[Ant3000]

Reseat the RAM - look for LEds on riser board to show faulty modules. If it persists, pull faulty RAM.
Try SMC reset / PRAM reset.

 

[izzy0242mr]

Reseat the RAM - look for LEds on riser board to show faulty modules. If it persists, pull faulty RAM.
Try SMC reset / PRAM reset.

Will test it out thanks.

UPDATE: Audio working mysteriously now. I rebooted a few times.

 

[rthpjm]

Hi guys, I just wanted to check in and let you know that my installation of El Capitan 10.11.6 is up and running. I have just installed boot64 as well, I hope I won't have to trouble you too much again.


Big thanks for the great work and help, you guys are fantastic.

Great.

You probably will not need Boot64. Apple are unlikely to release any system updates (e.g. 10.11.7) for El Capitan. We will probably see one or two more security updates, however, security updates do not typically include modified boot.efi files...,

 

[Nward85]

As Ant3000 says, it's usually RAM.

Look at the responses above on this page (dhammans). Lots of RAM installed but not all of it was being recognised.

Check, then check again. Read back a few pages. Most users who have sought help recently have all had similar experiences, and it's down to RAM...

Well I installed the new ram, a total of 24 gigs, 4-4gigs and 4-2gigs. Did the 'Reinstall OS X' from OS X Utilities, it rebooted, and took me back to OS X Utilities.

So it was not the ram.

Any thoughts?

 

[Ant3000]

Its the installer that needs the extra RAM to work correctly. Have you tried reusing the original USB installer or taking the steps necessary to be able to reuse the USB installer you originally created?

 

[Nward85]

Its the installer that needs the extra RAM to work correctly. Have you tried reusing the original USB installer or taking the steps necessary to be able to reuse the USB installer you originally created?

I was using the new 2017 method, not the USB installer. Am I able to use the USB installer if I cannot access the computer? I do have a laptop to use to setup the USB.
[doublepost=1503779312][/doublepost]

Even Newer:
Coming soon.... The Pikify App.
I rushed this a little, and I have just found the App is crashing, I'll sort it out soon...


Please treat the App as initial Alpha code. It's a bit rough, but it works. I might find the time to give the app a bit more polish, it could really do with some more error checking, there's no help file, etc...

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.

The same conditions apply:

• You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.
• If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later; I suggest Lion 10.7 because that's what I've tested this version on!

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

if you are using El Capitan to install another copy of El Capitan, and if SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer (hint: try holding the C key immediately after you hear the start up chime)... (hint 2: disable SIP before you start)​

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD
[your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer (hint: try holding the C key immediately after you hear the start up chime)...



++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (Install Piked OS X El Capitan.zip) = c4272187f6f6e060a4580b5812872463

I see things have been updated, how do I use the 2017 version with a USB?

 

[Nward85]

I was using the new 2017 method, not the USB installer. Am I able to use the USB installer if I cannot access the computer? I do have a laptop to use to setup the USB.
[doublepost=1503779312][/doublepost]
I see things have been updated, how do I use the 2017 version with a USB?

Okay so...It's the same but I choose my USB instead of my hard drive I am assuming?

 

[Nward85]

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:

• El Capitan branch of the Piker-Alpha bootloader - still in active development
  
• rthpjm's Pikify installer script and accompanying files can build a pre-patched OS X El Capitan installer with the Piker-Alpha bootloader for the 2006/2007 Mac Pro
• MacVidCard's guide for installing El Capitan to a 2006/2007 Mac Pro using a second El Capitan-supported Mac

________________________________________________________________

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.

• Good, but without Metal API support: The least expensive El Capitan-compatible recommended graphics card that can provide boot screens in any 2006-2012 Mac Pro is a properly-Mac-flashed Nvidia GeForce GT 120, which was Apple's branding for the Nvidia GeForce 9500 GT. MacVidCards has a promotion on the EFI32 dual-DVI and DVI/DisplayPort version of this card with 256MB for readers of this thread for $70 USD.
• Better, adding Metal support: Other more powerful graphics cards that can provide boot screens and Metal API support in a 2006/2007 Mac Pro are AMD Tahiti-based such as a properly Mac-flashed AMD Radeon R9 280/AMD Radeon HD 7950 (similar memory architecture and clocks as the AMD FirePro D500 available on the 2013 Mac Pro but with more cores) or better yet a properly Mac-flashed AMD Radeon HD 7970 (with the same GPU as the AMD FirePro D700) based on EBC firmware modified by MacVidCards.
• Best: Currently, the highest-performing graphics card that can provide boot screens and Metal support in a 2006/2007 Mac Pro is a properly-Mac-flashed AMD Radeon R9 280X 3GB/AMD Radeon HD 7970 GHz Edition (~10-15% faster clocks from the AMD Radeon 7970). This does not include the 6GB version of the R9 280X which has issues when flashed for a Mac Pro. MacVidCards sells a fully Mac Pro-ready AMD R9 280X 3GB card and also offers flashing services for customer-supplied cards.
• Note that if for some reason you still need to boot OS X Lion or early Mountain Lion versions that all AMD Tahiti-based cards (7950/7970 and R9 280/280X) are only properly supported by OS X 10.8.3 or higher, although there are OS X 10.7.5-10.8.2 AMD Tahiti graphics card device driver kernel extensions that may work in a 2006/2007 Mac Pro when used with tiamo's boot loader.

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.

Any thoughts on the best graphic card to upgrade to for dual monitors?
[doublepost=1503802954][/doublepost]Okay so I've got El Capitan up and running perfectly! Just one issue I have noticed so far, no audio! Is this normal?

 

[rthpjm]

Any thoughts on the best graphic card to upgrade to for dual monitors?
[doublepost=1503802954][/doublepost]Okay so I've got El Capitan up and running perfectly! Just one issue I have noticed so far, no audio! Is this normal?

Many people use a card such as the ATI 5770. You can get a stock PC version and with a bit of effort reflash it to have both BIOS firmware and EFI firmware on the card. This means a cheap PC Card can be made fully Mac compatible showing the initial EFI-generated boot screens.
There are other makes and models that work just fine too. My advice, do some research.

Most cards from that era, or newer will work great, once Mac OS X takes over from the EFI. If you want EFI boot screens you are limited to Apple branded cards, or a small set of generic PC brand cards that the community has managed to modify the firmware.

The more recent cards are going to be a struggle (the ATI 1050 and newer) due to the Mac OS X drivers not being available. Luckily, NVidia are producing drivers independently of Apple, so many of their newer cards will work.

It's a wide field. Do some research and take your pick.

 

[robbier]

Hi All,
I am running into the random kernel panic / restart issue that has been documented in this thread. The kernel panics only occur under El Capitan with the new boot.efi file - it is perfectly stable under Lion. It has been suggested to only use 2GB FB-DIMMs to avoid having kernel panics, however I already am using 2GB FB-DIMMs only, so I am not quite sure where to go from here. Any help is appreciated!

Thanks!

Robert

 

[chrisrm9208]

G'day!

Up to two days ago, I had a happily-working MP1,1 with El Cap, then I tried Kaspersky AV...

I've now got to the point of having recovered El Cap back onto a spare HDD using pikify3.1, so I threw caution to the wind (downwind, at that), erased the old SSD with the screwed Library and pikified the SSD. The SSD has the OS X Install directory, is blessed, doesn't appear in Startup Disk, does appear in Finder, and refuses to continue with the installation.

What have I missed/done wrong?

thanks in advance,

Chris M

 

[Adesz88]

Please help!
This memory good for my mac pro 2,1 with el capitan?
Samsung 16GB (4X4GB) PC2-5300F DDR2-667MHZ ECC Fully Buffered FB-DIMM Server RAM

I have now 2 2gb pc2-5300f ram and 1 1gb pc2-6400f ram and 1 1gb pc2-5300f ram and i have kernel panic in el capitan.
I tried just with the 2 gb sticks but its crashes.
I wan't to buy this 16gb ram.

 

[robbier]

Hi All,
I am running into the random kernel panic / restart issue that has been documented in this thread. The kernel panics only occur under El Capitan with the new boot.efi file - it is perfectly stable under Lion. It has been suggested to only use 2GB FB-DIMMs to avoid having kernel panics, however I already am using 2GB FB-DIMMs only, so I am not quite sure where to go from here. Any help is appreciated!

Thanks!

Robert

Update: After installing an additional two 2GB memory modules, the system is running perfectly with no kernel panics or instability. My configuration is now 4 x 2GB for a total of 8GB, with two modules on each riser card. I'm not sure exactly why this fixed the issue, but my theory is that it has something to do with both riser cards being populated with DIMMs instead of the bottom card being left empty as in my previous configuration.

 

[rthpjm]

Update: After installing an additional two 2GB memory modules, the system is running perfectly with no kernel panics or instability. My configuration is now 4 x 2GB for a total of 8GB, with two modules on each riser card. I'm not sure exactly why this fixed the issue, but my theory is that it has something to do with both riser cards being populated with DIMMs instead of the bottom card being left empty as in my previous configuration.

These machines are usually dual CPU.
For this reason each DIMM (or pair of DIMMs) must be installed in a specific order.

If you have:
Two DIMMs (standard configuration):

One on the top memory card and one on the bottom card​

Four DIMMs:

One pair on the top memory card and one pair on the bottom card​

Six DIMMs

Two pairs on the top memory card and one pair on the bottom card​

Eight DIMMs:

Two pairs on the top memory card and two pairs on the bottom card​

There is a graphic printed on the inside of the side panel.
Apple still have a support article on the subject: Mac Pro (Original)

 

[robbier]

These machines are usually dual CPU.
For this reason each DIMM (or pair of DIMMs) must be installed in a specific order.

If you have:
Two DIMMs (standard configuration):

One on the top memory card and one on the bottom card​

Four DIMMs:

One pair on the top memory card and one pair on the bottom card​

Six DIMMs

Two pairs on the top memory card and one pair on the bottom card​

Eight DIMMs:

Two pairs on the top memory card and two pairs on the bottom card​

There is a graphic printed on the inside of the side panel.
Apple still have a support article on the subject: Mac Pro (Original)

Ah, that explains it! Thanks for the info. For some reason I thought that a two DIMM configuration required installing DIMMS just on the top card. Interesting that it didn't cause any issues under Lion but it did under El Capitan.

Edit: I knew there was a reason why I thought two DIMMs were supped to be installed on the top card only...for some reason, the side panel graphic on my 2,1 machine depicts two DIMMs installed in a pair on the top riser card and nothing on the bottom riser card.

 

[chrisrm9208]

G'day!

Up to two days ago, I had a happily-working MP1,1 with El Cap, then I tried Kaspersky AV...

I've now got to the point of having recovered El Cap back onto a spare HDD using pikify3.1, so I threw caution to the wind (downwind, at that), erased the old SSD with the screwed Library and pikified the SSD. The SSD has the OS X Install directory, is blessed, doesn't appear in Startup Disk, does appear in Finder, and refuses to continue with the installation.

What have I missed/done wrong?

thanks in advance,

Chris M

OK, the beat goes on....

Have thrown away the entire MP, as it descended on startup to the chime, followed by 10 seconds of blank screen, then shutdown. No response to any startup keys, nothing. So, to Ebay and another MP1,1 for very little money. This is running Lion (10.7) and the drive I want to install ElCap onto is the SSD. The Pikify app ('Install Piked OS X El Capitan') has been supplied with the requisite ElCap installer (10.11.3) in Applications, it's been run pointing at the newly-formatted SSD(which now *does* appear in Finder), and Boot64.v3 has then been run against the same SSD. No errors reported, but the reboot simply sits with a blank white screen and goes nowhere. I did leave it for 15 minutes in case it was going to do something amusing or religious but no.

Any ideas as to what I've missed out or done wrong?

Chris M