Nice. Out of curiosity, how far away are you from being able to get rid of the nvram boot-args="-no_compat_check" requirement? Is that just a matter of finding all of the platform checks or has something more significant changed in Catalina that requires this?
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 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Nice. Out of curiosity, how far away are you from being able to get rid of the nvram boot-args="-no_compat_check" requirement? Is that just a matter of finding all of the platform checks or has something more significant changed in Catalina that requires this?
Just to report success to install Catalina DP 2 on my Mac Pro 3.1 with Dosdude1 installer Beta 15.
Congiguration:
Congiguration:
- Processor: 2 x 3,2 GHz Quad-Core Intel Xeon
- Memory: 32 GB
- Samsung SSD 850 PRO 1TB
- APFS ROM installed
- Graphic card NVIDIA GeForce GTX 770 4 GB with MacVidCards ROM
- Two LG Ultrawide monitor at 3440 x 1440
- Full Video accelaration
- Ethernet and wifi working
- Bluetooth activated and working
- TRIM enable for SSD with the commands : sudo mount -uw /; sudo trimforce enable
- USB Audio working
- Handoff
seemsactivatedbut is not workingand working. - Apple watch to unlock the mac seems activated but is not working
- Facetime Video freeze after a few seconds but audio continue
- AppleTV, Music, News apps working. Video and audio quality is goog.
- Font a little bit blurry in News app.
- Home app working but with some oddities.
- Siri working
- Printer HP Officejet Pro 8600 working
Last edited:
I know of two checks. One is on the Preboot container and the other is on the Data. There may be a third on the System’s container. And it is also a boot.plist in the template for the when the Data container is created. It is on the System’s container.
Thanks for this, I do have that card in my MP3.1, in fact I have another one in a Windows PC , I was going to flash that one for my MP but decided against it and bought a Mac version off Ebay, I will get round to trying again using your instructions when I have the time as I have a project on the go building a gaming PC for a friend, so thanks again anyway, I do really appreciate what you and the rest of the maestro's of Mac's do.
I'm using 0403979's patcher on a Macbook Pro 7,1 and I get this error. Anyone know what i'm doing wrong?
Actually, the latest 1.0b15 release of macOS Catalina Patcher now has a patch installer utility. So the easiest approach would be to recreate your patched Catalina DP2 usb installer and, after the installation reboot, option select it again to use the new macOS post install application to apply the non-metal patch set.
I investigated this issue and a fix will be released tomorrow, along with the USB fix for the MacBook6,1. Stay tuned for macOS Patcher 3.0 beta 2.
Sorry if this has been asked before, @dosdude1 is it normal that your macOS Catalina PartialPatcher does not currently work successfully when you try to use it when already running Catalina DP2? I left it for about hour and it was still going no errors but there was also no read writes to the USB anymore and no Complete notification.
Same here with MacBook Pro 5,5. @dosdude1 b15 did not work either.
When apply the post install patches, I have two volumes two choose from, one is labeld with “-data”. Which do I choose ?
The one that does not have the "Data" suffix. That is the main system volume.
On a MacPro 3,1 running Catb2 using the combined dosdude1, Starplayr, jhowarth method, I am seeing this damaged kext warning (attached) on a restart. It does not seem to affect anything yet and the OS is running as expected with the usual bugs.
CloneToolX update. It is now restoring volumes from disk images. It is pretty fast. Overcoming some on minor obstacles along the way.
I had to get Mrs. NiceMac a new car today. And I decided Starplayr needed a new car too. If you are around Charlotte, NC. You might see an Electric Blue Mini Cooper with StarPlayrX on the back. BTW, my mini recognized my radio player iOS app on my Mini and it is read some metadata in the stream that I couldn't find myself. It was pretty cool seeing my App and a partial PDT working on a car that I never designed it for.
Not a lot got done today. I'll be sticking to its original goal of a beta in 2 weeks starting this weekend. It is moving along nicely.
I had to get Mrs. NiceMac a new car today. And I decided Starplayr needed a new car too. If you are around Charlotte, NC. You might see an Electric Blue Mini Cooper with StarPlayrX on the back. BTW, my mini recognized my radio player iOS app on my Mini and it is read some metadata in the stream that I couldn't find myself. It was pretty cool seeing my App and a partial PDT working on a car that I never designed it for.
Not a lot got done today. I'll be sticking to its original goal of a beta in 2 weeks starting this weekend. It is moving along nicely.
Last edited:
macOS Patcher 3.0 beta 2 has now been released. This is the description from the macOS Patcher releases page:
"This is the second beta of macOS Patcher 3.0, the first version of macOS Patcher to support macOS 10.15 Catalina.
Release notes for macOS Patcher beta 2:
Important notes:
This is a beta release of macOS Patcher with support for a beta release of macOS. If you discover an issue, please make sure it’s an issue with macOS Patcher 3.0 and not with macOS 10.15 Catalina. If your issue is with the macOS Patcher 3.0, then contact us on Discord or MacRumors Forums, or create an issue on the macOS Patcher GitHub page.
You have to run sudo nvram boot-args="-no_compat_check" before installing macOS 10.15 Catalina on an unsupported Mac. If you use the patched installer on a supported Mac, this is not required.
You can read about the removal of the integrated utilities, and the future of macOS Patcher, here."
macOS Patcher 3.0 beta 2 is available here.
"This is the second beta of macOS Patcher 3.0, the first version of macOS Patcher to support macOS 10.15 Catalina.
Release notes for macOS Patcher beta 2:
- Fix issues in installation
- Fix issues in patching
Important notes:
This is a beta release of macOS Patcher with support for a beta release of macOS. If you discover an issue, please make sure it’s an issue with macOS Patcher 3.0 and not with macOS 10.15 Catalina. If your issue is with the macOS Patcher 3.0, then contact us on Discord or MacRumors Forums, or create an issue on the macOS Patcher GitHub page.
You have to run sudo nvram boot-args="-no_compat_check" before installing macOS 10.15 Catalina on an unsupported Mac. If you use the patched installer on a supported Mac, this is not required.
You can read about the removal of the integrated utilities, and the future of macOS Patcher, here."
macOS Patcher 3.0 beta 2 is available here.
Last edited:
After tested thoroughly this method: fix AirDrop on Catalina unsupported Mac with AirPort Broadcom Wifi
I have discovered that with the same method I was able to patch and use all the stock Catalina IO80211Family*.kext , but this method is only valid for "AirPort Broadcom Wifi cards" previously supported on HighSierra/Mojave , the advantage of my manual method is that it will fix the Catalina stock Wifi and more over will add the AirDrop channel capability.
I attach a guide I wrote.
I have discovered that with the same method I was able to patch and use all the stock Catalina IO80211Family*.kext , but this method is only valid for "AirPort Broadcom Wifi cards" previously supported on HighSierra/Mojave , the advantage of my manual method is that it will fix the Catalina stock Wifi and more over will add the AirDrop channel capability.
I attach a guide I wrote.
I add also (as working example) for a stock Catalina beta2 IO80211Family*.kext a working pre-patched
AirPortBrcm4360 to enable Wifi and AirDrop both on MacBook7,1 and MacBookPro6,2 .
In few words using that driver without the 4331 (absent from Catalina) you spoof your Broadcom Airport as a Catalina supported AirDrop one. It's totally working.
Instead consider that for Broadcom Airport Wifi card from 2012 apple uses this other driver: "AirPortBrcmNIC.kext" , so my patch doesn't affect a recent Broadcom AirPort Wifi that works OOB.
I am still hoping that by the time Catalina ships that cards which should be supported natively like the BCM94360CD are working with the stock kexts. If that happens, the optimal patching would be to detect the installed card and layer on the patches as required like Mojave currently does.
Agree, as I wrote, the Broadcom AirPort Wifi cards produced after 2011 use this IO80211Family driver: "AirPortBrcmNIC.kext"
While Catalina IO80211Family.kext has removed this AirPortBrcm4331.kext, but in its place can be used a manual patched AirPortBrcm4360.kext , that will enable also the AirDrop for legacy pre-2012 Broadcom AirPort Wifi cards.
Made an USB stick with @dosdude1 patcher. 35 minutes booting in a Macbook Pro 17 2011 but the screen never passes the grey apple. Dedicated GPU disabled with the method of the same creator.
Update: 49 minutes but booted the installer at last.
Update: 49 minutes but booted the installer at last.
Last edited:
Check with 'sudo nvram -p boot-args' that you really have set that to "-no_compat_check"
Thanks. Yes, it was. And before the reboot I Made a nvram -p to be sure.
Did that appear after the initial installation and patching or is it something that appeared on a later reboot? If not, I would try reinstalling from the 1.0b15 created usb installer and use dosdude1's bundled patcher to see if that eliminates it. Otherwise, you might want to check that smart isn't shows any failures on your storage device. I've done around 10 reinstallation this week and never saw anything like that.