Contribute
Register

[Guide] Lenovo Yoga 2 Pro El Capitan using Clover UEFI

Status
Not open for further replies.
Non-deterministic means you cannot predict the order that Clover will choose.
Hence the need for SortedOrder.



No idea.
Do a fresh install.

I've done 3 fresh installs and the same thing has happened each time, to reiterate an earlier question, could it be an issue with IO framework?
 
I've done 3 fresh installs and the same thing has happened each time, to reiterate an earlier question, could it be an issue with IO framework?

Isolate what is causing it by doing things one at a time.
Then you'll know.
Note that you can patch for pixel clock with CoreDisplayFixup.kext + Lilu.kext.
 
Isolate what is causing it by doing things one at a time.
Then you'll know.
Note that you can patch for pixel clock with CoreDisplayFixup.kext + Lilu.kext.

That did it! fresh install with no IOKit or CoreDisplay patch using CoreDisplayFixup.kext + Lilu.kext instead and paste is retained.

Thanks again
 
That did it! fresh install with no IOKit or CoreDisplay patch using CoreDisplayFixup.kext + Lilu.kext instead and paste is retained.

Thanks again

Sounds like you must have been patching for the pixel clock incorrectly.
CoreDisplayFixup.kext does the same thing you can do manually with the-darkvoid's script.

Note that usually a botched IOKit/CoreDisplay patch results in a system that is not bootable.
 
Sounds like you must have been patching for the pixel clock incorrectly.
CoreDisplayFixup.kext does the same thing you can do manually with the-darkvoid's script.

Note that usually a botched IOKit/CoreDisplay patch results in a system that is not bootable.

I would assume that I needed CoreDisplay (which was done correctly before) and the old IOKit patch has a different function in HS. The only thing that ended up being different was not applying the IOKit patch.
 
Alright so I finally got audio and brightness working well, so It's down to cosmetics mostly now (and power management, haven't made SSDT.aml yet). I'm putting this together almost exclusively for Logic Pro and MainStage 3 and right now in logic pro some display features are pixelated and discolored as shown in the attached picture (Make note of the control pane at the bottom and the playback head). I saw some of this pixelation at the top part of the login screen on an earlier install, but not this one.

The only other issue I've seen with the graphics is when photobooth is open the display starts to go crazy and glitch until photobooth is closed.

I can deal with the photobooth problem (ill never use it), but I would like to have Logic Pro displaying correctly if possible.

Anyone have ideas about what could cause this?

Thanks
 

Attachments

  • problem_reporting.zip
    4.9 MB · Views: 146
  • Screen Shot.png
    4 KB · Views: 166
I would assume that I needed CoreDisplay (which was done correctly before) and the old IOKit patch has a different function in HS. The only thing that ended up being different was not applying the IOKit patch.

The script by the-darkvoid automatically patches IOKit or CoreDisplay (not both) based on the system that is running.
Read the FAQ:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

But CoreDisplayFixup.kext does the same thing, so if you don't mind the additional kexts, then don't bother looking into it.

Alright so I finally got audio and brightness working well, so It's down to cosmetics mostly now (and power management, haven't made SSDT.aml yet). I'm putting this together almost exclusively for Logic Pro and MainStage 3 and right now in logic pro some display features are pixelated and discolored as shown in the attached picture (Make note of the control pane at the bottom and the playback head). I saw some of this pixelation at the top part of the login screen on an earlier install, but not this one.

The only other issue I've seen with the graphics is when photobooth is open the display starts to go crazy and glitch until photobooth is closed.

I can deal with the photobooth problem (ill never use it), but I would like to have Logic Pro displaying correctly if possible.

Anyone have ideas about what could cause this?

Thanks

Problems/questions/comments:
- ioreg shows CPU PM not implemented
- what is DVMT-prealloc set to?
- config.plist lacks SortedOrder to specify SSDT load order
 
The script by the-darkvoid automatically patches IOKit or CoreDisplay (not both) based on the system that is running.
Read the FAQ:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

But CoreDisplayFixup.kext does the same thing, so if you don't mind the additional kexts, then don't bother looking into it.



Problems/questions/comments:
- ioreg shows CPU PM not implemented
- what is DVMT-prealloc set to?
- config.plist lacks SortedOrder to specify SSDT load order

The script I ran for IOKit was the one from this guide that explicitly calls out IOKit.framework

I ran a similar scrip previously that called out CoreDisplay.framework

None of it really maters now, would just be nice to isolate what had cause the paste error for future knowledge.

CPU PM is not implemented because the guide says to create SSDT.aml in MACiasl with the given values (15w, 3000max, 1800min), but entering the clock speed of 1800 returns an error stating that the value is too small and I have yet to try a different method. Would the ssdtPRGen method suggested earlier by another user be advisable?

DVMT-Prealloc is set to 96mb. I think the config.plist in the .zip I attached has it set to 128mb (for some reason it got changed), but I have it at 96mb.

I must not have understood the implementation of sorted order. Is the "#SortedOrder" commented out to disable it? Otherwise it is setup for the order of my DSDT/SSDTs
 
The script by the-darkvoid automatically patches IOKit or CoreDisplay (not both) based on the system that is running.
Read the FAQ:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

But CoreDisplayFixup.kext does the same thing, so if you don't mind the additional kexts, then don't bother looking into it.



Problems/questions/comments:
- ioreg shows CPU PM not implemented
- what is DVMT-prealloc set to?
- config.plist lacks SortedOrder to specify SSDT load order


CPU PM implemented via ssdtPRGen

Sorted order should be implemented: all relevant SSDTs are created and in ACPI patched and #SortedOrder list in clover is edited to reflect them

Logic pro graphics issue as stated in previous post and minor similar glitches in various GUI elements around the system still apply

I've noticed that every once in a while when closing a program (textedit, MACiasl, finder) the screen will go black for an instant and return to normal

Updated problem reporting files attached
 

Attachments

  • problem_reporting.zip
    4.9 MB · Views: 104
The script I ran for IOKit was the one from this guide that explicitly calls out IOKit.framework

This guide is for El Capitan.
Why are you taking advice for El Capitan so literally when you're running High Sierra?
Read FAQ:
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html

CPU PM is not implemented because the guide says to create SSDT.aml in MACiasl with the given values (15w, 3000max, 1800min),

Again.. bad advice in the guide.
Read here:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.232993/

DVMT-Prealloc is set to 96mb. I think the config.plist in the .zip I attached has it set to 128mb (for some reason it got changed), but I have it at 96mb.

DVMT-prealloc setting *must* match the patch you have for the framebuffer.

Is the "#SortedOrder" commented out to disable it?

Yes.
 
Last edited:
Status
Not open for further replies.
Back
Top