Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I have the Problem that my system is ultra slow. ve a late 2013 iMac with a Fusiondrive. At the Beginning, that system on the early Betas of Big Sur wasn't that slow. But now it is
Read the first post carefully. imac 2013 does not have metal card and acceleration. So your GPU will be slow and machine will be effected.
 
Hi,
I am using PatcherSur patcher on my Macbook pro mid 2012. When I am trying to boot the macos via USB key its taking me to mac os recovery, where it is asking me for user password and when I am entering the password, it is not accepting that password (with correct password). Can anyone help?
This is a FileVault issue. Go back into you regular install, check to see if its turned on. If it is you have two options; 1. Turn it off, and attempt the update again. Or option 2, and what you'll most likely have to do; Do a time machine backup of your current install, then completely wipe the drive, and do a fresh install of 11.1. It has been a reoccurring problem with the patchers and Big Sur in general, it doesn't seem to jive with FileVault
 
Yeah that often has issues. Use BenSova's Patched Sur.
BenSova's patcher is useless in that case, this Mr-nice-guy tryed to repeat my install (yes i that "some german guy"), thats i shared in youtube, micropatcher don't up wifi, but crash audio. And i not seen any reason to waste time in that useless case with no graphics acceleration. It's only for install the system and looking at it works.
 
Read the first post carefully. imac 2013 does not have metal card and acceleration. So your GPU will be slow and machine will be effected.
The iMac 2012 and later all have a Metal GPU included. The systems are perfectly capable of running Big Sur. But disable the Fusion drive, use the small SDD for the MacOS, the HDD for your data...
 
Hi,
Just got my first "Your computer has detected a potential problem" and the Show Report links to eficheck.dump.

I checked my NVRAM settings on Terminal with:
nvram -p | grep "run-efi-updater"
And got this:
run-efi-updater No%00
So, perhaps it is no longer working with the combination of OpenCore 0.6.3 and Big Sur 11.1 (20C69)?

View attachment 1695978
Move over to 0.6.4 immediately. I pulled all Big Sur config files from the 0.6.3 version available on the GPU thread.
 
  • Like
Reactions: macinfo
The iMac 2012 and later all have a Metal GPU included. The systems are perfectly capable of running Big Sur. But disable the Fusion drive, use the small SDD for the MacOS, the HDD for your data...
I read some users conclusion doing the split. Performance is nearly the same for these drives once you ran the ssd separately.

 
Is there any way of running shell scripts with an in-app log in objective-c?
(Objective)-C knows (and every other programming language, too) the system call making it possible to run every possible executable as on the command line, of course you can catch stdout and stderr. Do not know the best most recent solution, stopped programming objective-c 20 years ago.
 
Last edited:
  • Like
Reactions: MacHacJac
Could you do me a favor and run blackmagic speedtest for this setup?
Find bellow the print screen after running the test. It was Write 483 mb/s and read 518mb/s.
 

Attachments

  • DiskSpeedTest.png
    DiskSpeedTest.png
    223.4 KB · Views: 97
  • Like
Reactions: amaze1499
Was curious if anyone encounters unresponsive network (either wifi or hardwire) on "unsupported" Macs running BS 11.1, mine specifically being mid-2012 rMBP with the original wifi card. A reboot easily fixes this issue, however annoying each time. I've seen it occur after some sleep or taxing traffic but not consistently.
 
Was curious if anyone encounters unresponsive network (either wifi or hardwire) on "unsupported" Macs running BS 11.1, mine specifically being mid-2012 rMBP with the original wifi card. A reboot easily fixes this issue, however annoying each time. I've seen it occur after some sleep or taxing traffic but not consistently.
Same computer as me and (originally) the same wifi card.
I didn't get any actual dropouts of wifi but occasionally something I click on would sort of freeze and either take a while to load or end up at a Safari could not find........ notice.
A quick refresh would re-connect without issue.
I also changed from 5GHz band to 2.4GHz band and it stopped.
But now I have the upgraded wifi card in and it hasn't happened since.
 
  • Like
Reactions: cab_007
However, I WOULD prefer to run complete shell scripts, rather than just commands. Anything for that?
 
Installed 11.1 (20C69) on MBP5,2, on external USB ssd.
Refrained from OTA installation once more, but used full installer obtained via MDS.

Prepared khronokernel's USB OpenCore Legacy Patcher 0.0.3 (page 1 option 4). **
Updated existing USB BS installer made with jackluke's BigSurFixes (page 1 option 3), using the BigSurSharedSupportfix.command with 11.1 installer app in /Applications.

Then using this installer in two ways. In both cases starting stage1 from USB BS installer.
- 1st way: continuing stage2 and stage3 from USB BS installers's Utilities pulldown menu, applying Legacy USB and graphics framebuffer fixes, omitting Frameworks fix (nightshift) this time. Booting via Apple boot selector.
- 2nd way: continuing by booting macOS installer (at start of stage2) via OC-L-P and not applying patches to disk. Booting via OC-L-P.
In both cases installed over 11.1 beta2. In both cases boots fine into setup of BS 11.1.

** In the OC case, I first tried version 0.0.7 but got an error message and reboot soon after starting stage2, related to SerialATAPI reconfiguration (picture). Tried again with 0.0.3 without problems.

Thanks to jackluke and khronokernel.
For OC Legacy Patcher, also tried the other versions between 0.0.3 and 0.0.7 for completeness. In summary
- 0.0.4-0.0.7 all show the SerialATAPI message a few (3-4) times and then fail
- 0.0.3 works.
When looking at the protocol of the OC build process, 0.0.4 (and higher), as compared to 0.0.3, use in addition legacy IOHIDFamily Patch, VoodoHDA v296, and dual GPU patch (and leave out OpenCanopy GUI).

This is just for reporting, if of interest to @khronokernel . I can well live with 0.0.3, thanks!
 

Attachments

  • build OC-L-P 004.png
    build OC-L-P 004.png
    45 KB · Views: 99
  • build OC-L-P 003.png
    build OC-L-P 003.png
    45.1 KB · Views: 102
  • Like
Reactions: macinfo
Same computer as me and (originally) the same wifi card.
I didn't get any actual dropouts of wifi but occasionally something I click on would sort of freeze and either take a while to load or end up at a Safari could not find........ notice.
A quick refresh would re-connect without issue.
I also changed from 5GHz band to 2.4GHz band and it stopped.
But now I have the upgraded wifi card in and it hasn't happened since.
Do you know the replacement part number (upgraded) I can use on mine?
rMBP (Mid 2012) 10,1
 
Yes. It's not that difficult a job except for the 3 very small aerial connectors on the card.
The ac compatible card is
Broadcom 94360CSAX although some seem to be marked 94360CS on one side and sometimes CSAX on the other.
Mine was thirty odd quid. There are cheaper ones but could be copies - not sure.
 
Last edited:
  • Like
Reactions: cab_007
Yes. It's not that difficult a job except for the 3 very small connectors on the card.
The ac compatible card is
Broadcom 94360CSAX although some seem to be marked 94360CS on one side and sometimes CSAX on the other.
Mine was thirty odd quid. There are cheaper ones but could be copies - not sure.
Is that the A1389 part number or something else, I'm seeing various form factors and don't want to buy the wrong size/factor.

Really appreciate the info - HUGE Thank you!!!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.