MP 1,1-5,1 Activate AMD hardware acceleration

[h9826790]

is it necessary, to mod the config plist when I have downloaded bevor the full installer ? I made before with the OPLP. a Full InstallerStick with 12.7.1. So , I mean it is much simpler - Or am I wrong ?

Full installer or not is irrelevant.

I am not sure for the OCLP settings, most likely other OCLP users can tell you how to update macOS by using OCLP.

If you are using my OC package, mod the config is necessary for every macOS update. It increase the complexity a bit, but it's a very safe approach so far.

 

[polanskiman]

Not sure if this is the right place to ask this but here it goes.
Recently upgraded GPU to Pulse RX 580. Currently under Mojave.
What is the recommended route to upgrade to Catalina or even Monterey:

- OpenCore Legacy Patcher
or
- OpenCore package v0.9.5 by our beloved guru Martin Lo.

I have seen some videos stating that the Legacy Patcher will modify the OS, although I have no clue whether that is true or not. In any case I want the least intrusive loader. I don't think I'll bring my cMP above Monterey due to potential compatibilities issues. This will probably be the last OS this machine will see. Ventura and Sonoma don't seem that well adapted to our old machines.

 

[h9826790]

Not sure if this is the right place to ask this but here it goes.
Recently upgraded GPU to Pulse RX 580. Currently under Mojave.
What is the recommended route to upgrade to Catalina or even Monterey:

- OpenCore Legacy Patcher
or
- OpenCore package v0.9.5 by our beloved guru Martin Lo.

I have seen some videos stating that the Legacy Patcher will modify the OS, although I have no clue whether is that true or not. In any case I want the least intrusive loader. I don't think I'll bring my cMP above Monterey due to potential compatibilities issues. This will probably be the last OS this machine will see. Ventura and Sonoma don't seem that well adapted to our old machines.

Just my personal opinion.

I believe that my OC package is less intrusive. In fact, if you follow cdf's guide to build your own EFI folder, it can be least intrusive. My package is somewhere in between.

My package aim at "one setting fit all" as much as possible. Therefore, some kext may be injected but not really required for your machine (e.g. a kext that for multi CPU, but your setup only has one CPU). Even though, there is no evidence that this cause any issue / performance drop so far.

AFAIK, OCLP's approach is even more generic, and some usual technique that for Hackintosh, but not really required on native Mac, are also added into the EFI folder / settings. But the good thing is that approach will support even more hardware.

Both cdf and my approach prefer the users spend a reasonable amount of money to upgrade the cMP. So that they can start from the compatible hardware, but we only need to bypass the software restriction. Therefore, when we start to hit the "AVX wall", our approach won't work. And OCLP is the only option.

If all you need is just Monterey, and you have the compatible hardware (including BT/wifi if you need it), then you can simply install my package to run Monterey. And when you have time, you can read through the cdf's OpenCore thread, then customised your own OC EFI folder to best fit your cMP / usage.

But if any of your hardware is not natively supported. Then you better go for OCLP, which should save you quite a bit of time to trouble shoot.

OCLP assume you will run the root patcher to mod some system files. So, it you use OCLP, I personally recommend you follow their way. I know some people only use OCLP to generate and install the EFI folder, but then they don't run the root patcher. In this case, unless they know what's being done inside out. Otherwise, they may only have a half working system. Which is not ideal.

In short, you may treat it there are 3 options.

1) You have the compatible hardware, and build the OC EFI folder by yourself. You can follow cdf's guide to do this. This should be least intrusive.

2) You have the compatible hardware, but you want a "just work" solution. Then you may use my preconfigured package.

3) Some of your hardware are not natively supported by Monterey. Then you better go for OCLP.

 

[polanskiman]

Thank you @h9826790

This cMP is basic in terms of use. No photo/video editing, no audio transcoding, no gaming etc. The only hardware upgrade/software I ever did where:

- upgrade BootRom from 4.1>5.1 and replaced CPUs for X5670 and added 48GB of ram;
- added an SSD SATA drive;
- replaced the original GPU with the RX 580;
- replaced the original BT module for a 4.2.

That's all. I might down the road add an NVME drive if money permits and maybe a USB3 card but those are really not a priority for me since I intend to continue using this cMP more like a family computer so mostly basic type of working.

If I am not mistaken, your package should be able to handle all this hardware. Correct?

 

[solaris8x86]

Not sure if this is the right place to ask this but here it goes.
Recently upgraded GPU to Pulse RX 580. Currently under Mojave.
What is the recommended route to upgrade to Catalina or even Monterey:

- OpenCore Legacy Patcher
or
- OpenCore package v0.9.5 by our beloved guru Martin Lo.

I have seen some videos stating that the Legacy Patcher will modify the OS, although I have no clue whether that is true or not. In any case I want the least intrusive loader. I don't think I'll bring my cMP above Monterey due to potential compatibilities issues. This will probably be the last OS this machine will see. Ventura and Sonoma don't seem that well adapted to our old machines.

Of course, the OpenCore Legacy Patcher. It is an all-in-one package. Especially, it can deal with the hardware acceleration issue on h264, h265 at once (no need additional steps). And the blue-tooth too for the old bluetooth board shipped with Mac Pro 5,1 originally.

 

[h9826790]

If I am not mistaken, your package should be able to handle all this hardware. Correct?

Correct

 

[basslik]

I tested on my setup. It should work.
View attachment 2302429

Martin I'm ready to install Monterey and I can't remember if I'm suppose to disable SIP on boot up?

Going from Mojave. I love your package script, and I needed to go back to a Mojave because of certain projects I was working on back then and it's not all fresh in my brain.

I thought I bookmarked the step by step install of OpenCore, your script. THANK YOU

 

[polanskiman]

Martin I'm ready to install Monterey and I can't remember if I'm suppose to disable SIP on boot up?

Going from Mojave. I love your package script, and I needed to go back to a Mojave because of certain projects I was working on back then and it's not all fresh in my brain.

I thought I bookmarked the step by step install of OpenCore, your script. THANK YOU

Yes.

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

 

[polanskiman]

Got some side question before proceeding with MLOC package installation.
I want to first download Catalina for now, however I am unable to download it through the AppStore. I guess it is detecting my cMP is not compatible hence the refusal to download. Ok so I tried downloading it from OCLP, but it is not listed there. 🧐

What's up with that and is there something I need to be aware about Catalina??

 

[h9826790]

Got some side question before proceeding with MLOC package installation.
I want to first download Catalina for now, however I am unable to download it through the AppStore. I guess it is detecting my cMP is not compatible hence the refusal to download. Ok so I tried downloading it from OCLP, but it is not listed there. 🧐

What's up with that and is there something I need to be aware about Catalina??

You may try Dosdude Catalina patcher, I think that will allow you to download the Catalina installer.

 

[polanskiman]

You may try Dosdude Catalina patcher, I think that will allow you to download the Catalina installer.

Ok great got it.

Now before I go forward with your package let me know if I got the process right:
1. install the package as directed and modify the config.plist file to allow updating to Catalina (turn ON VMM flag / turn OFF SMBIOS spoofing)
2. reboot
3. install catalina
4. edit config.plist file again to revert previous edits

 

[h9826790]

Ok great got it.

Now before I go forward with your package let me know if I got the process right:
1. install the package as directed and modify the config.plist file to allow updating to Catalina (turn ON VMM flag / turn OFF SMBIOS spoofing)
2. reboot
3. install catalina
4. edit config.plist file again to revert previous edits

correct

 

[polanskiman]

correct

Magnific. Worked flawlessly.
Now time to clean up that Dock 😂

Also noticed something since Mojave. The About This Mac window is only showing Mac Pro and not Mac Pro (early 2009) or even 2010 since BootRom was upgraded. Is this expected? Not that it matters much but I am curious.

Finally when booting, I see in the Bootpicker the name of the drive which I am booting from. Weird thing is that it is showing the previous name I had. For instance the drive was called Mojave SSD and I renamed it Catalina SSD (as you can see above) but it is still showing Mojave SSD during boot on the Bootpicker.

 

[h9826790]

Also noticed something since Mojave. The About This Mac window is only showing Mac Pro and not Mac Pro (early 2009) or even 2010 since BootRom was upgraded. Is this expected? Not that it matters much but I am curious.

AFAIK, this is cosmetic, and this behaviour base on the Apple server side's response. Not user's error.

Finally when booting, I see in the Bootpicker the name of the drive which I am booting from. Weird thing is that it is showing the previous name I had. For instance the drive was called Mojave SSD and I renamed it Catalina SSD (as you can see above) but it is still showing Mojave SSD during boot on the Bootpicker.

There are few ways to change the disk label in boot picker. What I found the most reliable way is as follow (it's a bit complicated, but works well for me).

1) Open Terminal, and enter diskutil list, then look for the disk ident of the Preboot volume of the disk that you want to update the label. e.g. In your case, you should see something like APFS Volume Catalina SSD - Data, then one line below it, you should see that Preboot volume's disk ident. In the below example, the Preboot volume ident is disk5s2

2) In terminal, enter diskutil mount diskXs2 (replace the X with your own disk ident), in my example, that will be disk5s2

3) In Finder, go to the top left menu bar, select Go

4) Select Go to Folder

5) Enter /Volumes/preboot/, then press Enter

6) One of the folder will be named with UUID, go into that one

7) Further go to /System/Library/CoreServices/ then press Command + Shift + . (Command + Shift + dot) to show the hidden files. Then copy the .disk_label.contentDetails to your desktop

8) Open this file with TextEdit, and change the content inside to the label you want. e.g. In your case, you may use Catalina. Then save change, and copy this file back to the Preboot volume to replace the original file.

9) Press Command + Shift + . again to hide the hidden files.

And now, when you reboot, the OpenCore boot picker should show you the disk name you want.

 

[polanskiman]

AFAIK, this is cosmetic, and this behaviour base on the Apple server side's response. Not user's error.

Ok but I see other people's 'About this mac' that says Mac Pro (early 2009). How is that possible? Can I change it manually?

Also noticed another odd thing. Today just got this usual welcome notification when you install a new OS. This said the welcome page was for imac Pro. What's up with that ?

 

[h9826790]

Ok but I see other people's 'About this mac' that says Mac Pro (early 2009). How is that possible? Can I change it manually?

Also noticed another odd thing. Today just got this usual welcome notification when you install a new OS. This said the welcome page was for imac Pro. What's up with that ?

That can be changed by editing a system file. e.g. I can make that "Early 2009" become "OpenCore 0.9.5".

All you need to do is just copy the com.apple.SystemProfiler.plist from ~/Library/Preferences/ to your desktop.

Open it with Text Editor. Then you can manually change that "Mac Pro" entry to whatever you want.

And then put the file back into ~/Library/Preferences/ and reboot.

That year label is coming from the Apple server, they decode the serial number, then should make macOS show the year info in About this Mac automatically. However, for unknown reason, they suddenly stop this recently for some computer. AFAIK, no one figured out their logic yet. We only know some cMP shows the year, some others don't.

 

[polanskiman]

That can be changed by editing a system file. e.g. I can make that Early 2009 become OpenCore 2009.
View attachment 2305832All you need to do is just copy the com.apple.SystemProfiler.plist from ~/Library/Preferences/ to your desktop.
View attachment 2305833
Open it with Text Editor. Then you can manually change that "Mac Pro" entry to whatever you want.
View attachment 2305834And then put the file back into ~/Library/Preferences/ and reboot.

That year label is coming from the Apple server, they decode the serial number, then should make macOS show the year info in About this Mac automatically. However, for unknown reason, they suddenly stop this recently for some computer. AFAIK, no one figured out their logic yet. We only know some cMP shows the year, some others don't.

I did try that mod yesterday to no avail. It just kept saying Mac Pro. In fact the file already had Mac Pro (early 2009) written on it before I edited it.

 

[h9826790]

Then please try to change the region, and see if that force the cMP to make a new entry and use it.

As you can see, there are two entries in my config, because I moved from Hong Kong to Japan.

 

[polanskiman]

This is what I have in the file before editing anything:

 

[polanskiman]

Then please try to change the region, and see if that force the cMP to make a new entry and use it.
View attachment 2305862

As you can see, there are two entries in my config, because I moved from Hong Kong to Japan.

Nope. File was neither updated nor recreated after the change of region. Wondering if deleting or renaming that file would force macOS to recreate it with default values.

 

[h9826790]

Nope. File was neither updated nor recreated after the change of region. Wondering if deleting or renaming that file would force macOS to recreate it with default values.

You may try. Do NOT delete it, but simply rename it to .bak, or just move the file to desktop, then reboot (you have to reboot to make any change in this file active. Even long out / in won't work)

AFAIK, worst case is just that you can't open that About this Mac window, until the file is recovered. No actual danger or system crash etc.

 

[MacGarage]

correct

I successfully upgraded my 2010 from OS 11.2.2 to OS 12.7.1, following this without any issues. Thanks!

 

[polanskiman]

You may try. Do NOT delete it, but simply rename it to .bak, or just move the file to desktop, then reboot (you have to reboot to make any change in this file active. Even long out / in won't work)

AFAIK, worst case is just that you can't open that About this Mac window, until the file is recovered. No actual danger or system crash etc.

If you delete/rename/move the file, it will always get recreated once you go to "About this Mac" after a reboot (I could replicate this reliably), albeit with default and minimal values. I tried hacking it around and changing some values but it still refuses to show me any custom name in the model name. I am also not sure what makes the OS update that file. Once created I wasn't able to reliably make macOS update it when changing multiple settings in System Preferences.

I did the same hack on my MacBook Pro that was only showing MacBook Pro for some reason as well and I was eventually able to make it show 'MacBook Pro (Retina, 15 inch, mid 2015)' by simply removing some old entries in the CPU name field. So I am not sure what is going on with the Mac Pro.

 

[basslik]

I had to make this change to get the stock WIFI card working using Martin’s 0.7.0 package.

Will this method work on my original stock Wi-Fi for Monterey?

 

[h9826790]

Will this method work on my original stock Wi-Fi for Monterey?

Most likely not