Search results

The PR has been merged into the main repo. WEG 1.3.0 now contains this fix. Please take a look at it and carefully read the manual. All boot arguments, i.e. -igfxcflhdmi and -igfxcflhdmi2, used in the public testing stage have been removed.

Try the latest WEG 1.3.0. It now supports specifying the connector index for the converter. Please carefully read the LSPCON section in the manual .

Thanks for your response. What do you mean by not supported? You mean you can't even get 1080p HiDPI before putting the system to sleep? Hmm, really interesting result. In my case, the display still works and is lit up after the system wakes up. Good, so in your case HDMI audio output...

The public test stage 2 is now available. Looking forward to your responses.

I have some good news for you. HDMI 2.0 hotplug after the system boots is now working now. Public test will be available soon.

Not sure what you mean by "not working". Are you referring to HDMI output or the basic graphics acceleration. I have observed at least three issues in your config.plist. - You didn't specify the framebuffer id in the device property. - You didn't enable the framebuffer patch. - You didn't...

Thanks for your feedback. :clap: It seems that you are using a HDMI 1.4 cable, and your HDMI audio is working properly. Are you able to test with a HDMI 2.0 cable? i.e. Connect to an external monitor with a HDMI 2.0 port.

Take a look at https://www.tonymacx86.com/threads/fix-coffee-lake-intel-uhd-graphics-630-on-macos-mojave-hdmi-output-issue-public-testing-stage.275126/.

For those who have issues with HDMI output, check out https://www.tonymacx86.com/threads/fix-coffee-lake-intel-uhd-graphics-630-on-macos-mojave-hdmi-output-issue-public-testing-stage.275126/. I have tested on my XPS 15, and I am looking for feedback from others.

Time just seems to fly. It's April now. Finally I have some time to work on this issue, and I have found a solution to it. ;) - Brief Background and Issue Description So after you have applied my fix for the division-by-zero kernel panic (*1), your laptop should have graphics acceleration...

All binary patches for this issue are going to be deprecated. I have implemented a fix in WhateverGreen. Waiting for the PR being merged to the main repo. If you want to be the early bird and try the new fix, take a look at https://github.com/0xFireWolf/WhateverGreen. And here is the manual...

The ALT patch still works under 10.14.2. You can still find the same sequence of bytes in the latest driver. After you have upgraded to 10.14.2, you need to manually rebuild the kernel cache (type “sudo kextcache -i /“ in your terminal), otherwise Clover’s KextsToPatch does not seem to work.

Thanks for your reply. I would highly recommend you to use 0x14 (HBR2) instead, as it is a common max link rate value reported by 4K displays. The driver could adjust the final link rate based on some specific situations.

Hi bavariancake, Sorry for the late reply. I have noticed this issue and it might be related to the framebuffer port patching. Anyway, please use the following patches right now until I have time to fully investigate framebuffer ports. ALT: Set the maximum link rate in DPCD buffer to 0x14...

Your laptop is equipped with an Intel Core i7-8550U which is a Kaby Lake R processor, so you should use the AppleIntelKBLGraphicsFramebuffer driver. I checked your panic logs, and it turned out that you were using the frame buffer driver for Skylake at some day and the one for Kaby Lake at the...

I have updated the new patch and the new story. The previous patch should be discarded. Please use the new patch and leave comments if you have any issue.

I have identified the real issue that caused the kernel panic. The current patch is now deprecated and may have an impact on no display after waking up. For whoever watch this thread, please stay tuned. I will reply to this thread once I have updated it with the new patch.

I am not sure either. It seems that Camellia is another code base (??) and some framebuffers have this feature enabled. Update: For example, Apple uses 3E9B0006 on their RMBP 15 with Camellia enabled. Other framebuffers like 3E9B0000 and 3E9B0007 have Camellia disabled.

Yes, I agreed. We don't even need the original implementation of hwSetBacklight, as we don't use Camellia and you have just provided your own implementation.

I just tried your fork of WhateverGreen and it works well on my laptop. (without patching the ightUpEDP function) I didn't use the "Brightness Fix (ACPI 100)" patch. SSDT-PNLF.aml and the brightness slider works well now.