Bug 387956 - s2ram does not work out of the box on my MacBook
Summary: s2ram does not work out of the box on my MacBook
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: Forgotten User ZhJd0F0L3x
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 19:50 UTC by Felix Möller
Modified: 2008-05-23 10:06 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Möller 2008-05-07 19:50:15 UTC 
On my MacBook s2ram does not work out of the box:

# s2ram -n
Machine matched entry 2:
    sys_vendor   = 'Apple Computer, Inc.'
    sys_product  = 'MacBook1,1'
    sys_version  = ''
    bios_version = ''
Fixes: 0x4  VBE_SAVE
This machine can be identified by:
    sys_vendor   = "Apple Computer, Inc."
    sys_product  = "MacBook1,1"
    sys_version  = "1.0"
    bios_version = "    MB11.88Z.0061.B03.0610121324"

So there is a workaround for my machine in the whitelist, but it just works without it.

"s2ram -f" suspends and resumes the machine just fine whereas "s2ram" hangs the machine on resume.
Comment 1 Forgotten User ZhJd0F0L3x 2008-05-08 08:23:51 UTC 
Did it work before, on 10.3?
Comment 2 Felix Möller 2008-05-08 09:29:23 UTC 
yes it did work with 10.3, but there i could not resume reliably because of bug #159962.

Now it works reliably with "s2ram -f".
Comment 3 Forgotten User ZhJd0F0L3x 2008-05-09 10:06:39 UTC 
Ok. I'll think about how to fix this upstream, for 11.0 i'll probably just patch the whitelist entry (the fixes are needed before kernel 2.6.25, but harmful with 2.6.25 and newer :-( )
Comment 4 Felix Möller 2008-05-21 21:27:49 UTC 
s2ram was updated, but this was not fixed as far as I can see:
* Do Mai 15 2008 seife@suse.de
- update to current CVS:
  - the save-compressed-images-faster patch is upstream
  - whitelist update for s2ram, fixing various novell bugzillas
Comment 5 Forgotten User ZhJd0F0L3x 2008-05-23 10:06:17 UTC 
I submitted a package with suspend-0.80-whitelist-openSUSE11.diff, which does remove the workaround for your machine (0 instead of VBE_SAVE).

So this is fixed for 11.0, still need to decide what to do upstream.