Contribute
Register

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

santitf said:
Is there any option to "delete" the PCIe Slot1?
Thanks!!!
Click to expand...
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: 30
Ayvan said:
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
Click to expand...
Thanks so much!!!
No display nvidia on pci1, and monitor sleeps works fine!!
 
R-88 said:
@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?
Click to expand...
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.
 
CaseySJ said:
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>[email protected],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>[email protected],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>
Click to expand...
Yes!!! it worked! Firefox up running! Thank you again for your fantastic guides and help! :) :)
 
giertosan said:
Yes!!! it worked! Firefox up running! Thank you again for your fantastic guides and help! :) :)
Click to expand...
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:
CaseySJ said:
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).
Click to expand...
By the way. your oc.073 is not attached in the first post. :)
 
Hey @CaseySJ finally I've done built my PC that we talked about on the previous post.
But actually, I've found one problem that really frustrating me to the max, and I dunno how to do after every attempt I did and such a wasted time.

The problem is on PowerColor RX 6800 XT Red Devil, my system has dual-boot Big Sur + Windows 10, everytime I wanna boot to windows from your recent OC 0.7.3 it goes blank and nothing. After I restart the PC, it went same, either entering the Mac OS or Windows 10, it became no display no signal, I was so frustrating to the hell and dunno what to do. I did what I could like reset CMOS, reset NVRAM, remove the CMOS battery, re-flashing the BIOS up and down, nothing work. But its weird when I plugged my other GPU RX 5500 XT 4GB it went fine both windows and mac.

Does the latest OC 0.7.3 has GPU bug for NAVI21 or else? I couldnt find any post that has the same case as mine, I just really tired swapping the GPU for good and waiting for the solution.

Thanks,
 
Last edited:
bishop21 said:
Hey @CaseySJ finally I've done built my PC that we talked about on the previous post.
But actually, I've found one problem that really frustrating me to the max, and I dunno how to do after every attempt I did and such a wasted time.

The problem is on PowerColor RX 6800 XT Red Devil, my system has dual-boot Big Sur + Windows 10, everytime I wanna boot to windows from your recent OC 0.7.3 it goes blank and nothing. After I restart the PC, it went same, either entering the Mac OS or Windows 10, it became no display no signal, I was so frustrating to the hell and dunno what to do. I did what I could like reset CMOS, reset NVRAM, remove the CMOS battery, re-flashing the BIOS up and down, nothing work. But its weird when I plugged my other GPU RX 5500 XT 4GB it went fine both windows and mac.

Does the latest OC 0.7.3 has GPU bug for NAVI21 or else? I couldnt find any post that has the same case as mine, I just really tired swapping the GPU for good and waiting for the solution.

Thanks,
Click to expand...
Good morning,

Search for "6800" in this thread and you will find some ideas and links to other threads that may help you
 
iMac 19,1
Z390 DESIGNARE |  i7 8700K |  RX 580 Armor
iMac 20,2
Z490 Vision G |  i9 10850K |  HD 630
@CaseySJ A while go, not sure if you remember, I posted a message about my dual boot Windows/macOS. Up to OC 0.6.1 I could dual boot with no issue. Then, after that as soon as I selected Windows 10 from the OC picker, the screen would go black showing the Windows spinning wheel for a grand total of 3-4 seconds then would freeze and reboot. Today I tried again, and I add the same BSOD but there was a reason for crashing. The error was ACPI_BIOS error. Any idea what could cause this error in OC. The bug has to be in OC because pressing F12 and booting Windows 10 from the BIOS works. But it is so inconvenient. I remember when I was on 0.6.2 or above, at one point in time I switched back to 0.6.1 without changing anything in the BIOS, and I could boot Windows from the OC. So it is definately something in the OC bootloader.

Forgot to add that when that issue started to appear I was on BIOS F5. I upgraded to F20 a couple of months ago. So I don't think it is an issue with the BIOS since no new settings were introduced, and it crashed anyway with F5.
 
You must log in or register to reply here.
Copyright © 2010 - 2023 tonymacx86 LLC
Back
Top