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.
For enabling Wifi 802.11n on any 2012 Mac or any other unsupported Big Sur but supported Catalina Mac (in few words those who use the AirPortBrcm4360 driver), this will work:

To install it properly, simply open a BigSur terminal and copy paste (one line at once) :
Code:
sudo mount -uw / ; killall Finder

cd /System/Library/Extensions/

sudo mv IO80211Family.kext IO80211Family.backup

open /System/Library/Extensions/

copy using Finder the IO80211Family.kext from the link attached

return to BigSur terminal and continue typing:

sudo -s

chown -R 0:0 /System/Library/Extensions/

chmod -R 755 /System/Library/Extensions/

kmutil install --update-all

kcditto

At next reboot you should have a working Wifi 802.11n and a working AirDrop channel.
Will this work on a Mac mini mid 2011 or do I need to get myself a combo USB dongle
 
Got BS 11.3.1 installed on a 17" MBP 8,3 Core i7, -AMD HD6770M/intel HD 3000 using the micropatcher..... EVERYTHING works great except I can not adjust screen brightness.... Is there a fix for this?
Please, sir, would you be so kind to send me the EFI folder you have in the EFI partition? I have the same mac.

Thank you
 
Just updated OC using OCLP 0.1.2 and I was slightly confused by the new default settings. Why are the Acceleration Patches enabled by default on a MacPro5,1 with a Metal GPU (5700 XT)? I turned them off since they shouldn't apply to my machine and I'm running Big Sur, but I'm wondering if this might trip up other people if they don't modify the defaults.

Also, should I change setting #4 or just let it detect my GPU?

Screen Shot 2021-05-09 at 10.21.47 PM.png
 
Will this work on a Mac mini mid 2011 or do I need to get myself a combo USB dongle
Making the root system volume writable changed, you can either search through this thread to understand the complete development or just go to the first post, search the micropatcher download link on GutHub and read the docs (very last chapter).

You should try OCLP with your Mac mini and check things first before changing things yourself manually and end up in an completely unsupported unsupported configuration :) There might be even graphics acceleration patches available for the HD3000, again, go to the first post and check download link of OCLP and the docs on this GitHub page.
 
  • Like
Reactions: CAPS369 and Dilli
Please, sir, would you be so kind to send me the EFI folder you have in the EFI partition? I have the same mac.

Thank you
You can easily generate these EFI folders yourself using the OCLP app either directly on the target system (it will detect the hardware) or by setting the model manually when using the app on a different machine.
 
You can easily generate these EFI folders yourself using the OCLP app either directly on the target system (it will detect the hardware) or by setting the model manually when using the app on a different machine.
Thank you sir. Can I do it from High Sierra? It´s the latest macOs supported in my Macbook Pro.
 
Thank you sir. Can I do it from High Sierra? It´s the latest macOs supported in my Macbook Pro.
It is working on my iMacs supported from Apple with High Sierra. The OCLP app depends only on a recent Python stack which can be installed using brew or similar UNIX package management tools on even older macOS versions.
 
No luck. Thu installert USB always says "this versión can´t be installed…"
What version of macOS do you want to install and did you read the docs linked on the GitHub pages. This error message is explained there....
(and you need no luck when it comes to install and use software :) )
 
Last edited:
T
Making the root system volume writable changed, you can either search through this thread to understand the complete development or just go to the first post, search the micropatcher download link on GutHub and read the docs (very last chapter).

You should try OCLP with your Mac mini and check things first before changing things yourself manually and end up in an completely unsupported unsupported configuration :) There might be even graphics acceleration patches available for the HD3000, again, go to the first post and check download link of OCLP and the docs on this GitHub page.
Thanks so so much … ill look at the first post and I’ve tried Big Mac patcher and opencore fixed the graphics… cheers
 
I’ve used OLCP 0.1.1 to install Big Sur 11.2.3 on my trusty MacBookPro4,1 (early 2008) main internal SSD.

It’s running quite nicely so far, the one thing missing is, that my second internal drive (SATA HDD in PATA adapter enclosure), which replaced the internal DVD drive, does not mount.

Probably this might be fixed in the current OCLP 0.1.2 beta, as I’ve read someting about IDE fixes, or does this relate only to certain machines?!
What about wifi issue. No problem?
 
I have tried, unsuccessfully. I admit that due to my low qualifications

Hi, this dialog touches on a point where unsupported macs config is crossing over with hackintosh config....

(tl;dr jump towards end)

I've been coming at the forums as resources from both perspectives, so this caught my eye. Esp, wrt OpenCore which in my view is becoming the defacto framework for applying patches. For hackintosh there's potentially interesting work going on to build an automator for OpenCore config that will allow users to organize golden configs. It's too soon to tell how this will go, but you could have a point of view where Apple Macs are themselves regarded as golden builds, in terms of OC config mgmt.

The key is OpenCore layout of EFI folder. And it's also in the amazing resource of the Dortania OpenCore Guide, which I suggest everyone here can benefit from at least an awareness. But I mention this just as an aside.

In this case of troubleshooting the external black-screen, this is a common problem with hackintosh config, trying to get various combos of on-board intel vs discreet AMD / Nvidia graphics to work, including VDA (Intel Quicksync) to work for efficient graphics.

The agpmod=vit9696 patch suggestion is one of several Whatevergreen.kext (graphics patch manager) options for overriding board-ids so macOS doesn't punt on graphics output on unsupported configs.

OK, so given the above context as a bacground, I'll get to your issue at hand, switching to OCLP and lost graphics output:

When you write you were "unsuccessful" fo you mean unsuccessful in the sense that the suggestion to add the agpmod=vit9696 device property didn't help your setup? Or in the sense that you weren't able to add the option because of unfamiliarity with applying OC patches?

I'll assume the latter, just to avoid an exchange and because maybe the details will be useful to others playing with OCLP. Here, due to the way you are applying patches, you may have a case where your point of view on unsupported Mac config might as well be POV of troubleshooting a hackintosh based on OpenCore.

tl;dr:

The agpmod=vit9696 patch referenced by @Ausdauersportler was provided in the context of OpenCore config.plist option to Whatevergreen.kext, either by adding a boot-arg, or adding a DeviceProperty for the graphics ACPI device node (my jargon might be a little goofy here 'cause various vernaculars are getting smashed together: OC, ACPI, Windows, etc).

So to add the patch option, you will edit your OCLP EFI config.plist and add the option on of these two ways. Typically the boot-arg option is used when trouble-shooting, and the DeviceProperties option is used to cement working config. Boot args can be applied in the EFI shell to speed trouble-shooting, but there may sometimes implications with NVRAM persistence, so the shell is for the canny troubleshooter — with great power comes great responsibility, something something stan lee / peter parker.

So if you want to learn more about this, the Dortania OpenCore Guide is the place to go. Just search the googlez.

P. S.

IMO the strengths of the OC approach should have a lasting positive effect on approaching config for "unsupported macs", which means that looking at it from hackintosh perspective will be time well-spent. The cool aspect of OC is that it demystifies UEFI, and what you learn can in the long run cross over better understanding of Linux and Windows too.

So you are on a good path by playing with OCLP.
 
This is the Big Sur thread :) You need the moderate spoofing enabled as mentioned on my post on the Catalina thread and within the OCLP docs. Let us move the Catalina related discussion over to the other thread. It will only confuse the readers here.

I think i have understood the question. OCLP can only be run on Catalina and above but OCLP generated EFI can be use from HS onward :) So one need at least a modern system to create the files that will help upgrade the older one.
 
Many users trying hard to upgrade to 11.3.1 but my 11.3 is working just fine. There is some issues with bluetooth and airdrop but this issues are the story of my life with macOS so I'm not considering. Is there a strong reason to upgrade to 11.3.1?
 
Keyboard Backlight is unlikely to be fixed anytime soon, however apps like LabTick will allow for a menubar approach to controlling the keyboard backlight
Thank you for your help. I know this team will manage these problems, I can wait, it is the first time Big Sur runs so smooth on my mbp
 
This is the Big Sur thread :) You need the moderate spoofing enabled as mentioned on my post on the Catalina thread and within the OCLP docs. Let us move the Catalina related discussion over to the other thread. It will only confuse the readers here.
So sorry. You are so right.
 
Hi Everyone
I have an issue trying to run this code
Code:
sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume/
Password:
dyld: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD
  Referenced from: /Applications/Install macOS Big Sur.app/Contents/Resources/createinstallmedia
  Reason: no suitable image found.  Did find:
    /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x10AF65000, size=0x00008000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD
    /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x10AF80000, size=0x00008000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD

$ sysctl -n hw.model
MacBookPro8,1

MacBook Pro (13-inch, Late 2011)
2,8 GHz Intel Core i7
4 GB 1333 MHz DDR3
 
No idea why anyone would want to install Big Sur on unsupported machines, other than for the cool technical aspect of it. It runs terribly on my officially supported Early 2015 MBP and I ended up downgrading back to Catalina.
 
  • Haha
Reactions: Larsvonhier
No idea why anyone would want to install Big Sur on unsupported machines, other than for the cool technical aspect of it. It runs terribly on my officially supported Early 2015 MBP and I ended up downgrading back to Catalina.
I'm not going to use that partition everyday.I have mint Linux on the other partition.I need to compile a software for my Iphone under XCode every week.
 
Hi Everyone
I have an issue trying to run this code
Code:
sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume/
Password:
dyld: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD
  Referenced from: /Applications/Install macOS Big Sur.app/Contents/Resources/createinstallmedia
  Reason: no suitable image found.  Did find:
    /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x10AF65000, size=0x00008000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD
    /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x10AF80000, size=0x00008000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Big Sur.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD

$ sysctl -n hw.model
MacBookPro8,1

MacBook Pro (13-inch, Late 2011)
2,8 GHz Intel Core i7
4 GB 1333 MHz DDR3
You are better suited trying OCLP right now. The main developer of the micropatcher went away more than six month ago and I stopped developing on my fork.

OLCP includes even HD3000 graphics acceleration right now. Check the docs ... and the first post.
 
  • Like
Reactions: Whynot2018
No idea why anyone would want to install Big Sur on unsupported machines, other than for the cool technical aspect of it. It runs terribly on my officially supported Early 2015 MBP and I ended up downgrading back to Catalina.

Plenty of quad-core Haswell iMacs with discrete graphics that run Big Sur very well. It runs at least as well as Catalina.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.