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.
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!!!
Mine is a A1398 but you don't want one from that because it's the same as the one you've got.
I believe the upgraded one is from a A1502, with ac compatibility. Then you don't need to run patch-kexts.
 
Last edited:
  • Like
Reactions: cab_007
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!
You should open an issue on the GitHub site. I cannot imagine that @khronokernel will follow all the posts here. He wrote in his announcement something like this.
 
  • Like
Reactions: hvds
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
  • Like
Reactions: cab_007
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
Well.... as a good studen I followed this very advice.
now I have a nice metal mid21 brick that is stuck in system setup loop...))
Installation starts, but at some point gets interrupted. Tried like 5 times with different variations.(((( sooooo time consuming....
used micropatcher....
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
While you are on big sur desktop. connect your usb installer and open it. Open Terminal window and drag patch.kexts.sh to the terminal window. Press enter and let it do its thing and when you see last line in terminal window as successful, restart your machine. You will get wifi etc.
Thank you my friend, but when i execute the patch-kexts.sh on my terminal, the script can't complete. there is this error that i attach. I Hope that you can help me! THANK YOU!!
 

Attachments

  • Immagine JPEG.jpeg
    Immagine JPEG.jpeg
    711.9 KB · Views: 104
While I understand this will avoid future wifi kext-patch, would I need to reinstall BS 11.1 once I swap the wifi card or will the current install of BS 11.1 work without having to reinstall?
I didn't do it that way myself but I would think it would be good as it is. Yes no need for patch-kexts in the next install :)
See private message 👍
 
  • Like
Reactions: cab_007
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 here with late 2013 iMac. Ethernet just stops working. 11.0 was rock solid, .1 is little more buggy.
 
  • Like
Reactions: OKonnel
Well.... as a good studen I followed this very advice.
now I have a nice metal mid21 brick that is stuck in system setup loop...))
Installation starts, but at some point gets interrupted. Tried like 5 times with different variations.(((( sooooo time consuming....
used micropatcher....
Not sure what you're trying to say, or if your implication is that my advice somehow bricked your machine... But regardless, your system is not bricked. Without seeing exactly what you've done, because you've provided no information, you simply made an error somewhere down the line. I assume you made a backup of all important data, as you shouldn't be messing with this if you're not willing to fail or lose that data. That being said, assuming you have that backup. Wipe the drive and install again using a properly patched usb drive.
 
Last edited:
  • Like
Reactions: OKonnel
This is the form factor you want. No sticking up aerials or cutout on one corner
https://www.amazon.com/Broadcom-Bcm94360cs-Bcm94360csax-Bluetooth-Wireless/dp/B00PDN4H9E
And it's from an A1502 maybe not A1425 then :)
Just to be sure, here's the Amazon part that works. As it says, this 802.11ac card fits A1398 and A1502 MBP's.

Also, not to disagree with Quackers, but I'd reinstall a fresh 11.1 (20C69) with a new patched USB without the wifi kext. It also means you can run the -e option with the install-setvars.sh command since you don't need to disable SIP, etc.
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Can you find an example of both? Honestly I was thinking about both but can't think of which one would be more convenient.
There is no difference. These interfaces open a sub shell and run the command you entered there. A command can be some normal system command as well as a self written script. A lot of these unix commands you know may be scripts.

May be I do not understand want you intend to do: But I guess you want to call the patch-kext.sh downloaded to some place in the filesystem and run it from there and gather the output (this is what you normally see on the screen in a terminal is in the unix semantics it is just another predefined file descriptor called stdout, another is stderr).

I guess you should use the one bigger search engine or the most recent Apples objective-c docs. There you will find hundreds of code examples...

Try a search like "running a unix shell script from an apple objective c program" :)
 
Last edited:
Not sure what you're trying to say, or if your implication is that my advice somehow bricked your machine... But regardless, your system is not bricked. Without seeing exactly what you've done, because you've provided no information, you simply made an error somewhere down the line. I assume you made a backup of all important data, as you shouldn't be messing with this if you're not willing to fail or lose that data. That being said, assuming you have that backup. Wipe the drive and install again using a properly patched usb drive.
My fellow experimentator. Definitely I am not accusing anyone.... it’s just a sad Statement, and an attempt to make a joke in this sad situation))) (and also a warning to anyone following my trail))

being serious:
MBP mid2012 (non retina)
11.0 installed flawlessly
But due to FileVault - could not install the 11.1 update on top (password was not accepted)
So I re-assembled the fusion drive. Started installation again.
Process is breaking some time 50-60 minutes after start (somewhere at stage „one minute left“)
Attempt to pull the backup out of the timecapsule- no success. „Error while connecting to timecapsule“ not even prompting to fill in the password.
I guess the next attempts will be to try installing the 11.0 again and restoring backup. Not sure if I’ll succeed with that.
 
There is no difference. These interfaces open a sub shell and run the command you entered there. A command can be some normal system command as well as a self written script. A lot of these unix commands you know may be scripts.

May be I do not understand want you intend to do: But I guess you want to call the patch-kext.sh downloaded to some place in the filesystem and run it from there and gather the output (this is what you normally see on the screen in a terminal is in the unix semantics it is just another predefined file descriptor called stdout, another is stderr).

I guess you should use the one bigger search engine or the most recent Apples objective-c docs. There you will find hundreds of code examples...

Try a search like "running a unix shell srcipt from an apple objective c program" :)
Alright, thanks! I will do research tomorrow. I FINALLY finished shoveling out. I got almost 5 feet of snow lmbo :)
 
  • Like
Reactions: Ausdauersportler
Affermative Sir! THANK YOU!!
There has not been much effort spent into machines without a metal GPU as your MacBook. The usability will be bad, especially because your system is meant to be used from the GUI unlike a Mac mini which may serve as a head less server (plex, file services, and so on).

I guess your SandyBridge CPU will need more patches as the standard 2011 set contains to run (like the 2011 iMacs). Nevertheless patching it should not create such errors while linking. Try a fresh installation or unpatch the system by calling patch-kext.sh -u - a method described in the online docs. Did you try to patch an already once patched system?
 
Alright, thanks! I will do research tomorrow. I FINALLY finished shoveling out. I got almost 5 feet of snow lmbo :)
Climate change killed the real winter in my part of the world more than a decade ago. When I was a kid we were able to skate on frozen lakes at least twice a winter, now less than once a decade. And the NHL has a break, too. A lot of time for coding :)
 
  • Like
Reactions: MacHacJac
Many parts of New England got above average snowfall for 19 out of the last 20 years. (2015-16 winter was very warm)
 
There has not been much effort spent into machines without a metal GPU as your MacBook. The usability will be bad, especially because your system is meant to be used from the GUI unlike a Mac mini which may serve as a head less server (plex, file services, and so on).

I guess your SandyBridge CPU will need more patches as the standard 2011 set contains to run (like the 2011 iMacs). Nevertheless patching it should not create such errors while linking. Try a fresh installation or unpatch the system by calling patch-kext.sh -u - a method described in the online docs. Did you try to patch an already once patched system?
Yes i try to patch an already once patched, maybe is this the problem, therefore i try to do a clean and fresh installation from zero and retry the patch-kexts.sh procedure again! THANK YOU!!
 
  • Like
Reactions: Dilli
Just an update on Radeon 6x support. Final drivers are being released tomorrow......
Like I told you all weeks ago before it was annnounced apple would no longer provide update packages as standalone! Just annnounced today....I have some ways around this.....stay tuned for announcement Tuesday

 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.