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

[djangovic]

Thanks for the reply. I got OpenCore installed. Finally got the boot selector to show up. So now I am trying to install Windows 10. I followed the steps and tried 3 different USB drives, but none of them show up in the boot selector.
I used Mac to format the USB into the exFat MBR, copied the windows iso with rsync to the USB. Updated the config and copied over the exFatDxeLegacy.efi to the drivers folder and added the line to the drivers array in config. Not sure what I am doing wrong.
Edit: I figured it out, there is a mistake for following the copy command too closely.

~ % rsync -r /Volumes/CCCOMA_X64/ /Volumes/USB


rsync: link_stat "/Volumes/CCCOMA_X64/." failed: No such file or directory (2)


rsync error: some files could not be transferred (code 23) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/main.c(996) [sender=2.6.9]

i always geht this answer when I try. I did all the previous steps. Could you help me out with that?

 

[h9826790]

Euuuh not sure I understand what you meant, the MacPro has 8 slots right.. So right now I have managed to run 128GB filled in this oder 1-3 ; 5-7 it is still 4 slots and 4 DIMMs then when I get the other sticks it will be filled with the remaining which will be 2-4 ; 6-8 .. on the board you still read 1;2;3;4 -- 5;6;7;8 --

Unless I overlooked,

Ok, got it. Confusion due to the numbers expression.

In my city, 1-3 means “from 1 to 3”, therefore, it means you filled all slot 1,2 and 3.

That’s why I want to confirm if you mean the DIMM were filled in slot 1,3,5,7 in the first message.

 

[h9826790]

Anyway, it’s an amazing break through already. Even still “just” 128GB, but able to use 32GB DIMM is already a big achievement.

 

[205Maxi]

Ok, got it. Confusion due to the numbers expression.

In my city, 1-3 means “from 1 to 3”, therefore, it means you filled all slot 1,2 and 3.

That’s why I want to confirm if you mean the DIMM were filled in slot 1,3,5,7 in the first message.

Ohhh yeah I am sorry very sorry, you are about right ... My bad for confusing you..

What a great machine...

 

[jackluke]

After booting through OpenCore and in Tools enabled Auxiliary, adding BootKicker.efi and selecting it does work exiting from opencore to the apple startup manager, but after selected any bootable drive only a green screen is shown. Does anyone know how to fix this BootKicker.efi green screen issue ?

 

[205Maxi]

Anyway, it’s an amazing break through already. Even still “just” 128GB, but able to use 32GB DIMM is already a big achievement.

Yeah I know that's amazing, I would love to be able to correct the memory tab showing green. and also the PCIe Cards Tab, I am pretty sure we can do something about it...

I had it working under Catalina everything was showing green check with 128GB of ram...

 

[205Maxi]

After booting through OpenCore and in Tools enabled Auxiliary, adding BootKicker.efi and selecting it does work exiting from opencore to the apple startup manager, but after selected any bootable drive only a green screen is shown. Does anyone know how to fix this BootKicker.efi green screen issue ?

I never got that I should try and report to see if I am getting the same thing.

Hold on..

 

[205Maxi]

Anyway, it’s an amazing break through already. Even still “just” 128GB, but able to use 32GB DIMM is already a big achievement.

The only thing I am trying to get is the ECC enabled, and as of now I am getting it disabled.
and these are 32GB sticks with ECC registered.

 

[cdf]

After booting through OpenCore and in Tools enabled Auxiliary, adding BootKicker.efi and selecting it does work exiting from opencore to the apple startup manager, but after selected any bootable drive only a green screen is shown. Does anyone know how to fix this BootKicker.efi green screen issue ?

This must be for a Mac Pro with a flashed graphics card or a Mac other than a Mac Pro. BootKicker does not work at all on a Mac Pro without a flashed graphics card because of a missing protocol, which still hasn't been identified.

 

[startergo]

After booting through OpenCore and in Tools enabled Auxiliary, adding BootKicker.efi and selecting it does work exiting from opencore to the apple startup manager, but after selected any bootable drive only a green screen is shown. Does anyone know how to fix this BootKicker.efi green screen issue ?

Not really. Sorry.

Apple BootPicker support · Issue #692 · acidanthera/bugtracker

I believe we should implement the support of running Apple BootPicker in firmwares where it is available as an alternative to our current UI. This will require the following changes: Add ExternalPi...

github.com

Allow Running BootKicker from Boot Picker and Fix Vague Documentation · Issue #1084 · acidanthera/bugtracker

Allow Running BootKicker from Boot Picker It seems at the moment that the only way to run BootKicker is to bless it directly and that it is Noop when attempted as anyother tool from the boot picker...

github.com

 

[jackluke]

This must be for a Mac Pro with a flashed graphics card or a Mac other than a Mac Pro. BootKicker does not work at all on a Mac Pro without a flashed graphics card because of a missing protocol, which still hasn't been identified.

I am using a MacBookPro with stock dualGPUs graphics and get that BootKicker green screen.

 

[startergo]

I am using a MacBookPro with stock dualGPUs graphics and get that BootKicker green screen.

you can reply to this issue:

Allow Running BootKicker from Boot Picker and Fix Vague Documentation · Issue #1084 · acidanthera/bugtracker

Allow Running BootKicker from Boot Picker It seems at the moment that the only way to run BootKicker is to bless it directly and that it is Noop when attempted as anyother tool from the boot picker...

github.com

@vit9696 mentioned it was working on his MBP12,1 although that one only uses Intel Iris 6100 and that maybe the difference.

 

[jackluke]

you can reply to this issue:

Allow Running BootKicker from Boot Picker and Fix Vague Documentation · Issue #1084 · acidanthera/bugtracker

Allow Running BootKicker from Boot Picker It seems at the moment that the only way to run BootKicker is to bless it directly and that it is Noop when attempted as anyother tool from the boot picker...

github.com

@vit9696 mentioned it was working on his MBP12,1 although that one only uses Intel Iris 6100 and that maybe the difference.

Mine is MBP6,2 dual GPUs IntelHDGraphics and Nvidia GT 330 M , default resolution 1680x1050 , but even if scaled 1440x900 is acceptable , currently using BootKicker.efi from opencore menu, after apple boot picker correctly showed selecting any bootable macOS drive getting a green screen and after some seconds returns to opencore menu, since are used stock GPUs, maybe this issue is related to OpenCanopy.efi ?

edit:
It's not a OpenCanopy issue, just tested with Builtin opencore text mode, text menu correctly showed but selecting a volume still getting green screen with BootKicker, then automatically returns after 10 seconds to opencore menu.

 

[paalb]

hello, i have the issue that i can't get the "config.plist: OK". It says that that the file does not exist or is not readable. Any ideas what i'm doing wrong?

Try this:
Open Terminal.
Write: cd
Add space behind.
Drag the folder from Finder that contains config.plist into terminal.
Hit Return or Enter.

Now you are in the right place and can run the plutil command. I recommend copy/pasting it from the guide.

 

[HuRR]

Just saw that 0.6.3 was released. Is there anything that needs to change in order to run Big Sur? I saw that 11.0.1 had some changing to spoofing. I was planning to just use @h9826790's package to go from 0.6.2 to 0.6.3.

 

[h9826790]

Just saw that 0.6.3 was released. Is there anything that needs to change in order to run Big Sur? I saw that 11.0.1 had some changing to spoofing. I was planning to just use @h9826790's package to go from 0.6.2 to 0.6.3.

I adopted cdf's findings in my pre-configured package (all credits go to him). Which should allow you to run Big Sur by default.

If everything works as expected, then all you need to do is just turn on the VMM flag to install / update Big Sur. But of course, until Big Sur release officially, nothing can be confirmed.

 

[cdf]

If everything works as expected, then all you need to do is just turn on the VMM flag to install / update Big Sur.

Actually, you should be able to install Big Sur from Catalina without VMM.

 

[startergo]

Mine is MBP6,2 dual GPUs IntelHDGraphics and Nvidia GT 330 M , default resolution 1680x1050 , but even if scaled 1440x900 is acceptable , currently using BootKicker.efi from opencore menu, after apple boot picker correctly showed selecting any bootable macOS drive getting a green screen and after some seconds returns to opencore menu, since are used stock GPUs, maybe this issue is related to OpenCanopy.efi ?

edit:
It's not a OpenCanopy issue, just tested with Builtin opencore text mode, text menu correctly showed but selecting a volume still getting green screen with BootKicker, then automatically returns after 10 seconds to opencore menu.

} else {
    //
    // Green. BootPicker started but returned.
    //
    Pixel.Pixel.Green = 0xFF;
  }

The bootkicker code Uses different colors for errors, but as I said earlier there is no solution yet. You may still report it as it is not only a MacPro issue.

 

[HuRR]

I adopted cdf's findings in my pre-configured package (all credits go to him). Which should allow you to run Big Sur by default.

If everything works as expected, then all you need to do is just turn on the VMM flag to install / update Big Sur. But of course, until Big Sur release officially, nothing can be confirmed.

Thanks! This is helpful. I will update and let you know if there are any issues.

Actually, you should be able to install Big Sur from Catalina without VMM.

I have Big Sur installed on a separate drive already. I'm on whatever the last beta was before 11.0.1.

Edit: Spelling

 

[jackluke]

} else {
    //
    // Green. BootPicker started but returned.
    //
    Pixel.Pixel.Green = 0xFF;
  }

The bootkicker code Uses different colors for errors, but as I said earlier there is no solution yet. You may still report it as it is not only a MacPro issue.

Is possible to add and enable in Tools Auxiliary any refind.efi (also in text mode) ?

I tested some refind from opencore but similar BootKicker behavior after selection it returns to opencore menu, I'd need booting from opencore then exiting from opencore and load refind or apple startup manager to select a macOS drive.

 

[jackluke]

I noticed that opencore 0.6.3 is released, could someone explain this feature ?

• Increased slide allocation reserve to 200 MB for Big Sur beta 10

 

[startergo]

Is possible to add and enable in Tools Auxiliary any refind.efi (also in text mode) ?

You can do it, but @Dayo rEFInd uses the same upstream libraries as OC and the result will be the same.

 

[jackluke]

You can do it, but @Dayo rEFInd uses the same upstream libraries as OC and the result will be the same.

But could you link any refind.efi version in text mode that loads from OpenCore Tools Auxiliary ?

I ask this because I guess the issue to load refind after opencore is similar to BootKicker .

 

[h9826790]

Actually, you should be able to install Big Sur from Catalina without VMM.

But from Mojave to Catalina / Big Sur, still need VMM, correct?

 

[startergo]

But from Mojave to Catalina / Big Sur, still need VMM, correct?

No VMM only firmware features and firmware mask from iMacPro1,1 (and board-id)