Contribute
Register

Yosemite 10.10.2 - No wakeup from sleep

Status
Not open for further replies.

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,497
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Tried quite a number of frame buffers.
0x0a16000c also works (as-in gives display), but the same problem occurs.

I will try reverting the AppleIntelFramebufferAzul.kext to 10.10.1, just to see if that resolves the problem.
That way the problem can be isolated to the frame buffer.

Updated:

Reverted AppleIntelFramebufferAzul.kext resolves the issue, so its indeed isolated to the framebuffer.
Scratching my head on how this can be resolved though.

Maybe try patching 0xa260006 to meet your QHD+ requirements.
 
Joined
Jul 3, 2014
Messages
934
Motherboard
Dell XPS 9360 (KabyLake R)
CPU
Intel i7 8550U
Graphics
Intel UHD 620
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. Android
Maybe try patching 0xa260006 to meet your QHD+ requirements.

0xa260006 does not seem to generate any display on my machine.
I'd assume with patching at least the main display would blank during bootup.

Both 0xa2e0008 and 0x0a16000c work properly waking up from sleep with reverted AppleIntelFramebufferAzul. But obviously I would like not to revert kext versions.

I will re-try 0x0a260006 just to be sure.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,497
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
0xa260006 does not seem to generate any display on my machine.
I'd assume with patching at least the main display would blank during bootup.

Both 0xa2e0008 and 0x0a16000c work properly waking up from sleep with reverted AppleIntelFramebufferAzul. But obviously I would like not to revert kext versions.

I will re-try 0x0a260006 just to be sure.

I mean 0xa260006 with some of the patching you're already doing for 0xa2e0008.
 
Joined
Jul 3, 2014
Messages
934
Motherboard
Dell XPS 9360 (KabyLake R)
CPU
Intel i7 8550U
Graphics
Intel UHD 620
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. Android
I mean 0xa260006 with some of the patching you're already doing for 0xa2e0008.

Yes, but I patched only the frame buffer size on 0xa2e0008.
The display on it at least always tries to display on my internal panel.

With 0xa260006 nothing happens at all, it stays on the verbose boot log.
I am not sure how to fix that issue.

Let me see if I can patch the LVDS / eDP connector info from the working framebuffer into 0xa260006.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,497
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
...
Let me see if I can patch the LVDS / eDP connector info from the working framebuffer into 0xa260006.

There definitely is a slight difference there... (or maybe I was seeing things... because now I see no diff with the connector).
 
Joined
Jul 3, 2014
Messages
934
Motherboard
Dell XPS 9360 (KabyLake R)
CPU
Intel i7 8550U
Graphics
Intel UHD 620
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. Android
Hurray :clap:.

I sledge-hammered 0xa260006 as suggested and its working with the 10.10.2 kext.

Code:
Find: 0600260A 01030303 00000002 00003001 00006000 
Replace: 0600260A 01030303 00000006 00002002 00005001

This makes the 0xa260006 frame buffer work with QHD+.
Also using 0xa260006 resolves the wake-up issue as suggested by you and vbo.

I will see if I can slowly revert some of the changes to see what the most minimal change for 0xa260006 is which works.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,497
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hurray :clap:.

I sledge-hammered 0xa260006 as suggested and its working with the 10.10.2 kext.

Code:
Find: 0600260A 01030303 00000002 00003001 00006000 
Replace: 0600260A 01030303 00000006 00002002 00005001

This makes the 0xa260006 frame buffer work with QHD+.
Also using 0xa260006 resolves the wake-up issue as suggested by you and vbo.

I will see if I can slowly revert some of the changes to see what the most minimal change for 0xa260006 is which works.

Nice.
 
Joined
Jul 3, 2014
Messages
934
Motherboard
Dell XPS 9360 (KabyLake R)
CPU
Intel i7 8550U
Graphics
Intel UHD 620
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. Android
Display being "powered" or not on boot-up is determined by the framebuffer size, 24MB or 32MB works.
19MB and 16MB does not.

6MB cursor bytes works, but gives a small corruption transitioning from Apple boot logo to login window.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,497
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Display being "powered" or not on boot-up is determined by the framebuffer size, 24MB or 32MB works.
19MB and 16MB does not.

6MB cursor bytes works, but gives a small corruption transitioning from Apple boot logo to login window.

BIOS size is not significant?

BTW, I wonder if cursor-bytes=0 means "calculate automatically" (or "choose [unknown] default"). Just remembering that OatmealDome set it to zero for the Lenovo Y50 (1080p).
 
Joined
Jul 3, 2014
Messages
934
Motherboard
Dell XPS 9360 (KabyLake R)
CPU
Intel i7 8550U
Graphics
Intel UHD 620
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. Android
BIOS size is not significant?

Setting cursor bytes to 0 causes kernel panic. So I am not sure how OatmealDone has done that.
Maybe he's patching a different framebuffer then the one he is using?

Ok, no corruption during boot up happens at all with cursor bytes at 34MB.

BIOS is still set to 96MB, I will see about reducing it.
This could prevent the BIOS unlock patch for the Dell XPS 9530 being required.
 
Status
Not open for further replies.
Top