• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Strange suspend problem *solved*

S

SickBeast

Lifer
Under Linux, my computer freezes while trying to "sleep". The strange thing is, it works fine the first time my computer sleeps after I boot it up. The second time around, however, my monitor fails to power down, several of the fans in my case continue spinning, and then my computer becomes completely unresponsive.

This issue happens under the following distros:

Ubuntu 10.10 x64
Ubuntu 10.10 32-bit
Peppermint Ice
Ubuntu 10.04.1 x64
Mint Debian
OpenSuse 11.3 x64

This issue does *not* happen under Windows!

I've tried changing just about every setting possible in my BIOS. I loosened the memory timings, tried enabling and disabling 64-bit hardware memory remapping, and I tried disabling Cool N Quiet.

My rig:

Opteron 165
Asus A8N-E (Nforce 4 motherboard)
4gb DDR ram
8800GTS 320mb

I also tried pulling out my memory sticks and running with just one stick of ram. This did nothing to solve the problem.

If any of you have any insight into this problem I would really appreciate it!

TIA

*edit*

I've solved this problem by adding "acpi_sleep=old_ordering" to my boot/grub/grub.cfg file. You need to put it after the kernel near where it usually says "quiet splash".

It turns out this is a bug in the Linux kernel since 2.6.22.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/347150

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/210543
 
Last edited:
Check your ACPI settings in the BIOS. I had a problem with my mobo and Sleep, so I just Hibernate instead.

EDIT >> I just checked again for the first time in a while, and Sleep works fine. I'll start using Sleep again.
 
Last edited:
linux sleep is always breaking it will work for long periods then stop. And going back to old versions doesnt fix it.

Currently taking a break from linux because of this.
 
KeypoX said:
linux sleep is always breaking it will work for long periods then stop. And going back to old versions doesnt fix it.

Currently taking a break from linux because of this.
Click to expand...
Yeah it's really annoying.

If I weren't so happy with my Ubuntu setup I would switch as well.
 
SickBeast said:
Under Linux, my computer freezes while trying to "sleep". The strange thing is, it works fine the first time my computer sleeps after I boot it up. The second time around, however, my monitor fails to power down, several of the fans in my case continue spinning, and then my computer becomes completely unresponsive.

This issue happens under the following distros:

Ubuntu 10.10 x64
Ubuntu 10.10 32-bit
Peppermint Ice
Ubuntu 10.04.1 x64
Mint Debian
OpenSuse 11.3 x64

This issue does *not* happen under Windows!

I've tried changing just about every setting possible in my BIOS. I loosened the memory timings, tried enabling and disabling 64-bit hardware memory remapping, and I tried disabling Cool N Quiet.

My rig:

Opteron 165
Asus A8N-E (Nforce 4 motherboard)
4gb DDR ram
8800GTS 320mb

I also tried pulling out my memory sticks and running with just one stick of ram. This did nothing to solve the problem.

If any of you have any insight into this problem I would really appreciate it!

TIA
Click to expand...

It's almost always the NVIDIA drivers.
 
SickBeast said:
Is there any way to work around the problem?
Click to expand...

You could try the nouveau drivers and see if that fixes the problem, i haven't used them for quite some time (and i have NO idea how stable they are at this point in time), i pretty much gave up on Nvidia drivers for Linux a long time ago and moved on to less performing but more stable solutions.

Other option, for strictly 2D is VESA, you could try that and see if that fixes the problem, then at least you have that much cleared up.

I assume you know how to config the unloading and loading of the agp and video module and that you are using the NVIDIA AGP module and not native? If not, search for that, there has to be hundreds of web pages on how to do that.
 
JohnOfSheffield said:
You could try the nouveau drivers and see if that fixes the problem, i haven't used them for quite some time (and i have NO idea how stable they are at this point in time), i pretty much gave up on Nvidia drivers for Linux a long time ago and moved on to less performing but more stable solutions.

Other option, for strictly 2D is VESA, you could try that and see if that fixes the problem, then at least you have that much cleared up.

I assume you know how to config the unloading and loading of the agp and video module and that you are using the NVIDIA AGP module and not native? If not, search for that, there has to be hundreds of web pages on how to do that.
Click to expand...
I've tried turning off all the visual effects and disabling the NV driver.

I'm not sure how to do the rest of the stuff you're talking about.

Isn't the "Nouveau" driver installed by default?

Thanks for your help! Hopefully I can get this sorted out eventually.
 
SickBeast said:
Is there any way to work around the problem?
Click to expand...

You could try removing the closed source driver and using the "nouveau" driver. I have a laptop that wouldn't resume from sleep when the nvidia_96 driver was enabled, but now it works great with the open nouveau one. You won't get much love from compiz with it though.
This is what I ended up with in my xorg.conf on that laptop (after lots of trial and error).
Code: 
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       30.0 - 110.0
    VertRefresh     50.0 - 150.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nouveau"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
        Modes      "1280x800"
    EndSubSection
EndSection
My desktop has a GTS250 1GB and it sleeps just fine with ubuntu 10.04, (I use the "nvidia-current" driver from the restricted-updates repository).

Another possible issue is if you have any network shares set to auto mount in fstab, this can sometimes interfere with sleep.
 
Last edited:
SickBeast said:
I've tried turning off all the visual effects and disabling the NV driver.

I'm not sure how to do the rest of the stuff you're talking about.

Isn't the "Nouveau" driver installed by default?

Thanks for your help! Hopefully I can get this sorted out eventually.
Click to expand...

Ok, let's step back here, which driver are you using? "nv" or "nvidia"?

The nouveau driver is not installed by default in any other distro than Fedora as far as i know (i'm out of the loop though so that might have changed since i last looked).

Normally (if i remember this correctly) in Ubuntu you'll get the nv driver from setup but you then have the choice to install the closed source nvidia driver through "restricted drivers" and if you do that, you get the nvidia driver.

Whichever one you got, try the other and just disable loading of the native USB module and make sure you load your nvidia agp module via the x config file.

I don't really remember how to disble and enable modules based on waitstates in Ubuntu, it's been a long time and i have no access to a search engine here either so... you'll have to look that up on your own, it's not that hard, i do know how to do this in arch but it uses a BSD like system which none of the distros you mentioned does.

In OpenSUSE you should be able to do it via the "control panel" - "services" (excuse me if the name isn't exactly right, it should be close enough).

Sometimes it's the USB drivers, but that has more to do with failing to wake up so..
 
Thanks very much, John. It's going to take a bit of research on my part to figure it all out, but you've given me a start in the right direction.

I'm running the "Nvidia" driver to clear things up a bit. That said, even using whatever Ubuntu defaults with, I was still having the same suspend issue, so I'm not sure what to make of all this just yet.

Anyhow, thanks again! I'll report back once I try to implement your suggestions.
 
KeypoX said:
so when they go from something like 2.6.36.8 --> 2.6.36.9 nothing is changed but security?
Click to expand...

Well, kernel updates within a release are security updates only for OpenSUSE and Ubuntu unless they are moving version numbers (which has happened, Ubuntu might be popular but it's quite uselss).

For distros like Arch, i suggest you check the web frontpage to see what's changed and see if you can live with all changes, disable some changes or not update.
 
SickBeast said:
Thanks very much, John. It's going to take a bit of research on my part to figure it all out, but you've given me a start in the right direction.

I'm running the "Nvidia" driver to clear things up a bit. That said, even using whatever Ubuntu defaults with, I was still having the same suspend issue, so I'm not sure what to make of all this just yet.

Anyhow, thanks again! I'll report back once I try to implement your suggestions.
Click to expand...

Oh, in that case, ask nothingman (debian guru as i understand it) how to prevent the loading of the chipset specific agp and add nvagp = 1 to your X config file (probably found in /etc/xorg).

In Arch linux you just put a ! in front of the module in /etc/rc.conf but Ubuntu doesn't follow the BSD standard.

That is the first thing you should try, if it doesn't work, just write in "vesa" instead of "nvidia" it will be pure 2D but if your hibernation works after that, you'll know for sure where the problem is.

And you are welcome, i'm just sorry i don't have access to search or being at home where i could test it myself.
 
Ok, so today I tried Fedora 14 which uses the Nouveau driver by default. The suspend problem persisted.

That said, I tried Lubuntu 10.10, and I got the following message on the screen as it was trying to suspend:

powernow-k8: ph2 null fidtransition 0xa

I have a feeling that this has something to do with my problems.

Have any of you seen that message before?

TIA
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top