- Joined
- May 14, 2013
- Messages
- 24
- Motherboard
- I didn't read
- CPU
- the RULES
- Graphics
- so ignore me
Posting a EFI/Clover folder that you're NOT using is not helpful.
Well I guess you're right There you go: View attachment CLOVER.zip
Posting a EFI/Clover folder that you're NOT using is not helpful.
EDIT: Look like it's not related to your problem. Can you take a screenshot of garbled screen?
So you have to set 1024x768 in config.plist or enable CSM to fix the garbled screen?
It's the untouched CLOVER from the HP post installer (Version 6.4.2 (September 14th 2015)), except that I changed to OsxAptioFixDrv-64.efi per your advice.
View attachment 152097
Let me know if you want me to re-upload that.
Jep I understand. Let me double check fast boot.
Same problem on Dell Broadwell. If you have to set 1024x768 or CSM enabled, use "Yosemite S" theme instead.Yes exactly, both workarounds do not cause the garbled screen. Here is a screenshot:
View attachment 152131
Another workaround is going to standby and wake-up
/edit: Actually a simple screen-off / on fixes it as well...
Yes exactly, both workarounds do not cause the garbled screen. Here is a screenshot:
View attachment 152131
Another workaround is going to standby and wake-up
/edit: Actually a simple screen-off / on fixes it as well...
Name (LMAX, 0xad9)
// KMAX: defines the unscaled range in the _BCL table below
Name (KMAX, 0xad9)
// _INI deals with differences between native setting and desired
Method (_INI, 0, NotSerialized)
{
// This 0xC value comes from looking what OS X initializes this
// register to after display sleep (using ACPIDebug/ACPIPoller)
Store(0xC0000000, LEVW)
Same problem on Dell Broadwell. If you have to set 1024x768 or CSM enabled, use "Yosemite S" theme instead.
Seems like a reasonable work around as long as these settings are available.
Unless someone wants to determine the true cause with ACPIDebug...
I can help..
you can give me the steps to do ACPIDebug
or can release remote access chrome remote desktop and then posted the experience here
Experiment with a couple of settings in the PNLF patch.
Code:Name (LMAX, 0xad9) // KMAX: defines the unscaled range in the _BCL table below Name (KMAX, 0xad9) // _INI deals with differences between native setting and desired Method (_INI, 0, NotSerialized) { // This 0xC value comes from looking what OS X initializes this // register to after display sleep (using ACPIDebug/ACPIPoller) Store(0xC0000000, LEVW)
Try with LMAX=0.
Try removing the Store(0xC*, LEVW) line.
It could be additional debugging of the IGPU registers is required (I originally figured out the 0xC0000000 for Haswell using ACPIDebug).
I tried both by editing the DSDT.aml (in CLOVER/ACPI/patched) with MaciASL, but no luck yet. I guess we'd need to debug that - it's not a major issue actually, but I might be willing to try.