Suspend fails on Sony Vaio SZ650, nVidia 8400M GS and nvidia-glx-new

Bug #196596 reported by Michael Doube
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Suspend fails on the Vaio SZ650N when running in SPEED mode, i.e. the nVidia 8400M GS is in use, and the configuration is left as per Hardy alpha 5 with the additional restricted driver (nvidia-glx-new).

This predicament can be rescued by following the instructions here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/188455

and here:
https://wiki.ubuntu.com/NvidiaLaptopBinaryDriverSuspend

Revision history for this message
Michael Doube (michael-doube) wrote :
Revision history for this message
Michael Doube (michael-doube) wrote :

Failed suspend...

Revision history for this message
Michael Doube (michael-doube) wrote :

Unfortunately making these changes breaks suspend when rebooting in STAMINA mode (intel 965), so perhaps the configs will need to be switched a la the xorg.conf switching script.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

Ideally, xserver should be able to automatically select the right driver (and options) when switching, if no xorg.conf is present. In testing, though, it appears that the hardware's edid information is not getting read (ddcprobe returns 'edidfail').

So, could you also attach your /var/log/Xorg.0.log, and the (binary) output of get-edid (from the read-edid package)?

Changed in linux-restricted-modules-2.6.24:
status: Triaged → Incomplete
Revision history for this message
Michael Doube (michael-doube) wrote :

Booting with the i386 version of the LiveCD (required because of 1386 limitation to read-edid) was fine - correct screen res detected, nv driver installed, progress bar during boot. All the problems I've seen have been in the 64-bit LiveCD. Here's the output of get-edid:

get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination does not support DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged

Revision history for this message
Michael Doube (michael-doube) wrote :

Running up-to-date Hardy, just installed nVidia proprietary drivers to test bug #95444 and realised that I hadn't tested this bug for ages.

I had a successful resume from suspend while using the nVidia's proprietary drivers on my Vaio SZ650, so I guess this bug is fixed.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.