I was having a lot of trouble getting El Capitan to work with my 5450, mainly because I couldn't modify the kexts or install any with kext utility, kept getting errors. Finally after a fresh install, I tried just adding ati5000injector(modified to look for amd) and i was able to get the graphics card to work. Before I modified El Capitan to boot up with my mac pro I had turned on screen sharing so I could see if it was working and make changes for the card. Now that its working, I'm having all those issues of sluggishness and refresh and reboots. I had this problem before with Mavericks I believe, but can't remember how I fixed it. It might have been by removing or adding ati accelerator, but I'm not sure. Has anyone had this problem that they were able to fix? I've already tried searching, but there's so many posts and none seem to have the answer, only to install the other kexts which don't work.
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
When the script is done am I suppose to have a usb drive with the install app inside of it? The script finishes and when I open the usb drive of Install OS X El Capitan its just a drive with the application to upgrade. I am not infront of my Mac Pro so I can't run it. But when I try to restart my macbook it doesn't boot from the usb. It does see it in the startup options when I hold down option during boot. It then just boots to my install disk. I just wanted to make sure that this is normal.
I also get this message at the end of the script so I should be good I guess.
######### DONE PIKIFYING ###########
I also get this message at the end of the script so I should be good I guess.
######### DONE PIKIFYING ###########
The built/patched installer is designed to boot your 32-bit machine (Mac Pro). You should boot your Mac Pro from the USB drive and it will automatically present you with the Apple Installer. (You should not try to run the installer directly from a booted OS, you must boot from the volume)
Hello all worlds
I do not arrive has to make the key El Capitan.
The terminal gives me ca
"Cannot find copy of Apple's Install OS X El Capitan application in your Applications folder.
Please use the App Store to download a copy...
bash-3.2#"
I do not arrive has to make the key El Capitan.
The terminal gives me ca
"Cannot find copy of Apple's Install OS X El Capitan application in your Applications folder.
Please use the App Store to download a copy...
bash-3.2#"
Do you have "installer osX el capitan" in your application folder ?
you should download it frmm app store first, or pick it on another mac.
Pikily needs the original installer to create the modified one. it does not contains installer itself.
Last edited:
Double click the El Capitan installer in Launchpad as though beginning the install. Then Quit the installer from the menu bar. The installer may then appear in the Applications folder if it isn't already.
EDIT: just removed the installer from my applications folder and it also removes it from Launchpad so not sure how it can be in your Launchpad but not also in the applications folder.
Last edited:
\
Ok This is what the script gives me when I run the createpikeinstallmedia script.
I used a Macbook Pro Retina running El Capitan 10.11.2 when I try and make the install disk. I have tried using an SSD and a USB Key as well as a HDD all make the same install disk in the picture.
I used both your v8 and v2 installers folders.
Also this is the terminal readout:
Code:
Pikify3.1 contains a script and other items to create install media for Mac OS X El Capitan to be used on 32-bit EFI based Macintosh computers
It uses Apple's "Install OS X El Capitan.app" application which must be located in your /Applications folder
There are a number of processing steps, please be patient and let this script run through to completion
A small number of users have been too eager to get started and pulled their installer volume out of the USB socket too early
The script will end with ######### DONE PIKIFYING ########### if all goes well
------------------------------------------------------------------------------------------------------------------------------------------------------------
Running Apple's createinstallmedia tool...
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
Piking the .IABootFiles directory
Open the InstallESD disk image
Piking the OSInstall collection
Copy the BaseSystem disk image to /tmp
building file list ...
1 file to consider
BaseSystem.dmg
477.05M 100% 71.70MB/s 0:00:06 (xfer#1, to-check=0/1)
sent 477.10M bytes received 42 bytes 73.40M bytes/sec
total size is 477.05M speedup is 1.00
Open the BaseSystem disk image
Piking the Base System
Adding the missing fonts...
Close the BaseSystem disk image
Put the modified BaseSystem back into the InstallESD disk image
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $5F3764E7: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $CBD63B0C: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $7E75A5A2: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
..........................................................................
(CRC32 $BFFF63ED: disk image (Apple_HFS : 4))
Reading (Apple_Free : 5)…
..............................................................................
(CRC32 $00000000: (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
..............................................................................
(CRC32 $7E75A5A2: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
...............................................................................
(CRC32 $8FC8CBF7: GPT Header (Backup GPT Header : 7))
Adding resources…
...............................................................................
Elapsed Time: 37.797s
File size: 477044709 bytes, Checksum: CRC32 $B9E55B9A
Sectors processed: 4191128, 2972548 compressed
Speed: 38.4Mbytes/sec
Savings: 77.8%
created: /Volumes/OS X Install ESD/BaseSystem.dmg
Close the InstallESD disk image
Put the modified InstallESD back into the Install OS X El Capitan volume
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $778956DC: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $DFEBF1DD: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $9139EE86: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading EFI System Partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B : 4)…
..
(CRC32 $B54B659C: EFI System Partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B : 4))
Reading disk image (Apple_HFS : 5)…
.............................................................................
(CRC32 $BE96C8B2: disk image (Apple_HFS : 5))
Reading (Apple_Free : 6)…
..............................................................................
(CRC32 $00000000: (Apple_Free : 6))
Reading GPT Partition Data (Backup GPT Table : 7)…
..............................................................................
(CRC32 $9139EE86: GPT Partition Data (Backup GPT Table : 7))
Reading GPT Header (Backup GPT Header : 8)…
...............................................................................
(CRC32 $82419D4F: GPT Header (Backup GPT Header : 8))
Adding resources…
...............................................................................
Elapsed Time: 2m 38.584s
File size: 6190912589 bytes, Checksum: CRC32 $FB08BAB5
Sectors processed: 13277760, 12792796 compressed
Speed: 39.4Mbytes/sec
Savings: 8.9%
created: /Volumes/Install OS X El Capitan/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg
######### DONE PIKIFYING ###########Attachments
Hello peterc18st
Okay. That all looks to be correct.
Now attach the Install OS X El Capitan volume (presumably this is a removable media) to your Mac Pro.
Reboot the Mac Pro, when you hear the chime hold down the ALT key until you see the boot picker.
Use the arrow keys or your mouse to select the Install OS X El Capitan volume (the arrow in the circle should move to be under the selected volume). Hit the Enter/Return key, or double-click the mouse (you might need to click the arrow in the circle with the mouse I can't remember because I always use the arrow keys).
Your Mac Pro should boot up, and immediately present you with the Installer. Now follow the Installer instructions...
OK will do. Its weird because most usb keys I use to make install media for os installs you get a much different usb key contents. File and folders etc. It just looked weird to have the install app in the usb key all by itself.
I'm away from the Mac Pro right now but will be installing it on a actual 2,1 system with 16GB of ram and a newly bought from eBay used 5770 mac vid card for $100 as the X1900XT isn't capable of running Capitan. I will drop a line in a week when I have my machine back. Waiting on a new SSD to arrive also. Wanted to have the install media ready at the go to make this happen.
I will use Boot64 as well after I get this up and running.
There are a number of files/folders on the install media, it's just that Apple (being Apple) has hidden them! Open a terminal and use the ls list command if you're interested...
Code:
ls -l /Volumes/Install\ OS\ X\ El\ CapitanBonjour wolf1734,
Is your system configured as French? It occurred to me last night that the pikify3.1 script is written in English, and expects the OS to be English too.
Votre système est configuré en tant que français? Réalisation venu à moi la nuit dernière que le script de pikify3.1 est écrit en anglais, et attend l'OS d'être anglais aussi.
Please use the Terminal to list the contents of the directory at / and the directory at /Applications
S'il vous plaît utiliser le Terminal pour afficher le contenu du répertoire à / et le répertoire dans /Applications
Code:
ls -l /
ls -l /ApplicationsPlease copy and paste the results here
S'il vous plaît copier et coller les résultats ici
OS X only shows translated names in the GUI when set to a language other than English, so any terminal script expecting the english moniker will work just fine.
After thinking about it for a while I decided to give up on el capitan for my macpro.
I mistakenly understood that only the bootable installer had the memory problem.
I thought about buying more memory, but don't feel good about it. The leak might corrupt my work and photos. For me its not worth it anymore.
I am going to live out this macpro on yosemite and windows 7. Divided the new ssd I bought between windows 7 and yosemite.
Feel mostly let down by apple for not supporting a still great mac.
I mistakenly understood that only the bootable installer had the memory problem.
I thought about buying more memory, but don't feel good about it. The leak might corrupt my work and photos. For me its not worth it anymore.
I am going to live out this macpro on yosemite and windows 7. Divided the new ssd I bought between windows 7 and yosemite.
Feel mostly let down by apple for not supporting a still great mac.
What problem other than needing 12gb of RAM to install do you refer to? Yosemite is fine but as I understand it El Cap runs fine too - certainly does in my tests - 12gb of RAM isn't that expensive - I bought 32gb for around £135 with the proper big heat sinks. I don't know how a memory leak on the installer would affect your files though.
I dont mind the money. I have 5 gig. i normaly dont need more.
I almost ordered another 8, but that would be stupid.
I have random reboots, I even had multiple hours without a reboot.
I dont feel good having a leak that cant be catched by the kernel.
Something seems to corrupt memory that the kernel has no control over. ( but obviously uses )
I almost ordered another 8, but that would be stupid.
I have random reboots, I even had multiple hours without a reboot.
I dont feel good having a leak that cant be catched by the kernel.
Something seems to corrupt memory that the kernel has no control over. ( but obviously uses )
Sounds like you have had problems. I installed on test HD using Pikify 3.1 v7 as described in post 1569 by rthpjm and so far so good - no crashes at all. I am still using Yosemite until I get a new SSD but will move over at some point. I think the 512mb chips were an issue in failed installs too, but installation methods have also evolved a lot.
Last edited:
I can almost positively assure you that the 512MB modules cause problems and instability. I had an impossible time with the OEM ram and I've had exactly zero issues since I upgraded. You can buy the ram for $2/GB or less. If you can't spend $32 to keep your MacPro running... Well, I don't know what to say.
Code:
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *960.2 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage Macintosh HD 959.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3I do have a recovery partition and I am even able to mount it. I tried running by hand the command your script is trying to run and got the same failure. I will try version two and see if that makes any difference.
I upgraded to 10.11.12by putting Pikes boot.efi into a previous install/ Now every time that I boot Capitan it won't boot because the boot.efi has revertedd back to the Apple one. I;ve using Cocktail to delete these Apple boots but I only had a demo version of Cocktail.and I have used up the trial. How can I delete the Apple boot.efi files.
A couple of possible issues come to mind.
Do you have more than one Recovery HD? If two are mounted at the same time then one will have the path "/Volumes/Recovery HD", and the other will be "/Volumes/Recovery HD 1".
The other possibility is copy n paste. You say you are running things manually. If you copy n paste a path with a space in it, you need to enclose the path in quotation marks, or escape the space with a \
E.g.
chflags nouchg "/Volumes/Recovery HD/com.apple.recovery.boot/boot.efi"
Or
chflags nouchg /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi
Or your Recovery HD is old (or messed up) and doesn't contain a boot.efi file.
Can you list the content of your Recovery HD and post the result, I'll take a look at it
Code:
ls /Volumes/Recovery\ HD/com.apple.recovery.boot
It's your computer, dude, not the OS. Start with the odd amount of memory of yours, I bet at least one of your 512 MB sticks is toast but you refuse to accept it because of your being too smart and too cheap to spend 30 bucks for decent amount of quality RAM. I mean, come on.
So the memory works fine in yosemite and windows 7 and somehow magically fails on el capitan ?
Yes, that's a well known fact. Most failed OS X installs on "but this hardware worked for years!" computers are due to failing RAM, giving no other symptoms beforehand (on an earlier OS).