Contribute
Register

Yosemite - No wake up strange message about crypted memory

Status
Not open for further replies.
Joined
Nov 28, 2011
Messages
330
Motherboard
GA-Z77X-UD5H-Clover
CPU
i7-2600K @ 4.6GHz OC
Graphics
GTX 1060
Mac
  1. MacBook Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Hello,

Dell E6320 Bios A15 - Core i5 2520M - 8 Go DDR3 - HD3000 - SSD Sandisk - Yosemite 10.10 - Chameleon.

Sleep was working (most of the time) with Mavericks.
With Yosemite it is going to sleep and then don't wake up.
I need to reboot:
I am getting this message from Chameleon:
"Resuming from encrypted image is unsupported.
Uncheck "use security virtual memory" in "Security"pane on system preferences.
Press any key to proceed with normal boot."

No such option in Security...
I try with some terminal commands found on internet... without success.

Someone has a clue?
 
Hello,

Dell E6320 Bios A15 - Core i5 2520M - 8 Go DDR3 - HD3000 - SSD Sandisk - Yosemite 10.10 - Chameleon.

Sleep was working (most of the time) with Mavericks.
With Yosemite it is going to sleep and then don't wake up.
I need to reboot:
I am getting this message from Chameleon:
"Resuming from encrypted image is unsupported.
Uncheck "use security virtual memory" in "Security"pane on system preferences.
Press any key to proceed with normal boot."

No such option in Security...
I try with some terminal commands found on internet... without success.

Someone has a clue?

Disable hibernation. 'sudo pmset hibernatemode 0' in Terminal.
 
Thanks.
It is now hibernating as a desktop, not on file (similar to the choice of "Hibernate Mode - Desktop" in MultiBeast).
A way to fix the hibernate on file?

AFAIK, hibernation is not supported, especially with Chameleon/Chimera. There is some work that has been done in Clover, but I do not know the status. To me, suspend to disk with a laptop is silly (there is a battery), and detrimental to SSD life span.
 
Disable hibernation. 'sudo pmset hibernatemode 0' in Terminal.

This did not solve my problem.

Clearing standby mode, i.e. setting it and standbydelay to 0 did not solve the problem.

I have no solution yet.
 
This did not solve my problem.

Clearing standby mode, i.e. setting it and standbydelay to 0 did not solve the problem.

I have no solution yet.

Download patchmatic: https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-patchmatic-2015-0107.zip
Extract the 'patchmatic' binary from the ZIP. Copy it to /usr/bin, such that you have the binary at /usr/bin/patchmatic.

In terminal,
Code:
rm -Rf ~/Downloads/RehabMan
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

Post contents of Downloads/RehabMan directory (as ZIP).

Also, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

And output from:
Code:
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
 
This did not solve my problem.

Clearing standby mode, i.e. setting it and standbydelay to 0 did not solve the problem.

I have no solution yet.


Sorry for missing your post RehabMan. Just got a whole bunch of snow, 7 feet, over the past 3+ weeks. Guess where I live.


I've seen this issue come and go on the same OS version. It is now gone.

The changes I made were:

1. reduce the overclocking to zero, i.e. use graded speed.
2. use: pmset -a hibernateFile /dev/null

The second is to make sure if the OS tries to save a hibernate image, yes hibernateMode is 0, it will fail.

Anyway the issue disappeared. Tomorrow or the weekend I will attempt to return my overclock rate to 4.0GHz.

Oh, I can't be certain that changes 1 or 2 fixed this problem or it just crept away. It crept back two weeks ago after been absent for 3+ months.

Do you believe it worth while doing the IOReg dump now?

T
 
Sorry for missing your post RehabMan. Just got a whole bunch of snow, 7 feet, over the past 3+ weeks. Guess where I live.


I've seen this issue come and go on the same OS version. It is now gone.

The changes I made were:

1. reduce the overclocking to zero, i.e. use graded speed.
2. use: pmset -a hibernateFile /dev/null

The second is to make sure if the OS tries to save a hibernate image, yes hibernateMode is 0, it will fail.

Anyway the issue disappeared. Tomorrow or the weekend I will attempt to return my overclock rate to 4.0GHz.

Oh, I can't be certain that changes 1 or 2 fixed this problem or it just crept away. It crept back two weeks ago after been absent for 3+ months.

Do you believe it worth while doing the IOReg dump now?

T

What laptop are you able to overclock?
 
Status
Not open for further replies.
Back
Top