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

[startergo]

OK. I've just verified this with an Apple wired mouse connected directly (rather than connected to the Apple wired keyboard).

I have the mouse connected to the keyboard and only the keyboard connected to the USB port. Second issue is freeze of certain Apps with some devices. For instance I have a USB Bluetooth, which if connected freezes ioregistry explorer and some other Apps. My iPad sometimes freezes apps when I connect it to a USB 3 PCIE card. I might have fixed that issue with the USB map kext.
This patch provides a USB1.1 support. We might want to take a look at it:

GitHub - SuperBox64/bigmac: Big Mac, macOS 11 Big Sur and macOS Monterey disk installer and back up tool for Intel based Macs

Big Mac, macOS 11 Big Sur and macOS Monterey disk installer and back up tool for Intel based Macs - SuperBox64/bigmac

github.com

 

[TECK]

One of the issues is that if you have a keyboard and mouse connected directly to the USB ports (front or back) and unplug/reconnect the cable it will not reinitialize.

I'm using a wired Apple keyboard plugged in front USB, it is properly detected and everything works properly for me after an unplug/plug. I'm actually typing this with the wired USB keyboard and use Hammerspoon to get notifications what is going on with anything in my Mac.

When removed, my Mac sees the wired Apple keyboard as Hub:

When I plug it back, I can write fine with the wired keyboard. I use an original wired Apple keyboard plugged directly into front USB:

 

[Dayo]

This patch provides a USB1.1 support.

The code apparently came from @jackluke.
He might be able to give pointers.

 

[startergo]

I'm using a wired Apple keyboard plugged in front USB, it is properly detected and everything works properly for me after an unplug/plug. I'm actually typing this with the wired USB keyboard and use Hammerspoon to get notifications what is going on with anything in my Mac.

View attachment 1709391

When removed, my Mac sees the wired Apple keyboard as Hub:

View attachment 1709394

When I plug it back, I can write fine with the wired keyboard. I use an original wired Apple keyboard plugged directly into front USB:

View attachment 1709384

I am using the older plastic keyboard.

The code apparently came from @jackluke.
He might be able to give pointers.

I was inspecting the code last night. It looks like there is a patched kext.

 

[h9826790]

This USB problem seems mainly affect USB 1.1 device (when connect directly to a USB 2.0 port).

Since the USB wired keyboard in post #6183 has a build in USB 2.0 hub, that must be a USB 2.0 device, but not 1.1.

I think we should confirm if anyone has any USB 2.0 device connection issue so far?

This can eliminate some confusions, and clarify what problem we are actually facing.

 

[Dayo]

It looks like there is a patched kext.

Seems he stopped working on it a while ago in favour of the USB mapping approach the OCLP adopted.

Seems the reasons were:

macOS 11 Big Sur on Unsupported Macs Thread

khronokernel made a very advanced OpenCore setup that also remapped Legacy USB devices for spoofing BigSur supported Mac, so if you want to use BigSur OTA updates, don't apply any kext or framework patch, because those break the OTA update feature that requires: - Sealed System Volume (locked...

forums.macrumors.com

Work on OCLP has been suspended apparently due to headaches from extensive spoofing.

Not sure if the issues actually affect cMP

 

[startergo]

Seems he stopped working on it a while ago in favour of the USB mapping approach the OCLP adopted.

Seems the reasons were:

macOS 11 Big Sur on Unsupported Macs Thread

khronokernel made a very advanced OpenCore setup that also remapped Legacy USB devices for spoofing BigSur supported Mac, so if you want to use BigSur OTA updates, don't apply any kext or framework patch, because those break the OTA update feature that requires: - Sealed System Volume (locked...

forums.macrumors.com

Work on OCLP has been suspended apparently due to headaches from extensive spoofing.

Not sure if the issues actually affect cMP

I am using the USB map, but that does not help:

IONameMatch wrong for AMD matisse chipset USB controller · Issue #20 · corpnewt/USBMap

The name of the controller does not match the name of its container (not sure if that's the correct term), so IONameMatch tries to insert ports (and also the power settings I included) at the wrong...

github.com

StarPlayrX/bigmac: Big Mac 🍔 🍟 The macOS 11 Big Sur patch tool designed For Mac Pro 2008, 2009, 2010, 2012. Models 3,1 4,1 and 5,1. (github.com)

USB 2.0​

• Input devices that get disconnected do not reconnect. Workaround, use a USB 2.0/3.0 hub. Plug that into a Mac USB port and plug your input devices into the hub. This has been tested. USB 3.0 PCIe cards will also work but not at boot time.
• USB storage devices are hotswapped with issue.
• Certain thumb drives via USB 3.0 PCIe card, some will disconnect on idle. USB Thumb drives tend to not work on USB 2.0 unless seen at boot time.

Also my ASMEDIA USB3.2 PCIE card works for hot swapping, but I cannot wake from sleep if the keyboard/mouse are connected there.

 

[PeterHolbrook]

This USB problem seems mainly affect USB 1.1 device (when connect directly to a USB 2.0 port).

Since the USB wired keyboard in post #6183 has a build in USB 2.0 hub, that must be a USB 2.0 device, but not 1.1.

I think we should confirm if anyone has any USB 2.0 device connection issue so far?

This can eliminate some confusions, and clarify what problem we are actually facing.

I haven't used Big Sur extensively yet, and I don't have any USB 1.x devices. Perhaps that's why I haven't noticed any problems with USB 2.x or 3.x devices (the latter, connected via Thunderbolt). I've connected USB 2.0 flashdrives to the front USB sockets of the Mac Pro 5,1, and, along with a USB 3.0 SATA disk hub, a USB 3.0 Blu-ray disc writer and several USB 3.1 flash drives via a USB-C/3.2 hub. No problems whatsoever, but, as I've pointed out, my experimentation has been rather limited.

 

[startergo]

Another issue with the USB devices that the disconnect on sleep/wake up.

 

[Paolo-Sp]

Things are starting to look better for Big Sur and the classic Mac Pro: This week, WhateverGreen was updated to enable DRM on Big Sur systems with older CPUs and supported AMD GPUs (many thanks to Acidanthera developer vit9696), and based on this development, NightShiftEnabler was rewritten for Big Sur compatibility. The kexts should be available with next month's releases.

Hello, please is it possible to bring NightShiftEnabler 1.1 compiled ".kext" online?
I would like to test it with LILU 1.5.1 pre-release. that I just found.
Thanks

 

[TECK]

Hello, please is it possible to bring NightShiftEnabler 1.1 compiled ".kext" online?

Just clone the Git repo and run xcodebuild on master. You do the same for Lilu no? For OpenCore is different, I have a simple tutorial to follow.

 

[startergo]

Hello, please is it possible to bring NightShiftEnabler 1.1 compiled ".kext" online?
I would like to test it with LILU 1.5.1 pre-release. that I just found.
Thanks

You can use this script:

#!/bin/bash
#

echo ":D"
xcode-select --install

clear

echo "##### !!! DOWNLOADING FILES !!! #####"
mkdir /$HOME/Desktop/OC
cd /$HOME/Desktop/OC

echo "##### !!! COPY LILU TO FOLDERS !!! #####"

git clone https://github.com/acidanthera/Lilu
cd /$HOME/Desktop/OC/Lilu
git clone https://github.com/acidanthera/MacKernelSDK
cd /$HOME/Desktop/OC

Git clone https://github.com/cdf/NightShiftEnabler

xcodebuild -project ./Lilu/Lilu.xcodeproj -configuration Debug clean build ARCHS=x86_64 ONLY_ACTIVE_ARCH=YES CONFIGURATION_BUILD_DIR=/$HOME/Desktop/OC/Release

cd /$HOME/Desktop/OC
cp -r ./Release/Lilu.kext ./NightShiftEnabler

mkdir /$HOME/Desktop/OCRelease
cd /$HOME/Desktop/OCRelease

echo "##### !!! START BUILD FILES !!! #####"

cd /$HOME/Desktop/OC/NightShiftEnabler/
git clone https://github.com/acidanthera/MacKernelSDK
xcodebuild CONFIGURATION_BUILD_DIR=/$HOME/Desktop/OCRelease

echo "##### !!! DONE !!! #####"

 

[h9826790]

Another issue with the USB devices that the disconnect on sleep/wake up.

I think this is a long time issue since Apple change the logic to cut all PCIe power during sleep.

Not OpenCore or Big Sur related, and I believe there is nothing we can do about it.

 

[Macschrauber]

In some circumstances a powered usb hub helps

 

[Paolo-Sp]

Thanks everyone for the answers.
Now I show you what happens
1) Start with config1, use BoardProduct = Mac-7BA5B2D9E42DDD94 (iMac Pro) and load video card and all necessary kext including Lilu 1.5.0 and NightShiftEnabler 1.0
- OC boot menu then black apple and black line
- At a certain point black screen then reappears apple but white with black line and at the end user login Big Sur
- Obviously NightShift is not working
2) Start with config2, use BoardProduct = Mac-27AD2F918AE68F61 (Mac Pro 7.1) does not load video card and I only use AppleMCEReporterDisabler
- OC boot menu then black apple and black line
- At a certain point black screen then reappears apple but white with black line and at the end user login Big Sur
- Obviously NightShift is not working
3) Start with config3, use BoardProduct = Mac-27AD2F918AE68F61 and SystemProductName = MacPro7,1 (full Mac Pro 7.1), does not load video card and I only use AppleMCEReporterDisabler
- OC boot menu then black apple and black line
- At a certain point black screen then reappears black apple with black line and at the end user login Big Sur
- NightShift works
4) If I start with config1, I use BoardProduct = Mac-7BA5B2D9E42DDD94 (iMac Pro) and load video card and all necessary kext including Lilu 1.5.1 and NightShiftEnabler 1.1
- OC boot menu then black apple and black line
- At a certain point black screen then reappears apple but white with black line and at the end user login Big Sur
- NightShift works but and obviously also the fans and temperature sensors OK but, the fact of the white apple does not convince me, surely something is not yet working in the DRM

 

[Paolo-Sp]

When I start up my Mac Pro 5.1, a screen as indicated below appears briefly with Opn Core, then load the OC one as in the first photo of my previous message. Depends on what? Can I not make it appear?

 

[rx78]

I've installed Windows 10 using the guide in post 1 and up to now it's been running fine until recently where it'll refuse to boot and throws up an error code 0xc000000f that suggests a boot configuration issue.

I've googled and most of the solutions involve going into advanced start up or using command prompt to use bootrec to repair the boot record, both of which seem to be unavailable with my install.

WinRE is disabled in my install, and apparently enabling that might allow advanced start up to let me access command prompt but I'm worried this will adversely affect the Mac as I'm not sure it'll be booting through OpenCore (and then messing up the NVram or whatever it's called, name escapes me!)

Any Windows users here can chime in? Cheers

 

[hot-gril]

Thanks for the guide. I got OpenCore working with a patched Big Sur boot drive, an AHCI M.2 SSD, on my dual-CPU MacPro4,1 upgraded to 5,1 firmware. But then I tried enabling video acceleration for my RX580 like described, and now my machine gets stuck with a black screen at boot, sometimes turning off by itself.

It even happens when I remove the disk that has OpenCore's EFI on it. And if I keep in the OpenCore disk, remove the M.2 SSD with Big Sur, and leave in an old disk that has High Sierra on it, I get the OpenCore boot screen, then it boots as normal. I tried the usual PRAM and SMC resets in between boots. I don't understand, how could the presence of the M.2 SSD have any effect on my boot screen?

Edit: Ignore, I think it's something else. The machine is behaving too inconsistently for me to gather clues. Also realized my OpenCore was out of date, which might've been a problem with the accel kexts. I'll go back to what I was trying.

Edit 2: Ok... For some reason, it doesn't like the DVD drive SATA ports are connected to two SSDs, which have no data on them. It shuts off mid-chime. I feel like it's a lack of power or something. Without them, everything works great!

 

[Paolo-Sp]

Thanks for the guide. I got OpenCore working with a patched Big Sur boot drive, an AHCI M.2 SSD, on my dual-CPU MacPro4,1 upgraded to 5,1 firmware. But then I tried enabling video acceleration for my RX580 like described, and now my machine gets stuck with a black screen at boot, sometimes turning off by itself.

It even happens when I remove the disk that has OpenCore's EFI on it. And if I keep in the OpenCore disk, remove the M.2 SSD with Big Sur, and leave in an old disk that has High Sierra on it, I get the OpenCore boot screen, then it boots as normal. I tried the usual PRAM and SMC resets in between boots. I don't understand, how could the presence of the M.2 SSD have any effect on my boot screen?

Edit: Ignore, I think it's something else. The machine is behaving too inconsistently for me to gather clues. Also realized my OpenCore was out of date, which might've been a problem with the accel kexts. I'll go back to what I was trying.

Edit 2: Ok... For some reason, it doesn't like the DVD drive SATA ports are connected to two SSDs, which have no data on them. It shuts off mid-chime. I feel like it's a lack of power or something. Without them, everything works great!

I have RX580 flash, but acceleration in config.plist no change. See / download my file from 6198 message

 

[startergo]

I've installed Windows 10 using the guide in post 1 and up to now it's been running fine until recently where it'll refuse to boot and throws up an error code 0xc000000f that suggests a boot configuration issue.

I've googled and most of the solutions involve going into advanced start up or using command prompt to use bootrec to repair the boot record, both of which seem to be unavailable with my install.

WinRE is disabled in my install, and apparently enabling that might allow advanced start up to let me access command prompt but I'm worried this will adversely affect the Mac as I'm not sure it'll be booting through OpenCore (and then messing up the NVram or whatever it's called, name escapes me!)

Any Windows users here can chime in? Cheers

try starting WIndows more than 3 times in a row and it will offer repair options.

 

[joevt]

I've googled and most of the solutions involve going into advanced start up or using command prompt to use bootrec to repair the boot record, both of which seem to be unavailable with my install.

Isn't the repair option on the Windows installer USB?

 

[rx78]

try starting WIndows more than 3 times in a row and it will offer repair options.

That's how I've been booting it. It did try automatic repair but now it's stopped doing that.

 

[rx78]

Isn't the repair option on the Windows installer USB?

Guess I'll have to redo the installer USB.

 

[cdf]

- At a certain point black screen then reappears apple but white with black line

This is probably a Big Sur thing because it happens late in the boot process. Enabling the black bootscreen (which supported Macs have) would fix this annoyance.

surely something is not yet working in the DRM

That's because DRM on Big Sur only works by enabling "unfairgva" on a prerelease of WhateverGreen. On the next official release, I will update the wiki with the details.

When I start up my Mac Pro 5.1, a screen as indicated below appears briefly with Opn Core, then load the OC one as in the first photo of my previous message. Depends on what? Can I not make it appear?

There are two issues here. First, "PlayChime" should be configured as

<key>PlayChime</key>
<string>Disabled</string>

rather than

<key>PlayChime</key>
<false/>

Second, the message about APFS is a well-known issue dating back to High Sierra. This annoyance happens when using a flashed graphics card.

Guess I'll have to redo the installer USB.

Perhaps try recreating the boot files using the installer. The commands are the same as those described in the guide.

 

[Dayo]

It becomes the "9999.99.99.99.99" trick then

I tried before the 4 digit number and it only accepts the 3 digit number with the cMP SMBIOS, Also it did not change anything.

Do you think this will not work then ... or only on non-cMP: