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.
There is no FirmwareFeatureMask in the config.plist I am using (from pdf post#1). Already have VMM turned off. Still I see the red badge notification for BigSur update...even though if I tried to do it, it should not work.
 
Last edited:
I have Catalina installed on a seperate hard drive on my 4.1>5.1 Mac Pro via DosDude patch. Mojave is my main OS installed on an SSD

can I install OC on the Catalina EFI to enable software update so that i can update to Big Sur ???
 
I clean installed Big Sur on an NVMe (from Catalina/OC 0.63) and all seemed to go rather well and seems to be working just fine. I restarted at some point to Catalina to try and sort out my huge email library which I would like to continue but dont seem able to (another issue) but then noticed I have a new drive icon named "Update" on the desktop - in Disk Utility on the APFS 'Container disk 3' I see three partitions: 'disk3s6' (unmounted), 'BigSur - Data' (mounted) and 'Update' (mounted). Is this normal or has something gone awry?
I see the same. After a reboot or two it's gone for me anyway.

Hmm. I take that back. I now see3 of them on my desktop after booting back into Catalina HD!?
 
Last edited:
I'd like to thank @cdf for his awfully helpful guide, @TECK for his python plist generator and @h9826790 for all the help provided! I was able to install Big Sur this morning up from Catalina, and upgraded OpenCore from 0.5.9 to 0.6.3 all very easily. Thank you everyone here, for getting even more juice out of these machines! 😁
 

Attachments

  • Screenshot 2020-11-16 at 09.25.07.jpeg
    Screenshot 2020-11-16 at 09.25.07.jpeg
    170.3 KB · Views: 147
  • Like
Reactions: TECK
That says it can only ignore eligible UPDATES from what I see ... is the Big Sur UPDATE eligible for being ignored on Catalina?
Not sure where machines come in.
 
The message is saying that I am not eligible for BigSur, therefore I can't ignore it...even though its not being ignored. I'm guessing this is because I have the so called "hybrid" machine id as described in forum post #1
 
The message is saying that I am not eligible for BigSur, therefore I can't ignore it...even though its not being ignored. I'm guessing this is because I have the so called "hybrid" machine id as described in forum post #1
You are interpreting it that way but that is not what it says.
It says Software Update can only ignore updates that are eligible for installation

Software Update is a program/utility on your machine. It is the Software Update utility that has this restriction. If you roll back a few versions of Software Update, it will work fine but this means undoing some security updates.

Restrictions on ignoring major updates were introduced into Software Update in one of the recent security updates. That's what is probably behind your issue. I believe there is a way to delay things but that the ability to completely ignore was removed. (Always read the notes that go with the security updates. Can't recollect the details for Catalina as I use Mojave)

Check online for workaround.
 
Last edited:
OK, so I added the needed lines

In the Kernel Key.

I've added the lines just after

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>RadeonBoost.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<false/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>


So look for the Kernel key, under <dict> you have the <key>Add</key> in which you have the <array> in which you are adding the 2 dict éléments from the original post.

Of course you have to add the kext in the right folder
I’m a complete noob when it comes to editing this plist file and have made some progress, unfortunately it resulted in an in bootable state. Could you post you plist so I can see where I’m going wrong
Many thanks
 
Managed to upgrade directly from Mojave to Big Sur with the latest pack from @h9826790. Installation did hang once, but after a reboot all went more or less okay. But...
  • Every time after I restart I get an error saying that my computer didn't shutdown properly.
  • Good test. Back to Mojave for now.
Curious.. are you using straight OC or in conjunction with chainloader. I had the same problem.
 
Installation did hang once, but after a reboot all went more or less okay.
I had similar experiences, except I'm losing Bluetooth on random reboots. I'm using the @cdf setup with my plistlib generator, @tsialex showed me where are the issues and I hired him to rebuild my ROM, so I can flash it clean and fix all problems. I have a feeling you are in the same boat.

Edit: @tsialex noted the Bluetooth looks like is being a widespread issue.

1605543052272.png
 
Last edited:
  • Like
Reactions: DanSilov
Per Netflix:
Netflix in Ultra HD
To stream in Ultra HD, you will need:
  • A Mac computer with macOS 11.0 Big Sur installed.
  • The latest version of Safari browser
  • Select 2018 or later Mac computer with an Apple T2 Security chip
  • A 60Hz 4K capable display (with HDCP 2.2 connection if external display).
    NOTE:

    Every monitor connected to your computer must meet these requirements to successfully stream in Ultra HD.
  • A plan that supports streaming in Ultra HD. A steady internet connection speed of 25 megabits per second or higher.
  • Streaming quality set to Auto or High.
NOTE:

4K Ultra HD support for macOS 11.0 Big Sur is currently in development may not be available at all times.
Netflix in HDR
Netflix is available in HDR on Mac computers using the Safari browser.
To stream HDR content on your Mac computer, your system must meet or exceed the following requirements:
  • macOS Catalina 10.15.4 or later
  • A compatible Mac model with an HDR-capable display
  • If using a cable or adapter, it must support HDR
  • The High Dynamic Range checkbox is selected in System Preferences > Display
If you don't know if your computer meets these requirements, contact the manufacturer.
All of those have T2 chip. So I am not sure how we can get DRM in Big Sur. Although someone noted that he got it working with iMac19,1 (No T2 chip) and -igfxvesa boot argument. Perhaps we can try iMac19,1 board Id and boot argument -igfxvesa.
 
I have a Mac Pro 4,1 (flashed to 5,1) that has been gathering dust since almost a year. I am thinking about putting it back to active duty.
Since my experience with macOS 11 is positive on my MP 2013, I'd be inclined to try going for Big Sur directly.

Can I assume that the procedure in the wikipost at the head of the thread is equally applicable to a Big Sur installation?
 
I guess this could also be handled with the freely available PlistBuddy also
I use plistlib, which is part of the OS also, but allows you to programatically create your plist from a specific input. So when there is a configuration change, you can easily update only that change, not the entire file.
 
@TECK Is there a specific reason why your script still copies SSDT-PNLFCFL.dsl to the kexts folder?

I appeciate the work you put into the script!
I fixed that into a previous PR, now all .dsl files are deleted. :)
Once 0.6.4 is released, all these changes will be included into a release, for now use:
Code:
git clone https://github.com/axivo/opencore.git
 
  • Like
Reactions: tsialex and OneyedK
I had similar experiences, except I'm losing Bluetooth on random reboots. I'm using the @cdf setup with my plistlib generator, @tsialex showed me where are the issues and I hired him to rebuild my ROM, so I can flash it clean and fix all problems. I have a feeling you are in the same boat.

Edit: @tsialex noted the Bluetooth looks like is being a widespread issue.

View attachment 1669403

Hello,

So the Bluetooth that comes with the 4,1 is a hit or miss thing?

Can someone please add the fix to the main post?

Thanks!
 
Can someone please add the fix to the main post?
Is a BootROM fix in cMP, not related to OC. Basically, you need to know what you are doing or be a firmware engineer or an Apple technician to fix it. That is why I hired @tsialex to build me a clean ROM. From what I read, the ROM gets corrupted in time and the only solution is to re-flash a clean ROM.
 
  • Like
Reactions: Enricote
Is a BootROM fix in cMP, not related to OC. Basically, you need to know what you are doing or be a firmware engineer or an Apple technician to fix it. That is why I hired @tsialex to build me a clean ROM. From what I read, the ROM gets corrupted in time and the only solution is to re-flash a clean ROM.

I've just updated my machine to 144.0.0.0.0 today and backed up the rom with the romtool. If you need it I can get it to you....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.