Anyone successfully install the El Cap security update that came out in the last few days?
Yup, no problem whatsoever.
Anyone successfully install the El Cap security update that came out in the last few days?
Yup, no problem whatsoever.
Hello maukkuSuccesfully upgraded my 1.1-server from Yosemite to El Capitan by using my MBP and attaching the boot disk of MP as external drive. After copying the boot.efi and plugging the SSD back to the 1.1, it booted the new OS just fine.
The machine has a old PC Radeon HD4650, which I had managed to get fully working under some previous Yosemite version, but after some later update broke it, it has been sitting idle as I had no extreme need for it and no interest to fix the required kexts.
The problem is, that as I run the machine headless, I have to access it trough SSH or VNC. When I updated to latest El Capitan version (10.11.6) and installed a couple of other updates, VNC stopped working. Connecting to machine works (from windows or mac), but after selecting my user account in the login screen and entering my password, the view freezes for a moment and then just returns to initial login view with all user accounts listed.
To diagnose the issue, I checked system.log, and found out that every time I try to login via VNC, I get some (or quite much really) error output about graphics. Could it be that after some update, a proper GPU acceleration is needed to run the VNC-desktop? SSH, file sharing and other server features work just fine, but maintaining a os x-server via command line is just not very handy.
Does anyone have experiences of similar VNC-problems, or generally about getting HD 4650 to work under 10.11.6? Google found some pre-patched kexts, but they were for 10.11.5 and didn't work. I also checked that vanilla kexts provided by Apple already contain the required device-id (0x9498) for this specific card so I can't figure out why it is not auto-detected.
Also there is the SIP. What mechanism is the one that re-activates it? As it has to be disabled via recovery mode, where I can't boot due to missing GPU, every time I need to disable it to tinker with kexts I have to attach my boot drive to my MBP, boot to recovery with it and do the disabling, which is quite annoying. And after a while it is again re-enabled
chflags nouchg /Volumes/MacPro/System/Library/CoreServices/boot.efi
Hello maukku
[doublepost=1481892949][/doublepost]I had the same problem. But it happened to me when I updated to the latest Security update. My Mac 1.1 went crazy like yours. I couldn't even reinstall Yosemite. I finally Cloned my other Mac Pro 1.1 and installed the Hard Drive. It worked great. It seems maybe Apple came up with something in there last update that squashed us from keeping our old Mac Pro's 1.1 -2.1 form being updated. If anyone has a better way of getting updates let me know. I currently do it thru the App. Store..My Mac Pro 1,1 is now FUBAR. I had a fully functioning Yosemite install and tried to upgrade to El Capitan. I have no idea what went wrong, but all of a sudden starting the computer results in the graphics card fan instantly spinning full bore. Within 15 seconds all the system fans start to ramp up. There's no startup chime. I'm wondering if I've done something to the EFI or firmware? I've now stripped out the computer to minimum RAM and only 1 HD. I also replaced the power supply. Any suggestions would be greatly appreciated.
Thank you for everyone providing such amazing help and instructions and I was able to upgrade my Mac Pro 2007 2,1 to El Capitan 10.11.6. It is running very well. I am now thinking of moving to a Mercury Electra 3G SSD from OWC to speed up my system. I have two questions, please.
1. Is installing 10.11.6 onto this SSD same as I did for my HDD, or are there any differences? Which installation package I should prefer, please?
2. Is it better to mount it into one of the SATA HDD slots on my Mac Pro or on a PCIe card, please? Which will give me a faster response?
Thank you very much for your help.
[doublepost=1481892949][/doublepost]
I had the same problem. But it happened to me when I updated to the latest Security update. My Mac 1.1 went crazy like yours. I couldn't even reinstall Yosemite. I finally Cloned my other Mac Pro 1.1 and installed the Hard Drive. It worked great. It seems maybe Apple came up with something in there last update that squashed us from keeping our old Mac Pro's 1.1 -2.1 form being updated. If anyone has a better way of getting updates let me know. I currently do it thru the App. Store..
Surely sometime during the more then a year you've been running El Cap you must have made a backup?
Boot from this backup and copy the boot.efi file over to your non functioning updated install.
USE CARBON COPY CLONER you have an Trial for 30 DAYSThank you for everyone providing such amazing help and instructions and I was able to upgrade my Mac Pro 2007 2,1 to El Capitan 10.11.6. It is running very well. I am now thinking of moving to a Mercury Electra 3G SSD from OWC to speed up my system. I have two questions, please.
1. Is installing 10.11.6 onto this SSD same as I did for my HDD, or are there any differences? Which installation package I should prefer, please?
2. Is it better to mount it into one of the SATA HDD slots on my Mac Pro or on a PCIe card, please? Which will give me a faster response?
Thank you very much for your help.
I have MacPro 2,1 with 20GB RAM and ATI Sapphire 7950, main HDD is FusionDrive (Samsung 850 EVO 512GB + Western Digital WD10EAR-X 1TB). No problem with any update till now.
Updated with last Security Update 2016-003 10.11.6, everything went as normal. Mac rebooted, but was little sluggish at first. When all drives appeared, everything disk related went slow. Opening the main disk lasted for almost a minute (spinning beach ball in between). There were all files on drive, but not one program worked. For every one there was a message “Application XX is damaged or incomplete and cannot be run”. This also happened on second WD10EAR-X which has a copy of system 10.11.4. All applications appeared as damaged.
So, I restored from TimeMachine, almost 24 hours later Mac was working again. For two days. Then I applied the security update again, with the same result.
Another restore from Time Machine and I have no more desire to apply the security update again.
In the Riser A card are two 4 Gig modules in position 1 and 2, and in the Riser B card are two 4 Gig modules also in position 1 and 2. Two 2 Gig modules are placed on the Riser A card in position 3 and 4. Should work fine.Question, are your 4 1Gig modules all on 1 memory daughter card?
You don't "need" to upgrade the firmware, but you do not need to be afraid.So I have managed to get El Capitan running on my Mac Pro 1.1 without any issues using pikify3.1.v12. I have also setup Boot64.v3 so that I could update from the version of El Cap that I have, (10.11.4), to the latest. (I haven't actually done this yet).
I have replaced the graphics card with an AMD Radeon 6870 and am running 20GB RAM.
I also decided to install two X5365's which I have now done. Everything seems to be working perfectly but I read somewhere that I should upgrade the firmware to 2.1 for these processors? I downloaded the firmware upgrade tool, hold down the power button on restart until the long beep but it doesn't do anything.
Any Ideas? Do I need to update to 2.1? It seems to be running fine and reports all 8 cores... it does say unknown processor though.
You don't "need" to upgrade the firmware, but you do not need to be afraid.
Upgrading the firmware helps to identify the processors to the OS. My MacPro 1,1 is flashed to 2,1 firmware and it has been very stable.
Boot64 and the boot.efi files are not the same as "the firmware upgrade" they are different.Ah that's good to know. So any ideas why I can't get the firmware update to work? could it be because of the boot64 updating the EFI each time I shutdown?