Bug 502570

Hum, actually the workaround does not work anymore, so this bug is even more annoying...

Well, "s2ram -f" is not a supported mode of operation ;)

What does "s2ram -n" as root say? What kind of graphics card does the machine have?

Would it be possible to attach /var/log/pm-suspend.log after trying to suspend via the KDE or GNOME applet?

I see the same problem on my notebook.
s2ram -n
Machine matched entry 261:
    sys_vendor   = 'FUJITSU SIEMENS'
    sys_product  = 'LIFEBOOK E8410'
    sys_version  = ''
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "FUJITSU SIEMENS"
    sys_product  = "LIFEBOOK E8410"
    sys_version  = " "
    bios_version = "Version 1.12 "
See http://en.opensuse.org/S2ram for details.

hwinfo --gfxcard
27: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_10de_428
  Unique ID: VCu0.taFWsnr5yyA
  Parent ID: vSkL.GplIvOMTy34
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GeForce 8400M G"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0428 "GeForce 8400M G"
  SubVendor: pci 0x10cf "Fujitsu Limited."
  SubDevice: pci 0x1422
  Revision: 0xa1
  Memory Range: 0xde000000-0xdeffffff (rw,non-prefetchable)
  Memory Range: 0xe0000000-0xefffffff (rw,prefetchable)
  Memory Range: 0xdc000000-0xddffffff (rw,non-prefetchable)
  I/O Ports: 0x2000-0x2fff (rw)
  IRQ: 11 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v000010DEd00000428sv000010CFsd00001422bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: nv
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #9 (PCI bridge)

Primary display adapter: #27

Created attachment 302611 [details]
This is the needed pm-suspend.log

Guenther: your issue is different: your machine crashes during suspend or resume. That's significantly different from "the backlight does not come back on" ;)

sorry, without the requested information from comment #2 I cannot do much. Feel free to reopen once you can provide that.

Thanks!

Hi,

here is the info, sorry for the delay (this is a relative's computer and can't work on it anytime).

Output of s2ram -n :

Machine unknown
This machine can be identified by:
    sys_vendor   = "Sony Corporation"
    sys_product  = "VGN-SR39XN_S"
    sys_version  = "C6016US3"
    bios_version = "R2070Y1"

Created attachment 315164 [details]
pm-suspend.log

Reopening, thanks in advance for checking.

What kind of graphics card does this machine have?

From what I found on the internet, it should be intel graphics.

But the "i915" module is not loaded, so I'm not sure.

It is an Intel GM45 Express chipset.

The module is not loaded, because it is using vesa for now (there is another issue with the intel driver and xorg, causing a segfault).

Well, VESA is not really supported, suspend only can work reliably when the drivers know the hardware.

You can try if one of the options on http://en.opensuse.org/s2ram does get the machine back, I'd try "s2ram -f -a3" and "s2ram -f -p -m" first, and then enter those options as, e.g.

S2RAM_OPTS="-f -a3"

in /etc/pm/config.d/suspend.

But anyway, this is a workaround. Using i915 is the correct solution.

I actually had the same problem so I figured I'd add a comment rather than file a new bug.  I have an IBM X40 Thinkpad and when I resume from suspend, the backlight is not on.  I found a bug on Launchpad that matches my exact bug:

https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/292256

From that bug and the following posting on the forum:

http://forums.opensuse.org/hardware/392914-need-help-fixing-suspend-ram.html

I found that I had to put the following options in the /etc/pm/config.d/config file:

S2RAM_OPTS="--force --vbe_post"

These are the only options that would get it to work correctly.  Hope this helps.

Thanks.

Unfortunately, s2ram -f -p -m or s2ram --force --vbe_post work randomely, but it crashes very often.

In general, but even not always, it will work at the first suspend and resume, but the second one will hang all the system (blank screen and caplocks light sparkling).

Sadly, there is a no go for openSUSE on this machine...