@Barry K. Nathan @jackluke just unpatched 0.3.2, repatched to 0.4.2, set-vars with EFI Boot and applied to BS B10 on Mac mini 2010 ...Almost all works excepted USB mouse and Keyboard and SIRI.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
I guess we will have to live (for now) with the manual whitelisting unless someone comes up with a real sophisticated hardware detection software piece identifying the WiFi card in use and doing all proper adjustments. Have the same currently with the BCM943602CPD working OOB while the close relative BCM94360CD needs the whitelisting (both do not need a WiFi patch).
Since the developers cannot have all possible hardware and in particular not your specific hardware setup it would be your turn to figure out the solution and post it back here.
Try
--wifi=hv12v-new and see if that adds Continuity support. If not, then just run patch-kexts.sh again without a --wifi switch to go back to the default.
Hi @jackluke - I am trying to work with EFI code, and I saw you've included a
(Sorry if this is getting close to off-topic, I'd be very happy to accept any suggestions for somewhere better to discuss/ask about this!)
UEFIShell.efi in your very helpful OpenCore package. I copied that into a FAT32 partition on its own as bootx64.efi and it boots up and works fine, but whenever I try to run any other .efi file from it (even a mega-simple program to print "Hello, World!" and return EFI_SUCCESS) then whilst the other EFI works and runs fine to completion, the UEFI shell then hangs and doesn't return to its command prompt. Have you seen this behaviour? Do you have any tips?! (EDIT: It does exactly the same behaviour if I enable and run it from within OpenCore tools, I just checked.)(Sorry if this is getting close to off-topic, I'd be very happy to accept any suggestions for somewhere better to discuss/ask about this!)
Last edited:
Even so, I think it may still have bugs in at least some circumstances, so I'll test it myself in the next week or so (maybe in the next day if I can find the time).
Right now, at least, Siri doesn't work without a Metal GPU.
I need to try Big Sur again on my MacBook6,1 -- that might give me a better idea of what's going on with USB. Hopefully later this week, although it might have to wait for next week.
Thank you Mr @Barry K. Nathan for your great workI'm still catching up on this thread, but I have just released Big Sur Micropatcher v0.4.2. I had to deal with non-patcher stuff over the past several days, which is why I wasn't able to finish this release until now.
Release notes (edit: forgot one of the bug fixes):
GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs
A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatchergithub.com
Hi @jackluke , is there one of your patches that I can try to fix USB mouse and Keyboard on Mac mini 2010 BS B10 Penryn? They were perfectly working until Beta 4 with your prekernel fixes.
Thank you! They was working until Beta 4 with @jackluke prekernel fixes.
I have one issue , after installed beta 10 , I changed the language , then after restart unable to boot Big Sur and I got the dead screen and random restart
Can a little help, whatever I do I can not install WIFI, I have a iMac late 2012, everything else works only wifi I can not install, cant mount -uw error cant mount or / Volumes / Image \ Volume / patch-kexts .sh / Volumes / Big_Sur (my) \ HD error unable to find the volume ;-(
It might be easier to run patch-kexts.sh from within the Big Sur installation. Make sure the USB stick is plugged in, open Terminal, then drag-and-drop patch-kexts.sh from the patched USB stick in the Finder to the Terminal window, then press Enter/Return.
I just tried Big Sur beta 10 with patcher v0.4.2 on my MacBook6,1, and for the first time since beta 3, USB 1.1 is working. (The change I made in patcher v0.4.2, by the way, is that patch-kexts.sh uses beta 3's kmutil if LegacyUSBInjector is being installed.)
All I can suggest for now is to try running zap-snapshots.sh and see if that fixes USB. I doubt it will, but I can't think of anything else to try.
Actually, I just thought of one more thing to try: Try booting with Command-S for Single User mode, then run "exit" to continue booting. (If this trick is going to work, then the USB keyboard will work once it's in Single User mode.) I don't expect this to work either, but please let me know if it does.
BS beta10 installed on MBP5,2 (mid 2009, legacy USB) on a freshly erased external SSD on USB. Many thanks to jackluke and Barry! jackluke provided essential extra guidance in a private communication, including for the use of his OpenCore 4b.
That installation is for testing - no production system without acceleration, as said many times on this thread. But I'm writing this from that system.
I used a rather special hybrid installation scheme:
USB BS installer made with createinstallmedia of beta10, then applied jackluke's BigSur BaseSystem legacy usb fix b9 to it, then copied the payloads of Barry K. Nathan's big-sur-micropatcher-0.4.2 to the root of the USB installer (necessary parts only).
- USB installer boots fine after choosing English. In installer's terminal executed jackluke's + ASentientBot’s Hax3.sh.
- Then started installation with target SSD on one of the on-board USB connectors. Phase1 finishes.
- Phase2 can't proceed very far, as visible in single user mode: the legacy USB (power) problem*.
- Hot swap the SSD to one of the USB3 ports of a nanoTECH ExpressCard34 which I had bought after Larsvonhier's hint earlier in this thread. Phase2 continues to the end of the long white-on-black phase.
- Swap back to on-board USB for booting of the volume now called MacOS Installer (can't boot from the express card ports), then after legacy USB problem (after some 15sec) hot swap to USB3 for continuation.
- Same for the next booting. Afterwards installation to the target SSD is finished, but can't boot BS yet due to missing/wrong kexts.
- Boot USB BS installer again and run Barry's patch-kexts.sh with option --2009. That works successfully and without error message, and needs no further bless.
Then BS beta10 boots fine from an on-board USB port, no further use of USB3 or swapping needed. CMD+S/exit wasn't needed (but useful for inspection) in the whole process.
Next time I'll try to avoid the USB3 swapping by using jackluke's OpenCore 4b.
*Edit: when using single user mode during installation, an external keyboard is needed connected to the 2nd USB3 port, at least to type exit. Internal keyboard, connected to internal USB, can‘t work before the LegacyUSB injector is in place after patch-kexts.sh.
That installation is for testing - no production system without acceleration, as said many times on this thread. But I'm writing this from that system.
I used a rather special hybrid installation scheme:
USB BS installer made with createinstallmedia of beta10, then applied jackluke's BigSur BaseSystem legacy usb fix b9 to it, then copied the payloads of Barry K. Nathan's big-sur-micropatcher-0.4.2 to the root of the USB installer (necessary parts only).
- USB installer boots fine after choosing English. In installer's terminal executed jackluke's + ASentientBot’s Hax3.sh.
- Then started installation with target SSD on one of the on-board USB connectors. Phase1 finishes.
- Phase2 can't proceed very far, as visible in single user mode: the legacy USB (power) problem*.
- Hot swap the SSD to one of the USB3 ports of a nanoTECH ExpressCard34 which I had bought after Larsvonhier's hint earlier in this thread. Phase2 continues to the end of the long white-on-black phase.
- Swap back to on-board USB for booting of the volume now called MacOS Installer (can't boot from the express card ports), then after legacy USB problem (after some 15sec) hot swap to USB3 for continuation.
- Same for the next booting. Afterwards installation to the target SSD is finished, but can't boot BS yet due to missing/wrong kexts.
- Boot USB BS installer again and run Barry's patch-kexts.sh with option --2009. That works successfully and without error message, and needs no further bless.
Then BS beta10 boots fine from an on-board USB port, no further use of USB3 or swapping needed. CMD+S/exit wasn't needed (but useful for inspection) in the whole process.
Next time I'll try to avoid the USB3 swapping by using jackluke's OpenCore 4b.
*Edit: when using single user mode during installation, an external keyboard is needed connected to the 2nd USB3 port, at least to type exit. Internal keyboard, connected to internal USB, can‘t work before the LegacyUSB injector is in place after patch-kexts.sh.
Attachments
Last edited:
I've been having a lot of issues in the past few days that have been really bugging me. I keep getting kernel panics on my Mac and sometimes my SSD wonks up. I have received quite a few DMs, both on Discord and here about my patcher updates and I assure you that a lot of work is being done, I just don't have the time to post updates every few minutes, especially given the major issues my Mac is facing. I am considering completely wiping and resetting my SSD to start from a clean slate, and keep all of the important files on a backup, including the patcher. However, there is a big problem affecting my Mac right now. I ran a hardware test to see if the kernel panics were due to hardware, but it isn't hardware, fortunately. However, it seems my SATA cable is a goner (See attached image).
Unless one of you tells me that it's not the SATA cable that's the problem, I will have to replace it, meaning a day or two without the patcher. My Mac has been really problematic lately and I am considering trying to reconcile my freshly acquired broken 2013 iMac for daily use, as my 2011 MBP has too many issues to be productively usable. I really want to keep this Mac alive though because I need it to test graphics acceleration on Big Sur. Consequently, the work on my patcher has been moving forward, but very slowly. I am reaching out to @ASentientBot about graphics acceleration as well. I really want to keep this Mac alive though because I need it to test graphics acceleration on Big Sur. Any help is appreciated in these hard computer times. I just want to let you all know that I'm still here and on Discord to help and support everyone and I want to let you know that I'll never let you down. If anyone has any suggestions for me about my 2011, the patcher, or a solution to the SATA problem, please let me know. I really hate having to dodge kernel panics on every single boot.
Thank you and peace out. I will never let you down.
-MacHacJac
Unless one of you tells me that it's not the SATA cable that's the problem, I will have to replace it, meaning a day or two without the patcher. My Mac has been really problematic lately and I am considering trying to reconcile my freshly acquired broken 2013 iMac for daily use, as my 2011 MBP has too many issues to be productively usable. I really want to keep this Mac alive though because I need it to test graphics acceleration on Big Sur. Consequently, the work on my patcher has been moving forward, but very slowly. I am reaching out to @ASentientBot about graphics acceleration as well. I really want to keep this Mac alive though because I need it to test graphics acceleration on Big Sur. Any help is appreciated in these hard computer times. I just want to let you all know that I'm still here and on Discord to help and support everyone and I want to let you know that I'll never let you down. If anyone has any suggestions for me about my 2011, the patcher, or a solution to the SATA problem, please let me know. I really hate having to dodge kernel panics on every single boot.
Thank you and peace out. I will never let you down.
-MacHacJac
I ended up changing the plist in IOFRamework to enable the Mac Pro 5,1 motherboard for Continuity
Code:
/usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/Volumes/BigSur/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"Seems to work so far - at least for Watch Unlock.
Yes, yes...have to do exactly the same using my iMac 12,2 board-id after every new installation of BigSur. Of course this is easy to script in a patcher tools getting access to all hardware info (system_profiler alike).
I've seen apparent cable errors that actually turned out to be the drive. I guess I would suggest replacing the cable first, then replacing the drive if the cable doesn't fix it -- but if it's cheaper or easier to replace the drive, then you could try replacing the drive first if you want.
Kepler cards should work natively In Big Sur.
There are changes in Big Sur's kernel that prevent the Catalina IO80211Family.kext (or any of its Plugins) from working on Big Sur. It might be theoretically possible to create some kind of shim, but I personally doubt it would be worth the effort. (It might end up being easier to just directly binary patch the Big Sur IO80211Family.kext or its Plugins.)
That doesn't answer the Bluetooth question (is there a need to downgrade the Bluetooth driver?), but hopefully that answers the WiFi question.