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

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-09-08, 01:56 PM   #37
olifre
Registered User
 
Join Date: May 2008
Posts: 50
Default Re: [180.08] Screen off after suspend to ram

Sorry for the late answer, there was a lot of other stuff to do :P.

Well, there is an option 'MODULES=""' in ACPI-Support. However, it seems that Intrepid does not use these options anymore, but now does standby using the kernel (or some other method). Thus, all the other ways tried here can't work.

Currently, I'm lacking time to do further investigation - maybe somebody else knows more about Ubuntu's way to suspend?

I am not sure whether the X-Server really would have to be unloaded - maybe, the module is unloaded / loaded before the CPU is completely reactivated. But, as I said, I don't know so much about the newer methods to standy.

TuxOnIce might do a better job, though - however, you'd have to recompile your kernel, and you need time for that :P.
olifre is offline   Reply With Quote
Old 12-09-08, 03:02 PM   #38
overkll
Registered User
 
Join Date: Dec 2008
Posts: 2
Default Re: [180.08] Screen off after suspend to ram

I don't know if this pertains to 180.xx, but I've needed it for my Geforce 8400M/MCP768 based laptop in order to get suspend AND hibernate to work with ANY of the newer stable nvidia drivers 173+. Works with Gentoo and Ubuntu Intrepid. I couldn't even boot the Hardy Heron or Intrepid beta live-cds without it.

Try adding `pci=nomsi` to your bootloader's kernel command line.
overkll is offline   Reply With Quote
Old 12-09-08, 03:30 PM   #39
huiii
Registered User
 
Join Date: Jan 2007
Posts: 43
Lightbulb Re: [180.08] Screen off after suspend to ram

Quote:
Originally Posted by olifre View Post
Sorry for the late answer, there was a lot of other stuff to do :P.

Well, there is an option 'MODULES=""' in ACPI-Support. However, it seems that Intrepid does not use these options anymore, but now does standby using the kernel (or some other method). Thus, all the other ways tried here can't work.

Currently, I'm lacking time to do further investigation - maybe somebody else knows more about Ubuntu's way to suspend?

I am not sure whether the X-Server really would have to be unloaded - maybe, the module is unloaded / loaded before the CPU is completely reactivated. But, as I said, I don't know so much about the newer methods to standy.

TuxOnIce might do a better job, though - however, you'd have to recompile your kernel, and you need time for that :P.
As far as I know, there was a change performed in suspend/hibernation methods with the release of ubuntu hardy;
since then the suspend-stuff is done by pm-utils and not by acpi anymore.
so, if we need to investigate on how to deal with the video-card during suspend, i guess we need to understand how pm-utils work...
huiii is offline   Reply With Quote
Old 12-09-08, 03:31 PM   #40
huiii
Registered User
 
Join Date: Jan 2007
Posts: 43
Default Re: [180.08] Screen off after suspend to ram

Quote:
Originally Posted by overkll View Post
I don't know if this pertains to 180.xx, but I've needed it for my Geforce 8400M/MCP768 based laptop in order to get suspend AND hibernate to work with ANY of the newer stable nvidia drivers 173+. Works with Gentoo and Ubuntu Intrepid. I couldn't even boot the Hardy Heron or Intrepid beta live-cds without it.

Try adding `pci=nomsi` to your bootloader's kernel command line.
what does it do, actually, `pci=nomsi`?
huiii is offline   Reply With Quote
Old 12-09-08, 03:49 PM   #41
overkll
Registered User
 
Join Date: Dec 2008
Posts: 2
Default Re: [180.08] Screen off after suspend to ram

It disables Message Signaled Interrupts system wide. From menuconfig:
Code:
  │ CONFIG_PCI_MSI:                                                         │  
  │                                                                         │  
  │ This allows device drivers to enable MSI (Message Signaled              │  
  │ Interrupts).  Message Signaled Interrupts enable a device to            │  
  │ generate an interrupt using an inbound Memory Write on its              │  
  │ PCI bus instead of asserting a device IRQ pin.                          │  
  │                                                                         │  
  │ Use of PCI MSI interrupts can be disabled at kernel boot time           │  
  │ by using the 'pci=nomsi' option.  This disables MSI for the             │  
  │ entire system.                                                          │  
  │                                                                         │  
  │ If you don't know what to do here, say N.
EDIT: IIRC, Ubuntu ALWAYS enables MSI in their kernels.
overkll is offline   Reply With Quote
Old 12-09-08, 06:49 PM   #42
ledoc
Registered User
 
Join Date: Jan 2008
Posts: 330
Default Re: [180.08] Screen off after suspend to ram

In my experience, you can have other devices use MSI (like soundcard, ethernet) without necessarily causing suspend problems. But having the nvidia module and GPU use MSI will break suspend.

I think there is an option for the nvidia module to enable/disable MSI for it (check in /proc/interrupts what is used).
ledoc is offline   Reply With Quote
Old 12-10-08, 12:14 AM   #43
nevion
Registered User
 
Join Date: Dec 2004
Posts: 74
Default Re: [180.08] Screen off after suspend to ram

pci=nomsi and NVreg_EnableMSI=0 changes nothing. I've tested them both in all permutations. Each time my machine hardlocked before it could even turn on the screen.

Nvidia's driver is what broke, the distributions have not changed, at least not ubuntu/opensuse. Nvidia can you please comment on the matter?
nevion is offline   Reply With Quote
Old 12-10-08, 03:10 PM   #44
tomee
Registered User
 
Join Date: Dec 2008
Posts: 2
Default Re: [180.08] Screen off after suspend to ram

I am not sure yet, but it seems like applying the following changes to /usr/share/hal/fdi/information/10freedesktop/21-video-quirk-nvidia.fdi helps in Ubuntu Intrepid:

Code:
14,15d13
<         <remove key="power_management.quirk.s3_bios"></remove>
<         <remove key="power_management.quirk.s3_mode"></remove>
18a17,18
>         <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
>         <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
(Lenovo T61, NVidia NVS140m)
tomee is offline   Reply With Quote

Old 12-10-08, 04:09 PM   #45
perfectska04
Registered User
 
Join Date: Nov 2008
Posts: 31
Default Re: [180.08] Screen off after suspend to ram

Quote:
Originally Posted by tomee View Post
I am not sure yet, but it seems like applying the following changes to /usr/share/hal/fdi/information/10freedesktop/21-video-quirk-nvidia.fdi helps in Ubuntu Intrepid:

Code:
14,15d13
<         <remove key="power_management.quirk.s3_bios"></remove>
<         <remove key="power_management.quirk.s3_mode"></remove>
18a17,18
>         <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
>         <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
(Lenovo T61, NVidia NVS140m)
What exactly does this do? Does it completely fix resuming from suspend?
perfectska04 is offline   Reply With Quote
Old 12-10-08, 05:28 PM   #46
nevion
Registered User
 
Join Date: Dec 2004
Posts: 74
Default Re: [180.08] Screen off after suspend to ram

I've tried this method using the fdi and - as usual - there is no change in behavior. In my earlier posts I mentioned that I could resume if I suspended and resumed back to back only seconds apart - I theorize this has to do with memory discharge over time in the suspend power state and the driver's assumption of memory state upon resume. If the memory loses its state from discharging too much over a few seconds (something dram is known to do) then the driver is foobared on resume. Now if you make it in that narrow window where the memory state is intact, then things resume fine. This is the card's memory btw, not system memory. So it would seem it's a case of not storing and recovering the card's state properly. So again, suspend is completely broken atm. Somebody would have posted a working configuration by now if one existed.

*Cough* nvidia, enough people have gathered on this now right? Can haz driver fix now pleez?
nevion is offline   Reply With Quote
Old 12-12-08, 09:47 AM   #47
tomee
Registered User
 
Join Date: Dec 2008
Posts: 2
Default Re: [180.08] Screen off after suspend to ram

Quote:
Originally Posted by perfectska04 View Post
What exactly does this do? Does it completely fix resuming from suspend?
Don't know, haven't tested extensively.
Before these changes resume always broke, now for 5 tries that I did it always worked.
tomee is offline   Reply With Quote
Old 12-12-08, 02:30 PM   #48
nevion
Registered User
 
Join Date: Dec 2004
Posts: 74
Default Re: [180.08] Screen off after suspend to ram

Quote:
Originally Posted by tomee View Post
Don't know, haven't tested extensively.
Before these changes resume always broke, now for 5 tries that I did it always worked.
Have you tried waiting some period of time (>1 min) before trying to resume? Does it resume consistently then?
nevion 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
RHEL 5.6 .nvidia-settings-rc settings un-applied on screen lock bluziff NVIDIA Linux 1 06-14-12 05:12 AM
Black screen after switching between graphical virtual consoles five times rrr-wtf NVIDIA Linux 1 05-21-12 04:40 PM
Stubborn screen res problem Alpsoandso NVIDIA Linux 6 05-03-12 06:00 PM
Toshiba Sat 1950 screen setup beaulieu NVIDIA Linux 7 06-13-03 03:17 PM
Redhat 8.0 NVIDIA works - INSTRUCTIONS STEEL1 NVIDIA Linux 267 04-15-03 06:48 PM

All times are GMT -5. The time now is 07:37 PM.


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