WhatEverGreen Support Topic

[obus]

Hi all.

I have a Xeon W 2175 processor without internal IGPU running OpenCore latest compile 0.0.4. and everything is working flawlessy. 

For Graphics I use a Sapphire water-cooled RX Vega 64 reference card. I just use Lilu and AppleALC-kext. My problem is that as soon as I use WEG I have the Apple logo and then black screen after progress bar.

Yesterday I've red here: https://www.insanelymac.com/forum/topic/337637-amd-radeon-vii-in-macos-mojave/?page=9 that the pink artefacts when booting in to Mojave 10.14.6 are fixed with new version of Lilu and WEG.

Today I compiled my own Lilu and WEG (embedded) and tested. Could confirm that the artefacts is gone but I am still booting to black screen with injected WEG. 

 

Any help appreciated.

 

 

 

Lilu_WEG.zip

Edited August 1, 2019 by obus

[Tony Arnold]

On 8/2/2019 at 5:12 AM, obus said:

I have a Xeon W 2175 processor without internal IGPU running OpenCore latest compile 0.0.4. and everything is working flawlessy. 

For Graphics I use a Sapphire water-cooled RX Vega 64 reference card. I just use Lilu and AppleALC-kext. My problem is that as soon as I use WEG I have the Apple logo and then black screen after progress bar.

 

I have a very similar setup (although I route my air-cooled Sapphire Vega 64 via a DP cable into a Thunderbolt 3 PCIe card and out to a TB3 display - the LG 5K Ultrafine). I found that I needed to add the following to my boot arguments to prevent it dumping to a black screen on boot (seems one of the other automatically applied patches is causing problems for me, at least):

agdpmod=pikera

The display still turns off during the boot process close to the end, but comes back on again before it's finished. See if that helps?

 

I still have black screens upon waking from sleep sometimes, but I assume that's the Thunderbolt card, not the GPU/display. Connecting/disconnecting the power to the display always brings it back (despite being a massive PITA).

Edited August 2, 2019 by Tony Arnold
Adding more information

[obus]

9 hours ago, Tony Arnold said:

 

I have a very similar setup (although I route my air-cooled Sapphire Vega 64 via a DP cable into a Thunderbolt 3 PCIe card and out to a TB3 display - the LG 5K Ultrafine). I found that I needed to add the following to my boot arguments to prevent it dumping to a black screen on boot (seems one of the other automatically applied patches is causing problems for me, at least):

agdpmod=pikera

The display still turns off during the boot process close to the end, but comes back on again before it's finished. See if that helps?

 

I still have black screens upon waking from sleep sometimes, but I assume that's the Thunderbolt card, not the GPU/display. Connecting/disconnecting the power to the display always brings it back (despite being a massive PITA).

hi @Tony Arnold

This is exactly the same behaviour as I have without WEG and the only difference is that I connect my display using a DP to HDMI cable. 

Tested with agdpmod=pikera and newly compiled Lilu and WEG and everything work like a charm. Pink artefacts gone and booting into macOS works as it should even if I have NO SIGNAL for a second between the  progress bar and the login window. 

Thank's for the tip. 

[asstastic]

So a couple of errors I could use help with.

First I have the following set in OpenCore config.plist

	<key>DeviceProperties</key>
	<dict>
		<key>Add</key>
		<dict>
			<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
			<dict>
				<key>layout-id</key>
				<data>AQAAAA==</data>
			</dict>
			<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
			<dict>
				<key>AAPL,ig-platform-id</key>
				<data>BwCbPg==</data>
				<key>framebuffer-patch-enable</key>
				<true/>
				<key>enable-hdmi-dividers-fix</key>
				<true/>
				<key>framebuffer-con0-enable</key>
				<true/>
				<key>framebuffer-con0-type</key>
				<data>BAAAAA==</data>
				<key>framebuffer-con1-enable</key>
				<true/>
				<key>framebuffer-con1-type</key>
				<data>AAgAAA==</data>
			</dict>
		</dict>
		<key>Block</key>
		<dict/>
	</dict>

However WhateverGreen does not appear to be patching the framebuffer connectors:

WhateverGreen:     weg @ (DBG) non-apple-fw proceeding with devprops 1
Lilu:   iokit @ (DBG) compatible property starts with pci1043,8694 and is 47 bytes
Lilu:   iokit @ (DBG) fixing compatible to have IGPU
Lilu:   iokit @ (DBG) read pci config discovered IGPU space to be 0x00001000
WhateverGreen:   iokit @ (DBG) getOSData device-id has 3E92 value
WhateverGreen:     weg @ (DBG) IGPU has real 3E92 acpi 3E92 fake 0000 and model Intel UHD Graphics 630
WhateverGreen:     weg @ (DBG) adding missing model Intel UHD Graphics 630 from autotodetect
WhateverGreen:     weg @ (DBG) found existing built-in
Lilu:   iokit @ (DBG) compatible property starts with pci19da,1438 and is 47 bytes
Lilu:   iokit @ (DBG) fixing compatible to have GFX0
WhateverGreen:     weg @ (DBG) found existing built-in
WhateverGreen:     weg @ (DBG) detecting policy
WhateverGreen:     weg @ (DBG) board is --REDACTED--
Lilu:   iokit @ (DBG) compatible property starts with pci1043,8694 and is 47 bytes
Lilu:   iokit @ (DBG) fixing compatible to have IMEI
WhateverGreen:   iokit @ (DBG) getOSData framebuffer-patch-enable was not found
WhateverGreen:   iokit @ (DBG) getOSData framebuffer-patch0-enable was not found
WhateverGreen:   iokit @ (DBG) getOSData dpcd-max-link-rate was not found
WhateverGreen:    igfx @ (DBG) MLR: No custom max link rate specified. Will use 0x14 as the default value.
WhateverGreen:   iokit @ (DBG) getOSData max-backlight-freq was not found

 

Next, my motherboard has 2 display connectors, DVI and HDMI. I have 2 monitors, a Dell 1909W (1440x900) and a Lenovo Y27gA (1920x1080). If I plug one monitor in to the motherboard, it is not detected at all. When I plug the 2nd monitor in, whatever monitor is plugged in to the DVI port gets detected and a display signal for the monitor plugged in to the DVI port is sent to the monitor on HDMI. For example: Dell monitor is plugged in to DVI and Lenovo is plugged in to HDMI. System Preferences > Displays shows a single Dell 1909 monitor plugged in. The Dell monitor does not receive a display signal and the Lenovo monitor displays an "Input Signal Out of Range" warning. I have also tested with a 1920x1200 Samsung SyncMaster display. With the Samsung plugged in to DVI and the Dell plugged in to HDMI, System Preferences shows a single SyncMaster display plugged in and the Dell monitor on-screen-display menu shows the Dell monitor is receiving a 1920x1200 resolution input signal that is obviously intended for the Samsung display.

 

WTF is going on here?

 

[stevezheng]

@vit9696Hi, the WTG really makes a big improvements on HDMI. Thank you guys!

 

I have a question about the usage of complete-modeset-framebuffer.

If I only want to enforce complete modest on con1, what value should I input for complete-modeset-framebuffer? I have some trouble understanding "Each index is a byte in a 64-bit word; for example, value 0x010203 specifies framebuffers 1, 2, 3." in https://github.com/acidanthera/WhateverGreen/blob/master/README.md. Could you give more details or write a config properties sample?

 

Thank you so much!

 

Edited August 10, 2019 by stevezheng

[bobpedro]

On 11/10/2018 at 11:20 PM, TheBloke said:

Hi all

 

I am considering upgrading my GPU to an AMD RX580 (potentially the Sapphire Radeon RX 580 NITRO+ 8GB).

 

Is there anyone in this thread who using an RX580 or RX560 with a Legacy boot system, such as an X58 system?  If so, I would be very glad to hear how it works for you: does the RX580 work perfectly, with picture at boot, no special tricks, no errors?   I'd be especially interested to hear from anyone who has a multi-monitor system on an RX580/560 using Legacy boot.  Especially if you have 3+ monitors.

 

My current 7970 / R9 280X works with six monitors, but from boot I only get a picture on two of the six.  I have to sleep and wake to get a picture on all 6.  I am unsure if this is specific to my current GPU, but I do think it might be somehow related to Legacy boot.  So I am wondering if I will get the same problem with an RX 580.  This problem is not too terrible.  However in order to use 6 displays with an RX580 I will need to use a DisplayPort hub, and I have heard that some hubs can have a problem with sleep & wake.  So ideally I hope I won't need to sleep/wake with the RX580 in order to get a picture on all monitors.

 

If anyone can give me their experience of an RX GPU with Legacy boot, I would be very grateful.  Thanks in advance.

 

Hey @TheBloke have you ever been able to find a solution for this problem? Or did you replaced the card with a RX580? I am facing the same issue with an RX 570. In my case the problem exists for both DVI-ports. I informed myself in advance about the OOB-Capabilities of the card before buying. Thats why I'm disappointed about this problem. Nevertheless I was happy to find your posts and I am looking forward to hear from you!

[TheBloke]

42 minutes ago, bobpedro2 said:

 

Hey @TheBloke have you ever been able to find a solution for this problem? Or did you replaced the card with a RX580? I am facing the same issue with an RX 570. In my case the problem exists for both DVI-ports. I informed myself in advance about the OOB-Capabilities of the card before buying. Thats why I'm disappointed about this problem. Nevertheless I was happy to find your posts and I am looking forward to hear from you!

Hi Bob

 

No, I never found a solution.  I spent literally days on it, and posted multiple times.  But no-one ever responded to my questions and none of my troubleshooting has ever helped.

 

My current situation is as follows:

1. I'm running the same AMD 7970Ghz (R9 280X) on my X58 legacy-boot mobo, in Mojave 10.14.5.  I currently have 5 monitors connected, but sometimes it's 6.
2. On boot, I get a picture on two of them, and the rest have no display.
3. Since 10.14.1, I've had an additional issue: the other monitors with no display aren't just black, they are flicking on/off rapidly, getting a signal then no signal.
4. Since 10.14.5, I got yet another problem:  purple lines on boot, and no picture on any monitor from boot.  At first the only way I could find to solve this was to unplug/replug monitors after boot, and eventually I would get a picture on the main monitor.
   1. Luckily, this was fixed by the latest WEG beta, 1.3.1, that someone posted here a few weeks ago.  Having this latest WEG installed means I now get a picture on two screens at boot again.
5. As soon as I can see the login screen, I put the computer to sleep.  Then I immediately wake it up.  After it has woken, I will have a picture on all monitors, and can then login and use the system as normal.
6. If I log in before the system sleeps, I will notice that the kernel is using 100% CPU, and opening Console will display a lot of errors from AMDRadeonAccelerator and other similar systems.  Something about an error on VBLANK interval.  It was googling this error that eventually lead me to some info on a German forum that suggested to me that my problems were the result of my legacy boot; before that I always thought it was related to framebuffer config or something like that.

 

I thought about upgrading to the RX580, however given there was no guarantee it would help, and also because I sometimes run 6 monitors and RX580s have at most 5 outputs, I haven't yet.  I hope to be upgrading to a new PC in the next few months, at which point I will finally have UEFI boot.  At that point I will get a new GPU as well (and maybe use DisplayLink switching in order to allow 5+ monitors)

 

Sorry to hear you have the same problem.   Do you get a picture on all screens after you sleep & wake?  If so then yeah it sounds like the same issue as me, and if you are on legacy boot then quite possibly there simply is not a solution    But it's not so terrible to have to sleep & wake after every boot, just a bit of an annoyance.

Edited August 14, 2019 by TheBloke

[bobpedro]

13 hours ago, TheBloke said:

Hi Bob

 

No, I never found a solution.  I spent literally days on it, and posted multiple times.  But no-one ever responded to my questions and none of my troubleshooting has ever helped.

 

My current situation is as follows:

1. I'm running the same AMD 7970Ghz (R9 280X) on my X58 legacy-boot mobo, in Mojave 10.14.5.  I currently have 5 monitors connected, but sometimes it's 6.
2. On boot, I get a picture on two of them, and the rest have no display.
3. Since 10.14.1, I've had an additional issue: the other monitors with no display aren't just black, they are flicking on/off rapidly, getting a signal then no signal.
4. Since 10.14.5, I got yet another problem:  purple lines on boot, and no picture on any monitor from boot.  At first the only way I could find to solve this was to unplug/replug monitors after boot, and eventually I would get a picture on the main monitor.
   1. Luckily, this was fixed by the latest WEG beta, 1.3.1, that someone posted here a few weeks ago.  Having this latest WEG installed means I now get a picture on two screens at boot again.
5. As soon as I can see the login screen, I put the computer to sleep.  Then I immediately wake it up.  After it has woken, I will have a picture on all monitors, and can then login and use the system as normal.
6. If I log in before the system sleeps, I will notice that the kernel is using 100% CPU, and opening Console will display a lot of errors from AMDRadeonAccelerator and other similar systems.  Something about an error on VBLANK interval.  It was googling this error that eventually lead me to some info on a German forum that suggested to me that my problems were the result of my legacy boot; before that I always thought it was related to framebuffer config or something like that.

 

I thought about upgrading to the RX580, however given there was no guarantee it would help, and also because I sometimes run 6 monitors and RX580s have at most 5 outputs, I haven't yet.  I hope to be upgrading to a new PC in the next few months, at which point I will finally have UEFI boot.  At that point I will get a new GPU as well (and maybe use DisplayLink switching in order to allow 5+ monitors)

 

Sorry to hear you have the same problem.   Do you get a picture on all screens after you sleep & wake?  If so then yeah it sounds like the same issue as me, and if you are on legacy boot then quite possibly there simply is not a solution    But it's not so terrible to have to sleep & wake after every boot, just a bit of an annoyance.

 

Thanks for the fast response!

Sad to hear that the problem still exist for you too...

 

I have a 2 monitor setup, initially I was running them on DVI with a Geforce Card. But when support for nVidia WebDriver was cancelled with the introduction of Mojave I moved to the radeon RX 570. After finding the problem with DVI I connected one monitor using a DVI to HDMI Adapter and the other Monitor using DP to HDMI Adapter (this Monitor luckily has a HDMI-Port). This was not a satisfying but working solution... 

 

Now I have the possibility to change one Monitor with an old Apple Cinema Display which gets connected with DVI-D. Therefore I gave this old problem another try. Unfortunately it seems that I have to go with another adapter in this case too - it costs some money but will probably be the faster solution...

 

Regarding UEFI: my MoBo is one of the first generations that supports UEFI, therefore I use Clover in UEFI-Mode so the problem might not be UEFI-related. When I start the machine with a monitor connected to DVI, I can confirm display flickering and everything feels unresponsive. Logs are spammed with VBLANK errors too. The monitor is recognised correctly (System Preferences and Settings) but the Display stays black. After going to sleep the DVI-Monitor gets image and the flickering and errors are gone...

 

Unless this problem persists in the future, using a MST-Hub might be a possible solution for your setup.

Regards

[asstastic]

Finally got UHD 630 working. Here are the troubleshooting steps I went through to figure it out.

 

First, I lucked out testing things out when I was able to get the DVI output working. To get the DVI port working, I had to update to the newest WEG kext, use a DVI to DVI cable to connect the monitor, and generate a patch in Hackintool with the following options:

• Set the platform ID to 0x3E9B0007 for a desktop UHD 360
• Enable the Framebuffer port limit option to reduce the port count from 3 to 2
• Enable the DP->HDMI patch option (HDMI and DVI are considered to be the same. Set Type to HDMI for both HDMI and DVI physical ports)

I also have the hotplug reboot fix and HDMI infinite loop fix enabled though I haven't fully tested to see if they are required. With the default connector info, the port worked on Index 3, Bus ID 0x04. While the monitor showed up in the hackintool connectors list, I only got a black screen with cursor or corrupted display when using the monitor. To fix this issue, I had to switch my system model from iMac18.2 to iMac18.1. Troubleshooting was helped by the fact that I could connect my 2nd display to a working nvidia card for fully working display on the 2nd monitor.

 

The final step was to get the HDMI output on the motherboard working for my 2nd monitor. Getting the HDMI port working required setting the correct Index and Bus ID for the port. There are four Index values that can be used; 0, 1, 2 and 3. Index 0 is reserved for internal laptop/iMac LCD displays and Index 3 was already used for the DVI port. That leaves Index 1 and 2 as possible options for the HDMI port. Using Index 2, hot-plugging a monitor into the HDMI port resulted in the displays briefly going black then the monitor on HDMI would show up in display preferences but output for the display would be sent to DVI. Using Index 1, hot-plugging a monitor into HDMI did nothing. This led me to deduce that Index 2 was the correct selection for the port. Next, I had to figure out the correct Bus ID. For HDMI, the valid Bus ID's are 0x01, 0x02, 0x04, and 0x06. Since Bus ID's must be unique and 0x04 was already used by the DVI port, I just had to test with 0x01, 0x02 and 0x06. In my case Bus ID 0x02 was the only one that worked for the port.

 

With the correct connector Index and Bus ID for the two physical ports on the motherboard set both UHD 630 ports are fully working.

 

The only issue I have now is that the displays start going crazy if I boot with both plugged in. Unplugging one display and plugging it back in after boot appears to resolve the issue until next boot.

[asstastic]

On 8/15/2019 at 3:38 AM, bobpedro said:

Unless this problem persists in the future, using a MST-Hub might be a possible solution for your setup.

Regards

Unless Apple has recently added support or AMD graphics are explicitly supported, macOS does not support MST. Using an MST hub or MST daisy-chaining on Apple hardware under macOS results in mirrored output on all the displays on the MST without the option to extend the displays. The issue appears to be an OS limitation as MST operates fine on Apple hardware running Windows through Boot Camp.

[camielverdult]

Hi all, I'm having trouble getting hardware acceleration to work with my Radeon VII. My setup is the following:

AMD Ryzen 5 3600X

Asus X470-PRO

MSI Radeon VII

macos 10.14.6 (18G87)

 

I have updated the vBIOS in windows, and have tried RadeonDeInit set to true and false. CSM is set to disabled. Here is my darwin dump for anyone interested 

DarwinDumper_3.0.4_24.08_16.24.31_iMacPro1,1_AMI_X64_5056_Unknown_18G87_camiel.zip

[Andres ZeroCross]

53 minutes ago, camielverdult said:

Hi all, I'm having trouble getting hardware acceleration to work with my Radeon VII. My setup is the following:

AMD Ryzen 5 3600X

Asus X470-PRO

MSI Radeon VII

macos 10.14.6 (18G87)

 

I have updated the vBIOS in windows, and have tried RadeonDeInit set to true and false. CSM is set to disabled. Here is my darwin dump for anyone interested 

DarwinDumper_3.0.4_24.08_16.24.31_iMacPro1,1_AMI_X64_5056_Unknown_18G87_camiel.zip

 

System profile shown that you have acceleration of Radeon VII

[iCanaro]

 

the cables between the radeon VII and the monitor are 4K 60Hz ???

[camielverdult]

On 8/24/2019 at 6:10 PM, Andres ZeroCross said:

 

System profile shown that you have acceleration of Radeon VII

Hi, thank you for the response. The card seems to be working, except for that many electron apps such as discord and the launchpad lag a lot and show a ton of artifacts. 

On 8/24/2019 at 6:52 PM, iCanaro said:

 

the cables between the radeon VII and the monitor are 4K 60Hz ???

Yes, they are. Everything is working on Windows, I’m pretty sure this is a macos specific issue. 

 

Edited August 25, 2019 by camielverdult

[camielverdult]

Hi again, I'm kind of at the end of my rope here. Does anyone have any idea on how to counter the problem I am having? The kernel seems to be throwing a ton of these errors while booting macos:

kernel: (AMDRadeonX5000HWLibs) AMD Error:
kernel: (AMDRadeonX5000HWLibs)   CAIL_ASICSetup() failed (CAILRESULT=1)
kernel: (AMDRadeonX5000HWLibs) AMD Error:
kernel: (AMDRadeonX5000HWLibs) initializeAdapter() failed!

 

 

Edited August 25, 2019 by camielverdult

[jsl2000]

3 hours ago, camielverdult said:

Hi again, I'm kind of at the end of my rope here. Does anyone have any idea on how to counter the problem I am having? The kernel seems to be throwing a ton of these errors while booting macos:

kernel: (AMDRadeonX5000HWLibs) AMD Error:
kernel: (AMDRadeonX5000HWLibs)   CAIL_ASICSetup() failed (CAILRESULT=1)
kernel: (AMDRadeonX5000HWLibs) AMD Error:
kernel: (AMDRadeonX5000HWLibs) initializeAdapter() failed!

 

 

Please try this GPU at 10.14.5 instead of 10.14.6 brcause it's working in Intel CPU hackintosh (you may google by AMD Vega VII hackintosh to find the link for your reference.)

Edited August 26, 2019 by jsl2000

[exquirentibus]

I've got a working 10.12.6 Gigabyte GA-Z270XP-SLI Kaby Lake i7=7700K with an nVidia GTX-285 with 2 dual port DVI @ 2560 x 1440. It's setup with Clover and kexts from exactly 2 years ago with no changes.

I want to move to 10.14.6, replacing the nVidia with an ASUS Radeon RX 570 4GB Gaming OC Edition (2 dual port DVI, HDMI, DP).

I really want to use the DVI ports, as I have a 4 station dual port DVI KVM that my other computers connect to. My test bed monitors have DVI and HDMI.

I don't care about how fast the graphics are. My only use is Logic Pro and XCode development with Xamarin.

I had to take a lot of time off due to medical issues - but I've been reading and reading all the threads and am about ready to start moving to 10.14.6 and the Radeon.

1. What kind of trouble am I going to be in trying to use the DVI ports? Did I pick the wrong card - or can this be salvaged using Hackintool, WEG, etc? I'd even be happy if I could just keep using the GTX 285, but I'm guessing they have dropped support for it in 10.14.6?

2. Should I just modify my config.plist and EFI - keeping same serials and iMessage, etc. (updating to current Clover, only latest recommended minimal kexts) and do a Fresh Installation to a formatted SSD from an Install USB, and then migrate Logic and my setup using a Carbon Copy clone of 10.12.6? I would guess that minimizing the variables would be a good thing, as in starting from scratch instead of upgrading? But, I could be wrong and maybe upgrading would work better?

3. Any non-obvious 'Most Important Tips' to get this working? Links, tips, anything you feel is important?

4. If upgrading is preferred over a clean install, can I keep WiFi turned off, so as not to alert Apple while I'm getting it all setup?

I still spend a lot of time interfacing with the horribly complex and uncaring medical system - and it would be great to have something in my life that just works well and doesn't cause massive stress!!

Thanks in advance!!!

[norton287]

I have macOS Catalina 10.15 Beta 7 running on my hack ok, but I don't get 4k out of my Saphire Pulse RX 580 8GB card on my 4k monitor.  I can scale the display to 4k through preferences but when I reboot all my windows are all over the place and not where I left them.  I am running the latest lilu and weg and don't have any options enabled in my config.plist other than inject intel for my headless UHD630 on board card.  

 

I get 4k fine in mojave with the same setup and config so I am not sure what needs to be done for catalina.  Any ideas?

 

Thanks in advance

 

 

[telepati]

I am getting boot glitch while using HD630. My connection type is HDMI and this is the only option for my monitor. is there a way to eliminate this glitch?

 

[bobpedro]

On 8/28/2019 at 6:11 PM, HighSierraWannabe said:

I've got a working 10.12.6 Gigabyte GA-Z270XP-SLI Kaby Lake i7=7700K with an nVidia GTX-285 with 2 dual port DVI @ 2560 x 1440. It's setup with Clover and kexts from exactly 2 years ago with no changes.

I want to move to 10.14.6, replacing the nVidia with an ASUS Radeon RX 570 4GB Gaming OC Edition (2 dual port DVI, HDMI, DP).

I really want to use the DVI ports, as I have a 4 station dual port DVI KVM that my other computers connect to. My test bed monitors have DVI and HDMI.

I don't care about how fast the graphics are. My only use is Logic Pro and XCode development with Xamarin.

I had to take a lot of time off due to medical issues - but I've been reading and reading all the threads and am about ready to start moving to 10.14.6 and the Radeon.

1. What kind of trouble am I going to be in trying to use the DVI ports? Did I pick the wrong card - or can this be salvaged using Hackintool, WEG, etc? I'd even be happy if I could just keep using the GTX 285, but I'm guessing they have dropped support for it in 10.14.6?

2. Should I just modify my config.plist and EFI - keeping same serials and iMessage, etc. (updating to current Clover, only latest recommended minimal kexts) and do a Fresh Installation to a formatted SSD from an Install USB, and then migrate Logic and my setup using a Carbon Copy clone of 10.12.6? I would guess that minimizing the variables would be a good thing, as in starting from scratch instead of upgrading? But, I could be wrong and maybe upgrading would work better?

3. Any non-obvious 'Most Important Tips' to get this working? Links, tips, anything you feel is important?

4. If upgrading is preferred over a clean install, can I keep WiFi turned off, so as not to alert Apple while I'm getting it all setup?

I still spend a lot of time interfacing with the horribly complex and uncaring medical system - and it would be great to have something in my life that just works well and doesn't cause massive stress!!

Thanks in advance!!!

 

Hey @HighSierraWannabe,

 

I have the exactly same card: Asus Radeon RX 570 4GB Gaming OC Edition, but don't expect too much from native support of the DVI ports.

As you probably read in @TheBlokes answer, the only known workaround at the moment requires a short period of sleep on the first start to get them properly working. If you find another solution feel free to share it, but I tried a lot of different things from clover patches (Framebuffer, InjectATI, RadeonDeInit, LoadVBios) to WEG boot args (-raddvi) and nothing got them to work properly on first boot. Maybe patching the Framebuffers is another option, but I just ordered a Dual-Link DP-DVI Adapter to run my Apple Cinema Display. It's not an elegant but probably working solution.

 

Good luck :D

[exquirentibus]

36 minutes ago, bobpedro said:

I have the exactly same card: Asus Radeon RX 570 4GB Gaming OC Edition, but don't expect too much from native support of the DVI ports.

As you probably read in @TheBlokes answer, the only known workaround at the moment requires a short period of sleep on the first start to get them properly working. If you find another solution feel free to share it, but I tried a lot of different things from clover patches (Framebuffer, InjectATI, RadeonDeInit, LoadVBios) to WEG boot args (-raddvi) and nothing got them to work properly on first boot. Maybe patching the Framebuffers is another option, but I just ordered a Dual-Link DP-DVI Adapter to run my Apple Cinema Display. It's not an elegant but probably working solution.

@bobpedro - which 'Dual-Link DP-DVI' adapters did you order?  I had searched for one, but seemed to only find negative reviews as far as getting true Dual-Link DVI out that would handle 2560 x 1440.

 

Please report on your success or failure with the device.  It if it works, that would be very useful!!

 

Are you using 10.14.6?

 

If I just need to buy another RX card to get DVI working, I'll certainly go for that.  Is it your understanding that for ANY RX cards, DVI output just won't work?

 

From my limited understanding, I think there will be a way to use Hackintool.  I ?believe? that HDMI and DVI are about the same as far as MacOS is concerned, and that setting the DP -> HDMI checkbox in Patch Options -> General will be necessary.   Then some config in the 'Connector Info' tab to setup a 'connector' for DVI.

 

As to how exactly to do that using Hackintools ... I'm totally clueless?

 

So, I may need to ask questions in the Hackintool thread?

 

[jsl2000]

3 hours ago, telepati said:

I am getting boot glitch while using HD630. My connection type is HDMI and this is the only option for my monitor. is there a way to eliminate this glitch?

 

Please check the specification of your HDMI cable and brand of monitor.

For example ASUS PB278 monitor with some HDMI cable was not fully compatible with Intel HD 4600 or UHD 630 connecting by HDMI port.

No such an issue by connecting DP port.

I had the similar glitch issue (different pattern) using ASUS PB278 monitor with HDMI port.

No such an issue using ASUS PB287Q monitor with HDMI port or changing to another HDMI 2.0 certified cable for PB278 monitor.

 

Edited September 2, 2019 by jsl2000

[jsl2000]

On 8/15/2019 at 2:22 AM, TheBloke said:

Hi Bob

 

No, I never found a solution.  I spent literally days on it, and posted multiple times.  But no-one ever responded to my questions and none of my troubleshooting has ever helped.

 

My current situation is as follows:

1. I'm running the same AMD 7970Ghz (R9 280X) on my X58 legacy-boot mobo, in Mojave 10.14.5.  I currently have 5 monitors connected, but sometimes it's 6.
2. On boot, I get a picture on two of them, and the rest have no display.
3. Since 10.14.1, I've had an additional issue: the other monitors with no display aren't just black, they are flicking on/off rapidly, getting a signal then no signal.
4. Since 10.14.5, I got yet another problem:  purple lines on boot, and no picture on any monitor from boot.  At first the only way I could find to solve this was to unplug/replug monitors after boot, and eventually I would get a picture on the main monitor.
   1. Luckily, this was fixed by the latest WEG beta, 1.3.1, that someone posted here a few weeks ago.  Having this latest WEG installed means I now get a picture on two screens at boot again.
5. As soon as I can see the login screen, I put the computer to sleep.  Then I immediately wake it up.  After it has woken, I will have a picture on all monitors, and can then login and use the system as normal.
6. If I log in before the system sleeps, I will notice that the kernel is using 100% CPU, and opening Console will display a lot of errors from AMDRadeonAccelerator and other similar systems.  Something about an error on VBLANK interval.  It was googling this error that eventually lead me to some info on a German forum that suggested to me that my problems were the result of my legacy boot; before that I always thought it was related to framebuffer config or something like that.

 

I thought about upgrading to the RX580, however given there was no guarantee it would help, and also because I sometimes run 6 monitors and RX580s have at most 5 outputs, I haven't yet.  I hope to be upgrading to a new PC in the next few months, at which point I will finally have UEFI boot.  At that point I will get a new GPU as well (and maybe use DisplayLink switching in order to allow 5+ monitors)

 

Sorry to hear you have the same problem.   Do you get a picture on all screens after you sleep & wake?  If so then yeah it sounds like the same issue as me, and if you are on legacy boot then quite possibly there simply is not a solution    But it's not so terrible to have to sleep & wake after every boot, just a bit of an annoyance.

My FX-6300 hackintosh with RX-560 GPU had the same issue as yours.

Only sleep-wakeup method can activate multiple monitors, otherwise only HDMI monitor working at 10.13.6/10.14.5/10.14.6.

[bobpedro]

On 9/2/2019 at 12:37 AM, HighSierraWannabe said:

@bobpedro - which 'Dual-Link DP-DVI' adapters did you order?  I had searched for one, but seemed to only find negative reviews as far as getting true Dual-Link DVI out that would handle 2560 x 1440.

 

Please report on your success or failure with the device.  It if it works, that would be very useful!!

 

Are you using 10.14.6?

 

If I just need to buy another RX card to get DVI working, I'll certainly go for that.  Is it your understanding that for ANY RX cards, DVI output just won't work?

 

From my limited understanding, I think there will be a way to use Hackintool.  I ?believe? that HDMI and DVI are about the same as far as MacOS is concerned, and that setting the DP -> HDMI checkbox in Patch Options -> General will be necessary.   Then some config in the 'Connector Info' tab to setup a 'connector' for DVI.

 

As to how exactly to do that using Hackintools ... I'm totally clueless?

 

So, I may need to ask questions in the Hackintool thread?

 

 

@HighSierraWannabe I ordered this adapter from Club3D as it is one of the only adapters available which is capable of a full 2560x1600 resolution. It arrived today, and after some configuration I was able to get the full resolution to work. The only issue I noticed is some blue flickering on black screens (noticeable on boot and youtube)... I think I will give the Apple (MB571Z/A) Adapter another try (I can lend one from work) as it might be superior to the Club3D adapter... but then an additional miniDP -> DP adapter is necessary - not sure if its a good idea...

 

I am on Mojave 10.14.5 now, but I want to perform the update in the next few weeks.

 

I think the problem exists for all RX cards, as @jsl2000 has it with the RX560, I have it with RX570 and @TheBloke with a RX580.

 

EDIT1: After uninstalling SwitchResX the blue flickering is gone, might have been related to this. Not sure if its worth trying the Apple (MB571Z/A) Adapter then...

 

EDIT2: I noticed some small red dot flickering in terminal window, verified by making it fullscreen. Seems like the adapter has some issues with black or the disorder is only noticeable there...

 

EDIT3: Today I tried the Apple (MB571Z/A) adapter at from with a miniDP -> DP adapter and it works perfectly. No more flickering and a lot more supported resolutions to choose from. The Club3D Adapter goes back, MB571Z/A ordered on eBay.

Edited September 3, 2019 by bobpedro

[telepati]

23 hours ago, jsl2000 said:

Please check the specification of your HDMI cable and brand of monitor.

For example ASUS PB278 monitor with some HDMI cable was not fully compatible with Intel HD 4600 or UHD 630 connecting by HDMI port.

No such an issue by connecting DP port.

I had the similar glitch issue (different pattern) using ASUS PB278 monitor with HDMI port.

No such an issue using ASUS PB287Q monitor with HDMI port or changing to another HDMI 2.0 certified cable for PB278 monitor.

 

 

I am using Apple MC838ZM/B HDMI to HDMI Cable and my monitor is old HP 2711x non K monitor (https://support.hp.com/ca-en/document/c02652519). These are both compatible with each other. Tomorrow I'm gonna try own cable that comes out of the monitor's box. We will see what will happens.