Jump to content
WarDoc

WhatEverGreen Support Topic

519 posts in this topic

Recommended Posts

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.
https://github.com/vit9696/WhateverGreen Faq's https://github.com/vit9696/WhateverGreen/blob/master/Manual/FAQ.en.md


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/>

Share this post


Link to post
Share on other sites
Advertisement

1. Multi-monitor Support is lacking and some what buggy

 

2. Some Id's are wrong or missing

 

3. some Gpu names are wrong 

 

4. and some gpu's like the nano or 390x does not work when they should.

 

1. Everything works like it should. How to avoid problems with R9 290X described in FAQ. Try "connectors", "connector-count" and "connector-priority"

  • When and how should I use custom connectors?

    In general automatic controller detection written in Apple kexts creates perfect connectors from your VBIOS. The logic of that can be found in reference.cpp. However, some GPU makers physically create different connectors but leave the VBIOS unchanged. This results in invalid connectors that are incompatible with your GPU. The proper way to fix the issues is to correct the data in VBIOS, however, just providing custom connectors can be easier.

    For some GPUs (e.g. 290, 290X and probably some others) WhateverGreen incorporates automatic connector correction that can be enabled via -raddvi boot argument. For other GPUs you may specify them as a GPU device property called connects, for example, via SSDT. You could pass your connectors in either 24-byte or 16-byte format, they will be automatically adapted to the running system. If you need to provide more or less connectors than it is detected automatically, you are to specify connector-count property as well. Please note that automatically detected connectors appear in the debug log to give you a good start.

  • How can I change display priority?

    With 7xxx GPUs or newer you could simply add connector-priority GPU controller property with sense ids (could be seen in debug log) in the order of their importance. This property may help with black screen issues especially with the multi-monitor configurations.

    Without this property specified all the connectors will stay with 0 priority. If there are unspecified connectors they will be ordered by type: LVDS, DVI, HDMI, DP, VGA. Read SSDT sample for more details.

2. What ID's are wrong or missing? WhateverGreen doesn't have fake-id option! So if device-id of your card is missing in vanilla AMD kexts you have to inject fake id with SSDT or Arbitrary array in config.plist

 

3. Once again read the FAQ. 

All the questions about automatic GPU model detection correctness should be addressed to The PCI ID Repository. In special cases you may submit a patch for kern_model.cpp. GPU model name is absolutely unimportant for GPU functioning.

 

4. Read the first paragraph

Share this post


Link to post
Share on other sites

1. Everything works like it should. How to avoid problems with R9 290X described in FAQ. Try "connectors", "connector-count" and "connector-priority"

 

saying it without having a example doesnt help your faq page doesnt help it can't it lacks so much info im sorry best to make it more full of information instead of try this and that without showing how and if you can't give support for your plugin why bother making it at all ? you don't just post a plugin and a useless faq pages and hope for the best

Share this post


Link to post
Share on other sites

saying it without having a example doesnt help your faq page doesnt help it can't it lacks so much info im sorry best to make it more full of information instead of try this and that without showing how and if you can't give support for your plugin why bother making it at all ? you don't just post a plugin and a useless faq pages and hope for the best

 

How?

Open SSDT sample and read notes... 

Share this post


Link to post
Share on other sites

How?

Open SSDT sample and read notes... 

it's messy and not going to help a new user not eveyone is a magic SSDt patcher most on this forum can't do it even hack pro's you need to find a better way of showing how things work and what to try to fix any issue less messy way a good way

Share this post


Link to post
Share on other sites

How?

Open SSDT sample and read notes...

 

This is a great advancement for AMD cards, it works great on my Intel i3 7350k, i5 6500, and pentium G3258 Haswel with RX 460 and RX 480.

 

It even works on my Ryzen 7 1700 with RX 480 but only in Sierra 12.5. In Sierra 12.5 I edit the info.plist of 9510 and 4100 kexts. I am able to boot with only RX 480 and no helper card.

 

In Sierra 12.6 there is no need to edit the kexts but it boots to black screen. The card accelerates at boot and I know it's booted but only black screen ( like days of old). With a Nvidia GT210 as a helper card it boots and shows the AMD Radeon Pro 480/575 so I know WhateverGreen is working.

 

Any ideas on why it won't work for Ryzen in Sierra 12.6?

Share this post


Link to post
Share on other sites

Is it possible to get the correct Frambuffer when using atribute "connectors" ?

right now it will allways be RadeonFramebuffer, but under old conditions we where able to choose different Frambuffers.

This weekend i tried the attribute "Connectors" by supplying it through my SSDT as in the sample SSDT it was adviced.

But it still shows AMD,RadeonFramebuffer as chosen framebuffer instead of "Orinoco", which i prefere to use.

 

Never the less: the kext is working great and as expected. No iGPU in BIOS activated and i have full 8-channel sound via HDMI of my Sapphire RX480 Nitro.

My question ist only a "cosmetic" question. I will explain in more details when i am back home and able to provide my SSDT with this post.

Share this post


Link to post
Share on other sites

This is a great advancement for AMD cards, it works great on my Intel i3 7350k, i5 6500, and pentium G3258 Haswel with RX 460 and RX 480.

 

It even works on my Ryzen 7 1700 with RX 480 but only in Sierra 12.5. In Sierra 12.5 I edit the info.plist of 9510 and 4100 kexts. I am able to boot with only RX 480 and no helper card.

 

In Sierra 12.6 there is no need to edit the kexts but it boots to black screen. The card accelerates at boot and I know it's booted but only black screen ( like days of old). With a Nvidia GT210 as a helper card it boots and shows the AMD Radeon Pro 480/575 so I know WhateverGreen is working.

 

Any ideas on why it won't work for Ryzen in Sierra 12.6?

 

Well interresting :

 

I have a simmilary build with Haswell Celeron and rx 460 :

 

I have spend lot of time this week end and unable to boot with PEG in bios.

 

Please may you upload your config.plist it will perhaps  helpfull for me.

Share this post


Link to post
Share on other sites

Is it possible to get the correct Frambuffer when using atribute "connectors" ?

right now it will allways be RadeonFramebuffer, but under old conditions we where able to choose different Frambuffers.

This weekend i tried the attribute "Connectors" by supplying it through my SSDT as in the sample SSDT it was adviced.

But it still shows AMD,RadeonFramebuffer as chosen framebuffer instead of "Orinoco", which i prefere to use.

 

Never the less: the kext is working great and as expected. No iGPU in BIOS activated and i have full 8-channel sound via HDMI of my Sapphire RX480 Nitro.

My question ist only a "cosmetic" question. I will explain in more details when i am back home and able to provide my SSDT with this post.

 

See the FAQ about named framebuffer. Custom connectors for Polaris are useless. Autodetect works fine with this cards.

  • When should I use a named framebuffer?

    Named framebuffers (Baladi, Futomaki, Lotus, etc.), enabled by "Clover GPU injection" or any other methods should never ever be used. This way of GPU injection is a common mistake, preventing automatic configuration of various important GPU parameters. This will inavoidably lead to borked GPU functioning in quite a number of cases.

It even works on my Ryzen 7 1700 with RX 480 but only in Sierra 12.5. In Sierra 12.5 I edit the info.plist of 9510 and 4100 kexts. I am able to boot with only RX 480 and no helper card.

 

In Sierra 12.6 there is no need to edit the kexts but it boots to black screen. The card accelerates at boot and I know it's booted but only black screen ( like days of old). With a Nvidia GT210 as a helper card it boots and shows the AMD Radeon Pro 480/575 so I know WhateverGreen is working.

 

Any ideas on why it won't work for Ryzen in Sierra 12.6?

 

I think it it is Ryzen kernel issue. 

Share this post


Link to post
Share on other sites

How?

Open SSDT sample and read notes... 

 

Referring to people to FAQ's all the time is not always helpful.

Not all people have the same level of expertise as Devs.

 

@vit9696 and others have a done a fantastic job in finding the solution of getting AMD cards to work but since it's closed-source solution, Devs should be more open to helping people solve their specific problems. Saying everything works does not help the person who is having problems.

 

If people say, "it does not work" then Devs should say "...ok, please post you debug, config.plist, or whatever I need to help you solve your problem" instead of saying "see the FAQ".

Yes it may be a "user problem" but if the user is not as an expert as the Dev, then don't assume that they can read the FAQ and solve the problem on their own.

E.g. the FAQ mentions Connectors and in the SSDT example, there's a Connectors section that is just a bunch of numbers...:

"connectors",
                        Buffer ()
                        {
                            0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x04, 0x01, 
                            0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00, 0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x01, 0x03, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x03, 0x00, 0x10, 0x00, 0x05, 0x06, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x11, 0x02, 0x06, 0x05
                        },

...and there's no help in that example as to what these numbers are and how to change them.

By the way, that SSDT example is very well documented compared to many others I've seen in 8 years of hacking (but clearly it's not enough).

 

People are not asking for "free fish" but "teach me how to fish, so that I can feed my self".

 

Keep up the good work.

Share this post


Link to post
Share on other sites

Referring to people to FAQ's all the time is not always helpful.

Not all people have the same level of expertise as Devs.

 

@vit9696 and others have a done a fantastic job in finding the solution of getting AMD cards to work but since it's closed-source solution, Devs should be more open to helping people solve their specific problems. Saying everything works does not help the person who is having problems.

 

If people say, "it does not work" then Devs should say "...ok, please post you debug, config.plist, or whatever I need to help you solve your problem" instead of saying "see the FAQ".

Yes it may be a "user problem" but if the user is not as an expert as the Dev, then don't assume that they can read the FAQ and solve the problem on their own.

E.g. the FAQ mentions Connectors and in the SSDT example, there's a Connectors section that is just a bunch of numbers...:

"connectors",
                        Buffer ()
                        {
                            0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x04, 0x01, 
                            0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00, 0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x01, 0x03, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x03, 0x00, 0x10, 0x00, 0x05, 0x06, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x11, 0x02, 0x06, 0x05
                        },

...and there's no help in that example as to what these numbers are and how to change them.

By the way, that SSDT example is very well documented compared to many others I've seen in 8 years of hacking (but clearly it's not enough).

 

People are not asking for "free fish" but "teach me how to fish, so that I can feed my self".

 

Keep up the good work.

it's like talking to a brick wall when you tell him that 

Share this post


Link to post
Share on other sites

Has anyone gotten the gigabyte radeon rx 560 to work with a ryzen build? I am booting 12.5 and having no such luck getting acceleration. I am willing to do hex edits or whatever is needed but as of now I am just running in circles!

Share this post


Link to post
Share on other sites

This is exactly like the normal connector patching done previously, just in a SSDT format. 

"connectors",
                        Buffer ()
                        {
                            0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x04, 0x01, 
                            0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00, 0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x01, 0x03, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x03, 0x00, 0x10, 0x00, 0x05, 0x06, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x11, 0x02, 0x06, 0x05
                        },

Share this post


Link to post
Share on other sites

 

This is exactly like the normal connector patching done previously, just in a SSDT format.

"connectors",
                        Buffer ()
                        {
                            0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x04, 0x01, 
                            0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00, 0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x01, 0x03, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x03, 0x00, 0x10, 0x00, 0x05, 0x06, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x11, 0x02, 0x06, 0x05
                        },
how is your progress so far ?

Share this post


Link to post
Share on other sites

 

This is exactly like the normal connector patching done previously, just in a SSDT format. 

"connectors",
                        Buffer ()
                        {
                            0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x04, 0x01, 
                            0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00, 0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x01, 0x03, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x03, 0x00, 0x10, 0x00, 0x05, 0x06, 
                            0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x11, 0x02, 0x06, 0x05
                        },

 

Yes it may be but if people have never had to deal with connector patching before (e.g. they are moving from nVidia to AMD) then it's of no help.

They will need to go off somewhere else google AMD connector patching and hope they figure out the old-way with SSDT-way.

If it was documented within the FAQ (or better within the SSDT), then all info is in one place.

Share this post


Link to post
Share on other sites

Just noticed they got the port count wrong on the 290x since the dp port counts as 3 and dvi dvi and HDMI count as another 3 wth they doing to get 4 ? Gimping 2 other ports would cause issues

Share this post


Link to post
Share on other sites

Has anyone gotten the gigabyte radeon rx 560 to work with a ryzen build? I am booting 12.5 and having no such luck getting acceleration. I am willing to do hex edits or whatever is needed but as of now I am just running in circles!

In your config.plist

System Parameters -> Inject Kexts -> Yes

Rt Variables -> CsrActiveConfig -> 0x67

Make sure your not injecting anything since the RX560 seems to use the same ID as the RX460.

Please also make sure your using the latest version of Clover since last night I spent like 7 hours helping a friend but then at the end noticed... he was using a outdated version of Clover after updating it started working.

Share this post


Link to post
Share on other sites

In your config.plist

System Parameters -> Inject Kexts -> Yes

Rt Variables -> CsrActiveConfig -> 0x67

Make sure your not injecting anything since the RX560 seems to use the same ID as the RX460.

Please also make sure your using the latest version of Clover since last night I spent like 7 hours helping a friend but then at the end noticed... he was using a outdated version of Clover after updating it started working.

I am going to use the latest version of Clover_v2.4k_r4128

I have the 0x67 command issued.

 

I am using a ryzen cpu with 10.12.6

 

If I cannot get the RX 560 to work on the Ryzen I will try it on the Z77

 

UPDATE! I GOT THIS RX 560 to WORK in my Z77X setup running 10.12.6! All I did was set inject kexts to yes, Rt variables to 0x67, and place the Kexts in the EFI kext folder! Wa-la! atleast she is not a paper weight. I will now try to do an install on the AMD.

Share this post


Link to post
Share on other sites

Rt Variables -> CsrActiveConfig -> 0x67

 

in sierra fully disabled sip is 0x1FF, highsierra 0x3FF

anyway, check for correct settings on boot clover->options....Sys.Par.

4128+

Share this post


Link to post
Share on other sites

Well interresting :

 

I have a simmilary build with Haswell Celeron and rx 460 :

 

I have spend lot of time this week end and unable to boot with PEG in bios.

 

Please may you upload your config.plist it will perhaps  helpfull for me.

 

Heres my EFI folder.   You will need to add serial number, UUID, and MLB, and I removed the Themes folder.   I also added the lilugreen kexts to System/Library/Extensions folder.

 

EFI.zip

Share this post


Link to post
Share on other sites

Well, if someone can explain - or a link -  to get connectors, and how to create with this connectors an ssdt - or a link - for this kext, I really appreciate the help.

 

I have an Amd 390x

 

thank you.

Share this post


Link to post
Share on other sites

Heres my EFI folder.   You will need to add serial number, UUID, and MLB, and I removed the Themes folder.   I also added the lilugreen kexts to System/Library/Extensions folder.

 

attachicon.gifEFI.zip

 

Thanks :)

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

  • Similar Content

    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers in Clover is no longer a viable method in Mojave. The good news is vit9696 and I have created a new framebuffer patching system for 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 or download a pre-created installer from here or here.
       
      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
      Remove:
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - Shiki
      - CoreDisplayFixup
       
      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.
       
      Can't Compile?
      If you can't compile your own please wait for the official binaries to be released soon.
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) We have two different types of patches:
      Hard-coded (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 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)
      - NOTE: The values are in bytes so you should convert MB to bytes (you can use this online converter)
      <key>Devices</key> <dict>     <key>Properties</key>     <dict>         <key>PciRoot(0x0)/Pci(0x2,0x0)</key>         <dict>             <key>AAPL,ig-platform-id</key>             <data>CQClPg==</data>             <key>framebuffer-patch-enable</key>             <integer>1</integer>             <key>framebuffer-stolenmem</key>             <integer>19922944</integer>             <key>framebuffer-fbmem</key>             <integer>9437184</integer>             <key>framebuffer-unifiedmem</key>             <integer>2147483648</integer>         </dict>     </dict> </dict> - Pipe / Port Count 3 to 2
      - Connector 1 (BusId 0x4) DP to HDMI
      - Connector 2 (BusId 0x6) Disable
      - NOTE: WhateverGreen will automatically set all connectors from DP->HDMI (you can use -igfxnohdmi boot flag to disable this)
      <key>Devices</key> <dict>     <key>Properties</key>     <dict>         <key>PciRoot(0x0)/Pci(0x2,0x0)</key>         <dict>             <key>AAPL,ig-platform-id</key>             <data>CQClPg==</data>             <key>framebuffer-patch-enable</key>             <integer>1</integer>             <key>framebuffer-pipecount</key>             <integer>2</integer>             <key>framebuffer-portcount</key>             <integer>2</integer>             <key>framebuffer-con1-enable</key>             <integer>1</integer>             <key>framebuffer-con1-type</key>             <integer>0x00000800</integer>             <key>framebuffer-con2-enable</key>             <integer>1</integer>             <key>framebuffer-con2-type</key>             <integer>-1</integer>         </dict>     </dict> </dict> Here is an example of the Find / Replace method:
      <key>Devices</key> <dict>     <key>Properties</key>     <dict>         <key>PciRoot(0x0)/Pci(0x2,0x0)</key>         <dict>             <key>AAPL,ig-platform-id</key>             <data>CQClPg==</data>             <key>framebuffer-patch0-enable</key>             <integer>1</integer>             <key>framebuffer-patch0-find</key>             <data>AAAIAAIAAACYAAAA</data>             <key>framebuffer-patch0-replace</key>             <data>AAAIAAIAAACHAQAA</data>         </dict>     </dict> </dict> 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 open this file 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 WhateverGreen please and use the -wegdbg boot flag. You will need to compile WhateverGreen as debug for both of these flags to work.
      To view debug output use:
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot Thanks
      Big thanks to vit9696 for all his help implementing this and also writing the amazing Lilu and WhateverGreen plugin. Also thanks to all the other contributors.
       
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione
      nel caso guardate...
       Mojave in HFS 
       
       
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip
×