Yes, I intend to do that the next time there's a significant version increment.
The sys.log implies some interesting theories, but my language deciphering skills are poor. There may be a ghost system folder - lines like "objc: Class LPPartitionMedia is implemented in both /path_a/ and...
It only requests the one reboot, and no, there's no progress bar under Apple logo.
"Install Now" >> "Downloading 2.43 GB" >> "Preparing MacOS Big Sur (about 15 minutes remaining)" >> "Restart" >> when it reboots, there is no "Mac Installer" image, nor does the update progress appear beneath the...
No luck, it does the same thing. Still at 11.2 ~ I even took the precaution of disconnecting all but my boot drive so as to reduce installer confusion.
Since the upgrade to 11.2 worked fine - and the changes between 11.2 and 11.2.1 seem minor - I may just give this update a pass, and try with...
The update partition doesn't show up when it reboots for the 11.2.1 update, unlike what happened in the 11.1 > 11.2 situation. I just get the "Macintosh HD" "Repair" and "Reset NVRAM" options onscreen.
Is there something I can do to force it?
It doesn't actually stop. The installer does its thing, downloads the update, then reboots back up in 11.2, and the Software Update still says "an update is available..."
I can post a text file of the system.log, if that helps?
TOTAL SUCCESS!! The updated EFI from Post #11352 did the trick, whatever it was! And I built a new Big Sur installer from scratch, as well.
So my steps:
1) I retained the system ID as iMacPro1,1
2) Added the boot argument for pikera (in /NVRAM/3rd UUID/boot_arg)
3) Populated serials for system...
Success: After pulling all 3 HDDs from the system and plugging in a fresh blank SATA drive, I was able to do a straight install using Clover5128/BigSur11.1, using iMacPro1,1 definition.
OpenCore still doesn’t work with this setup, fyi.
====== UPDATED ======
Thanks much for this!!
I was able to progress a bit further.
As of now, the iGPU is working, and the Big Sur installer has launched off a Clover5128 installer stick!
I can’t get OC965 or 066 to work at all right now.
Using Clover5128, I was able to get installing MacOS...
OK! I added the "agdpmod=pikera" line (both on Clover5128 as well as OC065) - no luck, the panics are happening in the same place. Can't imagine what the issue might be.
Would it help to take a look at my working Clover4918 config.plist (attached with post #11284) just in case there's some...
Pretty sure the installer disk is not at fault here, as I am able to boot into the Big Sur Installer if I startup using the current working Clover4918 EFI folder, even when it's on the USB. Am I right?
Is it worth risking installing Big Sur using the Clover4918 EFI?
Alternatively - wondering...
I DO have the MSI Radeon RX5500 XT installed - but under my Mojave 10.4.4 it was not being used for Mac, only for Windows boot (possibly the reason why we added back the inject_intel in the current working 2019 install?).... t/fore I have been using the HDMI output off the motherboard to power...
No, no intel_inject.
Re-examining my tools and progress:
- Since the past couple days I have run through nearly all combinations of OC065 and Clover5128 - varying system IDs between iMac18,1, iMac18,3, iMac19,2, and iMacPro1,1 - in combination with old AND new serials. Yet I'm not able to get...
As of now - I have a functional 10.4.4 OS with Clover 4918.
My notes show that the following changes were made:
- manual intel inject
- bypass Radeon inject
- using system iD 19,1 in this setup causes the system to go unstable.
My working Config.plist pages are modified as follows:
Also - I haven't changed the Serial No or Board Serial, etc., as I don't know for sure whether I need to change it from the existing iMac18,1 system description, which works fine. The documentation on OpenCore states to use iMac19,1 instead as that is the standard for Coffee Lake processors such...
Booting macOS recovery:
1) existing clover 4918 works fine
2) clover 5128 ends in a panic - I took 2 pics while the text was scrolling, pls see attached
3) OpenClover - did not allow recovery to launch (big "no entry" icon on screen)
This system has 3 HDDs
1) win boot - 120GB MBR-formatted, Windows with Win10 installed (disk3, KingstonSA400S37120G)
2) 500GB GUID (contains working Mojave 10.4.4 partition on APFS partition) (disk0, Samsung 970 EVO)
3) 2TB contents drive - data mostly relating to the Win boot (disk2, Samsung...