nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Unable to init X after resume from suspend to RAM (256.35) (http://www.nvnews.net/vbulletin/showthread.php?t=153830)

DeiF 08-06-10 03:54 PM

Unable to init X after resume from suspend to RAM (256.35)(SOLVED)
 
1 Attachment(s)
EDIT: Problem solved updating to 256.44.


When I resume from suspend to RAM, X isn't able to start.
The keyboard becomes unresponsive, but I can ssh from another comp and generate the bug report.

These are the last 2 lines in the Xorg log after the resume:

Code:

[  293.364] (II) NVIDIA(0): Setting mode "CRT:1024x768_85+0+0,DFP:1680x1050_60+1024+0"
[  298.367] (EE) NVIDIA(0): WAIT: (E, 0, 0x827d, 0)

AFAIK the other devices are resuming fine. In runlevel 3 (console) suspend to RAM works OK.

Any ideas? Should I try a previous driver?

rp9 08-08-10 07:17 PM

Re: Unable to init X after resume from suspend to RAM (256.35)
 
Hi DeiF, did you overcome the problem? I have exactly the same situation and goolge don't seem to have an answer...

rp9 08-08-10 07:22 PM

Re: Unable to init X after resume from suspend to RAM (256.35)
 
1 Attachment(s)
Just to be clear, here is my nvidia-bug-report.Attachment 40874

DeiF 08-11-10 03:57 PM

Re: Unable to init X after resume from suspend to RAM (256.35)
 
Quote:

Originally Posted by rp9 (Post 2299610)
Hi DeiF, did you overcome the problem? I have exactly the same situation and goolge don't seem to have an answer...

No, I didn't overcome the problem.
I'm still waiting for a response by NVidia or anybody else for ideas.
I'm willing to provide more info if necessary.

I did a lot of testing with the pm_trace kernel feature, until I realized that the problem was just X not coming up after resume. I originally had enabled MSI interrupts, but disabled them just to try if it was the cause: it didn't work.
I don't know if Nouveau is worth trying, just to discard hardware problems.

I've run out of ideas.
(bumping the thread also:D)



EDIT: Installing 256.44 seems to have fixed the problem.


All times are GMT -5. The time now is 06:27 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.