Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
you should rather ask your questions in a hackintosh forum
all here is for a real mac pro
not exactly friendly or helpful and since its the hackintosh community keeping your **** alive a little give and take I think into too much to ask.... what say you...
[automerge]1588429754[/automerge]
The first issues encountered when using false SMBIOS with valid serial number : iMessage will blocked eventually.

This was intended testing when I running hackintosh, tested on El Capitan back then. I only get so far because I am afraid my Apple account/ valid Mac Pro serial being flagged or blocked (I am emulated 6,1 with 5,1 serial). It might run just OK when Apple ID not signed, but not sure for long run.

off topics : I am curious and planning another test using valid serials from EOL/obsolete Macs. Having some of G5 and G4 case conversion, they still retain genuine serials on their enclosure and how happened if I marred them using today’s supported Mac SMBIOS. Might use dummy Apple account this time.


yes.. but keeping the system definition as a MacPro5,1 (and still reported that way in About This Mac) and keeping already working 5,1 serial and other smbios 5,1 parameters other than board-id... seems to be working for you guys in open core .. only difference is I am editing it with clover boot loader instead

I have not yet moved up to catalina so CPU spoofing is not needed... but its a supported westmere chip so I will cross that bridge in the future if/when I go to catalina..

when I changed the board-id to iMac Pro and removed the boot flag method to inject it.. I didn't even have to re-log into iCloud.. and iMessage debug tool didn't register any changes in my nvram keys so I 'think' iCloud / iMessage etc is safe for now

I am more interested in how the frameworks and kexts weave together... hackintoshing its always been critical to get the smbios right otherwise cpu power management and chipset calls etc would be broken..

and lets be clear... while you walk with the swagger of running real apple gear.. you are all hackintoshers now... since by definition you are running apple software on hardware not approved for such software ...

so welcome to hackintoshing...
 
Last edited:
  • Like
Reactions: leoaf79
The first issues encountered when using false SMBIOS with valid serial number : iMessage will blocked eventually.

This was intended testing when I running hackintosh, tested on El Capitan back then. I only get so far because I am afraid my Apple account/ valid Mac Pro serial being flagged or blocked (I am emulated 6,1 with 5,1 serial). It might run just OK when Apple ID not signed, but not sure for long run.

off topics : I am curious and planning another test using valid serials from EOL/obsolete Macs. Having some of G5 and G4 case conversion, they still retain genuine serials on their enclosure and how happened if I marred them using today’s supported Mac SMBIOS. Might use dummy Apple account this time.

on you serial number question.. it doesn't have to be a valid serial in an 'apple' database somewhere.. we have found as long as the generated serial 1>has a proper pattern, 2> isn't already in the apple database (don't want to conflict with an already established account but if its YOUR serial and not going to use that machine again knock yourself out), 3 > that the machine boots with the same nvram keys (mostly a hackintosh nvram issue) etc.. there is no problem.. there is a good thread.. idiots guide to iMessage or something along those lines.. good read...
 
Use this guide:
Code:
sudo VBoxManage internalcommands createrawvmdk -filename "</path/to/file>.vmdk" -rawdisk /dev/disk#
Where /dev/disk# is the disk number where you will be installing Windows revealed by diskutil list. First, make sure the drive is connected and unmounted. Make sure Vbox machine is in UEFI mode:
View attachment 901686
Otherwise you will be installing it in MBR mode. Next, start virtualbox with sudo:
Code:
sudo VirtualBox
Attach the drive as explained in the article. Attach Windows.iso image downloaded from Microsoft.
Start installing Windows from the Virtualbox, but during first reboot power down the virtual machine from the virtual box as soon as you see some text on the screen. Do not let it reboot completely from there. Continue installing Windows once you reboot the cMP through the OC where you will select the Windows option. Do not boot Windows without OC. Later you can replace bootX64.efi file in the Windows EFI folder with the OC bootX64.efi and point to bootmgfw.efi (you need to find the location of this file in the Windows EFI folder either in the debug log or with devtree > devtree.txt, map -r > map.txt from UEFI shell)

Is there any way to install Windows 10 at the same Mac OS disk?

I have Catalina installed on an 1TB NVMe drive, and I’d like to set 256GB to install Windows.

I already tried this:
Repartitioned it, installed Winddows 10 (using Unebotin + bootcamp support files folder), but after the first reboot during install, OC doesn’t see the new OS.
 
Last edited:
There is any way to install Windows 10 at the same Mac OS disk?
Yes there is. Just create a FAT32 partition on the Catalina drive before creating Vbox drive out of it and follow the same instructions. Once you open the whole disk in Virtual box and you install Windows it will create the boot file in the ESP partition of the drive.
 
  • Like
Reactions: leoaf79
Other info
  • Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool)
  • If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then follow step 11 in this post.
  • If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
  • For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
  • If you applied my previous non-OpenCore HWAccel mod, please revert them. For Lilu + WEG method, that means delete Lilu.kext in /Library/EXtensions/ and reboot. For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework

Finally pulled the trigger and installed Opencore using the instructions. Everything works great! iTunes Movies work correctly and was happy to see h.265 encoding accelerated. (Not sure when I will use that regularly though). GREAT WORK EVERYONE. Thank you.

One question, which I couldn't find searching the thread.

Carbon Copy Cloner will clone the drive, just without the modified EFI components it appears(?)

I assume the cloned drive should still boot regularly, just without OpenCore, and I can reinstall the Opencore in the EFI if needed in case of disaster?

Anyway.. so exciting!
 
  • Like
Reactions: h9826790
Hey everyone! I just spent about 2 or so hours going through the thread and I just want to make sure that I have this all correct since my brain kinda feels like mush right now lol.

My current setup is a mid-2010 MacPro 5,1 running High Sierra and the new card I want to install is a NON-MODDED Sapphire Pulse RX580 8gb.

So my first step would be to use the High Sierra 10.13.6 installer to upgrade my BootROM to MP51.0089.B00
Then use the Mojave 10.14.6 installer to upgrade BootROM to 144.0.0.0.0
Then install the new RX580 and actually upgrade to Mojave.
Then backup my BootROM as well as cloning my boot drive to another HD (just in case).
Then I disable SIP and follow all the instructions in post #1314.
And after the final reboot, I should have Mojave up and running with the bootscreen and full hardware acceleration (H.264 and HEVC) on my brand new RX580.

Also: will I be able to get Sound output through the HDMI/DP ports on the RX580?

Thanks!
 
Hey everyone! I just spent about 2 or so hours going through the thread and I just want to make sure that I have this all correct since my brain kinda feels like mush right now lol.

My current setup is a mid-2010 MacPro 5,1 running High Sierra and the new card I want to install is a NON-MODDED Sapphire Pulse RX580 8gb.

So my first step would be to use the High Sierra 10.13.6 installer to upgrade my BootROM to MP51.0089.B00
Then use the Mojave 10.14.6 installer to upgrade BootROM to 144.0.0.0.0
Then install the new RX580 and actually upgrade to Mojave.
Then backup my BootROM as well as cloning my boot drive to another HD (just in case).
Then I disable SIP and follow all the instructions in post #1314.
And after the final reboot, I should have Mojave up and running with the bootscreen and full hardware acceleration (H.264 and HEVC) on my brand new RX580.

Also: will I be able to get Sound output through the HDMI/DP ports on the RX580?

Thanks!
Correct.

You can actually backup the BootROM BOTH before and after update to 0089.B00 and 144.0.0.0.0.
 
Hey everyone! I just spent about 2 or so hours going through the thread and I just want to make sure that I have this all correct since my brain kinda feels like mush right now lol.

My current setup is a mid-2010 MacPro 5,1 running High Sierra and the new card I want to install is a NON-MODDED Sapphire Pulse RX580 8gb.

So my first step would be to use the High Sierra 10.13.6 installer to upgrade my BootROM to MP51.0089.B00
Then use the Mojave 10.14.6 installer to upgrade BootROM to 144.0.0.0.0
Then install the new RX580 and actually upgrade to Mojave.
Then backup my BootROM as well as cloning my boot drive to another HD (just in case).
Then I disable SIP and follow all the instructions in post #1314.
And after the final reboot, I should have Mojave up and running with the bootscreen and full hardware acceleration (H.264 and HEVC) on my brand new RX580.

Also: will I be able to get Sound output through the HDMI/DP ports on the RX580?

Thanks!


you must insert the RX580 for upgrade to 144.x !

and if you want a bootscreen (bootpicker) and full HWacc > come with opencore install
 
Correct.

You can actually backup the BootROM BOTH before and after update to 0089.B00 and 144.0.0.0.0.

Awesome, thanks for the confirmation! And I will take your suggestion.
Also, thank you for posting and maintaining all of this information. I'd be lost without it.

you must insert the RX580 for upgrade to 144.x !

I just found that out today as I unsuccessfully tried to get the Mojave installer to update the firmware. My RX580 does not arrive until Monday so until then I gotta play the waiting game (so this is what life was like before 2-day Prime delivery, huh? lol).
 
Hi all

I upgraded to OpenCore 0.5.8 from 0.5.7 with the Lilu and WhateverGreen kexts and changes to the config file for the kexts. On rebooting, HWA was not enabled. HWA works when I downgrade back to OpenCore 0.5.7.

My question is: Has anyone had success with OpenCore 0.5.8 and HWA?

Cheers

Michael
 
Hi all

I upgraded to OpenCore 0.5.8 from 0.5.7 with the Lilu and WhateverGreen kexts and changes to the config file for the kexts. On rebooting, HWA was not enabled. HWA works when I downgrade back to OpenCore 0.5.7.

My question is: Has anyone had success with OpenCore 0.5.8 and HWA?

Cheers

Michael
My 0.5.8 package has everything included. Please just download -> unzip -> copy the whole EFI folder into position. There is no need to manage your own Lilu, WEG, or config.
 
Hi guys
I think I am missing something and could use some help please
Mac Pro 5,1 with open core 5.8
AMD560 4GB

and I have followed the guide to my knowledge but still can't get HW acceleration
I have attached a screen shot with my key text the plugins folder

Many thanks :)
 

Attachments

  • Screenshot 2020-05-07 at 13.23.23.png
    Screenshot 2020-05-07 at 13.23.23.png
    2.8 MB · Views: 144
  • Like
Reactions: jamjam1993
Boot picker (only support EFI systems, only tested with wired keyboard. Light grey background, black text, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
Sorry I'm just seeing this now... your package works with my Apple Bluetooth keyboard. Guess BT is implemented at a pretty low level - it worked with Apple's own boot picker when I had a GPU that could display it natively.
 
  • Like
Reactions: h9826790
Finally pulled the trigger and installed Opencore using the instructions. Everything works great! iTunes Movies work correctly and was happy to see h.265 encoding accelerated. (Not sure when I will use that regularly though). GREAT WORK EVERYONE. Thank you.

So, testing out encoding stuff into h.265 HEVC and see why it is such a big deal-- the files are sizes are so much smaller with the same or better quality. The accelerated encoding from FCPX (you have to add a Compressor Setting) and via ffWorks (ffmpeg with gui) makes it tolerable to play with this format moving forward.

Good stuff! So awesome that activating and unlocking this acceleration on the 5,1 with AMD cards really continues to add value to our workhorse Macs.
 
  • Like
Reactions: h9826790
So, testing out encoding stuff into h.265 HEVC and see why it is such a big deal-- the files are sizes are so much smaller with the same or better quality. The accelerated encoding from FCPX (you have to add a Compressor Setting) and via ffWorks (ffmpeg with gui) makes it tolerable to play with this format moving forward.

Good stuff! So awesome that activating and unlocking this acceleration on the 5,1 with AMD cards really continues to add value to our workhorse Macs.

Sorry, what setting should I add in Compressor?
Thanks
 
test:

15" 8k prores 4444

encode to H265 UHD 192kbs audio

apple compressor (videotoolbox) 35"
handbrake (videotoolbox) 1'50"



Screenshot 2020-05-08 at 18.58.52.jpg
 
Last edited by a moderator:
  • Like
Reactions: Chung123
can anyone illuminate why video toolbox / hardware encoding doesn't permit constant quality? average bitrate files are usually much larger codec for codec than constant quality as it can upshift and downshift bitrate depending on pixel shift activity.. ie busier scenes with more original pixels vs images where little changes ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.