MP 1,1-5,1 Install Monterey, lose one CPU! cMP3,1

[DCBassman]

Just doing some 'About this Mac' screenshots, and noticed on the Mac Pro that it simply said Intel Quad-core Xeon. Checked System Report and sure enough, "1 processor, 4 cores". So where on earth has the other CPU gone?
If I fire up a live Linux (MX in this case), hey presto, both CPUs present.
Is this a Monterey thing? If so, this beast will immediately revert to Linux...

 

[mattspace]

How many cores does Activity Monitor's CPU Usage window show?

 

[tsialex]

Known OCLP 2.x workaround for Sequoia, for earlier releases of macOS you can disable the 1-cpu patch in OCLP Settings (Settings -> Build -> MacPro3,1/Xserve2,1 Workaround).

Release 2.0.0 · dortania/OpenCore-Legacy-Patcher

With the release of OpenCore Legacy Patcher 2.0.0, we're proud to announce macOS Sequoia support! And with it, 83 unsupported Mac models will be able to run Apple's latest operating system! With ...

github.com

 

[Dayo]

You used the OCLP to set OpenCore up for Monterey.

The OCLP is currently focused on Sequoia, which requires that MP31 is set to only use one processor.

You do not need the OCLP to set OpenCore up for Monterey on any cMP as long you are using a GPU supported on Monterey.

You appear to be running a GTX680. This is only supported up to Big Sur and requires OCLP patches to work on Monterey.

Being stuck with the OCLP and to save yourself rerunning it with the MP31 8-core workaround to avoid this issue, in the OpenCore config.plist file created by the OCLP for Monterey, look for cpus=1 in the bootargs and delete this.

 

[tsialex]

You do not need the OCLP to set OpenCore up for Monterey on any cMP as long you are using a GPU supported on Monterey.

While this is true for a MacPro5,1, you forgot to mention that to accomplish it with a MacPro3,1 you need MouSSE, without it you can't run a AMD supported GPU with MacPro3,1 after High Sierra.

 

[Dayo]

While this is true for a MacPro5,1, you forgot to mention that to accomplish it with a MacPro3,1 you need MouSSE, without it you can't run a AMD supported GPU with MacPro3,1 after High Sierra.

It is true for any cMP as originally stated. MP51 needs certain things in OpenCore and the MP31 needs certain additional/different things.

Those things are not tied to the OCLP. So as I said, you do not need the OCLP to run Monterey and older on any cMP as long as using a supported GPU.

 

[tsialex]

It is true for any cMP as originally stated. MP51 needs certain things in OpenCore and the MP31 needs certain additional/different things.

Those things are not tied to the OCLP. So as I said, you do not need the OCLP to run Monterey and older on any cMP.

You wrote in a way that a newbie reading that sentence would think that he/she can accomplish it without any other patches/hacks/hardware mods (like removing the factory BT module), which is not possible with a MacPro3,1.

 

[Dayo]

I wrote a factually correct statement that stayed within a specific scope. A person installing OpenCore any cMP needs certain things added.

You make it sound like that on MP51, all that is needed is to take a default OpenCore config and everything would work out of the box.

Anyway, this is off topic and a bit pointless. The user can just delete the boot arg and be good.

BTW, I run Monterey and Big Sur, both set up sans OCLP as I currently use an RX580, with the factory Bluetooth. Working on Big Sur and just ignored by Monterey.

 

[DCBassman]

@Dayo , you are correct, except that there's no need to delete the arg in the plist, it can just be switched off from the OCLP GUI settings. So now I have both CPUs running as expected. However this has led to a problem with the network settings, effectively disabling the applet in terms of wifi. No matter, I've plumbed everything together with GigE now, so no issue.
Additionally, I would not know where the config.plist for Opencore actually is...

 

[Dayo]

Yes, you can regenerate the plist after using the workaround setting in the GUI. Deleting the boot arg was just in the case of not wanting to regenerate.

The network thing is something else. Perhaps you mistakenly disabled something else. Advantage, I suppose, of simply deleting the boot arg in an already working plist.

 

[DCBassman]

Yes, you can regenerate the plist after using the workaround setting in the GUI. Deleting the boot arg was just in the case of not wanting to regenerate.

Yup, I guessed as much, but still have no clue as to how to edit the file. despite a search that brings up n othing but Hackintosh results.

 

[Dayo]

There are tools for editing plist files but at the end of the day, it is basically a text file and can be edited with TextEdit.

There are pitfalls with using TextEdit but would have been generally OK for simply deleting some text and saving.

It's all moot now since you have regenerated things via the GUI anyway. The original would have been overwritten.

 

[DCBassman]

There are tools for editing plist files but at the end of the day, it is basically a text file and can be edited with TextEdit.

There are pitfalls with using TextEdit but would have been generally OK for simply deleting some text and saving.

It's all moot now since you have regenerated things via the GUI anyway. The original would have been overwritten.

Fair enough, I still would have no clue where to finds the file anyway. I'm just glad you pinged my few remaining brain cells and led me to a solution! Thanks.

 

[Macschrauber]

Fair enough, I still would have no clue where to finds the file anyway. I'm just glad you pinged my few remaining brain cells and led me to a solution! Thanks.

Check my Dumper package, there are mount ESP tools in, what identify bootloaders with flavor and version.

Macschrauber-s-Rom-Dump/ESP_tools.md at main · Macschrauber/Macschrauber-s-Rom-Dump

A tool for dumping and analysing Mac firmwares. Plus flashing for Mac Pro 4,1 / 5,1 and Xserve 3,1 - Macschrauber/Macschrauber-s-Rom-Dump

github.com

Link in signature.