Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 08-06-10, 02:54 PM   #1
DeiF
Registered User
 
Join Date: Oct 2008
Posts: 114
Default Unable to init X after resume from suspend to RAM (256.35)(SOLVED)

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?
Attached Files
File Type: gz nvidia-bug-report.log.gz (36.4 KB, 86 views)

Last edited by DeiF; 08-21-10 at 02:44 PM.
DeiF is offline   Reply With Quote
Old 08-08-10, 06:17 PM   #2
rp9
Registered User
 
Join Date: Aug 2010
Posts: 2
Default 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 is offline   Reply With Quote
Old 08-08-10, 06:22 PM   #3
rp9
Registered User
 
Join Date: Aug 2010
Posts: 2
Default Re: Unable to init X after resume from suspend to RAM (256.35)

Just to be clear, here is my nvidia-bug-report.Attachment 40874
Attached Files
File Type: gz nvidia-bug-report.log.gz (58.1 KB, 87 views)
rp9 is offline   Reply With Quote
Old 08-11-10, 02:57 PM   #4
DeiF
Registered User
 
Join Date: Oct 2008
Posts: 114
Default Re: Unable to init X after resume from suspend to RAM (256.35)

Quote:
Originally Posted by rp9 View Post
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)



EDIT: Installing 256.44 seems to have fixed the problem.

Last edited by DeiF; 08-21-10 at 02:43 PM. Reason: Solution found.
DeiF is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 05:35 PM.


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