This should stop the Kill -9 errors users have been gettingīigMac2 should behave from the USB 2.0 disk and on Internal SSDs. Boot BigMac 2 up from an external USB 2.0 on an unsupported Mac:
Install BigMac 2 to an external hard drive or USB Flash thumb drive (should be relatively fast and min of 32 GB) This will also give you Airdrop and Handoff without any weird hacks. If you want native WiFi and BT4, do yourself a huge favor and get a 802.11ac/BT4LE Broadcom black iMac style combo card. (2009 - 2012 Mac Pros with upgraded firmware do not need this), You can reinstall it later after you run the Disable Bluetooth patchįor 2008 Mac Pros: If you have not installed dosdude1's APFS ROM Patcher, do that first. If you have Bluetooth 2 EDR Card, remove it. If Bigmac2 app does not run, try resigning it: codesign -force -deep -sign - /Applications/bigmac2.app
If running Bigmac2 recovery / install disk from OWC 2.5" SSD, use a 4x PCIe slot (on Mac Pro 3,1 use the 3rd PCIe slot, not the 1st or 2nd 16x slots) First Time User Guide macOS 11.2.3 (from an unsupported Mac) I lose a PCIe slot, but I can live with that. I use the same idea and routed the USB from the Lenovo PCIe card to a USB 3.0 port. Many users are modding the card and re-routing USB to a USB 3.0 card or USB 2.0 Hub. The culprit for my BCM 20702B0 card not working after Monterey Beta 1 is USB.
This weekend I started experimenting with a Lenovo WiFi 802.11ac/Bluetooth 4.2LE PCIe card using a combination of Open Source drivers that mess well with Apple's and was able to get Handoff working with Monterey Beta 2 and currently have WiFi and BT working on Big Sir 11.2.3 and Monterey Beta 2 and 3. Bluetooth, WiFi, Handoff possible on Monterey (Mac Pro 3,1 4,1 5,1):
For Mac enthusiasts who want to run macOS Big Sur or macOS Monterey on Unsupported Mac hardware.
I will eventually produce a guide on how to make the two products work seamlessly with each other. Sudo /Applications/bigmac2.app/Contents/MacOS/bigmac2Īdded Support for macOS Big Sur 11.6.8, "macOS Monterey 12.5 as of 8.13.22īecause of race conditions during macOS boot with Mac Pros years 2008 to 2012, Open Core Legacy Patcher is recommended and OCLP can compliement BigMac2. This will be fixed as soon as possible with a new priveleged launcher. I do not see any reason why they will not work with BigMac2 provided support gets added.įor those who are using TouchID for sudo, there is a problem with BigMac2's priveleged launcher. I believe all there models can be supported and they also will not have to worry about race conditons. There will be a check list etc etcīigMac2 is planning to add Ventura support for the following Unsupported Macs. As parts are working, it will be uploaded.
Using other types of admin privileges doesn't work which is driving me bonkers! The best alternative is to give sudo a full gui.īigMac 3 will only ask for privileges when it needs it. The main reason for this is Monterey 12.4 requires sudo for Apple Software Restore. This will be an complete overall, but hopefully it will be much easier to troubleshoot.īigMac 3 will have some nice features like a GUI for sudo and it will support not only admin/password, but Touch ID, Apple Watch and even a Yubikey! This change will work within the terminal as well, but smart enough not to affect ssh. The plan is to turn it into a menu bar app and have it designed in the order show operations should proceed. I've decided to start working on BigMac 3. ? After reviewing Big Mac 2 and its technicial issues expanding it. My guess is the permissions when run from an app even as root, do not carry over to asr's child processes.
^ If you run this command manually, you should be able to continue creating the installer disk. Sudo /usr/sbin/asr -s /Users/Shared/bigmac2/bigmac2.dmg -t /Volumes/bigmac2 -nov -nop -er In case you are wondering what is the command that is being skipped here it is: One workaround is to go back a 100% shell script experience, or a hybrid that does this step in terminal via a menu bar app. This same command works fine in the Terminal.īigmac2 is currently in a broken state until I find a fix. When running it as privileged / sudo as root within bigmac, it cannot clone the 800MB installer image and will receive the following error:Ĭouldn't set up partitions on target device - operation DeleteAPFSVolume, line #5502 - Resource busy One new development that is plaguing the development of BigMac 2 and 3 is the state of Apple Software Restore or ASR. ? Apple Software Restore - seriously broken when run from within an app!