Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

you would only need the one, and not have both listed in config.plist
thanks
I guess that's why I can't run Big Sur anymore...
both are checked in Casey's made config.plist
Screenshot 2020-11-03 at 22.45.47.png


EDIT:

When both are activated we can run into Catalina but not Big Sur
When only USBInjectAll-076.kext is activated we can run both Catalina and Big Sur

Don't tried USBInjectAll-071.kext
 
Last edited:
thanks
I guess that's why I can't run Big Sur anymore...
both are checked in Casey's made config.plist
View attachment 494099

EDIT:

When both are activated we can run into Catalina but not Big Sur
When only USBInjectAll-076.kext is activated we can run both Catalina and Big Sur

Don't tried USBInjectAll-071.kext
also the min and max kernels are different:
Code:
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>USBInjectAll-071.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/USBInjectAll</string>
                <key>MaxKernel</key>
                <string>18.99.99</string>
                <key>MinKernel</key>
                <string>18.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>USBInjectAll-076.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/USBInjectAll</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

what issue you having?
 
also the min and max kernels are different:
Code:
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>USBInjectAll-071.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/USBInjectAll</string>
                <key>MaxKernel</key>
                <string>18.99.99</string>
                <key>MinKernel</key>
                <string>18.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>USBInjectAll-076.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/USBInjectAll</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

what issue you having?
by default in Casey's config.plist both are activated and I didn't checked that so it was impossible to boot Big Sur (stuck on the Apple Logo) but no problem with Catalina.
When only USBInjectAll-076.kext activated I can boot into Catalina and Big Sur
 

thanks
I guess that's why I can't run Big Sur anymore...
both are checked in Casey's made config.plist
View attachment 494099

EDIT:

When both are activated we can run into Catalina but not Big Sur
When only USBInjectAll-076.kext is activated we can run both Catalina and Big Sur

Don't tried USBInjectAll-071.kext

by default in Casey's config.plist both are activated and I didn't checked that so it was impossible to boot Big Sur (stuck on the Apple Logo) but no problem with Catalina.
When only USBInjectAll-076.kext activated I can boot into Catalina and Big Sur
@Inqnuam,

Both are enabled, but they have different Min/Max kernel numbers. Version 0.7.1 should load under Mojave only, whereas 0.7.6 should load under Catalina and newer.

If you needed to disable 0.7.1 for Big Sur, then it could suggest a bug in OpenCore. Sometime to try would be to enter 20.99.99 for Max Kernel for 0.7.6.
 
@Inqnuam,

Both are enabled, but they have different Min/Max kernel numbers. Version 0.7.1 should load under Mojave only, whereas 0.7.6 should load under Catalina and newer.

If you needed to disable 0.7.1 for Big Sur, then it could suggest a bug in OpenCore. Sometime to try would be to enter 20.99.99 for Max Kernel for 0.7.6.
would using USBPorts.kext be a better alternative?
 
I'm about to test Mojave for the AMD GPU setup. I've disabled the iGPU (RX580 only for the iMP1,1)
Should I delete the igfxfw=2 part of the boot argument in:

NVRAM<Add<7C436110-AB2A-4BBB-A880-FE41995C9F82<boot-args<agdpmod=pikera alcid=11
(shikigva=128) igfxfw=2


?
 
Last edited:
I'm about to test Mojave for the AMD GPU setup. I've disabled the iGPU (RX580 only for the iMP1,1)
Should I delete the igfxfw=2 part of the boot argument in:

NVRAM<Add<7C436110-AB2A-4BBB-A880-FE41995C9F82<boot-args<agdpmod=pikera alcid=11
(shikigva=128) igfxfw=2


?
Boot arguments for OpenCore are very easy available on HackinDROM's CopyConfig.
Just select your Motherboard and needed OC version

Screenshot 2020-11-04 at 00.52.53.png
 
Glad it's working.

Gentle reminder to create a custom Thunderbolt DROM/SSDT as well.
I've flashed titan ridge in order to solve problem with lg 5k monitor - it didn't turn on after cold boot - i need to re-plug thunderbolt connector in order to get it turn on (after this it works correctly even if i reboot system). it's annoying to re-plug this connector every day. after titan ridge flashed - i see monitor in system report -> thunderbolt -> thunderbolt device tree correctly (before flashing i get 'no thunderbolt drivers loaded'). but problem with monitor cold boot didn't solved.
 
Back
Top