hi guys. i got suspend-to-RAM working on the weekend using
220.127.116.11+mactel and a modified version of Ortwin's "mbps2ram" script,
which i've attached to this email. after that, i tried to get the
iSight working. i had some success with Ekiga.
however, later on i noticed that i could no longer resume from a
suspend-to-RAM. when trying to resume, my MBP C2D would come come back
to life, but nothing appeared on the screen, and the sleep light on
the lid button was off. after leaving it like that for >5 minutes, i
had to power it off by holding the power button for 5 seconds. i tried
many more times, but each had the same result. i also tried in
i reset the SMC by removing the battery and AC cord and holding the
power button for 15 seconds. after putting the battery and AC cord
back in, i reset the PRAM and NVRAM by holding Command+Option+P+R just
after turning my Mac on, and not releasing those keys until the 2nd
i then booted into MacOS X and tried sleeping, which worked. i booted
into Linux 18.104.22.168+mactel, but resuming from a suspend-to-RAM had the
exact same results as before.
i thought the linux-uvc stuff might be causing problems, as i noticed
that the following modules were now being loaded, whereas before
playing with the iSight, they weren't:
so i deleted /lib/modules/22.214.171.124/ and reinstalled my kernel.
i made another attempt at suspending to and resuming from RAM. this
time when resuming, a few seconds after the DVD-ROM made its usual
noise, my Mac rebooted. i tried many more times with the same result.
the script that i use to suspend to RAM writes progress messages to a
log file. it seems that the suspend works. the message "Resuming from
RAM" isn't logged, which leads me to believe that the script isn't
brought back to life:
nick@...:~> cat /var/log/MBP_C2D_s2ram.log
2007-07-30 12:06:06 Beginning the suspend-to-RAM sequence.
2007-07-30 12:06:06 Switching to vt/1.
2007-07-30 12:06:07 Bringing down ath0.
2007-07-30 12:06:07 Unloading the wireless NIC's kernel module.
2007-07-30 12:06:07 Setting up s3_bios use.
2007-07-30 12:06:07 Storing the video card's state.
2007-07-30 12:06:07 Syncing data to the HDs.
2007-07-30 12:06:07 Suspending to RAM.
as a last resort, i tried suspending to and resuming from disk. that
so, has anyone else experienced this problem of resuming from a
suspend-to-RAM? any suggestions for what i can do to fix this?
thanks for your help!