macOS 11 Big Sur on Unsupported Macs Thread

[sergiodadi]

Hello,

after changing the graphics card on my mid 2011 27 inch iMac and installing Catalina with dosdude1 patch (see here), I tried installing Big Sur on this iMac. There are several "patchers" that allow Big Sur to be installed on unsupported iMacs. I chose to use the micropatcher "patcher".

As Big Sur has just been released, I installed it on a external USB SSD for testing. I will install on my working disk only after 1 or 2 Big Sur updates, it's more careful

Here are the different steps:

1) You need to get the Big Sur installation file. There are different ways to do this, one of the easiest is to run the installation from a Mac supporting Big Sur update, grab the file from the Applications folder and move it to a working directory ( and do not continue with the installation 😉). If you installed Catalina on your mid 2011 27-inch iMac, this method works 😄

2) You must create a USB key with the image and the patches (adapt the commands with your own directory names).

- image creation:

/Volumes/BOOT4T/Users/serge/Documents/Distrib/Apple/Install \ macOS \ Big \ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/name_de_la_clef_USB

- run the first patch command:

./micropatcher.sh

- then launch the command:

./install-setvars.sh

3) You must use the "Catalina Loader OC 0.6.3" (see here) with plist for my Dell WX4130 card, beware version 0.6.2 did not work on my iMac.


4) Reboot on the key, you should see your usual internal drives and 2 other choices: "EFI" and "install macOS Big Sur"





5) You must choose a first boot on "EFI", at this time; the iMac shuts down almost instantly, this is normal.

6) Restart and choose this time "install macOS Big Sur", you must then have the classic screen of an installation:





If you do not have the installation screen, but the no-entry sign, the micropatcher documentation indicates that you have to redo point 5 several times.

I had formatted the disk in APFS but strangely the selection of this disk was not possible, the installer asked for a disk in "Mac OS Extended (Journaled)" !!!!! So I had to stop the installation and reformat the USB drive to "Mac OS Extended (Journaled)". Of course, during the next installation this disk will be converted to APFS.


The installation takes quite a long time, around 2 hours, with several reboots.

7) After a while, you will see a classic configuration screen appear (language, CGU, etc.). After answering these questions, there is still a patch to launch (Ethernet and WIFI are not available elsewhere before this last patch). You must therefore restart on the micropatcher key and then launch a terminal to launch the last patch command which will install kernel extensions:

patch-kexts.sh --2010 "/Volumes/name_of_your_big_disk_on

EDIT 18 november : I make a error , no --2010, the right code is:

patch-kexts.sh "/Volumes/name_of_your_big_disk_on

There is a auto detection of your model and the GPU and you would get all the necessary patches needed for this particular model.

here is the result:








There are some errors but at the end it says "Installed patch kexts successfully". I will try to find out the meaning of these errors anyway. Someone had a idea ?

After a last reboot, we can therefore choose the boot in Big Sur:





The "About" is there





many thanks to @Ausdauersportler, @Barry K. Nathan and others peoples 👍

Description en français ici 🇫🇷

 

[elxeneize]

What is the normal temperature for a Macbook Pro 2012 (9.2)? I have it around 65-80c with Macs Fan control.
Thanks and sorry for my horrible English!

 

[air.man]

Hi Jackluke,
I don't know if this could help.

 

[Ausdauersportler]

Hello,

after changing the graphics card on my mid 2011 27 inch iMac and installing Catalina with dosdude1 patch (see here), I tried installing Big Sur on this iMac. There are several "patchers" that allow Big Sur to be installed on unsupported iMacs. I chose to use the micropatcher "patcher".

7) After a while, you will see a classic configuration screen appear (language, CGU, etc.). After answering these questions, there is still a patch to launch (Ethernet and WIFI are not available elsewhere before this last patch). You must therefore restart on the micropatcher key and then launch a terminal to launch the last patch command which will install kernel extensions:

patch-kexts.sh --2010 "/Volumes/name_of_your_big_disk_on

Description en français ici 🇫🇷

Hi!

This is not the correct way to use the micro patcher as of version 0.5.1 with a GPU modded iMac 2011. Please start the patch-kext.sh -u again to get into the original state and reboot. You can do this from the Terminal app while booted into Big Sur.

Then redo patching without the --2010. There is a auto detection of your model and the GPU and you would get all the necessary patches needed for this particular model. You can do this from the Terminal app while booted into Big Sur, too!

 

[vince22]

What is the normal temperature for a Macbook Pro 2012 (9.2)? I have it around 65-80c with Macs Fan control.
Thanks and sorry for my horrible English!

here's my 2012 MacBook Pro 13" comparison, no Macs Fan control, idle temp and youtube playing temp.

 

[RITAMA]

What is the normal temperature for a Macbook Pro 2012 (9.2)? I have it around 65-80c with Macs Fan control.
Thanks and sorry for my horrible English!

for browsing my mbp9.2 around 51 c

 

[Ron_]

Hi!

I really need some help with those kernel panics.

iMac 2011 with K2100m, clean install Big Sur with Micropatcher 0.5.1.
Wifi is working and brightness also thanks to OC 0.6.2.
I used this command line: /Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh --useOC /Volumes/Macintosh\ HD

Now I'm having kernel panics during the night.

Thank you in advance.

panic(cpu 0 caller 0xffffff80259efa76): Kernel trap at 0xffffff7fc4f10f61, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000001c0, CR3: 0x000000002a4e8000, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0xffffff937cc4dc00, RCX: 0x00000000ffffffef, RDX: 0x0000000000000000
RSP: 0xffffffacb62ebc80, RBP: 0xffffffacb62ebca0, RSI: 0x00000000ffffffef, RDI: 0x0000000000000001
R8: 0x000000000000001d, R9: 0x0000000000989680, R10: 0xffffff80266bbbd0, R11: 0xffffff86c04a8890
R12: 0xffffff937cd9b801, R13: 0xffffff937cc4d000, R14: 0x0000000000000000, R15: 0x0000001ffffffde0
RFL: 0x0000000000010202, RIP: 0xffffff7fc4f10f61, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000001c0, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffffacb62eb6a0 : 0xffffff80258bc66d
0xffffffacb62eb6f0 : 0xffffff80259ff073
0xffffffacb62eb730 : 0xffffff80259ef6aa
0xffffffacb62eb780 : 0xffffff8025861a2f
0xffffffacb62eb7a0 : 0xffffff80258bbf0d
0xffffffacb62eb8c0 : 0xffffff80258bc1f8
0xffffffacb62eb930 : 0xffffff80260bee1a
0xffffffacb62eb9a0 : 0xffffff80259efa76
0xffffffacb62ebb20 : 0xffffff80259ef75d
0xffffffacb62ebb70 : 0xffffff8025861a2f
0xffffffacb62ebb90 : 0xffffff7fc4f10f61
0xffffffacb62ebca0 : 0xffffff7fc4ef4df8
0xffffffacb62ebce0 : 0xffffff7fc4f038d6
0xffffffacb62ebd30 : 0xffffff7fc4ef4057
0xffffffacb62ebd70 : 0xffffff7fc5358d52
0xffffffacb62ebe10 : 0xffffff7fc5358ab0
0xffffffacb62ebe40 : 0xffffff7fc535fb0d
0xffffffacb62ebee0 : 0xffffff80260183f0
0xffffffacb62ebf30 : 0xffffff8026016b5e
0xffffffacb62ebf70 : 0xffffff8026016146
0xffffffacb62ebfa0 : 0xffffff802586113e
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(585.0)[BCCD5611-3116-3255-ADBF-C5521D3B39C6]@0xffffff7fc534d000->0xffffff7fc537bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8028a28000->0xffffff8028a4ffff
com.apple.driver.AppleIntelSNBGraphicsFB(10.0.4)[628D2F1C-66EC-340F-AB0A-576401250CCC]@0xffffff7fc4eee000->0xffffff7fc4f13fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[65A1D60D-F9AF-37E7-B854-4127FBB3172A]@0xffffff80284e5000->0xffffff80284e6fff
dependency: com.apple.iokit.IOGraphicsFamily(585)[BCCD5611-3116-3255-ADBF-C5521D3B39C6]@0xffffff7fc534d000->0xffffff7fc537bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8028a28000->0xffffff8028a4ffff

Process name corresponding to current thread: kernel_task
Boot args: -no_compat_check -amfi_get_out_of_my_way=1 agdpmod=pikera shikigva=80

Mac OS version:
20B29

Kernel version:
Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64
Kernel UUID: 84C6DC45-6B02-335F-9439-5D2A9BC385A4
KernelCache slide: 0x0000000025600000
KernelCache base: 0xffffff8025800000
Kernel slide: 0x0000000025610000
Kernel text base: 0xffffff8025810000
__HIB text base: 0xffffff8025700000
System model name: iMac12,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 10952709771388
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000009f6206016fa
Sleep : 0x000009f441d86d7b 0x00000011f51052b4 0x0000000000000000
Wake : 0x000009f44cdf95c1 0x000000002e49a17d 0x000009f44c004987
last started kext at 10946741744263: >!UAudio 401.4 (addr 0xffffff7fc4ffb000, size 307200)
last stopped kext at 10358947401445: >usb.cdc 5.0.0 (addr 0xffffff8027000000, size 8192)
loaded kexts:
org.hwsensors.driver.GPUSensors 1802
org.hwsensors.driver.CPUSensors 1800
org.netkas.driver.FakeSMC 1800
as.vit9696.WhateverGreen 1.4.3
as.vit9696.Lilu 1.4.8
@filesystems.afpfs 11.3
@nke.asp_tcp 8.2
@filesystems.smbfs 3.4.1
>AudioAUUC 1.70
>!ATopCaseHIDEventDriver 4000.27
>AGPM 119
@filesystems.autofs 3.0
@fileutil 20.036.15
>!AMikeyHIDDriver 131
>!AMikeyDriver 281.52
>!AUpstreamUserClient 3.6.8
@GeForce 16.0.0
>!AGraphicsDevicePolicy 6.1.27
>!A!IHD3000Graphics 10.0.4
@AGDCPluginDisplayMetrics 6.1.27
>!AHDA 281.52
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!ABacklight 180.3
|IO!BSerialManager 8.0.1f5
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!ADiskImages2 1
>!A!IMCEReporter 115
>!ASMCLMU 212
>!ASMCPDRC 1.0.0
>!AThunderboltIP 4.0.3
>!ALPC 3.1
>!AFWOHCI 5.7.4
>!A!ISNBGraphicsFB 10.0.4
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!ISlowAdaptiveClocking 4.0.0
>!AMCCSControl 1.5.9
>!AIR!C 360
>!UCardReader 511.40.9
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.41.1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
|SCSITaskUserClient 436.40.6
@filesystems.apfs 1677.50.1
>AirPort.Atheros40 700.74.5
|!ABCM5701Ethernet 10.3.5
@private.KextAudit 1.0
>!AAHCIPort 346
>!ARTC 2.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
>!UAudio 401.4
>usb.cdc 5.0.0
$SecureRemotePassword 1.0
>!AHIDKeyboard 222
>!AMultitouchDriver 4400.28
>!AInputDeviceSupport 4400.35
>!AHS!BDriver 4000.27
>IO!BHIDDriver 8.0.1f5
@kext.triggers 1.0
@nvidia.driver.NVDAGK100Hal 16.0.0
@nvidia.driver.NVDAResman 16.0.0
|IOAccelerator!F2 439.35.4
>!AGraphicsControl 6.1.27
>DspFuncLib 281.52
@kext.OSvKernDSPLib 529
>!ABacklightExpert 1.1.0
|IONDRVSupport 585
>!ASMBusPCI 1.0.14d1
|IOSerial!F 11
|IOAVB!F 900.12
>!AHDA!C 281.52
|IOHDA!F 281.52
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
@plugin.IOgPTPPlugin 900.11
@!AGPUWrangler 6.1.27
@!AGraphicsDeviceControl 6.1.27
|IOFireWire!F 4.8.3
>IOPlatformPluginLegacy 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
>!AThunderboltEDMSink 5.0.3
|IOGraphics!F 585
>!ASMBus!C 1.0.18d1
|Broadcom!BHost!CUSBTransport 8.0.1f5
|IO!BHost!CUSBTransport 8.0.1f5
|IO!BHost!CTransport 8.0.1f5
>usb.IOUSBHostHIDDevice 1.2
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!AThunderboltDPOutAdapter 8.1.4
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!ABSDKextStarter 3
|IOSurface 289.3
|IOSkywalk!F 1
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 436.40.6
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
|IOAHCISerialATAPI 268
|IOAHCIBlock!S 332
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
|IO80211!F 1200.12.2
>corecapture 1.0.4
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IOEthernetAVB!C 1.1.0
>mDNSOffloadUserClient 1.0.1b8
|IOAHCI!F 294
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.1f5
|IOReport!F 47
|IO!BPacketLogger 8.0.1f5
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.40.9
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1

 

[jowaju]

Any ideas on what to do when Big Sur won't make a sealed volume? I have re-installed Big Sur a half dozen times in different configurations and every time diskutil shows a broken seal. This is on a SUPPORTED Late 2013 MBP 13". Everything is stock 16GB 500SSD, BootRom was successfully updated during the upgrade. I've tried internal and external drives, upgrading from Mojave and Catalina from within the OS, doing a clean install via the USB with no patches. I've tried downloading the Setup package manually and also letting Software Update do it. Cleared the PRAM and reset the SMC just in case. Verified SIP is enabled. I'm at a loss.

 

[TA 455SD]

Is there any link for new InstallPackage 11.1 beta version?

I suspect that Apple just wanted to get a retail version of Big Sur out there because of the holiday season and they want to sell new macs , so by having the new OS out they can sell more for the holidays , since they were having a new beta version come out every couple weeks before ver 11 came out , I bet they will continue that path for a couple months yet

 

[Ausdauersportler]

Hi!

I really need some help with those kernel panics.

iMac 2011 with K2100m, clean install Big Sur with Micropatcher 0.5.1.
Wifi is working and brightness also thanks to OC 0.6.2.
I used this command line: /Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh --useOC /Volumes/Macintosh\ HD

Now I'm having kernel panics during the night.

Thank you in advance.



Process name corresponding to current thread: kernel_task
Boot args: -no_compat_check -amfi_get_out_of_my_way=1 agdpmod=pikera shikigva=80

Mac OS version:
20B29

You are simply using the wrong config.plist on your OC - rename the NVIDIA version. Using the AMD version you are spoofing the iMacPro1,1 ID and sleep fails. Move of the 0.6.3 and rename the file. Read the post I made about this.

I wonder how you got it working before with Catalina ....

P.S.: Next time put the panic.log into SPOILER Tags...

 

[sergiodadi]

Hi!

This is not the correct way to use the micro patcher as of version 0.5.1 with a GPU modded iMac 2011. Please start the patch-kext.sh -u again to get into the original state and reboot. You can do this from the Terminal app while booted into Big Sur.

Then redo patching without the --2010. There is a auto detection of your model and the GPU and you would get all the necessary patches needed for this particular model. You can do this from the Terminal app while booted into Big Sur, too!

I understand my error I have read on the readme of micropatcher "If you're going to use the installation on a 2010 or older Mac ..." , my mind (French) thought otherwise, you are right Imac 2011 is not OLDER . Thank, i do what you say 👍

 

[Ausdauersportler]

I understand my error I have read on the readme of micropatcher "If you're going to use the installation on a 2010 or older Mac ..." , my mind (French) thought otherwise, you are right Imac 2011 is not OLDER . Thank, i do what you say 👍

Everything is ok, but please ignore the flags like --2010 and --2011 - it is just a vehicle for system currently not detected automatically ....

You iMac needs special patches with will be only installed if you do not overrule the patcher. Let it simply doing it's work ... we hope to deliver a *complete* working system auto detection and patch selection in near future. At least for the iMac 2009 to 2011 having a new Metal GPU this should work right now...

 

[elxeneize]

Thank you very much for the answers! I have these temperatures browsing the web and playing Youtube. Sometimes even higher. I don't see it very normal. Install Big Sur with Patched Sur app. What I can do? Thank you!

 

[Ron_]

You are simply using the wrong config.plist on your OC - rename the NVIDIA version. Using the AMD version you are spoofing the iMacPro1,1 ID and sleep fails. Move of the 0.6.3 and rename the file. Read the post I made about this.

I wonder how you got it working before with Catalina ....

P.S.: Next time put the panic.log into SPOILER Tags...

Thanks for your help.

I followed your instructions and will keep you posted.

 

[BigSURfur]

Is my issue to do with this? - with b10 I can't delete the remaining snapshot from Recovery. Even with the BS System volume mounted and R/W, I get 'Error -69863: Insufficient privileges'. I've managed to delete all snapshots manually up to/incl b9.

After I updated b9 to b10, the usual 'com.apple.update...' sort of snapshot was listed - but with 'Purgeable: No' this time around. I added a newer snapshot and zapped the Apple one with Barry's script. The remaining one I added stated 'Purgeable: Yes' but it still just won't delete.

Any thoughts anyone?

EDIT: I just reapplied the full Beta10 Installer over the injected-into-b9 delta b10 update and I 'can' now delete the initial update snapshot from recovery, leaving none (even though it was flagged as 'Purgeable: No').

It's probably easiest to boot into Recovery mode using a USB installer stick, if getting to the BS one doesn't work with Cmd+R (mine never works because I've got 5 OS's installed, so maybe the mac boot screen firmware has a meltdown knowing which one to select!).

I still get the 'Error: -69863: Insufficient privileges' message while trying to delete snapshots. I can delete all but the most recent one - which always gives the error message on my cMP 2010.

I've ended up living with snapshot booting and with not being able to mount the BS System volume in BS. If I need to swap over or add a file to any BS system folders, I do it in Mojave, then boot into Recovery, mount the BS System volume as read-write and run (NB. change 11.0 to whatever your BS is called):
kmutil install --volume-root /Volumes/11.0 --update-all --force
/Volumes/11.0/usr/sbin/kcditto
bless --folder /Volumes/11.0/System/Library/CoreServices --bootefi --create-snapshot
reboot

The above commands seem to update the BS PreBoot volume and kext collections with the chances made in Mojave and start BS off from a fresh snapshot including the changes. The '--force' is recognised as a more-or-less deprecated command but I've found that my Mojave changes don't stick unless I keep typing this in.

Unfortunately, living with it is not an option for me. I’m trying to install BigSur on a RAID 0 using a workaround I discovered but it needs all the snapshots from the image to be GONE. “Bless” and “OS Update”, they need to go. If I can manage to delete both of em, then I can install BigSur on a RAID 0, which I know for a fact that no one has done yet.

 

[BigSURfur]

Is my issue to do with this? - with b10 I can't delete the remaining snapshot from Recovery. Even with the BS System volume mounted and R/W, I get 'Error -69863: Insufficient privileges'. I've managed to delete all snapshots manually up to/incl b9.

After I updated b9 to b10, the usual 'com.apple.update...' sort of snapshot was listed - but with 'Purgeable: No' this time around. I added a newer snapshot and zapped the Apple one with Barry's script. The remaining one I added stated 'Purgeable: Yes' but it still just won't delete.

Any thoughts anyone?

EDIT: I just reapplied the full Beta10 Installer over the injected-into-b9 delta b10 update and I 'can' now delete the initial update snapshot from recovery, leaving none (even though it was flagged as 'Purgeable: No').

Also, didn’t you say here “I 'can' now delete the initial update snapshot from recovery, leaving none.” So did u get an error or something?

 

[Pinarek]

Has anyone got the new update 11.1 with the running BigSur Final on an unsupported iMac? Or are the updates generally not coming? There is no full installer for the betas (not all).

 

[TA 455SD]

Has anyone got the new update 11.1 with the running BigSur Final on an unsupported iMac? Or are the updates generally not coming? There is no full installer for the betas (not all).

If you can find the installer pkg link for 11.1 , you might try using barrykn micropatcher to see if that works , it may be a few days before that link becomes available unless someone who has a supported mac posts a link to be available for everyone

 

[Stuessi]

Try https://www.mariogt.com/space-saver.html to delete your TM snapshots

That did the trick, thank you!

 

[tinyvee]

Hi All,

Many thanks for all the useful posts and work done for the unsupported macs.

Apologies if its a stupid question
I have managed to install big sur on my late 2012 MBP pro but i am unable to find the "post install" app on my machine or the hard drive i used to install the OS. where can i find it?

What patcher did you use? And what instructions did you follow?

 

[Ausdauersportler]

My imac display crashed suddenly after going though all the good things . Suddenly the screen flickered, then starting black and white, then got horizontal lines and then no movement nothing.

Edited.
After few hours same issue. I think my display card or the display itself is causing issue. damn.

Okay, this is surely no Big Sur issue. Try to do a PRAM reset, sometimes this helps with a changed GPU. Although I assume you have more likely a dying GPU. You should pay a visit to this thread, there are some more options available right now and event card offering native brightness unlike your 765M.

After PRAM reset boot into the EFI of your USB installer stick to set the correct values to avoid the stop sign....

 

[Bmju]

What is the normal temperature for a Macbook Pro 2012 (9.2)? I have it around 65-80c with Macs Fan control.
Thanks and sorry for my horrible English!

I've got a MacBoo Pro Late 2012 10,2. Those temperatures are normal.

 

[Alex-Microsmeta]

Carbon Copy Cloner 5.1.23 should FINALY make bootable clones of Big Sur! Download 5.1.22 then check beta updates.
Just trying to clone @jackluke patched BigSur SSD 11.0.1 (20B29) on internal iMac 2013 hard disk

Yes, you can have bootable backups on macOS Big Sur | Carbon Copy Cloner | Bombich Software

bombich.com

EDIT: Working! Done in less than 30 minutes (123 GB)

 

[borp99]

Also, didn’t you say here “I 'can' now delete the initial update snapshot from recovery, leaving none.” So did u get an error or something?

My post #6683 yesterday is more recent than the one you keep quoting. For the latest BS 11.0.1 release, I still get the ‘insufficient privileges’ error while trying to delete the initial snapshot. I do swap out an Assets.car file in Mojave and then rebuild the bindings in Recovery, plus creating a new snapshot. However, although I can delete the initial snapshot once there’s a later second one, trying to delete the second one (simply to see if it can be done) still gives the ultimate error message.

 

[borp99]

Carbon Copy Cloner 5.1.23 should FINALY make bootable clones of Big Sur! Download 5.1.22 then check beta updates.
Just trying to clone @jackluke patched BigSur SSD 11.0.1 (20B29) on internal iMac 2013 hard disk

Yes, you can have bootable backups on macOS Big Sur | Carbon Copy Cloner | Bombich Software

bombich.com

I tried out the CCC 5.1.23beta yesterday and the 11.0.1 clone backup drive booted up just fine on its own. The method Bombich is implementing is that the destination drive has to be fully erased by CCC first, so backups (so far) can’t be incremental ones, just full ones.