Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Same thing happens on the Dell Mini 9 (BIOS A05 - OS X 10.6.2- NBI 8.3 RC4)
Original comment by robinson...@gmail.com
on 15 Nov 2009 at 6:35
also confirmed for samsung nc10
Original comment by summel...@googlemail.com
on 16 Nov 2009 at 6:06
The same on Dell Optiplex 910, BIOS A04 Mac OS X 10.6.2 NetBookInstaller 0.8.2
final.
It says "Hibernate Image file too old by xxx seconds." and something about
"ForceWakeUp=y", but because of
quiet boot I can't seem to enter it.
Original comment by brov...@gmail.com
on 31 Dec 2009 at 12:15
Oh well. Just wanted to add this: this defect is to be found on every
non-Macintosh running Mac OS X.
I don't exactly know how it works, but my guess is that Macintoshes update
their system clock AFTER "Preboot", caused by the second stage bootcode. PCs
update their system clock immediately when turned on, caused by the low-level
bootcode.
So when resuming a hibernation-image, its timestamp on a Macintosh is exactly
the same as the system clock, and on a non-Macintosh its timestamp would differ
too much to the system clock.
I think I'll try the "ForceWakeUp"-flag within an hour, if results are positive
I'll write a quick guide on how to auto-resume it (so you don't have to enter
the flag by hand).
Original comment by brov...@gmail.com
on 13 Jul 2010 at 6:19
This issue is resolved by adding an entry to /Extra/com.apple.Boot.plist in the
<dict> section as follows:
<key>WakeImage</key>
<string>/var/vm/sleepimage</string>
This file cannot be modified unless the permissions are updated to allow, which
I would recommend doing temporarily and then changing back after.
http://www.mydellmini.com/forum/dell-mini-10v-mac-os-x-discussion/13711-hibernat
e-image-file-too-old-xxx-seconds-11.html
Original comment by jjwatmys...@gmail.com
on 29 Dec 2010 at 12:30
<key>WakeImage</key>
<string>/var/vm/sleepimage</string>
Changing this in /Extra/com.apple.Boot.plist in the <dict> section worked for
me on my 1005hab with 10.6.5 on it
Thanks!
Original comment by bryce.ha...@gmail.com
on 4 May 2011 at 3:59
Original issue reported on code.google.com by
dmscent...@gmail.com
on 3 Nov 2009 at 10:07