Jump to content
WarDoc

WhatEverGreen Support Topic

631 posts in this topic

Recommended Posts

what about playing Netflix on safari? do you see black window s+ green artifacts? while it's playing fine on firefox for example. obviously using Shiki + lilu

disable iGPU or use shiki.kext with shikigva=1 boot argument to use online render instead of offline.

Share this post


Link to post
Share on other sites
Advertisement

Hi I have an AMD 580 8 GB running with WhateverGreen.kext 1.04 and Lilu.kext 1.17 on Sierra 10.12.6

It is running fine. No Clover injection or anything else on Z270X-Gaming 5 Gigabyte mobo.

 

Now I want to add another 580 8 GB and then OSX just won't boot.

BIOS, Clover and OSX starts fine but when it comes to sending signal to screen it stops and ends with almost black screen.

 

Does anyone has an idea how to fix this? Or point me to an direction?

I have searched myself but can't find anything yet.

 

Using Clover_v2.4k_r4200

 

Thanks!

Got this thing running on High Sierra with Whatevergreen and Lilu and SMBIOS MacPro 6.1

Runs fine and all 36 units running. Have to do some real life test but I consider this as solved.

Thanks!

Share this post


Link to post
Share on other sites

disable iGPU or use shiki.kext with shikigva=1 boot argument to use online render instead of offline.

thank you for the tip.

I cannot disable igpu because I need quick sync.

tried with shikigva=1 and this is result: Netflix gives me error and now even youtube video have problems with green artifacts.

 

​that's strange because I was used with Sierra + Nvidia pascal to have Netflix working with same config.plist and same kexts combo

Share this post


Link to post
Share on other sites

thank you for the tip.

I cannot disable igpu because I need quick sync.

tried with shikigva=1 and this is result: Netflix gives me error and now even youtube video have problems with green artifacts.

 

​that's strange because I was used with Sierra + Nvidia pascal to have Netflix working with same config.plist and same kexts combo

did you install the supplemental update for High Sierra?

since this update Netflix don't work anymore and with iGPU get the green artifacts but only on Netflix.youtube works good and iTunes works fine without shiki.kext used the Offline decoder.

I don't no if it's possible to fix the green artifacts by patching the AppleGVA.framework via shiki.kext or so.

Share this post


Link to post
Share on other sites

did you install the supplemental update for High Sierra?

since this update Netflix don't work anymore and with iGPU get the green artifacts but only on Netflix.youtube works good and iTunes works fine without shiki.kext used the Offline decoder.

I don't no if it's possible to fix the green artifacts by patching the AppleGVA.framework via shiki.kext or so.

 

yes, I did the supplemental update.

and now, even my photo app get my hack freezing, like steam game app.

I get green artifacts when using shikigva=1, otherwise youtube runs perfectly.

​I can play Netflix well with firefox. issue only with safari

Share this post


Link to post
Share on other sites

Amazing it slept! Of course I want to see more, here is the faq bit im interested in:

 

How do I get HDMI audio to work?

In general it should be enough to rely on WhateverGreen automatic HDAU correction. It renames the device to HDAU, and injects missing layout-id and hda-gfx (starting with onboard-2) properties. This will not work well with two or more cards of different vendors (e.g. NVIDIA and ATI/AMD), please manually inject the properties in such a case. For identifiers not present in AppleHDAController and AppleHDA you have to add necessary kext patches, see AppleALC example for 290X

 

It's not worked. There is no nvidia card btw. Is it because of the already present dsdt edit for hdmi audio? Need I remove that or the latter here identifiers not present? How does one go about getting that going through clover injection? I may find the parts for the kexts but not sure on clover.

Share this post


Link to post
Share on other sites

Is device id 0x67C7 supported by Apple? It’s the Radeon Pro WX 5100 and a Polaris 10 spec card with less stream processors. Similar to the Radeon Pro 570. I see the WX 7100 in the whatevergreen code, but not the WX 5100. (I have the card btw if I need to test anything). If it does not work, I'll order a WX 7100.

 

More Info Bios

More Info General

 

 

//Edit

 

I tried with lilu and whatevergreen but it's not recognized. The device id is in AMDRadeonX4250.kext listed though.

 

Got it working by adding device id '67C0' as mask 'device-id' in a ssdt.

 

 

post-18792-0-09806200-1507621628_thumb.png

Share this post


Link to post
Share on other sites

Hi everyone,

 

I've just installed High Sierra on my hackintosh yesterday and everything seems to be working fine except for the fact that I can't get DVI output on my ASUS Radeon HD 7770 2GD5. HDMI works fine (I can't test the DisplayPort output because I don't have a DP cable lying around) but both DVI ports give me a black screen. The monitor is detected properly by macOS, but nothing is displayed, even if I boot with a single monitor plugged into the DVI port.

 

I have Lilu 1.2.0 and WhateverGreen 1.1.0 installed. Any ideas?

Share this post


Link to post
Share on other sites

Hi everyone,

 

I've just installed High Sierra on my hackintosh yesterday and everything seems to be working fine except for the fact that I can't get DVI output on my ASUS Radeon HD 7770 2GD5. HDMI works fine (I can't test the DisplayPort output because I don't have a DP cable lying around) but both DVI ports give me a black screen. The monitor is detected properly by macOS, but nothing is displayed, even if I boot with a single monitor plugged into the DVI port.

 

I have Lilu 1.2.0 and WhateverGreen 1.1.0 installed. Any ideas?

 

Try -raddvi, connector-priority, etc... Read the FAQ, read this topic...

Share this post


Link to post
Share on other sites

well initially sleep worked but nothing really changed except after trying out that example ssdt for r9 290x, it doesnt anymore.

made sure to remove all traces of it and the settings are the same as when sleep worked but it doesnt. This is an r9 290 and

have tried turning off the framebuffer "radeon" and removing the fakeid for sleep but that didnt help.

 

was also wondering if since the setup is using 10.11.6 that the hdmi audio does not work?

 

edit: ok i saw in the confirmation post it was 10.12.6/13 that the r9 290x worked with hdmi audio.

 

Still not sure what happened to the sleep all of a sudden... it worked the 1st time then stopped till the kexts went into 

"other" and was consistently working but not after trying that ssdt. now im stumped.

 

debug results in mostly this:

 

 cat /var/log/system.log | egrep '(WhateverGreen|Lilu)'

Oct 10 23:17:41 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:17:41 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

Oct 10 23:24:03 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:24:03 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

 cat /var/log/system.log | egrep '(AppleALC|Lilu)'

Oct 10 23:17:41 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:17:41 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

Oct 10 23:24:03 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:24:03 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

 

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

 

Maybe its the igfx needs load first but this processors igfx causes clover not to load in this case maybe try with supported igfx?

Share this post


Link to post
Share on other sites

Try -raddvi, connector-priority, etc... Read the FAQ, read this topic...

 

I hadn't noticed connector-priority, and I'm not sure how to use/apply it. I tried adding -liludbg, -liludbgall, and -raddbg to see what the default value is in while booting but I'm not seeing anything and I can't find the boot log anywhere on my computer. I'm using CloverConfigurator because I'm quite new to this. How would I go about defining something in connector-priority?

Share this post


Link to post
Share on other sites

I hadn't noticed connector-priority, and I'm not sure how to use/apply it. I tried adding -liludbg, -liludbgall, and -raddbg to see what the default value is in while booting but I'm not seeing anything and I can't find the boot log anywhere on my computer. I'm using CloverConfigurator because I'm quite new to this. How would I go about defining something in connector-priority?

 

Try to read this topic carefully. It's only 14 pages. I already explained how to do this. 

Share this post


Link to post
Share on other sites

Hi @vandroiy2012

 

I'm just curious Is it possible to use lilu and whatevergreen on older hardware to boot into High Sierra? I tried and it will give me the black screen. I remember I've read about not using these kexts on older hardware in the read me on the whatever green on git hub.

They work fine on Sierra though.

 

My rig is: GA-EP45, Core 2 Duo E8400 and the GPU is Sapphire Radeon HD 7790 Dual-X 1GB.

 

Thanks for you support and your time man :)

Share this post


Link to post
Share on other sites

Hi @vandroiy2012

 

I'm just curious Is it possible to use lilu and whatevergreen on older hardware to boot into High Sierra? I tried and it will give me the black screen. I remember I've read about not using these kexts on older hardware in the read me on the whatever green on git hub.

They work fine on Sierra though.

 

My rig is: GA-EP45, Core 2 Duo E8400 and the GPU is Sapphire Radeon HD 7790 Dual-X 1GB.

 

Thanks for you support and your time man :)

Sorry. I don't have non-uefi hardware for tests, but on applelife.ru several users gave positive reports with non-uefi rigs and WhateverGreen.kext.

Share this post


Link to post
Share on other sites

Sorry. I don't have non-uefi hardware for tests, but on applelife.ru several users gave positive reports with non-uefi rigs and WhateverGreen.kext.

Thanks for your quick reply and the tip, I will check applelife.ru to see how they did it :)

 

Cheers

Share this post


Link to post
Share on other sites

Try to read this topic carefully. It's only 14 pages. I already explained how to do this. 

 

I think I might actually be retarded; I don't know how I didn't see your previous answer on connector-priority. However, I had no luck playing around with that. WhateverGreen is properly detecting all the ports (DP, HDMI, DVI, DVI) but I tried all 24 possible combinations and I wasn't able to get anything out of DVI, and I know the changes were applying since when I checked the log the priority numbers changed. The system is properly detecting the card (AMD Radeon HD 7770, device ID 683D) and both monitors. I'm terribly confused.

 

Thanks for being so patient with me, and I'm sorry for being so dumb.

Share this post


Link to post
Share on other sites

I think I might actually be retarded; I don't know how I didn't see your previous answer on connector-priority. However, I had no luck playing around with that. WhateverGreen is properly detecting all the ports (DP, HDMI, DVI, DVI) but I tried all 24 possible combinations and I wasn't able to get anything out of DVI, and I know the changes were applying since when I checked the log the priority numbers changed. The system is properly detecting the card (AMD Radeon HD 7770, device ID 683D) and both monitors. I'm terribly confused.

 

Thanks for being so patient with me, and I'm sorry for being so dumb.

 

Did you try -raddvi bootarg?

  • Fixes transmitter/encoder in autodetected connectors for multimonitor support (-raddvi)

Share this post


Link to post
Share on other sites

On a R9 290. For arbitrary fake id I use the pci address but not sure what else. I try custom properties

 

key: fake id

 

value: 0x67B01002

 

then there is type.. string, data or number for that value

 

what does putting radeon in the frame buffer section in clover do since its not one?

 

not sure if this will help the situation. Does the debug info from post #261 give a clue to what the cause of 

inoperability is?

Share this post


Link to post
Share on other sites

On a R9 290. For arbitrary fake id I use the pci address but not sure what else. I try custom properties

 

key: fake id

 

value: 0x67B01002

 

then there is type.. string, data or number for that value

 

what does putting radeon in the frame buffer section in clover do since its not one?

 

not sure if this will help the situation. Does the debug info from post #261 give a clue to what the cause of 

inoperability is?

 

It should be like that

post-1069282-0-43637900-1507763273_thumb.png

 

Just copy it

		<key>Arbitrary</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Inject AMD Graphics properties</string>
				<key>CustomProperties</key>
				<array>
					<dict>
						<key>Key</key>
						<string>device-id</string>
						<key>Value</key>
						<data>
						sGcAAA==
						</data>
					</dict>
				</array>
				<key>PciAddr</key>
				<string>01:00.00</string>
			</dict>
		</array>

About choosing correct PciAddr look here http://www.insanelymac.com/forum/topic/325987-whatevergreen-support-topic/?p=2489296

 

And obligatorily disable clover ATI injection!!!

Share this post


Link to post
Share on other sites

Yep. Tried connector-priority with and without raddvi, no change.

 

Does your mainboard UEFI-capable? Does your card have UEFI VideoBIOS? If both questions "yes" try to disable CSM and make PCIe graphics card primary. If first question "yes" and second "no" try to find way to flash UEFI VideoBIOS in your card. Search Google how to flash UEFI GOP in AMD videocards. If first question "no" you could try different VideoBIOSes even from another vendor. Just make sure that type and amount of connectors, video memory and GPU/Memory frequencies will be equal to your card.

 

That's all i can suggest you.  

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By headkaze
      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
      - 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 (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-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:

       
      Debugging
      If you need a dump of your framebuffers in binary use the boot flag -igfxdump. The output will be in /AppleIntelFramebuffer_GEN_KERNX_Y on your boot drive (Eg. AppleIntelFramebuffer_10_17.7). Intel FB-Patcher can File->Open this and generate a config.plist/Devices/Properties patch for Clover. 010 Editor can also parse this file using the IntelFramebuffer.bt template.
      To get debug output from Lilu use the -liludbgall flag and for WhateverGreen use the -wegdbg boot flag. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work.
       
      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
       


    • By Thereman
      Hello, I'm a noob at installing MacOS on my current PC (which is running Windows 10 x64 Pro).
      Can I do a dual boot with windows 10 and MacOS Mojave? I already have windows 10 installed and I would like to put and MacOS Mojave, can it? If not, should I reinstall from 0 MacOS Mojave and after Windows 10?
       
      P.S: I have already make a topic about "Can I run MacOS" and the export boys on the forum said to me I can run it.
    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id) Removed com.apple.finder.plist Removed com.apple.QuickLookDaemon.plist rebuild the kextcache and reset the nvram  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.
       
      Cheers!
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+J partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+J partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+J and GPT HFS+J partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
      3. MBR-Automatic-Method (new for 10.13+, remove files, no more update),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use MBR-EasyInstallerMaker to make installer, it works with both MBR and GPT.
       
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       

       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.

       
       
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
      3. MBR-Automatic-Method (new for 10.13+, remove files, no more update),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use MBR-EasyInstallerMaker to make installer, it works with both MBR and GPT.
       
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       

       
×