[M76] [ASUSTeK Computer Inc. F3Sa] suspend/resume failure [non-free: fglrx]

[Eray Gürsoy]

Binary package hint: xorg-driver-fglrx

I am having suspend/resume problems rarely.
It usually works, but when I put my NB suspend mode after long hours of work (with java [jboss + eclipse]) It does not go suspend. Just stays with black screen. In the morning I find out it did not go suspend. But when I try to resume or any other thing (ctrl-alt F1, ctrl-alt backspace ,etc) it does not response.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer Inc. F3Sa
NonfreeKernelModules: fglrx
Package: linux-image-2.6.28-11-generic 2.6.28-11.39
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=053dc535-e9ba-4d77-a920-1a55211ed70f ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.39-generic
SourcePackage: linux
Tags: resume suspend
Title: [ASUSTeK Computer Inc. F3Sa] suspend/resume failure [non-free: fglrx]
UserGroups:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: ASUSTeK Computer Inc. Device [1043:14e7]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M76 [Radeon Mobility HD 2600 Series] [1002:9581]
     Subsystem: ASUSTeK Computer Inc. Device [1043:1562]

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.