I noticed this issue too but not on all rBPs. My dad's machine kept waking in a second while mine was taking maybe 30 seconds. I'll keep an eye on my machine over the weekend and see if it fixed this issue.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases MacBook Air and MacBook Pro Update 2.0
- Thread starter MacRumors
- Start date
- Sort by reaction score
I noticed this issue too but not on all rBPs. My dad's machine kept waking in a second while mine was taking maybe 30 seconds. I'll keep an eye on my machine over the weekend and see if it fixed this issue.
I think you better do a clean installation of the OS, then recover all the data from Time Machine and see if this could help.
Hey I have this same problem since the update
,I am getting that 8GB file no matter what I do ,any solutions anyone ? Yes the mode is 0 and everything,but it just keeps coming back after reboot Warning - this update seems to change the way "safesleep" is handled. If you currently have safesleep disabled in order to free up the drive space required by the sleep image, this will cause it to come back and even setting hibernatemode = 0 won't change it.
Not sure why. The 13" rMBP has this "feature" out of the box but the 2.0 update has been reported to have the same effect on the earlier Ivy Bridge macbooks.
----------
Ah, you beat me to it.
I'd really like to solve this. I don't like an 8GB sleepimage on my dinky 128GB drive.
Not sure why. The 13" rMBP has this "feature" out of the box but the 2.0 update has been reported to have the same effect on the earlier Ivy Bridge macbooks.
----------
Ah, you beat me to it.
I'd really like to solve this. I don't like an 8GB sleepimage on my dinky 128GB drive.
I hope you figure this out. Not cool as I have 16 gigs of ram and am not needing safe sleep for my needsWarning - this update seems to change the way "safesleep" is handled. If you currently have safesleep disabled in order to free up the drive space required by the sleep image, this will cause it to come back and even setting hibernatemode = 0 won't change it.
Not sure why. The 13" rMBP has this "feature" out of the box but the 2.0 update has been reported to have the same effect on the earlier Ivy Bridge macbooks.
----------
Ah, you beat me to it.
I'd really like to solve this. I don't like an 8GB sleepimage on my dinky 128GB drive.
For people concerned with the sleepimage file, it seems to be easily fixable.
MAKE SURE YOU UNDERSTAND WHAT YOU'RE DOING!
OK, basically you need to create a symbolic link to nowhere in the Terminal:
cd /var/vm
sudo rm sleepimage
sudo ln -s /dev/null sleepimage
That's all.
MAKE SURE YOU UNDERSTAND WHAT YOU'RE DOING!
OK, basically you need to create a symbolic link to nowhere in the Terminal:
cd /var/vm
sudo rm sleepimage
sudo ln -s /dev/null sleepimage
That's all.
..
----------
Do not install this update if you use Skype, now as soon as I sign in it crashes....
[EDIT]
Not using Skype but since upgrade my external monitor no longer works. Erratic behaviour. With lid closed external monitor worked, when open both screens black with just a cursor. Reboot fixed it for about an hour then back to unusable.
MBPr seems to work ok with external monitor disconnected. Up until thIs update all seemed good. Now unusable with external monitor.
Have Skype loaded but not used. Have not checked mail etc.
----------
Do not install this update if you use Skype, now as soon as I sign in it crashes....
[EDIT]
Not using Skype but since upgrade my external monitor no longer works. Erratic behaviour. With lid closed external monitor worked, when open both screens black with just a cursor. Reboot fixed it for about an hour then back to unusable.
MBPr seems to work ok with external monitor disconnected. Up until thIs update all seemed good. Now unusable with external monitor.
Have Skype loaded but not used. Have not checked mail etc.
Last edited:
Well, no I do not think so. I am very happy about the air and I have other machines too, this is the machine I bring with me everyday so it is important for me. I go by train for hours almost every day. They don´t come with 8GB in store and I did not have time for a BTO at the time.
It is not the biggest difference that they adjusted the amount of allocated VRAM, but it IS a difference and I don't see why. It is a ultra portable computer and it doesnt need 512 MB for the GPU right?
Also, what I noted after a few reboots is that the only amount of free ram is about 1,6GB immediately after a start. It is far less than before. But that might be temporary.
I do alot of different things on my machine but playing games is not one of them. I do quite alot of graphic processing on it but it has always worked great, even with my 27" apple led display connected..
Oh, sneaky. I didn't think about symlinking it to /dev/null.
----------
Sheesh, my 13" rMBP says 768MB video memory-- and I have fewer pixels to push than a 15" retina which has 512MB.
However, since that's shared system memory, I don't believe it actually *uses* that unless it's needed. That number just represents the max amount that can be allocated. So unless you're running 2 external 27" monitors it shouldn't be sucking up too much system memory.
My guess is that this is caused by the machine going into standby mode: http://support.apple.com/kb/HT4392
The machine will write the contents of RAM to the SSD after about an hour of sleep on battery. I have yet to apply the update, but perhaps it changed this behavior.
The long wake times were driving me crazy, so my solution was to change the timeout from the default 70 minutes to 12 hours using pmset. I have not tried this with the update, so try this at your own risk. I assume no responsibility whatsoever if this screws up your computer, dont do this if you dont know how to use Terminal, please be careful, etc. etc.
The relevant commands are:
Code:
sudo pmset -b standbydelay 43200
sudo pmset -c standbydelay 43200Replace 43200 with your preferred standby delay, in seconds. The default value is 4200.
And to check the current settings, this ought to work:
Code:
pmset -g custom | grep standbydelayIm guessing that resetting the PRAM resets these values.
Wow, this update totally fixed my battery life...
It used to tell me about an hour and half at best when I would be watching a movie on VLC...which makes the Geforce gfx run..
Now, its telling me 4hrs 45 mins!
It used to tell me about an hour and half at best when I would be watching a movie on VLC...which makes the Geforce gfx run..
Now, its telling me 4hrs 45 mins!
Nice that they bumped up the possible Gfx memory on the Air. It does mean that certain programs that might have issues with the gfx memory can now run without a hitch. Not necessarily gaming in general, but for a particular gfx memory hungry game called Might & Magic Heroes 6. (Which would work before this update, but would work much better with this update)
I've got the same issue. There's also problems with coming out of sleep, keychain access issues, and none of my external drives can be unmounted.
I've reset the PRAM and SMC. I've called AppleCare, and they seem to think it's related to FileVault2 encryption being on the disk. I'm not convinced, but going through their troubleshooting steps is all I have right now.
Dan
here's an explanation of sleepimage location and hibernate mode.
hibernate mode 0 does eliminate the sleepimage in SL, not sure about ML.
http://www.maclife.com/article/howtos/how_remove_diskhogging_sleepimage_file_your_mac
but not that you know the location, you can try the above and then check afterwards to see if it has been recreated.
hibernate mode 0 does eliminate the sleepimage in SL, not sure about ML.
http://www.maclife.com/article/howtos/how_remove_diskhogging_sleepimage_file_your_mac
but not that you know the location, you can try the above and then check afterwards to see if it has been recreated.
This update fixed the "turn on external monitor when waking up from sleep" issue on my 2012 MBA 8/256. Now my external displayport monitor wakes up from sleep successfully every time and I do not have to keep unplugging the mini dp connector and plugging it back in.