nvidia 180.* driver inhibits resume from suspend

I can confirm this, although it only seems to happen on laptops.
I have also posted in the following thread in the Nvidia support forums, along with others who are affected by this issue:
http://www.nvnews.net/vbulletin/showthread.php?t=123303

This symptom should be resolved in 2.6.28-3-generic for resume from both suspend-to-ram and suspend-to-disk. Please confirm.

Daniel, do you want for me to test with the available but out of date 180.11 package or do you want for me to install the current nvidia code (180.18)?

I'm running 180.11 just fine with 2.6.28-3-generic across resume from suspend-to-*. Are you using that kernel?

Daniel,

OK, I spent part of today testing this behavior in response to your post. I used 2.6.28-3 and 2.6.28-4 (from a PPA built to test NFS changes) with the same results. If I use 177.82, suspend and resume work fine. If I use the 180.11 or the 180.18 package that I built locally as an update to the 180.11 package, resume after suspend works ONLY from the initial login screen. If I login, the system will suspend, but NOT resume. This was very reproducible.

Daniel,

I have tested all combinations of [2.6.28-3, 2.6.28-4 (released version now, too)] w/ [177.82,180.11,180.18] and posted the results. Is there anything else that I can do for you? You have this still marked as incomplete, implying that you are waiting for some information.

I can absolutely confirm this bug, using 180.11, running ubuntu 8.10!! The system hangs completely after or while resuming! Could be only an issue on Laptop GPUs, as I have got a Geforce 8600m gt. Kernel version is 2.6.27-11. Everything worked fine before, using the recommended 177.82 driver version.

Lemmiwinks, I have a desktop and am also affected. Though my system never hangs at random, resuming from sleep has *always* left me staring at a blank screen.

Oh, I should add that I haven't tested the latest kernel, so don't use my info for any reference as of yet.

Sorry!

Some problem with the lastest and "stable" 180.22 driver release :-(

Same here. Latest kernel and the 180.22 driver. I can suspend and resume from the login screen, but not if I have a logged in session, as I had noted above.

Kernel is 2.6.28-4.10

same here with 180.11 or 180.22 on a Vaio VGN-VZ21E, Ubuntu 8.10 with kernel 2.6.27-11, GPU is GeForce 8400M GT, laptop does not wake up after suspend and requires a hard reset.

Works fine with 177.82 driver

Confirmed with intrepid, 180.22

Oddly enough, suspend worked for me flawlessly about five or six times when I came back and applied all updates.

Then, stupidly, I thought I'd test the waters and just install 180.22 on my machine.

.....now, it's broken again. Even on my old 180.06.

That'll learn me. :(

Anyone know if this will be resolved before the 9.04 release? I upgraded to 180.22 to get rid of the horrible CPU usage when viewing Flash sites but the lack of suspend/resume sucks.

This issue is fixed in the newly-released 180.25 Nvidia drivers.

I did not notice an improvement on cpu usage when viewing flash videos with the new driver...
Where can I get the 180.25 driver?

Already found it, thanks!

The Nvidia site seems to only list 180.22, where is that 180.25 supposed to come from? Neither is such a packet in the apt (official) sources. So where did you find this? Might also be valuable information for other people watching this thread.

I got the link off of the nvnews site:
http://www.nvnews.net/vbulletin/showthread.php?p=1914053

with the x86 link:
ftp://download.nvidia.com/XFree86/Linux-x86/180.25/

For beta Nvidia driver releases you have to go to the nvnews site Clarke Brunsdon mentioned. Nvidia doesn't always post beta drivers in their official page.

Hopefully these will be packaged for Jaunty, since thanks to the suspend fixes, mobile users can now take advantage of VDPAU and the other performance improvements the 180.XX series offers.

I confirm that 180.25 fixes the issue.

Any hope that 180.11 is updated to 180.25 soon in the 8.10 repositories ?

By the way, I can't see any hint that 180.25 is beta in the announcement. Perhaps
http://www.nvidia.com/object/unix.html
is simply not up-to-date.

180.25 still does not add support for Xorg 1.6, so you'll still need to add the following to your xorg.conf:

Section "ServerFlags"
    Option "IgnoreABI"
EndSection

That is strange. I find that I do not need the "ignoreABI" option anymore.

My apologies, right you are. I was going by the Phoronix article that said it still lacked 1.6 support:
http://www.phoronix.com/scan.php?page=article&item=nvidia_18025&num=1

But "ignoreABI" doesn't seem to be required any longer.

Works like a champ on Ubuntu 8.10.

I have opened Bug 322416 to request that nvidia-glx-180 be upgraded to 180.25 in all repositories.

Is anyone still having the suspend problem? Should this bug be closed?

I confirm that 180.27 fixes suspend/resume for me. I haven't tried hibernate (I rarely use it). Thanks to Anders Kaseorg for his packages.

I also confirm that the 180.27 driver appears to resolve the issue for suspend-to-RAM & resume. I have not yet tested suspend-to-disk.

HOWEVER, this bug should not be closed until there are official packages that fix it.

Works for me with Suspend and Hibernate on a Nvidia Dell XPS M1330 and using pm-suspend/pm-hibernate.

> this bug should not be closed until there are official packages that fix it.

So now that there are official packages for 180.27, and based on reports, I'm closing this. If anyone can still reproduce the problem, let us know to re-open it.

guys,

ive got a hp dv2845se+Ubuntu 8.10.

since ive installed the 2.6.27-11 kernel, and updated the nvidias driver to NVIDIA-Linux-x86-180.22-pkg1 or NVIDIA-Linux-x86-180.27-pkg1 i noticed this: ubuntu starts, i get to the logon page and, after entering 'username' and 'password' screen just fades black and dont come back.

i have tried to stop/start gdm as a test but, the same thing happens.

so, after checking some files over tty2, when i came back to tty7 to see it anything had changed, gnome was there(and as long as i authenticated before, i was in gnome authenticated allright).
so the problem is that, once ive upgraded the kernel to 2.6.27-11 and updated the nvidias driver to 180.22, after authenticating user/pass, screen fades black. going tty2 and coming back to tty7 kind of solve the problem but, this must be a bug or something, i dont know.

am i missing some configuration ?

by the way, kernel 2.6.27-11 works just fine with nvidias driver 177.82. and by 'works fine' i mean that everything works fine after entering user/pass. there is no fade to black without coming to the normal screen with the icons and stuff.

thank you all in advance,

ifho.

Hi,

I have the same problems here (but with Jaunty Alpha - 9.04). After the login, I got a black screen, but with the mouse pointer.
If I disable the compiz (chmod a-x /usr/bin/compiz.real), the metacity works normally.

But, change back to nvidia 173 didn't solve the problem.

The most strange thing is that the applications seems to run normally under the back screen (all show up in ps, and no segfault).

Anyone has any clue?

laptop hp dv6707us

I'm install nvidia180 and have this problem too...but ismael filho

here i press Fn+f4 and my desktop comeback after the login.

eu instalei o jaunty 9.04 e depois instalei a versao do nvidia 180 depois de colocar login e senha a tela fika preta como se estivesse no dispositivo auxiliar entaum uso o atalho do teclado para trokar o monitor e ela reaparece... alguem sabe qual a configuração??

hey, here i install the nvidia 173 and now it works from the comando:
sudo nvidia-glx-173

Shouldn't this fix (well, whole package) be backported to ubuntu 8.10? Right now in indrepid-updates there is a version 180.11 which is affected by this bug (at least on my thinkpad t61).

I think it should be at least put into the backports repo, but I have no power over this. I will put a build for Intrepid in my PPA, though.

thank you,
i have installed version 180.35 and copy another xorg.conf in the internet
at now its working !!!!

2009/3/8 Michael Marley <email address hidden>

> I think it should be at least put into the backports repo, but I have no
> power over this. I will put a build for Intrepid in my PPA, though.
>
> --
> nvidia 180.* driver inhibits resume from suspend
> https://bugs.launchpad.net/bugs/306315
> You received this bug notification because you are a direct subscriber
> of the bug.
>

2009/3/8 Pinguim Gringo <email address hidden>

> thank you,
> i have installed version 180.35 and copy another xorg.conf in the internet
> at now its working !!!!
>
> 2009/3/8 Michael Marley <email address hidden>
>
> I think it should be at least put into the backports repo, but I have no
>> power over this. I will put a build for Intrepid in my PPA, though.
>>
>> --
>> nvidia 180.* driver inhibits resume from suspend
>> https://bugs.launchpad.net/bugs/306315
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

i use jaunty 9.04

2009/3/8 Krzysztof Klimonda <email address hidden>

> Shouldn't this fix (well, whole package) be backported to ubuntu 8.10?
> Right now in indrepid-updates there is a version 180.11 which is
> affected by this bug (at least on my thinkpad t61).
>
> --
> nvidia 180.* driver inhibits resume from suspend
> https://bugs.launchpad.net/bugs/306315
> You received this bug notification because you are a direct subscriber
> of the bug.
>

HA HA HA forget all what i say!
here i needed to reinstall my jaunty 9.04
and my xorg.conf not solve the problem..... but.. when i plug my
external monitor and just reboot...... alll this shit works man!!
icant believe in NVIDIA driver

Please upload a fixed version of nvidia-180 to the interpid update repository. Apparently, intrepid users are affected by a bugm which is know to be fixed since the beginning of February.

  TIA,

   Wolfgang

I can confirm that this is NOT fixed in Intrepid. Here are the installed nvidia packages:

ii nvidia-173-modaliases 173.14.12-1-0ubuntu5.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-177-modaliases 177.82-0ubuntu0.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-180-kernel-source 180.11-0ubuntu1~intrepid1 NVIDIA binary kernel module source
ii nvidia-180-modaliases 180.11-0ubuntu1~intrepid1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-71-modaliases 71.86.04-0ubuntu10 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-96-modaliases 96.43.09-0ubuntu1.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-common 0.2.4.1 Find obsolete NVIDIA drivers
ii nvidia-glx-180 180.11-0ubuntu1~intrepid1 NVIDIA binary Xorg driver
ii nvidia-kernel-common 20051028+1+nmu2ubuntu2 NVIDIA binary kernel module common files
ii nvidia-settings 177.78-0ubuntu2.1 Tool of configuring the NVIDIA graphics driv

Intrepid updates broke resume with v 180.11 only *yesterday*, after running perfectly for months with 177.something. I'm using a Dell XPS M1330 (bought with some other OS although Dell does sell this model in some countries with Ubuntu pre-installed) which has a GeForce 8400M GS. I did ask for Intel graphics but it didn't arrive.

I don't care about 3D acceleration but suspend/resume is vital and the nv driver has the same problem (this is the only reason I use the nvidia driver).

Intrepid updates also broke my resume as well. Curiously, I also get black dots on the upper-left corner of the screen when I reboot the computer..... I have to restart the graphics to get them to go away.

Same thing as xoddam. I'm using a Dell XPS M1330 and resume stopped working for me with version 180.11 after yesterday's updates.

I am also using a Dell XPS M1330 and I am experiencing the same symptoms in Intrepid. Please could an updated version of the driver be uploaded to the repositories that provided the broken 180.11 yesterday.

As a fix is know and has been released (just not in the right repositories) I won't bother with the log excerpts etc that I had collected.
uname -a
Linux drt24 2.6.27-11-generic #1 SMP Wed Apr 1 20:57:48 UTC 2009 i686 GNU/Linux

As reverting to version 177 works as a workaround this problem is not too bad but it should be fixed before more people discover it and possibly loose work.

Fixing this by uploading the updated packages to the relevant intrepid repositories would be greatly appreciated.

So does this mean that the problem has been dealt with and is just not distributed yet? Two problems just cropped up at once after some updates a few days ago, and I hope the issue isn't too hard to fix...

The problem had been dealt with before the problem even appeared for intrepid users, but an old version of the nvidia driver was pushed out to intrepid users and this broke resume.
It should not be too hard to fix because all it needs is for the correct package to be put in the correct repository. I am hoping that people with the relevant knowledge and power have noticed that the problem is not fixed - especially now the status has been put back to 'Fix Committed' rather than released.
Unfortunately I don't have time to learn the relevant packaging foo to do it myself as I have exams coming up.

Any version of the Nvidia drivers >= 180.25 should have this fixed. People looking to get this fixed immediately could use the Nvidia driver in my PPA, which is currently at version 185.19.

Thanks, I updated it and resume is fixed. However, the black dots remain upon bootup. Could someone tell me what packages were updated so I can narrow my searches? I can't seem to find any information on it

Chauncellor, are you by any chance using a graphical framebuffer module (vesafb, uvesafb, etc)?

I have no idea what those really are. I researched what vesafb and uvesafb are, but I don't know how to check, and I don't recall tinkering with such a thing. I'm using an NVidia 8600GT, if that helps. Is this the proper place to discuss this issue, however?

If you did not manually enable them, then they are not in use. I was just wondering because I once had a problem that seems like what you were having, but it strangely went away. I am not sure what fixed it.

In case is searching and come across this - my experience:

Using Ubuntu Jaunty, 2.6.28-11 kernel - I tried various nvidia drivers (177 worked but had poor performance with Gnome Do/Docky). I tried various 180 versions (incl 180.27 that others professed success with) and latest 185 but all failed to resume. Finally came across 180.60 and that works like a charm!

Hi, I don't know why this was set to new, but I realized I didn't follow up on what happened to my computer.

It was a bad upgrade. I reinstalled (for Ext4, too :)) and graphics were just peachy out of the box.

I'm going to go ahead and close this bug due to inactivity. The updated drivers had fixed the bug for the releases it affected (and some of them are now no longer supported).

If there is a problem on Maverick or Lucid similar to this it would probably be best to open a new bug.