Jump to content

vit9696

Developers
  • Content count

    377
  • Joined

  • Last visited

  • Days Won

    19

vit9696 last won the day on July 11

vit9696 had the most liked content!

4 Followers

About vit9696

  • Rank
    InsanelyMac Sage

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. vit9696

    Lilu — kext and process patcher

    You cannot. Yet you can apply the necessary changes in the driver itself, but I suppose Disabler kext or something alike already supports something suitable.
  2. vit9696

    Lilu — kext and process patcher

    That's not possible (as the kexts won't even match without a faked device-id), and I am not positive anybody needs to dump the framebuffers anymore. WhateverGreen supports semantical patches anyway, and Clover framebuffers are just legacy:
  3. vit9696

    Lilu — kext and process patcher

    1. I am aware of both Canon Lake and Ice Lake. Not the priority at the moment. 2. You should normally dump on compatible hardware. Faking the device-id might work though, but you will have to change WhateverGreen sources to patch a different framebuffer kext for your cpu. https://github.com/acidanthera/WhateverGreen/blob/dd5bc7d/WhateverGreen/kern_igfx.cpp#L72
  4. vit9696

    Lilu — kext and process patcher

    Take a look: https://www.sweetscape.com/010editor/manual/Running.htm https://www.sweetscape.com/010editor/manual/TemplateResults.htm Also note, that the latest version of the bt template is in WhateverGreen repo in Manual folder. IGFX and NGFX repos are abandoned.
  5. vit9696

    Lilu — kext and process patcher

    Hi, you need 010 Editor (https://www.sweetscape.com/010editor/) to run this script on each framebuffer kext. And for 10.14+ framebuffers you need to dump them first via -igfxdump boot argument via WhateverGreen.
  6. vit9696

    WhatEverGreen Support Topic

    Tweaking BIOS and replacing AMI with Apple causes eficheck.kext to spam at Apple, and certain other nasty things. Forget it and stop doing. CoreDisplayFixup was also merged.
  7. vit9696

    WhatEverGreen Support Topic

    IntelGraphicsFixup, NvidiaGraphicsFixup, and Shiki are now officially dead and are part of WhateverGreen. Using them together is not supported and will lead to undefined behaviour. New WhateverGreen features should improve the maintainability, compatibility and performance of the overall solution, as well as simplify the installation. For the time being the latest versions of Lilu, AppleALC, and WhateverGreen are only available in source and are recommended for trying. Intel GuC firmware loading caused random freezes and kernel panics as well as no visible performance boost (aside different numbers in sensors) and was removed as harmful. The rest of the functionality is mostly intact.
  8. vit9696

    Lilu — kext and process patcher

    Hi, Regarding the links, it is kind of hard to keep everything in sync, so any pull requests will be welcome. Regarding the signal loss, it is most likely a hardware issue or a new problem that is not addressed by the kexts <which I do not plan to research at the moment>. One thing to suggest is to make sure you do NOT use GuC (igfxfw=1 boot arg). At the moment it causes a lot of issues. Other than that I have few ideas. Vit
  9. vit9696

    Lilu — kext and process patcher

    Yes, the projects are slowly moving to github.com/acidanthera. The point is to try to simplify and unify the ecosystem. All the existing links including the releases will automatically redirect to the new location, so there should be no changes for the end user.
  10. vit9696

    WhatEverGreen Support Topic

    Let me warn you about the state of WhateverGreen and Mojave Beta compatibility. In brief, certain functionality (including connector prioritsation) is partially incompatible and needs some work. For those in need of WhateverGreen I advise to wait for an update and stay on a current stable version of the operating system, which works great. One of the known issues affecting both High Sierra and Mojave is multimonitor compatibility, and the next update will try to address it in a better way. The current solution (which disables AGDC) seems to sometimes cause graphical glitches when waking from sleep. A more proper and reliable way seems to be using a more standard AGDP disabling code with mine or Piker-Alpha's patch commonly found in NvidiaGraphicsFixup. In the coming updates, for simplicity, maintainability, and unmeasurable boot speed improvements certain Lilu plugins dedicated for GPU patching will be merged in one, and appear as a single module.
  11. vit9696

    Clover Problems and Solutions

    @Zenith432, I do see the following post in regards to Xcode toolchains: And the only thing I can grasp from here is that you try to use Microsoft ABI linkage for all the functions instead of just EFIAPI ones meant to be used for external communication, and which only matter. Microsoft ABI calling convention reserves an extra shadow area and uses less registers for argument passing, so is slower by design than SYSV ABI. Given that prototypes of the functions meant to be used for external communication are marked EFIAPI, any calling convention misuse with XCODE5 properly results in a corresponding message, and I do not see why XCODE8 is necessary any longer. As for -flto, it does not work for XCODE8 for Slice. And last time I tried XCODE8, it failed to compile 32-bit Clover and failed to properly handle -arch flags. I may not see a full picture, but to my eyes XCODE8 feels like a legacy hack that gives us no benefit. While XCODE5 is maintained by Apple and edk2 teams, XCODE8 is only ours, and it brings no functional benefit but maintanance burden.
  12. vit9696

    Clover Problems and Solutions

    @Zenith432, is there still any benefit in using XCODE8 over XCODE5? From what I know XCODE8 does not support -flto and produces bigger binaries. XCODE5 is meant to work with any Xcode from 5 and onwards, and I am not particularly sure why we need to maintain an extra toolchain which has various compatibility issues. Could we drop it without losing any vital features of the buildsystem?
  13. vit9696

    AptioMemoryFix

    AMF version is included in APTIO_MEMORY_FIX_PROTOCOL, which AMF installs. Is it not enough? See: https://github.com/vit9696/AptioFixPkg/blob/master/Include/Protocol/AptioMemoryFixProtocol.h
  14. vit9696

    AptioMemoryFix

    Hi, thanks for the report, I can confirm that the check has changed. I committed a temporary workaround in the latest update, hopefully it will work for the time being, though I am starting to like the idea less and less.
  15. vit9696

    AppleALC — dynamic AppleHDA patching

    Please pay an attention to this: the latest AppleALC in master addresses all the issues of 10.14. It works just fine by simulating an existing layout id and does not require any manipulations with your previous preferences. The only issue preventing it from working on your system are obviously your borked hands, and clearly in such a case you should refrain from installing betas. What you do here is only confusing other people, and misguide them by providing some pseudotechnical information. To summarise I suggest everyone to take a break. Thank you for understanding. Please note, that HDMI audio may need separate updates, and it will be addressed later in other kexts.
×