MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[paalb]

forgive me for banging on about an issue which has been resolved.....but, I've loaded disklabel in BOOT in my EFI folder, and have successfully executed this command:
/Volumes/EFI/EFI/BOOT/disklabel

However, I've run into problems trying to execute the following command in terminal:

sudo ./disklabel -e "YourLabel" .disk_label .disk_label_2x

I constantly get the following error messages, for example:

sudo: ./disklabel: command not known
or
sudo: /disklabel: command not known

Can you suggest what I am doing wrong?
Thank you
Art S

Try with full path:
sudo disklabel -e "YourLabel" /Volumes/EFI/EFI/BOOT/.disk_label /Volumes/EFI/EFI/BOOT/.disk_label_2x

 

[MacNB2]

forgive me for banging on about an issue which has been resolved.....but, I've loaded disklabel in BOOT in my EFI folder, and have successfully executed this command:
/Volumes/EFI/EFI/BOOT/disklabel

However, I've run into problems trying to execute the following command in terminal:

sudo ./disklabel -e "YourLabel" .disk_label .disk_label_2x

I constantly get the following error messages, for example:

sudo: ./disklabel: command not known
or
sudo: /disklabel: command not known

Can you suggest what I am doing wrong?
Thank you
Art S

First, you should really not use the EFI folder for terminal executable apps. EFI for is used for boot purposes.
That OC disklabel command should be copied to a folder on your macOS drive (e.g. to /Users/YOUR_NAME) and then you have to change your current working folder to wherever you copied that command.

So in your case, it looks like you forgot to enter the cd command before executing sudo ./disklabel.....:

cd /Volumes/EFI/EFI/BOOT

 

[TECK]

Can you suggest what I am doing wrong?

You need to be inside the disklabel directory, you should not place the binary inside the EFI.

$ cd Downloads/OpenCore-0.7.4-RELEASE/Utilities/disklabel
$ ls -lah disklabel

Then you can run your command fine. Your /BOOT should contain only:

$ ls -lh /Volumes/EFI/EFI/BOOT
total 41
-rwxrwxrwx  1 me  staff    20K 25 Oct 14:29 BOOTx64.efi

Edit: sorry, just saw the previous replies.

 

[Eweie]

First of all thanks everybody for keeping this project alive. I've updated my 5,1 from Big Sur to Monterey without any issues.

But neither my internal or external usb bluetooth are working on boot up. I need to run "sudo kill -9 $(pgrep bluetoothd)" to make my external USB bluetooth dongle work. but this is after logging which is not ideal.

if I remove the internal stock bluetooth/wifi card from the Mac will my external USB dongle startup normally without having to run that code?
thanks.

 

[iRabbit]

I have questions that I really need help with. Please see this post for all the finer details is here:

Unsupported Catalina Install - but specific questions.

My system: - MacPro 5,1 2 x2.66 6-core intel Xeon - 64 Gb ram - Radeon rx580 8gb - 4 SSDs in standard HD sled Bays - installed OpenCore… I did this because I was having computer issues last week…. trying to debug and test things I got to a point where I thought a boot picker...

forums.macrumors.com

But quickly, if I installed OpenCore 0.7.4 and then did the DosDude Catalina patcher, what’s my best way to upgrade to BigSur? Everything is running great as of right now, but I want to be prepared for the future moving forward.

Thanks!!

(5,1 mid 2010 MacPro)

 

[PeterHolbrook]

There’s no reason whatsoever for dosdude1’s Catalina Patcher if you are using OpenCore.

 

[iRabbit]

There’s no reason whatsoever for dosdude1’s Catalina Patcher if you are using OpenCore.

So what should I do now?

 

[PeterHolbrook]

I don’t suppose dosdude1’s patcher, even though unnecessary, will keep you from upgrading to Big Sur or Monterey, provided OC is rightly configured. Study post #1.

 

[iRabbit]

I don’t suppose dosdude1’s patcher, even though unnecessary, will keep you from upgrading to Big Sur or Monterey, provided OC is rightly configured. Study post #1.

Since I did the OC install, my system has shown through Apple updates that Monterey is available (though I know not to install that yet)… so I gather I did OC correctly. I’ve just seen/heard conflicting things because of how I did Catalina (there was method to my madness). Ultimately I know I could likely just do a clean install on a different drive if I was really that worried. Would love to hear from people with the same combo… I know I’m not alone…

 

[PeterHolbrook]

I insist. Study post #1. Be aware that classic Mac Pros and other vintage Macs require SurPlus for anything beyond 11.2.3.

 

[Farravi]

Greetings all.

I've been trying to install Big Sur via the OCLP method and I cannot replicate the process. I do not get a boot(EFI) menu when i reboot the system whilst pressing the 'Option' button.

I have a cMP 5,1 (2010 model) with a metal supported GPU (Vega 56) card and my bootrom is 144.0.0.0.0 and currently running Mojave.

I have created the USB (Install macOS Big Sur) media as per the instructions.

Edit - Apologies, can the moderator please delete / move this to the appropriate thread.

 

[Klineex]

if you still have the stock BT card in your 5,1 it will work just fine. I have 4x 5,1's running 12.0.1 and BT works great!
I'm using OCLP 0.3.1

I thought Monterey dropped Bluetooth 2.1 chipsets? was that fixed in the RC?

 

[tsialex]

I thought Monterey dropped Bluetooth 2.1 chipsets? was that fixed in the RC?

Correct, from the Mac Pro factory cards and the usual upgrades done with cards from newer Macs, Monterey only supports the BRCM20702 v2 Bluetooth v4.0 controller from the BCM94360xxx AirPort Extremes. Newer AirPort Extremes are also supported by Monterey.

OCLP is hacking it to provide support for the factory cards.

 

[Eweie]

First of all thanks everybody for keeping this project alive. I've updated my 5,1 from Big Sur to Monterey without any issues.

But neither my internal or external usb bluetooth are working on boot up. I need to run "sudo kill -9 $(pgrep bluetoothd)" to make my external USB bluetooth dongle work. but this is after logging which is not ideal.

if I remove the internal stock bluetooth/wifi card from the Mac will my external USB dongle startup normally without having to run that code?
thanks.

 

[NC12]

While I am not sure if removing it will fix your bt dongle you could always make an automator app that would run that script on login

 

[EETagent]

I thought Monterey dropped Bluetooth 2.1 chipsets? was that fixed in the RC?

<dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>BlueToolFixup.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/BlueToolFixup</string> <key>MaxKernel</key> <string>21.99.99</string> <key>MinKernel</key> <string>21.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>Bluetooth-Spoof.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string>21.99.99</string> <key>MinKernel</key> <string>21.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict>

Support was dropped, but you can restore it using a modified BlueToolFixup from the OCLP GitHub repository and extend the life of the original Bluetooth card for a little longer.

Wi-Fi support can be restored as well by using IO80211ElCap and corecaptureElCap. You would not be able to connect to network without https://github.com/dortania/PatcherSupportPkg/tree/master/12-Monterey/CoreServices/Legacy-Wifi though, so OCLP system volume patching is needed here.

 

[tsialex]

OCLP and other OpenCore Packages/Managers

(I see a lot of talk but no action, so I'll take the plunge, even though I'll have little to contribute to this thread going forward.) OpenCore (code here, documentation here) is a boot loader; if you're not already familiar with it, here's an overview. If you are an advanced user or have...

forums.macrumors.com

BTW, OCLP developers are implementing novel ideas that will probably gonna be used here later - like no spoofing and the VMM patch set. Their implementation is robust and performs a lot better than spoofing a newer Mac or enabling the VMM flag from Catalina days. It's probably not being used here yet because you can't enable VideoToolbox hardware acceleration right now - but every developer here is following the commits there.

 

[Dayo]

Wi-Fi support can be restored as well by using IO80211ElCap and corecaptureElCap. You would not be able to connect to network without https://github.com/dortania/PatcherSupportPkg/tree/master/12-Monterey/CoreServices/Legacy-Wifi though, so OCLP system volume patching is needed here.

@EETagent ... thanks for that.

I already leverage the "ELCap" and "corecapture" kexts in MyBootMgr but I suppose the Legacy-WiFi kext you linked cannot be injected in OC because it contains resources (apparently a limitation of OC).

Presumably the only issue with not adding that (still mulling a system patching app) is not being able to "network" ... whatever that means.

 

[chrisrm9208]

Back in my world, how much longer do I have before i have to delve into the guts of my cMP5,1 and upgrade the wifi card? I take @tsialex's point re the patching at every release but my co-ordination is shot and the tiny push-on connections fill me with dread....

 

[tsialex]

Back in my world, how much longer do I have before i have to delve into the guts of my cMP5,1 and upgrade the wifi card? I take @tsialex's point re the patching at every release but my co-ordination is shot and the tiny push-on connections fill me with dread....

If you have an available PCIe slot, the Fenvi T919 is pretty inexpensive for a BCM94360 card and will solve the Wi-Fi connectivity without any kexts and having to mess with the U.FL connectors of the Mac Pro antennas, just install the card on a PCIe slot and forget, since it's fully supported and will work fine with the first post implementation.

Also, the Fenvi card have excellent Wi-Fi and Bluetooth reception, but for BT you to connect the USB data header of the Fenvi card to one of the Mac Pro USB ports or to the Molex PicoBlade JST USB data connector on the backplane that is used for the original bluetooth module - the black cable.

I have a Fenvi T919 installed in one of my Mac Pros, works fine.

 

[cdf]

I've been trying to install Big Sur via the OCLP method and I cannot replicate the process. I do not get a boot(EFI) menu when i reboot the system whilst pressing the 'Option' button.

That's probably because you don't have boot-screen support. You should bless OC from Recovery. This procedure is covered in the first post. See "First Boot".

Important: For those having similar procedural queries, I implore you to take a look at the first post before posting. You may be surprised to find your answer there. You'll also avoid irritating members that may interpret your query as a disregard for the material in the first post.

 

[cdf]

JST USB data connector on the backplane that is used for the original bluetooth module - the black cable.

Off-topic note: 1.25 mm JST is often confused with the Molex PicoBlade series. In this case, the correct connector is in fact a Molex:

802.11ac, BT 4.0 and Continuity & Handoff are working on Mac Pro 2010 (Keep Updating)

There seems to have been some confusion over the connector on the bluetooth cable. After some digging, I've determined that the correct connector is a Molex 51021-0400. Not only are the measurements right, but the tiny markings match up as well.

forums.macrumors.com

 

[iRabbit]

Off-topic note: 1.25 mm JST is often confused with the Molex PicoBlade series. In this case, the correct connector is in fact a Molex:

802.11ac, BT 4.0 and Continuity & Handoff are working on Mac Pro 2010 (Keep Updating)

There seems to have been some confusion over the connector on the bluetooth cable. After some digging, I've determined that the correct connector is a Molex 51021-0400. Not only are the measurements right, but the tiny markings match up as well.

forums.macrumors.com

I’m sorry to bother you. I’ve been desperate for some help and asked before a lot of bickering commenced. Appreciate opencore and all the work you and others have done!

Whether it was “correct” or not, I installed OC and then Dosdude’s Catalina Patcher (on 5,1 mid-2010, with Radeon rx580). All is running great, but I need to know how to keep things up to date moving forward.

More info is in my post history for anyone so inclined to help. I did start a dedicated thread to it in the Catalina forum.

Thank you.

 

[cdf]

Whether it was “correct” or not, I installed OC and then Dosdude’s Catalina Patcher (on 5,1 mid-2010, with Radeon rx580). All is running great, but I need to know how to keep things up to date moving forward.

I would not recommend mixing OpenCore with a hard-patched install. Moving forward, I would do a clean install of macOS Catalina or later (using a full installer on a freshly formatted drive) and then confidently apply OTA updates. Take a look at the first post here for how to obtain a full installer.

 

[iRabbit]

I would not recommend mixing OpenCore with a hard-patched install. Moving forward, I would do a clean install of macOS Catalina or later (using a full installer on a freshly formatted drive) and then confidently apply OTA updates. Take a look at the first post here for how to obtain a full installer.

Thanks. I actually went the route I did because I read other people had successfully done it and dosdudes video said it could even be used on supported macs.

If your solution is my only recourse, it’s certainly the way I’ll go. Was hoping to avoid that, but I can hope for the best and prepare for the worst … I have a spare 2tb SSD, so I can install BigSur to that and see how it goes.

Thanks!