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.
Hi Guys!

Successfully updated my Mac Pro 3.1 from 11.5B3 to 11.B4
OCLP 0.2.2

Issues - forbidden sighn on reboot after update process ended
On a second reboot - boots and works fine.

Снимок экрана 2021-06-30 в 11.02.22.png
Снимок экрана 2021-06-30 в 14.36.05.png


 
FWIW - Booting OCLP, installed Big Sur 11.5b3 from USB, then Migration Assistant via Time Machine BU on USB from another macOS 11 install. Beta 3 got many hours of testing on two Mini3,1s - a late '09 2.66GHz and a very early '09 2.0GHz both unpatched ROM pre-Metal Macs performed quite well within hardware limits. Wi-Fi, Bluetooth, sleep/wake, file sharing both SMB & AFS, screen sharing, printer sharing all intact.

Updated OCLP to v.0.2.3TUI, installed 11.5Beta4 via OTA (w/three auto-restarts😳) then option reboot into OCLP icon, then into Big Sur 11.5b4, re-ran TUI to perform the necessary Step #3. Reboot. Made certain the correct boot disk was set in Startup Disk CP. OCLP honors that selection.

Overall, Beta4 out-performs Beta3 with reduced memory overhead, cooler CPU temps, quieter fan, subjectively a bit more snappy overall, graphics performance equivalent to unsupported High Sierra or Catalina. Having tried all of the Big Sur versions since 11.2.3 on these unsupported legacy pre-metal Minis as a daily driver, this particular version, macOS 11.5Beta4 is preferred. Worth the effort. 😎 YMMV

BTW- Anyone else notice "macOS installer" morphed into "Macintosh HD" during these beta install processes? 👀
 
Last edited:
Just in case, does somebody have an iMac 14,3 (21.5’’ late 2013) ? If yes can you check in System Preferences —> Energy saver which option you have (« Wake up for WIFI network access », « Wake up for ETHERNET network access » or « Wake up for network access ») and just say the patcher you used.

That would help me to understand if this is a specific bug or not.
 
Yes, I had the 4,1 running with USB/trackpad/keyboard. But have not tried it with more recent OC versions.
One thing you can have a look at in the meantime (you triggered me resuming the 4,1 experiments again ;-) is the
USB definition within the USB-Map.kext info.plist file. This resides in the OC folder on your EFI partition.
I noticed that when I wanted to "unspoof" certain MacBooks (set them back to their original model-ID) I had to change contents there as well or lose USB/trackpad/keyboard functions.

Premise that I don't own a MacBook4,1 but I won't exclude that it could work on BigSur (and Monterey too) included the GMAX3100 drivers for framebuffer.

You made these patches and they worked correctly till Catalina: https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-27337044

While replacing those too many USB kext on BigSur is an issue for its kernelcollection, are you sure that using an OCLP spoofing setup for MacBook5,2 you get also on 4,1 responsive input devices ?

I noticed the parrotgeek1 legacyUSBInjector contains just this and of course it's incomplete for that machine:
Code:
        <key>MacBook4,1</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.driver.AppleUSBHostMergeProperties</string>
            <key>IOClass</key>
            <string>AppleUSBHostMergeProperties</string>
            <key>IOProviderClass</key>
            <string>AppleBusPowerController</string>
            <key>IOProviderMergeProperties</key>
            <dict>
                <key>kUSBSleepPortCurrentLimit</key>
                <integer>1000</integer>
                <key>kUSBSleepPowerSupply</key>
                <integer>1500</integer>
                <key>kUSBWakePortCurrentLimit</key>
                <integer>1200</integer>
                <key>kUSBWakePowerSupply</key>
                <integer>1700</integer>
            </dict>
            <key>model</key>
            <string>MacBook4,1</string>
        </dict>

Could you attach your USB-Map.kext Info.plist working for MacBook4,1 ?

Also you should consider that you are not using a MacBook5,2 USB properties, but a spoofed supported BigSur Mac USB remapped for MacBook5,2 .
 
Premise that I don't own a MacBook4,1 but I won't exclude that it could work on BigSur (and Monterey too) included the GMAX3100 drivers for framebuffer.

You made these patches and they worked correctly till Catalina: https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-27337044

While replacing those too many USB kext on BigSur is an issue for its kernelcollection, are you sure that using an OCLP spoofing setup for MacBook5,2 you get also on 4,1 responsive input devices ?

I noticed the parrotgeek1 legacyUSBInjector contains just this and of course it's incomplete for that machine:
Code:
        <key>MacBook4,1</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.driver.AppleUSBHostMergeProperties</string>
            <key>IOClass</key>
            <string>AppleUSBHostMergeProperties</string>
            <key>IOProviderClass</key>
            <string>AppleBusPowerController</string>
            <key>IOProviderMergeProperties</key>
            <dict>
                <key>kUSBSleepPortCurrentLimit</key>
                <integer>1000</integer>
                <key>kUSBSleepPowerSupply</key>
                <integer>1500</integer>
                <key>kUSBWakePortCurrentLimit</key>
                <integer>1200</integer>
                <key>kUSBWakePowerSupply</key>
                <integer>1700</integer>
            </dict>
            <key>model</key>
            <string>MacBook4,1</string>
        </dict>

Could you attach your USB-Map.kext Info.plist working for MacBook4,1 ?

Also you should consider that you are not using a MacBook5,2 USB properties, but a spoofed supported BigSur Mac USB remapped for MacBook5,2 .
I´ll cram it out of the shelf and try this again over the weekend!
 
  • Like
Reactions: jackluke
If I have a Mac Pro 5,1 with a stock Sapphire Radeon 580 running Mojave, evidently all I need to do is install OCLP 0.2.2, then do a Big Sur upgrade install from the Software Update Prefpane?

Edit: I had an earlier version of OpenCore installed for GPU acceleration, it looks like I could do it from that early version, think it's 0.5.6? Maybe I could just do that..
 
Last edited:
If I have a Mac Pro 5,1 with a stock Sapphire Radeon 580 running Mojave, evidently all I need to do is install OCLP 0.2.2, then do a Big Sur upgrade install from the Software Update Prefpane?

Edit: I had an earlier version of OpenCore installed for GPU acceleration, it looks like I could do it from that early version, think it's 0.5.6? Maybe I could just do that..
You should not update Big Sur! You system is broken with Big Sur versions later than 11.2.3. Check this thread...
Of course your should update your OpenCore version. OCLP is a cool tool to do this.
 
  • Like
Reactions: 0134168
Hi!
Updated My MacPro 4.1 (Flashed to 5.1) to MacOS Big Sur 11.5 Beta 4

I updated my OC config by OCLP 0.2.2 - and get freeze on boot into 11.5b1 (without expansion PCI cards)

After 1st restart - system booted and i started update process, after 1st reboot - freeze and 2 reboots. After install process gets started, all installed and 11.5 b4 booted sucessfully.

After i install my ThunderBolt 3 PCI Adapter - 11.5B4 never booted under OC. With boot-arg "-no_compat_check" - 11.5 B4 boots on native bootloader 2 time freezes, but after 2 reboots loads and it works.

I decide to rollup to old OC config (OCLP 0.1.1) and all boot and works!

P.S. In Verbose mode NVMEFIX got error - unsupported model (OCLP 0.2.2)
P.P.S my NVME SSD 512GB Apacer AS2280P4 [AP512GAS2280P4-1]

Снимок экрана 2021-07-02 в 08.34.25.png
Снимок экрана 2021-07-02 в 07.20.22.png


 
Last edited:
I have installed the latest MacOS 11.4 patched with OCLP 0.2.2 works so far but on every Mac Safari is unusable! Is there any fix ?

Webpage reloads all the time.
Safari v. 14.1.2 seems jerky and slow whereas Firefox ESR runs competent and quick, videos smooth, very acceptable on macOS 11.5Beta4 on a 2GHz Mini3,1.
 
  • Like
Reactions: Dilli
On my 2011 8,1 MBP running 11.4, the photos app doesn't sync with my iPhone. Seems like a glitch and a major flaw for me. Going back to Catalina for my daily use. Shame...
 
  • Like
Reactions: K two
For the GUI version of OCLP, how to I access some of the optional features, like "Don't show boot volume upon boot"?
 
  • Like
Reactions: K two
For the GUI version of OCLP, how to I access some of the optional features, like "Don't show boot volume upon boot"?
There is no such option in the TUI! Try to do a phrase by phrase comparison....I bet I know exactly what you are looking for but I cannot believe that you come up here with an arbitrary phrase :)
 
Last edited:
  • Like
Reactions: BeatCrazy
Yes, I had the 4,1 running with USB/trackpad/keyboard. But have not tried it with more recent OC versions.
One thing you can have a look at in the meantime (you triggered me resuming the 4,1 experiments again ;-) is the
USB definition within the USB-Map.kext info.plist file. This resides in the OC folder on your EFI partition.
I noticed that when I wanted to "unspoof" certain MacBooks (set them back to their original model-ID) I had to change contents there as well or lose USB/trackpad/keyboard functions.
Thanks. Actuallly I was trying with the kexts you posted on the Mojave page, then in BS I don't have to put those, but just edit the plist a little in the BS's kexts? Thanks!
 
Thanks. Actuallly I was trying with the kexts you posted on the Mojave page, then in BS I don't have to put those, but just edit the plist a little in the BS's kexts? Thanks!
Just re-did the test on my MB4,1 with the latest OCLP. No USB/keyboard/trackpad now.
So yes, we´ll have to mod at least the USB map file again. I suspect that more will be necessary, i.e. using some of the older kexts with the kext droplet tool, as you cannot just put them into the extensions folder any more due to volume sealing.
 

Attachments

  • Kext-Droplet.app.zip
    197.5 KB · Views: 75
  • Like
Reactions: chris1111
Just re-did the test on my MB4,1 with the latest OCLP. No USB/keyboard/trackpad now.
So yes, we´ll have to mod at least the USB map file again. I suspect that more will be necessary, i.e. using some of the older kexts with the kext droplet tool, as you cannot just put them into the extensions folder any more due to volume sealing.

Then which OCLP version allowed MacBook5,2 glitched MacBook4,1 responsive HID devices ?

They should use this (many ways enough similar to parrotgeek1 LegacyUSBInjector): https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts/Plists/AppleUSBMaps

but I guess when they update that file also overwritten previous versions.
 
Just re-did the test on my MB4,1 with the latest OCLP. No USB/keyboard/trackpad now.
So yes, we´ll have to mod at least the USB map file again. I suspect that more will be necessary, i.e. using some of the older kexts with the kext droplet tool, as you cannot just put them into the extensions folder any more due to volume sealing.
Maybe just getting the kext from older OCLP and putting it can help?

P.S. Do you have the version of OCLP that worked?
 
Last edited:
Just re-did the test on my MB4,1 with the latest OCLP. No USB/keyboard/trackpad now.
So yes, we´ll have to mod at least the USB map file again. I suspect that more will be necessary, i.e. using some of the older kexts with the kext droplet tool, as you cannot just put them into the extensions folder any more due to volume sealing.
+There is still a way to put kexts after sip is disabled. with terminal, it does work
 
@Larsvonhier maybe if you clone an already installed Big Sur, through this your earlier Teleport method:
https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-27007807

you could attempt to replace those MacBook4,1 kext (included the GMAX3100) from the target machine, maybe you could try this directly from Big Sur desktop : BigSurmountsrw2.app.zip
but backup replaced kext and restart BigSur only if kmutil returns no errors, I mean you can continue to replace any custom kext until kmutil outputs no errors then you could restart BigSur.

I could even attempt to make a patched prelinkedkernel embedding your MacBook4,1 kext , in this way the Big Sur BaseSystem environment is HID USB responsive and from there you can use kmutil to install any custom kext, but probably is required the target machine for this step.
 
Last edited:
  • Like
Reactions: PG7 and Larsvonhier
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.