It works with config.plist as with any plist. I use this to automate OpenCore configuration in MyBootMgrJust wondering if it works for config.plist without problems.
I don't see anything about qualifying machines in the message you got....it complains that I need to have a qualified machine.
I see the same. After a reboot or two it's gone for me anyway.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 don't see anything about qualifying machines in the message you got.
.
Software Update can only ignore updates that are eligible for installation.
.
Out of curiosity, how can you tell what is loaded via OC and what isn't?
kextstat | grep -v com.apple
You are interpreting it that way but that is not what it says.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
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 wrongOK, 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
Curious.. are you using straight OC or in conjunction with chainloader. I had the same problem.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.
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.Installation did hang once, but after a reboot all went more or less okay.
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) andNetflix in Ultra HD
To stream in Ultra HD, you will need:
NOTE:
- 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.
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:
If you don't know if your computer meets these requirements, contact the manufacturer.
- 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
-igfxvesa
boot argument. Perhaps we can try iMac19,1 board Id and boot argument -igfxvesa
.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.I guess this could also be handled with the freely available PlistBuddy also
You can generate one full working example with all the features listed into first post, using my plistlib generator. It will help you understand what you are missing.Could you post you plist so I can see where I’m going wrong
Same here. Weird.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!?
I fixed that into a previous PR, now all .dsl files are deleted.@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!
git clone https://github.com/axivo/opencore.git
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
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.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.