Debian Configuration :: Squeeze: Suspend/hibernate Resume Fails With Radeon Graphics
Aug 6, 2010
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
I'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation: I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options: Install newer kernel from Squeeze backports (220.127.116.11 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 18.104.22.168 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 22.214.171.124 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
I have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed) 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
I just got a Dell Inspiron 1764 and am dual booting it with Win7 and Ubuntu 9.10.Whenever I hibernate or suspend, it goes through everything fine, but then when I resume it just boots to a black screen and I have to do a hard shutdown. Is there a fix for this? I know it's a fairly common issue.
I've got a Thinkpad X31 with ATI M6 Ly card. Since Karmic, and Lucid, I get no suspend/hibernate/resume. If/when I select resume or close the lid, Lucid goes through the suspend cycle, and for approximately half a second it actually seems to go into suspend, then the screen comes back on, black, but definitely on, and absolutely no response to any keyboard input - have to hard-shutdown by holding down the power button. I've read that the problem is with the Ubuntu kernel, and that installing/compiling 2.6.33 fixes the issue, but causes other ones.
I have just joined the Debian community, for the past 2 years I have been using Linux Mint (ubuntu), I am now using Linux Mint Debian 64. I have a Lenovo A700 ideacentre with a Broadcom 4313 WiFi card. I manage to get the card working, now I have a new problem. If I suspend the machine the WiFi will not connect on resume. Is there a simple command I can use to getting the connection restarted, or better yet a work around so it will restart on its own?
Installed Debian 8.2 a while back, and I've been having issues with getting the machine to suspend correctly. If I try to put it to sleep when logged in to my regular user account the screen just goes black and then the computer hangs. However if I put it to sleep as root everything works fine. I do this by running this command (as root):
Code: Select allsystemctl suspend
What can I do about this? Worked fine on Debian wheezy..
Btw, just found this in the dmesg log. Connected perhaps..?
Code: Select all[ 6.863018] ACPI Warning: SystemIO range 0x00000000000018e0-0x00000000000018ff conflicts with OpRegion 0x00000000000018e0-0x00000000000018ef (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258) [ 6.863028] ACPI:
If an ACPI driver is available for this device, you should use it instead of the native driver
I've been running 6.0.2 amd64 stable since release day and recently have noticed my suspend and hibernate do not work. Normally I have transmission running and have set it to not enter sleep mode while torrents are active. However today I have not had transmission and was wanting to see if the sleep mode options would kick in. So I have set my display to "sleep when inactive for" 5 mins (this works perfect) I have set "put computer to sleep when inactive for" 10 mins (this does not work at all)
When I try to manually test suspend my display flashes black for a few seconds but remains backlit, then asks me to log back in When I manually go into hibernate mode my display turns off, pops back on for a second and in a terminal says something about a usb device (something failed but it happens so fast I cannot read it)
The good news: 11.4 seems to have much better support for my radeon graphics driver which makes many of my workarounds for 11.3 unnecessary
The bad news: whereas previously for 11.2, 11.3 using traditional ifup meant that I could easily restore internet (either wlan0 or eth0) with ifdown/ifup now this seems to have no effect. I haven't investigated further yet since without internet on hibernate or suspend 11.4 is not my grub of choice at the moment
There seem to be quite a few glitches with the 'stable' release of 11.4 but this seems to be the main problem for me. (Minimizing the beta 4 Firefox windows closing them is another...)
After I resume from hibernate with my cpu frequency manually set to the highest settings (2ghz) the network manager shows not wifi APs. "wlan0" shows under both ifconfig and iwconfig but "iwlist wlan0 scan" says no results. "sudo iwlist wlan0 scan" also says no results. I've tried rmmod then modprobe with no luck. Rebooting is the only way I can get WiFi working.
I can get wifi working again by: - rebooting - changing the cpu scaling to a lower setting then hibernate/resume - changing the cpu scaling to a lower setting then 'sudo rmmod ath9k; sudo modprobe ath9k;'
I am using Ubuntu 10.04 with Atheros ar5008 (AR5BXB72) using ath9k drives Code: $ lspci |grep Atheros 0e:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Code: $ uname -r 2.6.32-24-generic
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
I've tried editing .xinitrc to contain ck-launch-session and dbus-launch to no avail. Console kit is installed. I'm using Sid without a login manager, and xfce's suspend and hibernate work fine on my Wheezy computer. Xfce4-session and consolekit are installed. Is this a problem with permissions?
I have installed the latest virtualbox 4.1 on my desktop and laptop. It hosed suspend and hibernate.
The laptop is A Dell D630 with Intel Core2 Duo CPU, the desktop is an AMD based ASUS M3N78-VM mobo with Athlon II x2 250 CPU. Debian Testing 32-bit (same results with the 2.6.39 and the 3.0 kernels). Both have nvidia cards though - the desktop an integrated 8200, the laptop a NVS 135M. But suspend/hibernate was working before with the 4.0 series virtualbox.
The workaround is to clear the vboxpci vboxnetadp vboxnetflt vboxdrv modules from the memory before suspend/hibernate. I added the
service vboxdrv stop rmmod vboxpci vboxnetadp vboxnetflt vboxdrv
lines to my sleep script (i dont use power managers, just the acpi powerbutton/lid scripts modified). Everything is ok now.
If I suspend my notebook it starts the usual slow orange blinking indicating the suspend mode got reached. There is also evidence in the various log files that this works. If I try to resume it hangs a for 3 seconds and then I get the hdd-password screen from my bios and the notebook boots from zero. I couldn't find anything in /var/log/messages nor dmesg. If I first boot to windows (grub 2nd partition) and then restart and boot to linux, all the suspend works fine
i dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
I use my laptop at the college, and I've to suspend him frequently. So, I've decided to install the package pm-utils, to hibernate my PC, instead of power off it. When I try to do "# pm-hibernate", a tty appear, and this error is displayed :
[3506.405310] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2 [3506.405310] PM: Device usb1 failed to freeze: error -2 This is the result in pm-suspend.log : Initial commandline parameters:
I have Debian Squeeze x64 on ThinkPad T61p with standard 2.6.32-5-amd64 kernel. thinkpad_acpi loaded as module, suspend to RAM works fine from menu in KDE as well as by closing the lid, however machine doesn't appear to react on pressing Fn+F4 which should put it to sleep as well. I've read through thinkpad_acpi documentation and asked Google but so far can't find the solution. Can anyone, point me in correct direction?
I have an Acer Aspire TimelineX 4820TG. I'm running Wheezy and I can't seem to get switcheroo working correctly. I was running Squeeze, then upgraded to Wheezy because it had a kernel over 2.6.33 with switcheroo built in. Below is the layout of my build...
(~)$ uname -a Linux skipjack-debian 2.6.38-2-686 #1 SMP Thu Apr 7 05:24:21 UTC 2011 i686 GNU/Linux (~)$ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: ATI Technologies Inc Redwood [Radeon HD 5600 Series]
Alright, Lenny has a working "fglrx-driver" package for my laptop, but Squeeze does not. Would it be possible to install the one from Lenny on Squeeze since Squeeze has newer libraries and such? I know I can't install new stuff with older libraries, but can I install the old stuff with newer libraries? I am at the end of my rope here! I mean ATI sucks and we all know this, but I've always found a Linux/open-source alternative that worked, until Squeeze.
I have recently updated my Ubuntu 9.10 install to Ubuntu 10.04 and the default kernel to 2.6.32-23 on my Acer Aspire 5738z laptop with 3 GB RAM and Intel GMA 4500m graphics card.
My problem is sometimes the laptop fails to resume after being Suspended to RAM. The problem is not consistent. Most of the time the system resumes properly but then some times it doesn't . It even doesn't respond to the Magic Keys. I am left with no other alternative but to keep the power button pressed till the laptop shuts down.
I've just started using OpenSuse 11.2 KDE. I have KDE4.4 installed. I had this issue with KDE 3.4 as well. My HP Multimedia DV3065 laptop is encountering an issue with suspend/restore. After restoring, the mouse is frozen. I have already tried a few things.
1. Dropping to init 1 and then back up to init 5 did not provide a temporary fix. So this is probably hardware related in some sense (kernel?) 2. I tried a grub option (cant remember what it is now). i8500-reset something like that. It made no difference. 3. I tried modifying my 99ZGrub file per another posts suggested solution. That actually locked up my laptop and I could not reboot (even after a cold boot). I pulled the battery and let it sit for a bit and it booted again
So I have several issues.. 1. I would like suspend to restore my mouse. 2. I have not figured out how to program my Sleep button to Sleep. My menu bar icon has Log Out / Restart / Turn Off. The ALT+F1 menu tab Leave has those plus Sleep and Hibernate.
My hibernation was working out_off_the_box but now it has strange issue. This is debian testing with kernel 126.96.36.199 "hibarnation-disk" hibernate successfully ,with an error though ( seen from hibernate-disk -v2 --dry-run) hibernate-disk:Warning: Tuxonice binary signature file not found Anyhow , after executing the hibernation , on the next boot, the system boots from scratch and not from the resume image. During boot a message is displayed though Invalidating stale software suspend images I have done some google search but none of the solution work so far, including reinstalling the package itself.
I have a desktop system (P55-USB3 + Core i7 + Ubuntu 10.10) that fails to suspend/resume from memory. So I'm trying to diagnose the problem. The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries. All the pm_test modes from freezer to core succeed (I followed [URL] I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that. The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
Just got Ubuntu 9.10 and I'm liking it a lot, but my computer refuses to go into hibernate or suspend. I have a Dell M1530 but I don't really think it's a dell hardware issue because it's not just when I close the screen, it's also when I click suspend or hibernate from the menu.
My system cannot resume after hibernation. I have done all as described here [URL] ...
My have set up swap file "/swap_debian".
I have 3 partitions: sda1: windows boot partition. sda2: windows 8.1. sda3 : debian
I have the only linux distro installed: debian.
I have read lots of web pages. I have managed to set up suspend 2 disk. After dancing 2 days at the computer the system still cannot resume. I am getting "clearing orphaned inode" msgs while booting, and when booted to ram was not recovered.
Swap file is 4000 MB, RAM is 3860 something MB
My current grub is:
Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration'
And yes, I did update-grub.
My current /etc/uswsusp.conf is:
Code: Select all# /etc/uswsusp.conf(5) -- Configuration file for s2disk/s2both resume device = /dev/sda3 compress = y early writeout = y image size = 1855258869 RSA key file = /etc/uswsusp.key shutdown method = platform resume offset = 31606784
My current /etc/fstab is:
Code: Select all# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5).
I'm in need of a bit of assistance from you Debian users. I have two servers that I thought were identical installations, both running Debian Lenny. Tonight I started the upgrade to Squeeze on both servers and one of them went smooth. The other one started out good but fails on the postconfiguration of openssh-server. I'm getting the following message: