Recent content by DEXXX

  1. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    Setting 16 bits per channel is wrong, apple devices are 6 bits per channel: 6 for Red, 6 for Green and 6 for Blue, that gives 18 + 6 for Gamma (not sure) = 24 bit color in total, as shown in "About this Mac" info. So you should set byte 20 to "95" which is 10010101 in binary, where Bit 7=1...
  2. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    @RehabMan I compared the DarwinDumper EDID dump and it's the following. Original one: --- header: 00 ff ff ff ff ff ff 00 serial number: 0d af 20 17 00 00 00 00 02 15 version: 01 03 basic params: 80 26 15 78 0a chroma info: d8 95 a3 55 4d 9d 27 0f 50 54 established...
  3. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    my original EDID was: 00ffffffffffff000daf20170000000002150103802615780ad895a3554d9d270f5054000000010101010101010101010101010101012e3680a070381f40302035007ed710000018000000fe004e3137334847452d4c31310a20000000fe00434d4f0a202020202020202020000000fe004e3137334847452d4c31310a20006e my current...
  4. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    you can try injecting EDID via DSDT/SSDT patching with MacIASL, there is a corresponding patch called "Generic with EDID" in Rehabman's repo, connected to his MacIASL. You must detect where (DSDT or SSDT-***) appropriate device is located (actually the patch will tell you if it is applicable)...
  5. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    at least it is PID: 0x9cf2 and VID: 0x610 of Macbook Air, but probably some other values, unclear to me, as injecting only these in Clover didn't work in my personal case.
  6. DEXXX

    [FIX] Corrupt color depth in High Sierra/Mojave

    Hey guys! Recently I updated from my perfect Sierra hackintosh laptop directly to Mojave, skipping High Sierra, and encountered a nasty color depth glitch. Since Yosemite I've been using ig-platform-id = 0x0a260006 for my Haswell Intel HD4600 Mobile. But in Mojave, despite of full QE/CI, I...
  7. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    already injected EDID via ACPI patching, now it is shown correctly along with new ProductID and VendorID but doesn't affect my problem, so it looks like custom EDID cannot help here. scarceness of documentation and absence of any examples makes it impossible. found a solution - rolling back...
  8. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    Now answering this question I can say that BLKT values at least from 1 to 5 don't bring any changes. Can incorrect EDID be the reason of my problem? I also tried to inject CustomEDID in clover according to this guide https://www.tonymacx86.com/threads/fixing-brightness-with-custom-edid.219413/...
  9. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    I just read but it's really hard for a humanist like me :) besides it will be useful to me once in a lifetime maybe :) Name(BKLT, 4) disables brightness control totally, because of bit0 now is not set I suppose... How to set multiple bits then? For example I wish to set bit0=1 and bit2=1...
  10. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    Okay, I see that RMCF.GRAN set to 1 should do the thing, as it corresponds to 128-bit color depth. Right? But I can't understand what do bit0, bit1 and bit2 mean, how the syntax should look like if I wish to add those values to RMCF.BKLT? I can't find any examples with bit1 and bit2 neither in...
  11. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    You mean switching between Name(BKLT, 0) and Name(BKLT, 1)? Does it make sense if I'm using only AppleBacklightInjector.kext method as IntelBacklight.kext doesn't work for me starting from Sierra? I didn't even make SSDT patch for it, since I use AppleBacklightInjector.kext. Which settings...
  12. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    I tried and I'm not satisfied with the result, that's why I'm asking. The problem is that in both cases, either I set CSM in BIOS or I set 1024x768 in GUI section, my laptop's monitor switches to some kind of another mode while booting. That leads to a lower refresh rate and a lower color depth...
  13. DEXXX

    [README] Common Problems and Workarounds on 10.14 Mojave

    Is it possible to avoid setting BIOS to UEFI+CSM mode or setting Clover resolution to 1024x768 when booting to Mojave with garbled screen? Just like it was until Sierra inclusively.
  14. DEXXX

    [README] Common (some unsolved) Problems in 10.12 Sierra

    thank you! now it looks totally perfect :) as for HDMI/Nvidia I will do some checks and open a separate thread then. thanks again
  15. DEXXX

    [README] Common (some unsolved) Problems in 10.12 Sierra

    @RehabMan, I fixed this by disabling BOTH ports with the following patch: Comment: 0x0a260006 disable 0105 and 0204 ports Find: <01050900 00040000 87000000 02040900 00040000 87000000> Replace: <FF000000 01000000 40000000 FF000000 01000000 40000000> It appears that on my specific laptop the...
Top