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

[RandC]

Glad to hear it, but also a bit puzzled by the DP port issue. Is your RX 5700 XT made by either (a) XFX or (b) MSI?

No it’s Sapphire. Both DP ports don’t work. Only tried one of the HDMI ports and it works.

 

[CaseySJ]

@CaseySJ Hi there, given the huge amount of posts and requests for help, one of my previous question probably was missed. The question was related to disabling the GPU in the second slot either via the config.plist or the SSDT that is provided on the Dortania website.
I wanted to know if the GPU is disabled, should I expect to see an entry in the system reports or in IOReg under PEG1?
Currently, with both methods, I can see a new entry labelled "Display" in system report (which is the 6800 XT) on top of the valid entry for the 5600 XT.
In IOReg, under PCI0 IO can also see an entry under PEG1 the IGFX1. Under GFX1, the values for Name and IOname are the same ones that the ones mentioned in the Dortania solution which makes sense. However the values for class code are different. Dortania solution is to set them to FF FF FF FF whereas the values I get are 00 03 00 00 (something like that and the class code values are the same ones that the class code values under IGFX0 which is the 5600 XT).
I have followed the Dortania guide to the T but I can't tell if it is disabled or not. I have read that when an invalid class-code is detected, the corresponding device is disabled by the OS. FF FF FF FF is supposed to be invalid whereas 00 03 00 00 is not since it is the same value as teh 5600 XT.

If the PCI path for the 6800XT is correctly specified, and Class Code (and other device properties) are set to specific values (such as FF FF FF FF for Class Code) then theoretically the device should be disabled. If IOReg shows that Device Properties that we want to inject are not in fact being injected, then:

• We'll need to double check all of the steps we took to modify those properties.
• macOS could be overriding the device properties.

How is macOS treating the 6800XT? Does it attach the default frame buffer to it (IONDRVFrameBuffer)? It would be helpful to see the IOReg file.

 

[TripleYoThreat]

Thank you @CaseySJ for reply.

- after unplug all ext & internal USB Sleep works
- after reconnect all ext & internal USB excluding new YOUBO PC Hackintosh WiFi Card BCM94360CD Sleep works

It means that source of Sleep issue is YOUBO card itself. What do you think, better use old-one Fenvi T919?
I've replaced it because sometimes computer doesn't Wake-up from Sleep mode ... Do you have any idea to fix this sleep-wake-up-immediately issue for YOUBO?

Mouse and Keyboard is Apple Magic 2 ... in test time connected via USB cable and used Razer ProClick with USB dongle ...

Thank you ...

Were you able to get the sleep wake with Youbo card fixed? I'm having the same issue with the same card, different mobo

 

[joe12south]

After a lot of stumbling around (first time with OpenCore) I've finally got an almost perfect build. Currently, I'm left with one minor cosmetic issue that I can't seem to Google my way into a solution:
When OpenCore loads (either basic or with OpenCanopy) the screen resolution is left at the low resolution default. it doesn't switch to native until MacOS loads.
- I've followed the standard OpenCore post install clean-up recommendations
- I've made sure OpenCanopy is at the top of the list for drivers. (I read somewhere this might help)
- I made sure that CFM is off. (I read somewhere that this might help)

Any ideas? Is there a better place to go for OpenCore OpenCanopy support? Thanks!

 

[CamoViking]

...
When OpenCore loads (either basic or with OpenCanopy) the screen resolution is left at the low resolution default. it doesn't switch to native until MacOS loads.
...

Any ideas? Is there a better place to go for OpenCore OpenCanopy support? Thanks!

Hey there,

I have exactly the same problem. No idea how to solve it, and it doesn't really bother me that much, so I've just left it. Not much help, I'm afraid.

Although if you do find a solution, I'd love to know what it is...

Cheers,
V

 

[Aldwinn]

Hello everyone!

Let me tell you a little problem that is quite annoying. The hot plug of SATA disks is not really a hot plug.

• When I turn on a SATA disk with computer already turned on, it doesn't mount (not visible in the disk utility).
• If the disk is on when the computer boots, then it will mount properly, I can turn it off and on again properly, I can change the disk on the same sata port and everything will be fine.

In the BIOS, the SATA hot plug is of course enabled.

How do you think I can solve this problem? Thx!

 

[emistral]

@

If the PCI path for the 6800XT is correctly specified, and Class Code (and other device properties) are set to specific values (such as FF FF FF FF for Class Code) then theoretically the device should be disabled. If IOReg shows that Device Properties that we want to inject are not in fact being injected, then:

• We'll need to double check all of the steps we took to modify those properties.
• macOS could be overriding the device properties.

How is macOS treating the 6800XT? Does it attach the default frame buffer to it (IONDRVFrameBuffer)? It would be helpful to see the IOReg file.

@CaseySJ Here is a screenshot from IOReg. It does attach the default framebuffer. Name and IOName device properties are injected correctly s per either th config.plist or the SSDT. But the class-code is not as you can see in the below screenshot.

 

[joe12south]

Hey there,

I have exactly the same problem. No idea how to solve it, and it doesn't really bother me that much, so I've just left it. Not much help, I'm afraid.

Although if you do find a solution, I'd love to know what it is...

Cheers,
V

After some more searching, it appears it might be a Radeon Vega thing that can only be solved with a GPU firmware update.

 

[CaseySJ]

@

@CaseySJ Here is a screenshot from IOReg. It does attach the default framebuffer. Name and IOName device properties are injected correctly s per either th config.plist or the SSDT. But the class-code is not as you can see in the below screenshot.
View attachment 513100

That is indeed strange. If you post the SSDT you're using to modify the device properties, I can take a closer look. Just to confirm: This is on the Z490 Vision D with AMD 6800 XT in the top long x16 slot?

 

[CaseySJ]

Unfortunately 11.3 Beta 4 is not stable for me. What I've observed so far:

• I believe changes were made to the NVMe driver (IONVMeFamily.kext) to address SSD caching issues with M1 Macs.
• Unfortunately, the new version has been crashing my system repeatedly. Kernel panics for the past 15 of 15 crashes since updating to Beta 4 have all occurred in IONVMeFamily.kext.
• Restoring back to Beta 3 fixes this problem completely.
• I have reported the last 5 of these crashes to Apple via the crash dump reporter.

Note 1: The problem may depend on make/model of NVMe SSD. My system has both Silicon Power and Sabrent Rocket (PCIe 3.0) NVMe SSDs.

Note 2: The problem may not occur on some motherboards. For example, my Gigabyte B550 Vision D (AMD Ryzen) with Silicon Power NVMe SSD and Sabrent Rocket (PCIe 4.0 version) remains rock solid on Beta 4.

** Update Big Sur 11.3 Beta 5 **

MacOS 11.3 Beta 4 was very troublesome as described in the post quoted above, so I had reverted back to Beta 3. Because Beta 5 was just released to the public, I decided to update from Beta 3 directly to Beta 5, but ran into the same problems as with Beta 4.

But there is good news...

It seems the culprit was my flashed GC-Titan Ridge. Although the Z490 Vision D has an on-board Titan Ridge controller, I am also using a flashed GC-Titan Ridge for a total of 4 Thunderbolt ports. During the macOS install process, however, a fatal error occurs while attempting to activate the XHC (USB) controller on this card.

Physically removing the card allowed the update to proceed flawlessly, and the system is stable.

Update:

• Installing the flashed GC-Titan Ridge after the update to 11.3 Beta 5 causes the system to crash after a couple of minutes. Same as with 11.3 Beta 4, but this does not happen in Beta 3 and earlier.
• So for now the flashed GC-Titan Ridge will remain disconnected.