Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

Finally I replace my crashing 5700 XT by a 3060 Ti (for gaming).
I'm running Big Sur without acceleration. :thumbdown
I want to use the discrete with Windows and the Intel iGPU with Big Sur.
Before changing EFI files (I'm using AMD config.plist), I'm trying to boot using two cables: HDMI for macOS, DisplayPort for w10.
I updated my BIOS to F20 (for Resize-Bar), but can't see the BIOS using the HDMI (iGPU).
With the F20 BIOS, the iGPU option are limited to auto, enable, disable and can't select initial graphics card.
Any idea?
Any advice?
 
Any advice?
Go BIOS.
Set "CSM Support: Enabled".
Don't save, don't reboot!
Go to GPU options, now you have option "Initial Display Output", set iGPU.
Set "CSM Support: Disabled".
Save and reboot.


Add igfxonln=1 boot arg to your config.plist to fix display wake up issue if you need (if after display sleep it not wakes up).

UPD: With iGPU you can set "Re-size BAR: Auto" to enable it for Windows. With AMD card you need to set it "disabled".
 
Last edited:
@CaseySJ Thanks for the great guides.
I have only one small problem: dual boot with two disks, but when I boot from Win it sets itself as the default startup disk, basically ignoring the nvram, and I am forced to manually put the boot disk back from system preferences. Is there a solution to this?
 
Go BIOS.
Set "CSM Support: Enabled".
Don't save, don't reboot!
Go to GPU options, now you have option "Initial Display Output", set iGPU.
Set "CSM Support: Disabled".
Save and reboot.


Add igfxonln=1 boot arg to your config.plist to fix display wake up issue if you need (if after display sleep it not wakes up).

UPD: With iGPU you can set "Re-size BAR: Auto" to enable it for Windows. With AMD card you need to set it "disabled".
Thanks @Ayvan !!!
I can boot with the iGPU and boot with graphics acceleration on Big Sur.
Captura de Pantalla 2021-09-21 a les 15.22.51.png

It seems that Big Sur detect the Nvidia GPU.
Is there any option to "delete" the PCIe Slot1?
Thanks!!!
 
Is there any option to "delete" the PCIe Slot1?
Thanks!!!
Open your config in OpenCore Configurator, "Device Properties".
Add new device: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
Set properties:

name Data 23646973706C6179
IOName string #display
class-code Data FFFFFFFF
 

Attachments

  • Снимок экрана 2021-09-21 в 17.55.00.png
    Снимок экрана 2021-09-21 в 17.55.00.png
    91.1 KB · Views: 32
Open your config in OpenCore Configurator, "Device Properties".
Add new device: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
Set properties:

name Data 23646973706C6179
IOName string #display
class-code Data FFFFFFFF
Thanks so much!!!
No display nvidia on pci1, and monitor sleeps works fine!!
 
@CaseySJ Thanks for the great guides.
I have only one small problem: dual boot with two disks, but when I boot from Win it sets itself as the default startup disk, basically ignoring the nvram, and I am forced to manually put the boot disk back from system preferences. Is there a solution to this?
Windows can set itself as the startup disk when it installs a Feature update or some other Security/Incremental update. But Windows will not set itself as the startup disk under normal shutdown and reboot circumstances.

At the OpenCore Picker we can press and hold the CTRL key when selecting a boot disk. This will cause the selected disk to become the new default boot disk, hence it's not necessary to select Startup Disk from System Preferences.
 
Some comments:
  • I think you may have used config-Intel-iGPU.plist as the starting point. Because you have an AMD GPU (Radeon VII) it's best to use config-AMD-GPU.plist instead, which disables video output from the iGPU while still keeping iGPU enabled for compute tasks.
  • However, first let's follow the suggestion in the Dortania link from my previous reply and add device-id 0x3E98, which is 983E0000 in reverse byte order. Simply replace the PciRoot(0x0)/Pci(0x2,0x0) section in Device Properties with this modified version and reboot:
XML:
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>#AAPL,slot-name</key>
                <string>Internal@0,2,0</string>
                <key>AAPL,ig-platform-id</key>
                <data>BwCbPg==</data>
                <key>device_type</key>
                <string>Display controller</string>
                <key>framebuffer-con0-busid</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con0-index</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con0-type</key>
                <data>AAQAAA==</data>
                <key>framebuffer-con1-busid</key>
                <data>BgAAAA==</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con1-index</key>
                <data>AgAAAA==</data>
                <key>framebuffer-con1-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con1-type</key>
                <data>AAQAAA==</data>
                <key>framebuffer-con2-busid</key>
                <data>BAAAAA==</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con2-index</key>
                <data>AwAAAA==</data>
                <key>framebuffer-con2-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con2-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-con3-busid</key>
                <data>AAAAAA==</data>
                <key>framebuffer-con3-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con3-flags</key>
                <data>IAAAAA==</data>
                <key>framebuffer-con3-index</key>
                <data>/////w==</data>
                <key>framebuffer-con3-pipe</key>
                <data>AAAAAA==</data>
                <key>framebuffer-con3-type</key>
                <data>AQAAAA==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>Intel UHD Graphics 630 (Desktop 9 Series)</string>
                <key>device-id</key>
                <data>mD4AAA==</data>
            </dict>
If this also fails, we can replace the same section with the following, which disables video output from iGPU, but keeps iGPU enabled for compute tasks:
XML:
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>#AAPL,slot-name</key>
                <string>Internal@0,2,0</string>
                <key>AAPL,ig-platform-id</key>
                <data>AwCYPg==</data>
                <key>device_type</key>
                <string>Display controller</string>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>Intel UHD 630</string>
            </dict>
Yes!!! it worked! Firefox up running! Thank you again for your fantastic guides and help! :) :)
 
Yes!!! it worked! Firefox up running! Thank you again for your fantastic guides and help! :) :)
Glad to hear it!

I tried to reproduce the Firefox problem two days ago on my Z490 Vision D using the standard version of “config-Intel-iGPU.plist”, but Firefox didn’t cooperate — it continued to run properly! :)

So this solution should be applied by others only if they experience the same problem (i.e. Firefox unable to start).
 
Last edited:
Glad to hear it!

I tried to reproduce the Firefox problem two days ago on my Z490 Vision D using the standard version of “config-Intel-iGPU.plist”, but Firefox didn’t cooperate — it continued to run properly! :)

So this solution should be applied by others only if they experience the same problem (i.e. Firefox unable to start).
By the way. your oc.073 is not attached in the first post. :)
 
Back
Top