Unfortunately that version has been tested already. No fix so far.Big Sur 11.4 released, same build as RC.
Code:071-00696 11.4 20F71 2021-05-24 macOS Big Sur
Unfortunately that version has been tested already. No fix so far.Big Sur 11.4 released, same build as RC.
Code:071-00696 11.4 20F71 2021-05-24 macOS Big Sur
I dreaded the only answer would be that... Still, has anyone had any insight as to why it hangs?If at first you don't succeed, try, try again. I've had installs take the first time with no issues, I've had most fail 1/2/3 times requiring a power cycle, and I've had the system drive become corrupted during install, 5x now actually. Twice I was able to recover by booting into recovery and performing a reinstall, but I've also had to wipe the system drive and start over.
Note that even without the patch, ethernet initialization is a common point at which the hanging occurs.Looks like we have another machine that hangs on the ethernet initialization with this patch applied.
How can we deal with installation hanging continually?
Perseverance is great advice in general. But in this situation even if the installation eventually goes through, the hanging will just occur on the next reboot or so. If the purpose of the installation is just for testing, then it's easier to prepare a ≥11.3 bootable USB installer and try booting that.If at first you don't succeed, try, try again.
I tried both ways, System > Prefs update and usb 11.3 installer. In both cases the installer hung and kept on doing so after 8 forced reboots. I feel that if there were a way to determine the reason why installations hang we would be closer to finding a solution with regard to the behaviour of 11.3.x and up.then it's easier to prepare a ≥11.3 bootable USB installer and try booting that.
Did the USB installer even boot into the recovery environment? Because just booting into that will hang. The point is that simply trying to boot a USB installer is enough to test proposed patches.I tried both ways, System > Prefs update and usb 11.3 installer. In both cases the installer hung and kept on doing so after 8 forced reboots.
Yes it did. I was also able to start the terminal to to ensure SIP was off. When I clicked install macos, it started the installation, progressed to the first reboot where in OC you can choose the macos installer and then after a while in hung. Forced reboots allowed for a little progress of the bar to the point it came to a standstill.Did the USB installer even boot into the recovery environment? Because just booting into that will hang. The point is that simply trying to boot a USB installer is enough to test proposed patches.
Yes, however with the patch, it hangs at that point MUCH more frequently, at least in my case, and a couple others. It used to be much more random, but with the patch, it's near 100%. Syncretic was looking for change, and that's a change.Note that even without the patch, ethernet initialization is a common point at which the hanging occurs.
Is it safe to install?Big Sur 11.4 released, same build as RC.
Code:071-00696 11.4 20F71 2021-05-24 macOS Big Sur
Is it safe to install?
FYI you left your serial number on the screenshot... might be better to remove it/cover it.Its not any better at all.
More info on my experience using JohnD's config.plist file built using syncretic's information. My 5,1 boots 11.3.1 reliably if and only if I use the unaltered config.plist file. One change that makes it crash every time is activating SIP ( search for csr-active-config, change dwgAAA== to AAAAAA== ). Then when I go back to SIP deactivated (the "default" setting of the unaltered config.plist file) 11.3.1 boots reliably again. I had initially thought that some spaces were creeping into the config.plist file, but that was not the case. Activating SIP always causes 11.3.1 to crash on boot, at least for my machine. I'd like to try a few other changes to the config.plist file, such as retina support for the bootpicker and enabling the legacy wifi card. But I suppose if this prebuilt config.plist works as long as it's not altered at all it would be good enough for me!My 5,1 seems to be mostly OK with installing Big Sur 11.3.1 using OC 0.6.9 (and syncretic's unaltered config.plist) and then booting. One thing I learned the hard way was that I had to use a completely unaltered version of syncretic's config.plist file. My 5,1 crashed when I had altered the posted file for just legacy wifi and retina boot. I started with a SATA drive and moved on to an NVMe drive.
...
11.3.1 BOOT (Syncretic Patch/SIP Enabled) | RESULT | VERBOSE PIC |
---|---|---|
Warm | ✅ | |
Warm | ✅ | |
Warm | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Warm | ✅ | |
Warm | ✅ | |
Warm | ❌ | 11_3_1 Boot_Test Syncretic_Patch PIC_01.jpeg |
Cold (Forced Shutdown) | ❌ | 11_3_1 Boot_Test Syncretic_Patch PIC_02.jpeg |
Cold (Forced Shutdown) | ✅ | |
Warm | ❌ | 11_3_1 Boot_Test Syncretic_Patch PIC_03.jpeg |
11.4 BOOT (Martin OC Config 0.6.8/SIP Enabled) | RESULT | VERBOSE PIC |
---|---|---|
Warm | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Cold (*Regular* Shutdown) | ✅ | |
Warm | ❌ | 11_4 Boot_Test Martin_Config PIC_01.jpeg |
Cold (Forced Shutdown) | ❌ | 11_4 Boot_Test Martin_Config PIC_02.jpeg |
Cold (Forced Shutdown) | ✅ | |
Warm | ❌ | 11_4 Boot_Test Martin_Config PIC_03.jpeg |
Cold (Forced Shutdown) | ❌ | 11_4 Boot_Test Martin_Config PIC_04.jpeg |
Cold (Forced Shutdown) | ❌ | |
11.4 BOOT (Syncretic Patch/SIP Enabled) | RESULT | VERBOSE PIC |
---|---|---|
Warm | ❌ | 11_4 Boot_Test Syncretic_Patch PIC_01.jpeg |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ❌ | 11_4 Boot_Test Syncretic_Patch PIC_02.jpeg |
Cold (Forced Shutdown) | ❌ | 11_4 Boot_Test Syncretic_Patch PIC_03.jpeg |
Cold (Forced Shutdown) | ✅ | |
Warm | ✅ | |
Warm | ❌ | |
Cold (Forced Shutdown) | ✅ | |
One change that makes it crash every time is activating SIP ( search for csr-active-config, change dwgAAA== to AAAAAA== ). Then when I go back to SIP deactivated (the "default" setting of the unaltered config.plist file) 11.3.1 boots reliably again.
First of all why would Apple engineers keep/test very old vintage equipment?Aren't there any Apple engineers that have these systems at home as well, and help with the debugging?
Do an NVRAM reset, has happen to mine before.can’t do anything, recovery mode gets stucked too, BigSur installer too... any clue ?
It seems that with every update, the possibility to get 11.3.x (now it is 11.4) to work on 5,1 CMPs diminishes. I guess, sooner rather than later it will be null. I am not knowledgeable to the point I can ascertain this is a bug but I do not think so; I feel the problems cMPs have with said updates are by design. Hardware has changed a lot in the past ten years and, probably, whatever is inside our cMPs cannot fit in with the "modern crowd". I'd be curious to see Apple's new Mac Pro, the one with apple silicon in, how it will compete with modern threadrippers (64 cores - 128 threads, 128 PCI lines) paired with Nvidia's two or more RTX A6000. We'll see.Second, are you 100 percent sure this "bug" is not by design?
11.4 BOOT (Martin OC Config 0.6.8/SIP Disabled) | RESULT | VERBOSE PIC |
---|---|---|
Cold (*Regular* Shutdown) | ✅ | |
Warm | ❌ | 11_4 Boot_Test Martin_Config SIP_Disabled.jpeg |
Cold (Forced Shutdown) | ✅ | |
Warm | ✅ | |
Warm | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Warm | ✅ | |
Warm | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Warm | ❌ |
11.4 BOOT (Syncretic Patch/SIP Disabled) | RESULT | VERBOSE PIC |
---|---|---|
Cold (*Regular* Shutdown) | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Warm | ❌ | |
Cold (Forced Shutdown) | ❌ | 11_4 Boot_Test Syncretic_Patch SIP_Disabled.jpeg |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ❌ | |
Cold (Forced Shutdown) | ✅ | |
Warm | ❌ |
But the Mac Pro 3,1 has even older hardware and can boot fine.Hardware has changed a lot in the past ten years and, probably, whatever is inside our cMPs cannot fit in with the "modern crowd".
Maybe not by design (because we can verify the code), but convenient for Apple and therefore maintained (especially if it's been reported).I feel the problems cMPs have with said updates are by design.
Maybe this is a rather happy coincidence!But the Mac Pro 3,1 has even older hardware and can boot fine.
Maybe not by design (because we can verify the code), but convenient for Apple and therefore maintained (especially if it's been reported).
I tried but nothing better, I just tested with my old original nvidia radeon, I can start without problem even with Mojave, it’s seems to be a GPU problem, but I´m as stuck as my MP, it use to work well before, something go wrong but I can't figure what, is there a debug mode or boot logs I could check...?Do an NVRAM reset, has happen to mine before.