Resuming from s2ram on a Dell Inspiron E1505 causes distorted screen

[rez]

The bug is seen on a Dell Inspiron E1505 with Nvidia GeForce Go 7300. Ubuntu 7.04 is installed on the system and nv driver is used. Occasionaly, after the system resumes from a s2ram the screen is all distorted with splattered color and broken fonts. The only way to recover to a clear display is to kill and restart X (Ctl+Alt+BackSpace).

dell@amit-config:~$ lspci -v | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce Go 7300 (rev a1) (prog-if 00 [VGA])

dell@amit-config:~$ dpkg -l | grep video-nv
ii xserver-xorg-video-nv 2.0.0-0ubuntu3 X.Org X server -- NV display driver

[rez (rezwanul-kabir)]

Attaching xorg.conf

[Bryce Harrington (bryce)]

Does this bug match what you're seeing? https://bugs.freedesktop.org/show_bug.cgi?id=5817

[vlowther (victor-lowther)]

re: Bryce Harrington:

Huh? The bug you linked to is about issues using hotkeys to switch output display devices, not s2ram issues...

[Bryce Harrington (bryce)]

Sorry, I was thinking of one of rez's other bugs, you're right, that bug is not relevant.

[Bryce Harrington (bryce)]

The bug is seen on a Dell Inspiron E1505 with Nvidia GeForce Go 7300. Ubuntu 7.04 is installed on the system and nv driver is used. Occasionally, after the system resumes from a s2ram the screen is all distorted with splattered color and broken fonts. The only way to recover to a clear display is to kill and restart X (Ctl+Alt+BackSpace).

$ lspci -v | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce Go 7300 (rev a1) (prog-if 00 [VGA])

$ dpkg -l | grep video-nv
ii xserver-xorg-video-nv 2.0.0-0ubuntu3 X.Org X server -- NV display driver

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/109833

[Michael Morgan (mikmorg)]

You might want to visit this site: http://en.opensuse.org/NVidia_Suspend_HOWTO
It seems that NVidia is a common threat to s2ram.

Also, in case this also affects intel:
Machines with Intel graphics chipsets often work with "s2ram -f -a3", even when using vesafb framebuffer. If "s2ram -f -a3" does not work (for example on Dell machines), often "s2ram -f -p -m" works well.
Newer intel Xorg drivers seem to have problems with "-s" (VBE_SAVE), so "-m" (VBE_MODE) should be used if at all possible with them. See https://bugzilla.novell.com/show_bug.cgi?id=229603 . Generally speaking, VBE_MODE is preferable to VBE_SAVE.

[Bryce Harrington (bryce)]

rez, can you please re-test this bug using this newer Feisty -nv deb:
http://people.ubuntu.com/~bryce/Testing/nv_2.1.1-Feisty/xserver-xorg-video-nv_2.1.1-1_i386.deb

[Jose De la Rosa (jose-de-la-rosa)]

Changing status to reflect the fact that we still want this fixed at some point.

[Jose De la Rosa (jose-de-la-rosa)]

Tracking nv issues elsewhere.

[Bryce Harrington (bryce)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.

[Timothy R. Chavez (timrchavez)]

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1306189