Contribute
Register

VEGA 56 dual monitor / Catalina 10.15.7

Status
Not open for further replies.
I also have a ridiculous ammount of kexts in system library extentions, could it be that for example those AMD bundle files can introduce conflicts?
 

Attachments

  • L:E kexts.jpg
    L:E kexts.jpg
    1.4 MB · Views: 37
DarJok said:
I also have a ridiculous ammount of kexts in system library extentions, could it be that for example those AMD bundle files can introduce conflicts?
Click to expand...
you should not mess around with kexts in /S/L/E
 
Have you tried to add agdpmod=pikera to your bootargs?
For me it helped to solve black screen with vega 56 and dual monitors
 
thalaes said:
Have you tried to add agdpmod=pikera to your bootargs?
For me it helped to solve black screen with vega 56 and dual monitors
Click to expand...
i read somewhere that the argument shouldn't be needed with Vega cards and should be used on RX5000 series only

worth a try though :)
 
Hi,

I tried it, still getting black main screen and green square on the secondary hdmi monitor..

some said that adding video port number in graphics helps, well i tried many many things, nothing seems to work for me. I will continue searching out new methods.. at least vegatab and vegagraphics fixup kexts seem to work as i had blackouts for the vega graphics card.
 
@Feartech I also read that, but in some old thread I read that you could use that boot arg to solve black screen issues. I tried it as my to monitors where connected with one dp-cable and one dvi-cable with dp-adapter and that gave me problems with black screen and two different resolutions although the monitors are same model. Bought another dp-cable yesterday and like magic I got same res and could take away agdpmod=pikera from my bootargs. Sleep works perfect now and no black screens .
@ DarJok I was wondering about the necessity of vegagraphics fixup kext as I never had to use it, why do you need it? And have you tried to inject your vega 56 as a device with powerplaytable in stead of using vegatab kext?
As I am on OpenCore and not Clover I can't tell you how to do that but I can share my device settings for my vega.
These settings are from many different contributors here on tonymac so thank you all for sharing. Hope this can help you
(Sorry for bad grammar as english is not my native language)

<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>ATY,Kamarang</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>ATY,Kamarang</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>ATY,Kamarang</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>ATY,Kamarang</string>
<key>AAPL,boot-display</key>
<data>AQAAAA==</data>
<key>ATY,DeviceID</key>
<data>f2g=</data>
<key>ATY,EFIDriverType</key>
<data>Ag==</data>
<key>ATY,EFIEnabledMode</key>
<integer>1</integer>
<key>ATY,EFIVersion</key>
<data>MDEuMDAuMzE4MA==</data>
<key>ATY,EFIVersionB</key>
<data>MTEzLUQwNTAwMzAwLTEwMQ==</data>
<key>ATY,Rom#</key>
<string>113-D0500300-101</string>
<key>ATY,copyright</key>
<data>Q29weXJpZ2h0IEFNRCBJbmMuIEFsbCBSaWdodHMgUmVzZXJ2ZWQuIDIwMDUtMjAxOQ==</data>
<key>CFG_NVV</key>
<integer>2</integer>
<key>CFG_PTPL2_TBL</key>
<data>0gAAAMwAAADGAAAAwAAAALoAAAC0AAAAqgAAAKAAAACWAAAAjAAAAIIAAAB4AAAAbgAAAGQAAABaAAAAHgAAAA==</data>
<key>Force_Load_FalconSMUFW</key>
<integer>1</integer>
<key>PP_ACDCGpioDisabled</key>
<integer>0</integer>
<key>PP_DiDtSQPatternWidthOverride</key>
<integer>14</integer>
<key>PP_DiDtSQStallPatternOverride</key>
<integer>16383</integer>
<key>PP_DisableAutoWattman</key>
<integer>0</integer>
<key>PP_DisableClockStretcher</key>
<integer>1</integer>
<key>PP_DisableDIDT</key>
<integer>1</integer>
<key>PP_DisablePCCLimitControl</key>
<integer>1</integer>
<key>PP_DisablePowerContainment</key>
<integer>1</integer>
<key>PP_DisableULV</key>
<integer>1</integer>
<key>PP_EnableUploadFirmware</key>
<integer>0</integer>
<key>PP_Falcon_QuickTransition_Enable</key>
<integer>1</integer>
<key>PP_FuzzyFanControl</key>
<integer>0</integer>
<key>PP_GfxOffControl</key>
<integer>0</integer>
<key>PP_PhmSoftPowerPlayTable</key>
<data>pwIIAQBcAO8GAAAOLAAAGwBIAAAAgKkDAPBJAgAyAAgAAAAAAAAAAAAAAAAAAAIBXABAAjcClACPAbQAHgF6AIwArQEAAAAAYwIAAJAAmQJeATQBiAFoNgIAcQICAgAAAAAAAAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADtgPoA0wETASwBLAEsAQBAeIEAQGEAwAGYOoAAABAGQEAAdxKAQACAHcBAAOQkQEABWywAQAHAQjQTAEAAACAAAAAAAAAkKoBAAEAAAAAAAAAABDpAQACAAAAAAAAAAC0IQIAAwAAAAAAAAAASDMCAAQAAAAAAAAAAJh5AgAFAAAAAAEAAADwlAIABgAAAAABAAAAbKoCAAcAAAAAAQAAAAAEYOoAAABAGQEAANxKAQAAkF8BAAAACChuAAAALMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQBAAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEABQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAAAHARAQABAAAYcwEAAgAAAQgAmIUAAEC1AABg6gAAUMMAAAGAuwAAYOoAAJQLAQBQwwAAAnj/AABAGQEAtCcBAFDDAAADtCcBANxKAQDcSgEAUMMAAASAOAEAkF8BANxKAQBQwwAABdxKAQAAdwEAkF8BAFDDAAAGAHcBAAB3AQCQXwEAUMMAAAcAdwEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS6ANgCUEACgBUA5ABkAGQAZABkAGQAZABAAAAAAACBDEHpQClAKUALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CWAJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAACEA==</data>
<key>PP_PhmUseDummyBackEnd</key>
<integer>0</integer>
<key>PP_ToolsLogSpaceSize</key>
<integer>524288</integer>
<key>PP_WorkLoadPolicyMask</key>
<integer>1</integer>
<key>device_type</key>
<data>QVRZLEthbWFyYW5nUGFyZW50</data>
<key>hda-gfx</key>
<string>onboard-1</string>
<key>model</key>
<string>AMD Radeon RX Vega 56</string>
<key>name</key>
<string>ATY,KamarangParent</string>
</dict>
</dict>
 
thalaes said:
@Feartech I also read that, but in some old thread I read that you could use that boot arg to solve black screen issues. I tried it as my to monitors where connected with one dp-cable and one dvi-cable with dp-adapter and that gave me problems with black screen and two different resolutions although the monitors are same model. Bought another dp-cable yesterday and like magic I got same res and could take away agdpmod=pikera from my bootargs. Sleep works perfect now and no black screens .
@ DarJok I was wondering about the necessity of vegagraphics fixup kext as I never had to use it, why do you need it? And have you tried to inject your vega 56 as a device with powerplaytable in stead of using vegatab kext?
As I am on OpenCore and not Clover I can't tell you how to do that but I can share my device settings for my vega.
These settings are from many different contributors here on tonymac so thank you all for sharing. Hope this can help you
(Sorry for bad grammar as english is not my native language)

<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>ATY,Kamarang</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>ATY,Kamarang</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>ATY,Kamarang</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>ATY,Kamarang</string>
<key>AAPL,boot-display</key>
<data>AQAAAA==</data>
<key>ATY,DeviceID</key>
<data>f2g=</data>
<key>ATY,EFIDriverType</key>
<data>Ag==</data>
<key>ATY,EFIEnabledMode</key>
<integer>1</integer>
<key>ATY,EFIVersion</key>
<data>MDEuMDAuMzE4MA==</data>
<key>ATY,EFIVersionB</key>
<data>MTEzLUQwNTAwMzAwLTEwMQ==</data>
<key>ATY,Rom#</key>
<string>113-D0500300-101</string>
<key>ATY,copyright</key>
<data>Q29weXJpZ2h0IEFNRCBJbmMuIEFsbCBSaWdodHMgUmVzZXJ2ZWQuIDIwMDUtMjAxOQ==</data>
<key>CFG_NVV</key>
<integer>2</integer>
<key>CFG_PTPL2_TBL</key>
<data>0gAAAMwAAADGAAAAwAAAALoAAAC0AAAAqgAAAKAAAACWAAAAjAAAAIIAAAB4AAAAbgAAAGQAAABaAAAAHgAAAA==</data>
<key>Force_Load_FalconSMUFW</key>
<integer>1</integer>
<key>PP_ACDCGpioDisabled</key>
<integer>0</integer>
<key>PP_DiDtSQPatternWidthOverride</key>
<integer>14</integer>
<key>PP_DiDtSQStallPatternOverride</key>
<integer>16383</integer>
<key>PP_DisableAutoWattman</key>
<integer>0</integer>
<key>PP_DisableClockStretcher</key>
<integer>1</integer>
<key>PP_DisableDIDT</key>
<integer>1</integer>
<key>PP_DisablePCCLimitControl</key>
<integer>1</integer>
<key>PP_DisablePowerContainment</key>
<integer>1</integer>
<key>PP_DisableULV</key>
<integer>1</integer>
<key>PP_EnableUploadFirmware</key>
<integer>0</integer>
<key>PP_Falcon_QuickTransition_Enable</key>
<integer>1</integer>
<key>PP_FuzzyFanControl</key>
<integer>0</integer>
<key>PP_GfxOffControl</key>
<integer>0</integer>
<key>PP_PhmSoftPowerPlayTable</key>
<data>pwIIAQBcAO8GAAAOLAAAGwBIAAAAgKkDAPBJAgAyAAgAAAAAAAAAAAAAAAAAAAIBXABAAjcClACPAbQAHgF6AIwArQEAAAAAYwIAAJAAmQJeATQBiAFoNgIAcQICAgAAAAAAAAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADtgPoA0wETASwBLAEsAQBAeIEAQGEAwAGYOoAAABAGQEAAdxKAQACAHcBAAOQkQEABWywAQAHAQjQTAEAAACAAAAAAAAAkKoBAAEAAAAAAAAAABDpAQACAAAAAAAAAAC0IQIAAwAAAAAAAAAASDMCAAQAAAAAAAAAAJh5AgAFAAAAAAEAAADwlAIABgAAAAABAAAAbKoCAAcAAAAAAQAAAAAEYOoAAABAGQEAANxKAQAAkF8BAAAACChuAAAALMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQBAAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEABQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAAAHARAQABAAAYcwEAAgAAAQgAmIUAAEC1AABg6gAAUMMAAAGAuwAAYOoAAJQLAQBQwwAAAnj/AABAGQEAtCcBAFDDAAADtCcBANxKAQDcSgEAUMMAAASAOAEAkF8BANxKAQBQwwAABdxKAQAAdwEAkF8BAFDDAAAGAHcBAAB3AQCQXwEAUMMAAAcAdwEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS6ANgCUEACgBUA5ABkAGQAZABkAGQAZABAAAAAAACBDEHpQClAKUALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CWAJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAACEA==</data>
<key>PP_PhmUseDummyBackEnd</key>
<integer>0</integer>
<key>PP_ToolsLogSpaceSize</key>
<integer>524288</integer>
<key>PP_WorkLoadPolicyMask</key>
<integer>1</integer>
<key>device_type</key>
<data>QVRZLEthbWFyYW5nUGFyZW50</data>
<key>hda-gfx</key>
<string>onboard-1</string>
<key>model</key>
<string>AMD Radeon RX Vega 56</string>
<key>name</key>
<string>ATY,KamarangParent</string>
</dict>
</dict>
Click to expand...
Well now you mention it, the vegafixup kext is responsible in fixing the resolution I believe, I thought this was part of vegatab kext bundle as you render it with VGTAb, but it's separate, i'll try without it now.

Thanks for the settings, this will probably paste into config.plist below devices.
 
If I remember correctly clover divides the devices and the properties so PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) should go under devices and the rest should be under properties in clover configurator . You can check this thread
jaymonkey said:
RadeonVega-300.png


Injection of Device Properties for Power and Fan control
Last updated 14th May 2019

Update: MacOS Mojave 10.14.5+ includes a major overhaul of the Vega GPU drivers which should resolve all the power and fan control issues with most Vega cards and thus should make the methods outlined in this guide no longer necessary. Although you can still use the method to apply a core and/or memory overclock

For those users running earlier versions of MacOS the methods outlined in this guide should still work as long as you have a Vega GPU that can be controlled by MacOS.
Click to expand...
 
so this
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
should probably should be changed to something different
 
thalaes said:
so this
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
should probably should be changed to something different
Click to expand...
I tried your settings, then another try with VGTabMerge command, still black screen..
In the guide someone says to remove the vegatab kext because it is in devices anyway, tried that also.

in gfxutil i get the info: (hmm i'm not sure which one is devicepath?)
00:00.0 8086:191f /PCI0@0/pci8086,191f@0 = PciRoot(0x0)/Pci(0x0,0x0)
00:01.0 8086:1901 /PCI0@0/PEG0@1 = PciRoot(0x0)/Pci(0x1,0x0)
00:02.0 8086:1912 /PCI0@0/IGPU@2 = PciRoot(0x0)/Pci(0x2,0x0)
00:08.0 8086:1911 /PCI0@0/pci8086,1911@8 = PciRoot(0x0)/Pci(0x8,0x0)
00:14.0 8086:a2af /PCI0@0/XHC@14 = PciRoot(0x0)/Pci(0x14,0x0)
00:14.2 8086:a2b1 /PCI0@0/pci8086,a2b1@14,2 = PciRoot(0x0)/Pci(0x14,0x2)
00:16.0 8086:a2ba /PCI0@0/IMEI@16 = PciRoot(0x0)/Pci(0x16,0x0)
00:17.0 8086:a282 /PCI0@0/SAT0@17 = PciRoot(0x0)/Pci(0x17,0x0)
01:00.0 1022:1470 /PCI0@0/PEG0@1/PEGP@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
00:1c.0 8086:a294 /PCI0@0/RP05@1C = PciRoot(0x0)/Pci(0x1C,0x0)
00:1c.6 8086:a296 /PCI0@0/RP07@1C,6 = PciRoot(0x0)/Pci(0x1C,0x6)
00:1c.7 8086:a297 /PCI0@0/RP08@1C,7 = PciRoot(0x0)/Pci(0x1C,0x7)
00:1d.0 8086:a298 /PCI0@0/RP09@1D = PciRoot(0x0)/Pci(0x1D,0x0)
00:1f.2 8086:a2a1 /PCI0@0/PPMC@1F,2 = PciRoot(0x0)/Pci(0x1F,0x2)
00:1f.0 8086:a2c8 /PCI0@0/LPCB@1F = PciRoot(0x0)/Pci(0x1F,0x0)
00:1f.3 8086:a2f0 /PCI0@0/HDEF@1F,3 = PciRoot(0x0)/Pci(0x1F,0x3)
00:1f.4 8086:a2a3 /PCI0@0/SBUS@1F,4 = PciRoot(0x0)/Pci(0x1F,0x4)
00:1f.6 8086:15b8 /PCI0@0/GLAN@1F,6 = PciRoot(0x0)/Pci(0x1F,0x6)
02:00.0 1022:1471 /PCI0@0/PEG0@1/PEGP@0/pci-bridge@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
05:00.0 104c:823e /PCI0@0/RP07@1C,6/PXSX@0 = PciRoot(0x0)/Pci(0x1C,0x6)/Pci(0x0,0x0)
04:00.0 1b21:2142 /PCI0@0/RP05@1C/PXSX@0 = PciRoot(0x0)/Pci(0x1C,0x0)/Pci(0x0,0x0)
07:00.0 14e4:43a0 /PCI0@0/RP08@1C,7/ARPT@0 = PciRoot(0x0)/Pci(0x1C,0x7)/Pci(0x0,0x0)
06:00.0 104c:823f /PCI0@0/RP07@1C,6/PXSX@0/pci104c,823f@0 = PciRoot(0x0)/Pci(0x1C,0x6)/Pci(0x0,0x0)/Pci(0x0,0x0)
08:00.0 144d:a808 /PCI0@0/RP09@1D/PXSX@0 = PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)
03:00.0 1002:687f /PCI0@0/PEG0@1/PEGP@0/pci-bridge@0/GFX0@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
03:00.1 1002:aaf8 /PCI0@0/PEG0@1/PEGP@0/pci-bridge@0/HDAU@0,1 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x1)
Click to expand...

Is my devicepath as the default one like in the tutorial?
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top