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.
For Magic Mouse, that’s for charging only.

But for keyboard, that can become a wired keyboard. In fact, when you connected the keyboard via the Lightning cable. The keyboard shows inactive in the BT panel.
View attachment 1671758

Until you disconenct the Lightning cable, MacOS will show you the OSD that Magic keyboard connected via BT again.
View attachment 1671750

Or you can even completely switch off BT, but connect the keyboard via the Lightning cable, and it still works. Magic mouse doesn't have the same behaviour.
Actually I saw issues with BS and USB before. It would not recognize my keyboard and mouse attached to the keyboard's USB. That was mainly when I added iMacPro1,1 model name.
 
  • Like
Reactions: TECK
I am using a heavily upgraded cMP that started out life as a cMP 4,1 with 6 core dual processors and was upgraded to 6 core Westmere, a Saphire Radeon R580, AND an additional USB card with USB 3.0 ports (blue plastic).
Oh, OK. No Mac Pro will boot off an additional USB3 card, however any of the stock ports (front/rear) will all work.
And from what I have briefly read, it appears that upgrading Windows (I need Windows Pro) may require more knowledge than I currently have - none at all.

I would like to learn enough to not be dangerous to myself and others. Any suggestions?
I personally have had success with the VirtualBox method combined with removing the EFI\Boot folder from the Windows EFI partition. (using OC). Your mileage may vary.
 
Do we know what information macOS uses to determine if night shift is to be allowed or not? Seems most of these tweaks look at the board ID, but evidently that's not the case for night shift.

Does full spoofing including serial number make any difference?

Edit: read some more posts and I see that @cdf is looking into just that. I think I will go with 10.15.7 for now.
 
Last edited:
Yes. You plugged into one of the two front ports. Those are 1.0 ports identified by the white plastic.

When I started, I did not know that and plugged the keyboard and the trackball into the front two ports.

Since the 3.0 card was handy and I didn't know better, I plugged the USB, 3.0, blue plastic into one of those ports. They were seen by the computer, so I didn't give it another thought.

Then you suggested that I needed to use a 2.0 or slower. I didn't know how to identify the difference so I looked it up. White, 1.0; black, 2.0; blue, 3.0.

And I found that the two front ports were white, as were the original USB ports at the back. Once that was identified the process went forward.

I followed the procedure too, but unlike you, I put the USB stick in the wrong location.
Mac Pro 3.1 , 4.1 and 5,1 are USB 2.0. Apple doesn´t care about colors. The USB 3.0 of my Mac Mini are black.
 
I've tried to search for this (I suspect it has been asked before), but couldn't find the right post here, so forgive me for asking again (probably).

I've upgraded Mojave to Catalina, and my OpenCore is 0.6.3. Is there a way now to hide Big Sur update? My VMM flag is disabled, but I understand that OC now does something to allow updates anyway.
 
One thing I don't understand is the following. Before 0.6.3, Software Update didn't show me Catalina/Big Sur upgrade, because my Mac Pro is ineligible. To show Catalina, for example, I had to enable VMM flag. Now it shows Big Sur even with the VMM flag disabled.

And my friend with a Mac Pro still on Mojave has recently updated to OC 0.6.3 and started seeing Big Sur upgrade in Software Update.
 
I've upgrade my Mojave to BS and using OC 6.3 package from h9826790 :OC HW Acceleration

It does takes time and it reboot 3 or 4 times (can't recall) but some-times it does looks like it is stuck but it is not so be patient and let it finish.

What works:
- Video HW acceleration works (tested by playing Swordsmith video )
- Original WiFI and BT modules works using the https://github.com/khronokernel/IO80211-Patches
by following guides from EETagent: WiFI & BT kext patch

The only change I did from the original H98 OC package is disable the RadeonBoost.kext (by removing the setting in the OC config)

I experience issue with my account not able to be used as admin, fortunately it can be solved:
1. Go to recovery (choose BS recovery from the OC boot menu)
2. Once in recovery, open terminal and type:
Code:
rm "/Volumes/Macintosh HD/var/db/.applesetupdone"
3. Reboot to BS
4. Once boot you'll go through the steps as to newly setup the BS (don't worry your existing user will still exist)
and you'll be asked to add new user (Admin) and then once I logged using the newly created Admin user, I give my existing user the privilege to administer the computer.
 
  • Like
Reactions: Cerender
From memory, no report about Nano yet, but I believe only RX460 or above can provide HWAccel in MacOS.

Anyway, from your screen capture, the code for HWAccel isn’t working yet. Otherwise, you should see 3.5GHz but not 3.46GHz for the CPU speed.
Would be a bummer if there's no support for it, as it's a better card than most any of the other options until you get to RX580 and above. And I already have 3 of them. :D

I'm not sure what else I need to do for the HWAccel support in regards to the CPU speed. Any advice? Want to look at my config.plist or something?
 
I'm not sure what else I need to do for the HWAccel support in regards to the CPU speed. Any advice? Want to look at my config.plist or something?
That's nothing about CPU speed, but if you inject the required board ID correctly to activate HWAccel. The About This Mac will be changed the CPU speed presentation from 3 digit to 2 digit.

Therefore, you should see 3.5GHz, but not 3.46GHz anymore.
Official GPU name fix.png
 
i am running oc 0.6.3 and everything is working in big sur. the only thing which does not work ist night shift.
is there anything i can check why nightshift is not working?
i am using the hardware in my signature.
Thanks
With Big Sur NightShiftEnabler.kext not work, you can also disable it in the config.plist.
To activate night shift you need to add the string "SystemProductName" = "MacPro6,1" in the SMBIOS section into config.plist

<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>
A1QM4A==
</data>
<key>FirmwareFeaturesMask</key>
<data>
P/8f/w==
</data>
<key>SystemProductName</key>
<string>MacPro6,1</string>
</dict>
 
  • Like
Reactions: PeterHolbrook
Open Core Catalina according to post #1, working fine.

One question, how can I do NVRAM/PRAM reset now with the Graphical Boot Picker enabled? I can't seem to get the normal CMD_OPTION_P_R hold down to work now when going through the Graphical Boot picker...its just ignored. Any ideas that best way to be able to do that when I need to?

For some reason my Graphical Boot Picker has stopped responding to the arrow keys from my USB keyboard. It worked before, but recently I rebuilt my EFI from scratch after having messed it up...and this time around..the keyboard isn't work in Boot Picker to select the boot volume. The mouse works, so I can select the one I want and then wait for the timeout to boot it...but hitting the arrows or the RETURN key doesn't work in OpenCanopy now. I already tried to reset the SMC...can't figure out how to reset the NVRAM just in case that's it.
 
That's nothing about CPU speed, but if you inject the required board ID correctly to activate HWAccel. The About This Mac will be changed the CPU speed presentation from 3 digit to 2 digit.

Therefore, you should see 3.5GHz, but not 3.46GHz anymore.
View attachment 1672926
I totally get that it doesn't actually change the speed - just not sure why it's not working...
That's nothing about CPU speed, but if you inject the required board ID correctly to activate HWAccel. The About This Mac will be changed the CPU speed presentation from 3 digit to 2 digit.

Therefore, you should see 3.5GHz, but not 3.46GHz anymore.
View attachment 1672926
Okay, so progress, if you want to call it that!
I figured out why the cpu speed was not updating to the 2 digit indicator - I didn't have the UpdateSMBIOS setting changed to TRUE in my PLIST. I got that changed and the speed was listed as 3.5 BUT still no HW Accel, and more concerning, the machine hard locks if I try to open Microsoft Edge.
 
@cdf I implemented an easier way to convert Hex to Base64 data into plistlib generator. Example for FirmwareFeatures:

Code:
        'SMBIOS': {
            'BoardProduct': 'Mac-7BA5B2D9E42DDD94',
            'FirmwareFeatures': unhexlify_data('03 54 0C E0'),
            'FirmwareFeaturesMask': unhexlify_data('3F FF 1F FF')
        }

Translates to:
Code:
        <key>SMBIOS</key>
        <dict>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
            <key>FirmwareFeatures</key>
            <data>
            A1QM4A==
            </data>
            <key>FirmwareFeaturesMask</key>
            <data>
            P/8f/w==
            </data>
        </dict>

Now, all you have to do is input the actual Hex code into generator:

1605753235373.png
 
Last edited:
  • Like
Reactions: JedNZ and cdf
I totally get that it doesn't actually change the speed - just not sure why it's not working...

Okay, so progress, if you want to call it that!
I figured out why the cpu speed was not updating to the 2 digit indicator - I didn't have the UpdateSMBIOS setting changed to TRUE in my PLIST. I got that changed and the speed was listed as 3.5 BUT still no HW Accel, and more concerning, the machine hard locks if I try to open Microsoft Edge.
It should be working now. 99% of the cases are just the users haven’t refresh the detection in VideoProc and misinterpreted the indication.

I mentioned this is the HWAccel post Q&A section (post #1, Q29)
 
Last edited:
  • Like
Reactions: macnu
@h9826790 @startergo Have you found a way to disable the notification in Mohave telling Big Sur disk is invalid?
I think it’s unavoidable. There is no way for Mojave to support a “future” OS / file system. The most practical solution may be someone write a script to auto hide that notification. Or even auto in mount the associated partition after login.
 
  • Like
Reactions: TECK
With Big Sur NightShiftEnabler.kext not work, you can also disable it in the config.plist.
To activate night shift you need to add the string "SystemProductName" = "MacPro6,1" in the SMBIOS section into config.plist

<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>
A1QM4A==
</data>
<key>FirmwareFeaturesMask</key>
<data>
P/8f/w==
</data>
<key>SystemProductName</key>
<string>MacPro6,1</string>
</dict>
If you want to spoof the ident as well, it make much more sense to use the ident that match the board ID.

e.g. in this case, iMac Pro 1,1

But if the config is only for Big Sur, use the Mac Pro 7,1’s board ID and indent should be the best.

7,1 board ID can activate HWAccel, and activate all ports on the graphic card by default.

I haven’t use the 7,1 board ID in my public package mainly because want to keep the HWAccel support in Mojave.
 
  • Like
Reactions: w1z
I totally get that it doesn't actually change the speed - just not sure why it's not working...

Okay, so progress, if you want to call it that!
I figured out why the cpu speed was not updating to the 2 digit indicator - I didn't have the UpdateSMBIOS setting changed to TRUE in my PLIST. I got that changed and the speed was listed as 3.5 BUT still no HW Accel, and more concerning, the machine hard locks if I try to open Microsoft Edge.
For Edge, I really don’t know, never use it. How about other Chromium based browsers?
 
Have you found a way to disable the notification in Mohave telling Big Sur disk is invalid?

I think it’s unavoidable. There is no way for Mojave to support a “future” OS / file system. The most practical solution may be someone write a script to auto hide that notification.
Someone found a way already:
 
  • Like
Reactions: kkinto and TECK
Someone found a way already:
I think he mean how to suppress the notification when dual boot Mojave with another Big Sur drive onboard, then Mojave will warn the users about invalid disk. But not the "upgrade to Big Sur" notification.
 
  • Like
Reactions: startergo
I think he mean how to suppress the notification when dual boot Mojave with another Big Sur drive onboard, then Mojave will warn the users about invalid disk.
Yes that. I don't care about the Big Sur notification, :)
 
If you want to spoof the ident as well, it make much more sense to use the ident that match the board ID.

e.g. in this case, iMac Pro 1,1

But if the config is only for Big Sur, use the Mac Pro 7,1’s board ID and indent should be the best.

7,1 board ID can activate HWAccel, and activate all ports on the graphic card by default.

I haven’t use the 7,1 board ID in my public package mainly because want to keep the HWAccel support in Mojave.
Hi.
I used the SystemProductName of iMac Pro 1,1 like you mentioned and i got NightShift.
Thanks a lot.
 
  • Like
Reactions: h9826790
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.