[Solved] Catalina thinks my Corsair Commander Pro is a UPS

[jimbojingle]

This is great news.

Please explain how to add the kext to config.plist for OpenCore?

Thanks.

 

[Feartech]

This is great news.

Please explain how to add the kext to config.plist for OpenCore?

Thanks.

check your current config.plist and add a new entry for your new kext

 

[jimbojingle]

check your current config.plist and add a new entry for your new kext

Hi,

I have added 'CommanderProFix.kext' to kexts folder and created an entry in config.plist as follows but it's still not working. Please advise?

<dict>
<key>Arch</key>
<string>Any</string>
<key>BundlePath</key>
<string>CommanderProFix.kext</string>
<key>Comment</key>
<string>Corsair Commander Pro Fix</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/CommanderProFix</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

 

[Feartech]

Hi,

I have added 'CommanderProFix.kext' to kexts folder and created an entry in config.plist as follows but it's still not working. Please advise?

<dict>
<key>Arch</key>
<string>Any</string>
<key>BundlePath</key>
<string>CommanderProFix.kext</string>
<key>Comment</key>
<string>Corsair Commander Pro Fix</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/CommanderProFix</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

not used that kext before, but it looks like you have setup your config.plist ok though

 

[jimbojingle]

Thanks.

It is not running for some reason though as indicated by Hackintool or HackinDROM.

 

[r4eshaddict]

@aclee so many thank yous!

I installed your CommanderProFix.kext and it worked like a charm– no more annoying UPS power-saving non-sense. I can actually update OSX now, etc.
For others faced with this annoying an unexpected outcome of the Commander Pro – this kext works great.
Tested on Big Sur 11.4 using OpenCore 0.6.9.

 

[jimbojingle]

@aclee so many thank yous!

I installed your CommanderProFix.kext and it worked like a charm– no more annoying UPS power-saving non-sense. I can actually update OSX now, etc.
For others faced with this annoying an unexpected outcome of the Commander Pro – this kext works great.
Tested on Big Sur 11.4 using OpenCore 0.6.9.

That's great.

Please advise what you did exactly? As stated above, I installed the CommanderProFix.kext in the kexts folder and created an entry in config.plist but no luck as of yet. The kext does not seem to run and I still get a UPS error!

 

[r4eshaddict]

That's great.

Please advise what you did exactly? As stated above, I installed the CommanderProFix.kext in the kexts folder and created an entry in config.plist but no luck as of yet. The kext does not seem to run and I still get a UPS error!

Nothing fancy on this end– I added the .kext to the kext folder, opened my opencore config with ProperTree and did the "Shift + R" key combo which searches your opencore folder for any changes or added kexts, etc and automatigically adds them. Then booted and voila!

That said– here is a copy/paste directly from my config file if it helps:

<array>
    <dict>
        <key>BundlePath</key>
        <string>CommanderProFix.kext</string>
        <key>Comment</key>
        <string></string>
        <key>Enabled</key>
        <true/>
        <key>ExecutablePath</key>
        <string>Contents/MacOS/CommanderProFix</string>
        <key>Arch</key>
        <string>Any</string>
        <key>MaxKernel</key>
        <string></string>
        <key>MinKernel</key>
        <string></string>
        <key>PlistPath</key>
        <string>Contents/Info.plist</string>
    </dict>
</array>

 

[jimbojingle]

Nothing fancy on this end– I added the .kext to the kext folder, opened my opencore config with ProperTree and did the "Shift + R" key combo which searches your opencore folder for any changes or added kexts, etc and automatigically adds them. Then booted and voila!

That said– here is a copy/paste directly from my config file if it helps:

<array>
    <dict>
        <key>BundlePath</key>
        <string>CommanderProFix.kext</string>
        <key>Comment</key>
        <string></string>
        <key>Enabled</key>
        <true/>
        <key>ExecutablePath</key>
        <string>Contents/MacOS/CommanderProFix</string>
        <key>Arch</key>
        <string>Any</string>
        <key>MaxKernel</key>
        <string></string>
        <key>MinKernel</key>
        <string></string>
        <key>PlistPath</key>
        <string>Contents/Info.plist</string>
    </dict>
</array>

Thanks for your help.

Still not working for me. Tried several times the way you suggested. I must be doing something wrong.

Cheers.

 

[jimbojingle]

Nothing fancy on this end– I added the .kext to the kext folder, opened my opencore config with ProperTree and did the "Shift + R" key combo which searches your opencore folder for any changes or added kexts, etc and automatigically adds them. Then booted and voila!

That said– here is a copy/paste directly from my config file if it helps:

<array>
    <dict>
        <key>BundlePath</key>
        <string>CommanderProFix.kext</string>
        <key>Comment</key>
        <string></string>
        <key>Enabled</key>
        <true/>
        <key>ExecutablePath</key>
        <string>Contents/MacOS/CommanderProFix</string>
        <key>Arch</key>
        <string>Any</string>
        <key>MaxKernel</key>
        <string></string>
        <key>MinKernel</key>
        <string></string>
        <key>PlistPath</key>
        <string>Contents/Info.plist</string>
    </dict>
</array>

Hi,

I have these settings exactly the same as you but the CommanderProFix.kext is just not running.

Any ideas why this could be? It would be great to finally resolve this UPS Error in Big Sur!