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.
Can you teach me that? I want to apply this to Big Sur

I dion't know WHY but they work to me:

I noticed that, at least on my Mac mini 2010, often ejecting some USB devices drastically decreases my CPU usage. So I have made a simply batch executed at login to automatically unmount all devices, excepted one that I eject manually when CPU usage has gone down from 100% to 30-35%. Sometimes if you simply click on last drive icon with
right mouse button, CPU decreases suddenly:



#!/bin/bash

diskutil unmount "ExactDiskNameOnDesktop" && diskutil unmount "ExactDiskNameOnDesktop2" && diskutil unmount "ExactDiskNameOnDesktop3"

Watch how the 100% CPU meter on top right menu goes down to 9% after having ejected disks...


Other trick - kill CPU over-consuming processes:
sudo pkill -f "Spotlight" && sudo pkill -f "spindump"

Lowering CPU IDE usage from 30-35% to 4-10% makes a great difference on my Core2 Duo Penryn performances. With iMac 2013 Core i5 there is no need of this tricks.
 
Last edited:
  • Like
Reactions: webg3
Big Sur is only an exercise on Core 2 Duo Pernyn. Catalina 10.15.7 does surprising well on my Mac mini 2010, I have only to use some tricks to lower my "default" CPU usage from 30% at boot to 4%, to get all the power :)
Also here on MBP5,2, I'm more than happy with Catalina 10.15.7. Very stable, quite performant.

And yes, Big Sur is just an exercise on such C2D, non-metal hardware.
But such exercises I find (1) interesting, (2) maybe still successful in the longer run -
computers are finite (if big) systems, so certainly there is a solution for a BS suited for production on such machines.
 
Just a quick note: installation of BS beta 11.0.1 via installassistant.pkg using Barry's micropatcher 0.4.4 went well (after a slow download). Install MacOS Beta took 38 minutes on an external SSD (CrucialX8); MBPro 15inch Retina mid-2012 10,1.

I used Barry's -e option on 'install-setvars.sh'
Downloading was quick for the first few GB, then my DL speed got slower and slower, like 20..19.9..19.8..19.7 and so on, I paused the download, started again a few time, it always started fast but to crawl to a slow pace, last 2 Gb though were downloaded within 20 seconds, yes...I am on a Gb internet speed, I think, actually pretty sure networking on beta 10 was/is the issue.
See if this has been fixed in this new beta.

I Installed 11.0.1 just half an hour ago on a 2012 Mac Mini, took quite *a bit of time even though I have a Samsung Pro SSD, not PCI though, it is Sata.

* Probably a bit more than yours, I didn't time it.

What is odd is that the first stage said a time to install was something like 38 minutes, it was close to finished but in the second stage it again says >20 minutes, it used to be so much faster installing OSX, like just one reboot or 2 if there was a Firmware Update, now it takes 3 or 4 restarts and more time.
 
cMP Mid 2012 Big Sur 11.0.1 Beta1 updated with Barry's micropatcher-dev-v0.5.0 without any issue.
As usual as Recovery terminal command:
/Volumes/Image\ Volume/set-vars.sh

Big thanks to Barry and others created the micropatcher.
cMP Mid 2012 BS 11.0.1 Beta1.png
 
Last edited:
I used the Full installer along with the Barry Micropatcher and I was able to easily update to 11.01 on my MacPro 5.1 . Was able to use a time machine backup to quickly get up and running.
 
For those with Arrendale, Lynnfield and Clarkdale Macs, I figured out the Big Sur kernel panic. It seems to be due to IOPCIFamily becoming much pickier with their probes similar to X79 and X99's encore bridges, and so when it probes a device that's not present/functioning correctly it'll panic.

Fixing this panic is actually quite easy, you'll want to grab the below SSDT and inject it via OpenCore:

- SSDT-CPBG

This has been verified to work on iMac11,1, however would like more testers to ensure this is working with all affected models.

For those who want a prebuilt image of OpenCore to test with:

- OpenCore EFI

For more info on settings this up, I'm currently in the process of writing documentation(so currently not entirely finished):

- OpenCore for legacy Macs Guide

And a refresher with the affected models:

- iMac11,1
- iMac11,2
- iMac11,3
- MacBookPro6,1
- MacBookPro6,2
 
Last edited:
Hi
Trying to update to last beta on my Mac mini 2011 using micropatcher 0.4.4
When applying patch-kexts.sh —2011 got these errors. Both from the booted installation or from the Usb stick. What should I do?

B96452A9-D1CB-44C2-A44E-B1549FA206E9.jpeg
 
Hi
Trying to update to last beta on my Mac mini 2011 using micropatcher 0.4.4
When applying patch-kexts.sh —2011 got these errors. Both from the booted installation or from the Usb stick. What should I do?

View attachment 976296

Try this from a BigSur terminal environment:

diskutil list

(locate your "BigSur Data Volume" label)

cd /Volumes/YourBigSurLabel*Data/Library/Extensions

rm -r AMD* ATI*

then retry micropatcher patch kext .
 
For those with Arrendale, Lynnfield and Clarkdale Macs, I figured out the Big Sur kernel panic. It seems to be due to IOPCIFamily becoming much pickier with their probes similar to X79 and X99's encore bridges, and so when it probes a device that's not present/functioning correctly it'll panic.

Fixing this panic is actually quite easy, you'll want to grab the below SSDT and inject it via OpenCore:

- SSDT-CPBG

This has been verified to work on iMac11,1, however would like more testers to ensure this is working with all affected models.

For those who want a prebuilt image of OpenCore to test with:

- OpenCore EFI

For more info on settings this up, I'm currently in the process of writing documentation(so currently not entirely finished):

- OpenCore for legacy Macs Guide

And a refresher with the affected models:

- iMac11,1
- iMac11,2
- iMac11,3
- MacBookPro6,1
- MacBookPro6,2

Great work!

- Add your patched file to this path /EFI/OC/ACPI/SSDT-CPBG.aml

- edit the config.plist to include this:

Code:
    <key>ACPI</key>
    <dict>
        <key>Add</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>khronokernel Arrandale patch</string>
                <key>Enabled</key>
                <true/>
                <key>Path</key>
                <string>SSDT-CPBG.aml</string>
            </dict>
        </array>

tested and working (it's a dual GPUs with installed IntelHD Arrandale kext), thanks to @khronokernel ACPI patch and OpenCore, BigSur 11.0.1 beta can now boot with Arrandale MacBookPro, @fabioroberto, @Badruzeus and others who own similar machines, this attached picture is from an already installed external USB BigSur booting through USBopencore, but I provide a way to install BigSur on those Arrandale machines directly with createinstallmedia : BaseSystem Legacy USB fix

edit:
I attached my customised external USBopencore setup (simply unzip it to any USB device FAT32 formatted) for Arrandale Mac (and similar Intel architectures) and it can be used at apple startup manager with alt-option key to boot BigSur kernel on those machines.

You need to boot through this OpenCore4b1 any BigSur installer stages, if you encounter some issues try the previous OpenCore3b1 version .
 

Attachments

  • BigSur 11.0.1 beta on Arrandale opencore.png
    BigSur 11.0.1 beta on Arrandale opencore.png
    1.5 MB · Views: 987
  • OpenCore4b1.zip
    6.2 MB · Views: 467
  • BigSur 11.0.1 Arrandale IntelHD.png
    BigSur 11.0.1 Arrandale IntelHD.png
    1.4 MB · Views: 343
  • OpenCore3b1.zip
    6.1 MB · Views: 245
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.