Separate names with a comma.
Discussion in 'OS X El Capitan (10.11)' started by Mr. Zarniwoop, Jun 8, 2015.
Thanks for that report, I did the same thing and no problem so far.
--- Post Merged, Apr 8, 2018 ---
Could you send me a copy of kernel 2017 as my MacPro2,1 is in a boot loop after installing Security Update 2018-002 ?
Any instruction on how to find the kernel? (it seems hidden in my system). Thanks Aaron
--- Post Merged, Apr 8, 2018 ---
The kernel is found in your System/Library/Kernels Folder....
On my system it is the only file located there.
Thanks for the info.
It's much appreciated.
Does anyone have a copy of kernel2017
You can download the Security update from here...
then use Pacifist and these instructions...
* download the El Capitan 2017-005 update
* extract the 2017 kernel from it using Pacifist
* copy the 2017 kernel over the 2018 kernel on your El Capitan partition
* run 'touch /System/Library/Extensions' on the El Capitan partition
sent you a personal message.
Thank you so much rthpjm!
Yep I did the firmware update and all happy as a 2,1 and booting my Pikified OS 10.11
I had trouble doing the firmware update from 10.11
I booted on an old 10.6 drive and it worked from there...
My Mac was starting to be crashing on wake up, but the Firmware seems to have fixed that.
No performance increase. Geek bench still around 8000.
Thanks very much!!
This question is with regard to the Security Update 2018-xxx
I finally have a working system after following these directions.
We use this system at church for live streaming and to get things working required extra work.
We have an M-Audio 1814 Firewire Audio Interface. I had to do quite a bit of digging to finally find a forum where a member had compiled a driver that would work properly with El Capitan as the last supported OS from M Audio was 10.7.
I have that working, I have OBS Studio all loaded up and working the way it should as well.
Would Time Machine be the best way at this time to take a working snapshot of the system as it currently is to restore functionality in case something happens like that Security Update?
I am not the only one who operates this computer. I plan to put a notice on it, DO NOT INSTALL UPDATES, but, just in case, I want a working backup that can take me right back to right now.
Thanks in advance.
I'd use CCC.. Not Time Machine. Then if any problems you will have a bootable working back up.
As the last person said, once you have a working system that you're happy with, do a complete clone of that using Carbon Copy Cloner:
Clone it to a different hard drive, take that hard drive out of the Mac Pro and store it somewhere safe in case something goes wrong with your boot drive. If that should happen, you can simply boot from the backup and clone it back over to the boot drive, if you need it.
Where do I find the firmware update?
Without checking this thread, I mistakenly installed Security Update 2018-002. It really messed up my system. I did replace the kernel with the kernel from the Security Update 2017-005 and was able to boot my system again but I still had problems. (E.g. I could not install the latest version of iTunes (12.7.4) using the Apple installer without seeing a software installation error at the end of the attempted installation).
So I reformatted the drive and started again. This time I used version 14 of pikify and choose the grey screen. Pikify version 14 did install EL Capitan fine but it installed the black boot screen not the grey boot screen that I requested during the installation.
How can I change the colour of the boot screen back to grey from this black boot screen?
I hope I will need to just change a file somewhere.
P.S. I did not install boot64 etc since I no longer see the point in using it. Since I will no longer be installing Apple Security Updates (after Security Update 2017-005) and Auto Updates has been disabled, it is unlikely boot.efi will ever change.
There are many ways of getting the correct background colour.
Pike hard coded it. There are two versions of the boot.efi file, one with the grey background, the other with the black background.
Post #1 of this thread points you to Pike’s site where you can download one or both files. Simply copy your choice into the right place(s)
If you used my Pikify script, there are copies in the folder
If you used the App, there are copies in the app/Contents/Resources folder
If you have Boot64 installed there are copies in /Library/Application Support/Boot64
If you have CapitanPikeFix installed, there are copies in /usr/standalone/i386
There’s a bug in Boot64 version 3 it always copies the grey background version (sorry folks - I fixed it many moons ago but never bothered to release the update because nobody ever noticed!)
If you have Boot64 installed, you can run this command from the terminal
/Library/Application\ Support/Boot64/ensureBoot.sh -g
(Actually, it’s been so long since I looked at Boot64 I cannot remember the actual name of the command. Change directory and take a look. The file itself has plenty of comments)
Thanks. I got it working properly again.
Do you think Pike will ever update his boot loader to handle the new kernel etc introduced in Security Update 2018-001 and 2018-002? I hope he does so we can take advantage of the latest security fixes.
It is highly unlikely that we will benefit from Pike's efforts again, after sustaining multiple life-altering events in relatively short order, Pike has opted out of further participation in the at-large Hackintosh community.
refer to his blog:
Wow, that is sad to read. That guy was absolutely brilliant, good luck to him and hopefully things get back on track for him!
Out of interest - now that El Cap is at the bottom of the support chain and will be dropped by the end of the year by Apple, what are people's plans for their 1.1/2.1 systems?
Keep going with El Cap? Or, keep them running with Windows/Linux?
Or, sell them/ditch them altogether?
I get about 5 minutes into installation and my Mac Pro randomly restarts. installation did not finish I've tried re-patching several times and still won't work. any suggestions? did I get a corrupt copy of the installer somehow?
They run windows 10 pro 64 bit awesome!
Sko said "mv'ed kernel to kernel22018, cp'ed kernel2017 to kernel"
Do you really have to move the current kernel to kernel22018?
I'm asking as do I have to create such a folder or can I just junk it?
PS I'm quite sure that I was running modded Sierra and not El Capitan
@Aaron1966 I'm keeping it just for future reference, you may as well delete it.
Could you please describe the kind of bootloop you were getting? Was it like the 001 update, hapenning early on boot with a blinking light, or was it getting stuck on the apple logo? I've been stuck on boot for a while and didn't have the time to troubleshoot until now. I remember I had explicitly hidden the 002 update, but maybe it got installed somehow after all. My backup also has the same problem, scarily enough, I'm not sure how I screwed this up. I do hope it's not a hardware issue. I'll try your kernel swap method.
How much RAM do you have in your MacPro?
@sOwL I got an Apple logo and a progress bar for a split second, then it rebooted.
There's a thread at netkas.
About This Mac->Installations can tell you what kernel you have installed.