Sony Corporation VGN-FW139E suspend/resume failure non-free: fglrx

[smoosh]

Suspends, but shows backlit black screen upon resume every time. Using 9.10 beta 2.6.31-14-generic-pae i686.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: loren 2526 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2472 @ 40), (3, 27)
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd5200000 irq 22'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d2e00,00100302 HDA:14f12c06,104d1700,00100000'
   Controls : 31
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd0030000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,104d2e00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
Date: Wed Oct 14 08:13:48 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=ef13b765-f9d0-4d27-926d-404510bc3264
InterpreterPath: /usr/bin/python2.6
MachineType: Sony Corporation VGN-FW139E
NonfreeKernelModules: fglrx
Package: linux-image-2.6.31-14-generic-pae 2.6.31-14.46
ProcCmdLine: root=UUID=b9a8bb38-d470-4046-a1ed-44f2ec641394 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic-pae
RelatedPackageVersions: linux-firmware 1.22
SourcePackage: linux
Tags: resume suspend
Title: [Sony Corporation VGN-FW139E] suspend/resume failure [non-free: fglrx]
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 06/05/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0250Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0250Y0:bd06/05/2008:svnSonyCorporation:pnVGN-FW139E:pvrC600C08H:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW139E
dmi.product.version: C600C08H
dmi.sys.vendor: Sony Corporation

[Jeremy Foshee (jeremyfoshee)]

Hi smoosh,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 451456

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[smoosh (lolomcdoo)]

I believe this is still an issue. I gave up on Karmic because of it, and have been using Jaunty, which suspends fantastically. Is testing with a live CD acceptable? I don't really want to upgrade, just to have to reinstall Jaunty again, ya know!

[Jeremy Foshee (jeremyfoshee)]

smoosh,
    That should be fine. At least it will give us some idea if it will work.

Thanks!

~JFo

[smoosh (lolomcdoo)]

Same issue with the Lucid RC, the computer seems to suspend fine as the green power light turns to a flashing orange light. Everything normal there. But, when trying to resume, after the light turns solid green again, and the LED that indicates hard drive access flashes once, everything freezes. No backlight, caps lock does not work. No key combinations do anything... A hard shut-down is needed.

Smoosh

[smoosh (lolomcdoo)]

Update! Was reading this page: http://vaioubuntu.wordpress.com/2010/04/15/whats-about-latest-ubuntu-10-04-beta/#comments
and came across a comment that has the solution:

Add the following line to /etc/pm/config.d/unload_modules (you may have to create it)
SUSPEND_MODULES="video"

Which worked!

Note: I am NOT using Fglrx anymore, as the default driver in Lucid works great so far with Compiz. I could never get Compiz to work with the default driver in Jaunty, hence the Fglrx usage.

I have now installed Lucid, ditched Jaunty, and am happy as a clam!

I will install fglrx and report back if it works with that too...

Smoosh
Thanks!

[smoosh (lolomcdoo)]

Works with Fglrx as well...

Another note: Using the open-source driver, the cursor is invisible upon resume (if you disable the log-in screen), so you have to press Ctrl-Alt-F2, then Ctrl-Alt-F1. Just in case anybody asks....

I can't believe I finally upgraded! Yaaaaah!

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]