Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

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.
I thought I got it mounted and put in: rsync -r /Volumes/CCCOMA_x64/ /Volumes/dev/disk5s1.
I hit return and got the following failure:
rsync -r /Volumes/CCCOMA_x64/ /Volumes/dev/disk5s1
rsync: mkdir "/Volumes/dev/disk5s1" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52.200.2/rsync/main.c(545) [receiver=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52.200.2/rsync/io.c(453) [sender=2.6.9]
 
wnlewis said:
rsync -r /Volumes/CCCOMA_x64/ /Volumes/dev/disk5s1
Click to expand...
You have to replace CCCOMA_x64 by the actual name of the volume that you see after mounting the ISO. Also, you have to use the name of your USB drive.

The Spirit said:
Any ideas why i do not see the new big sur release candidate while vmm enabled?
Thanks
Click to expand...
From which OS are you verifying this? From Big Sur 11.0.1 beta, you actually no longer need VMM to have the update appear. See post #4,399.
 
JeDiGM said:
Hey 205Maxi. So you got 384GB working? That's perfect. It's a triple channel CPU anyway. Personally, I was never going to use 8x64 anyway. From the screenshot you sent it looks like that's the limit you are hitting? Is that the issue you mean or is it something else? Are you saying it doesn't work because it's not reporting properly in the RAM section?
Click to expand...
I think he installed 8x32=256GB only, but coded 384GB in the config.plist, which makes the OS shows 384GB.

IMO, that's not a good idea. If that's purely cosmetic, it's fine.

But since we know that's actually doing something (otherwise, it can't make the 32GB DIMM work). Therefore, better to make it reflects the actual RAM config. At least, should config it to show 256GB (if a different than 8x32GB memory config is required to make it works).
 
  • Like
Reactions: JeDiGM
h9826790 said:
I think he installed 8x32=256GB only, but coded 384GB in the config.plist, which makes the OS shows 384GB.

IMO, that's not a good idea. If that's purely cosmetic, it's fine.

But since we know that's actually doing something (otherwise, it can't make the 32GB DIMM work). Therefore, better to make it reflects the actual RAM config. At least, should config it to show 256GB (if a different than 8x32GB memory config is required to make it works).
Click to expand...
You are correct, I have installed 256GB 32GB x 8. I have tried yesterday 512GB with 64GB module and I got the flashing light, which means the maximum we can put is 32GB Module, unless otherwise.

What the system shows it purely cosmetic, I have tried all the configuration possible, unless otherwise, to get the system show only 8 modules but it was not working and I got the warning, even though the Mac was functioning properly.

To not get the error notification, you need to Mac with 12 slots like the 2019 model. Unless the IOIIIO comes up with the kext, but I prefer the 12 slots rather than adding another kext.

I have also tried the Single Processor Tray with 32GBx4 and it worked too.

I can take picture of the dual and the single tray with the ram loaded too. But Hey I am here to report what worked.

Y'all take care..
 
Last edited:
  • Like
Reactions: M.Switch, ddhhddhh2, yurc and 1 other person
205Maxi said:
You are correct, I have installed 256GB 32GB x 8. I have tried yesterday 512GB with 64GB module and I got the flashing light, which means the maximum we can put is 32GB Module, unless otherwise.

What the system shows it purely cosmetic, I have tried all the configuration possible, unless otherwise, to get the system show only 8 modules but it was not working and I got the warning, even though the Mac was functioning properly.

To not get the error notification, you need to Mac with 12 slots like the 2019 model. Unless the MIIIO comes up with the kext, but I prefer the 12 slots rather than adding another kext.

I have also tried the Single Processor Tray with 32GBx4 and it worked too.

I can take picture of the dual and the single tray with the ram loaded too. But Hey I am here to report what worked.

Y'all take care..
Click to expand...

Thanks 205Maxi. Did you try with less DIMMs? 6x64GB or 2x64GB? Do you still get flashing light there? Is the RAM same rank, type, etc?

I wonder if it would work with Catalina any better?
 
205Maxi said:
You are correct, I have installed 256GB 32GB x 8. I have tried yesterday 512GB with 64GB module and I got the flashing light, which means the maximum we can put is 32GB Module, unless otherwise.

What the system shows it purely cosmetic, I have tried all the configuration possible, unless otherwise, to get the system show only 8 modules but it was not working and I got the warning, even though the Mac was functioning properly.

To not get the error notification, you need to Mac with 12 slots like the 2019 model. Unless the MIIIO comes up with the kext, but I prefer the 12 slots rather than adding another kext.

I have also tried the Single Processor Tray with 32GBx4 and it worked too.

I can take picture of the dual and the single tray with the ram loaded too. But Hey I am here to report what worked.

Y'all take care..
Click to expand...
I see.

Just curious did you try iMac Pro SMBIOS with 32GB DIMM? This is avoid the memory error notification by default.
 
  • Like
Reactions: JeDiGM
JeDiGM said:
Thanks 205Maxi. Did you try with less DIMMs? 6x64GB or 2x64GB? Do you still get flashing light there? Is the RAM same rank, type, etc?

I wonder if it would work with Catalina any better?
Click to expand...
I tried everything I could with the 64GB Module, and I was sad cause, I really thought it would work, but it seems that our MacPro does not like 64GB Modules...

It works with Catalina as well I have tested too.
 
I was running OC 6.1 flawlessly for 2 months, today installed the 6.3 because of supposed better NVMe support. The update went smoothly and so did the installation of a NVMe drive. Then I tried to make the disk internal and poof... no bootpicker at all, just plain old black screen.

My PCI ID for the drive was weird because it looked like this: "PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)" and all other PCI cards had only 3 sections like in the tutorial. I checked it twice with gfxutil and it still showed up like this so i continued and this change somehow messed up the config apparently. Any ideas what might have gone wrong? I'm in the process of installing pure OS on another drive to revert the config.plist (fortunately made a backup) but would like to do it properly next time.
 
burnthefires said:
I was running OC 6.1 flawlessly for 2 months, today installed the 6.3 because of supposed better NVMe support. The update went smoothly and so did the installation of a NVMe drive. Then I tried to make the disk internal and poof... no bootpicker at all, just plain old black screen.

My PCI ID for the drive was weird because it looked like this: "PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)" and all other PCI cards had only 3 sections like in the tutorial. I checked it twice with gfxutil and it still showed up like this so i continued and this change somehow messed up the config apparently. Any ideas what might have gone wrong? I'm in the process of installing pure OS on another drive to revert the config.plist (fortunately made a backup) but would like to do it properly next time.
Click to expand...
Do you use your customised 0.6.1 config.plist with OpenCore 0.6.3?
 
burnthefires said:
Yup, but as i said it booted fine with 0.6.3 and my 0.6.1 config, adding the make-internal section messed it up.
Click to expand...
Even your problem may not be directly related to this misbehaviour. You have to mod the 0.6.3 config.plist as per you need. NEVER use other version's config.plist.
 
h9826790 said:
Even your problem may not be directly related to this misbehaviour. You have to mod the 0.6.3 config.plist as per you need. NEVER use other version's config.plist.
Click to expand...
That's what i was concerned about, didn't want to do the whole HWaccel stuff and now i wasted some more time by my laziness.
 
burnthefires said:
That's what i was concerned about, didn't want to do the whole HWaccel stuff and now i wasted some more time by my laziness.
Click to expand...
You may try my config, which has HWAccel activated by default.
forums.macrumors.com

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 forums.macrumors.com
 
This might be a dumb question, but how do i force USB boot now that there is no bootscreen, no recovery partition and Mojave requires a Metal card for install (so cant really use my 5770 just for bootpicker)?

EDIT: Nevermind, used 5770 to set boot from USB and then switched cards
 
Last edited:
Big Sur will be officially released on Nov 12, what do we need to do to upgrade? @cdf if possible please provide also instructions for an USB stick Big Sur clean install. I will want to start everything fresh, with such major OS change.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back