Search the Community: Showing results for tags 'whatevergreen'.
Found 3 results
This Post is for helping users with issue that come with Whatevergreen Feel free to join in and help users if you know your stuff also get the dev's of whatever green to join as well Whatevergreen has a few issues Multi-monitor Support is lacking as 2 monitors seems to be the limit for some even if the devs say it's not users say it's true Some Id's are wrong or missing (hence the nano and 390X not working) some GPU names are wrong ( which has been reported many times) FOR RYZEN OWNERS with Polaris : Modified kext:/S/L/E/AMD9510Controller.kext//Contents/Info.plistfrom:<key>IOPCIMatch</key><string>0x67EF1002</string>to:<key>IOPCIMatch</key><string>0x67FF1002</string> Updating clover to Clover_v2.4k_r4152 and using the config.plist here https://pastebin.com/TYiTEVcMwithbusratio=36 and npci=0x3000 ALSO THIS THREAD IS NOT FOR WHINING in anyway please do not post off topic if you don't like given support in this forum that's all you but majority of use need it. Source code: repository. FAQ and documentation: link. a real SSDT example https://www.dropbox.com/sh/el66izg1lmk1jiu/AADCZUEjyQyiWWELlmzW2ix-a?dl=0 Credits to Pavo for the hard work of decoding the mess Boot argumentsAdd -raddbg to enable debug printing (available in DEBUG binaries).Add -radvesa to disable ATI/AMD video acceleration completely.Add -radoff to disable WhateverGreen.Add -radbeta to enable WhateverGreen on unsupported os versions (10.13 and below are enabled by default).Add -rad24 to enforce 24-bit display mode.Add -radlogo to patch boot logo distortion.Add -raddvi to enable DVI transmitter correction (required for 290X, 370, etc.)Add radpg=15 to disable several power-gating modes (see FAQ, required for 7xxx GPUs). If you Don't Want To use WEG or LILU clover 4297 has a new patch that fixes the same issues without kexts You have to set in config.plist <key>Graphics</key> <dict> <key>RadeonDeInit</key> <true/>
Framebuffer patching in Mojave Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen. Not just for Mojave This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS. Coffee Lake Users Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's) Lilu + WhateverGreen WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video. Beta Warning Please note that it is currently in a "beta" state so use it at your own risk. I am just documenting this here for those of you who want to get framebuffer patching now. Preliminary 1. Remove: - FakePCIID_Intel_HD_Graphics - IntelGraphicsFixup - NvidiaGraphicsFixup - CoreDisplayFixup - Shiki 2. Turn off all graphics injections in Clover: - config.plist/Graphics/Inject/ATI=NO - config.plist/Graphics/Inject/Intel=NO - config.plist/Graphics/Inject/NVidia=NO - config.plist/Graphics/ig-platform-id= - config.plist/Devices/FakeID/IntelGFX= 3. Disable DSDT Clover fixes: - AddHDMI - FixDisplay - FixIntelGfx - AddIMEI 4. Disable UseIntelHDMI 5. Remove boot argument: -disablegfxfirmware 6. Remove any IGPU and HDMI entries from: - config.plist/Devices/Arbitrary - config.plist/Devices/Properties - config.plist/Devices/AddProperties 7. Remove any IGPU and HDMI related SSDT and DSDT from: - CLOVER/ACPI/patched 8. Renaming GFX0 -> IGPU - WhateverGreen will do this automatically (see caveat below) - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it Compile Lilu + WhateverGreen Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output. Having trouble compiling? If you're having trouble compiling you can wait for the official binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder). Get the device path of your IGPU: Download and use the gfxutil tool like so: $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist. What ig-platform-id should I use for my system? You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here. You can determine the generation of your CPU by the first digit after the hyphen. Examples: - Intel(R) Core(TM) i5-2760QM (Gen 2) - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5) - Intel(R) Core(TM) m3-6Y30 (Gen 6) - Intel(R) Core(TM) i5-8350U (Gen 8) Here are some recommended frames: Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000) - Support started with OS X 10.7.x and ended with macOS 10.13.6 - Metal support is not available - Desktop: 0x00030010 (default) - Laptop: 0x00010000 (default) Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000) - Support started with OS X 10.8.x - Desktop: 0x0166000A (default), 0x01620005 - Laptop: 0x01660003 (default), 0x01660009, 0x01660004 Gen 4: Haswell (Intel HD Graphics 4200-5200) - Support started with OS X 10.9.x - Desktop: 0x0D220003 (default) - Laptop: 0x0A160000 (default), 0x0A260005 (recommended) Gen 5: Broadwell (Intel HD Graphics 5300-6300) - Support started with OS X 10.10.2 - Desktop: 0x16220007 (default) - Laptop: 0x16260006 (default) Gen 6: Skylake (Intel HD Graphics 510-580) - Support started with OS X 10.11.4 - Desktop: 0x19120000 (default) - Laptop: 0x19160000 (default) Gen 7: Kaby Lake (Intel HD Graphics 610-650) - Support started with macOS 10.12.6 - Desktop: 0x59160000 (default) - Laptop: 0x591B0000 (default) Gen 8: Coffee Lake (Intel UHD Graphics 630) - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e) - Desktop: 0x3EA50000 (default), 0x3E9B0007 (recommended) - Laptop: 0x3EA50009 (default) Framebuffer Patching WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this: Here are some reasons why you might need extra Framebuffer Patching: - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem) - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem) - Disabling eGPU (disable-external-gpu) - Enable pixel clock patch for 4K support (enable-hdmi20) - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1) - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090) - Changing connector types to match your systems ports (framebuffer-conX-type) Framebuffer Patching Types We have three different types of patches: 1. Arbitrary (Recommended) framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist. Here are some example patches: - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram) - Pipe / Port Count 3 to 2 - Connector 1 DP to HDMI - Connector 2 Disable Here is an example of the All Data method: Here is an example of the Find / Replace method: Framebuffer Dumps There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions): 1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive) There are several ways of reading this dump: - Using 010 Editor along with the IntelFramebuffer.bt template - Using Intel FB-Patcher File->Open menu 2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen There are several ways of reading this dump: - Using dump_platformlist.sh shell script - Using Intel FB-Patcher File->Import->IOReg Dump menu Debug Output To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*. To view debug paste the following into Terminal (weglog.txt will output to your home directory): log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Credits - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits) - Andrey1970 for his guide on applelife.ru - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
macinsane posted a topic in ATiThis is bothering me for a long time now: Why does Apple deliberately disables the the RX4xx, RX5xx capabilities to hardware encode HEVC and is using Intel Quicksync instead? Is it to make the iMacPro look better than it is? I stumbled over a thread at tony-mac where people are going a totally different road for Radeon graphics. Instead of hassling around with getting Quicksync to work, they proposed to activate the AMD hardware renderer for Polaris GPU's. I tried it out and it works...somewhat I used a dummy kext from that tomato thread and edited it, so that it enables the AMDU7V4 IOGVACodec like on Vega cards, switched to iMacPro1,1 SMBIOS from iMac18,3, disabled the IGPU and the results were astonishing: My 3:34min 4k50p film was rendered by FCP with HEVC in 2:34 minutes. Nearly half the time than with Quicksync! With the iMac18 SMBIOS and the "help" of Intel Quicksync it took FCP 4:41 minutes to get it done! The problem is: As soon as the "wrong" IOGVACodec is enabled H.264 encoding leads to Mojave crashing at once (be it FCP, QuickTime or Videoproc). Watching H264 material is fine, though. If anyone has any idea how to handle this, I would be very grateful. I would even accept Mojave using software encoding for H264 if I could keep this amazing speeds on HEVC! BTW: Without IGPU on iMacPro1,1 SMBIOS no problem with DRM or iTunes, no need for Whatevergreen or Shiki. That is a bonus Ellesmere.kext.zip