Ubuntu :: Suspend Fails On Lenovo T400 / ATI Graphics?
Aug 31, 2010
Suspend works about 50% of the time on my T400. The other 50% of the time, the screen goes blank (light stays on), there is a blinking cursor in the top left, and the "moon" light blinks forever.
I've got the latest ATI (3470?) video driver installed. I've seen a few posts about this but no clear solution. Anyone here have this problem and (more importantly) been able to fix it?
I just got a new T400 and installed Ubuntu. Everything is fine and I'm really impressed by this OS. But seems my wireless network is very unstable. Sometimes it just can't connect.
I'm running Karmic Koala 64 bit on my Lenovo T400 laptop with switchable graphics having both Intel and ATI video cards. I've set my bios to use the intel card only and turned the automatic switching off. So far so good, but I'd like to turn on compiz for basic window animations. When I try to start compiz by selecting
doesn't show any new drivers that could be installed. This was working out of the box when I first installed Karmic Koala a few month ago, but things got messed up when I installed the restricted drivers for my ATI card. Now I can enable compiz if I switch to ATI from my bios settings and install the drivers but I don't want to use it due to high power consumption and I've removed the ATI drivers.
Here is my xorg.conf file:
Code:
Section "Device" Identifier "Configured Video Device" EndSection
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 have a Thinkpad T400 running FC11 and am using integrated (intel) graphics, because I know FC11 doesn't have 3-D acceleration support for the ATI Radeon Mobility 3470. I take this to be because the 2.6.29 kernel and the X Server release were too new, and unsupported. I know from phoronix that 2.6.29 is now in fact supported with the advent of 9.8, and that I believe my X server is supported too.
As far as I can tell, this means I **should** be able to use fglrx..I was wondering how one backed up their X configuration on Fedora, as it doesn't really use xorg.conf very much. I was also wondering how to reconfigure X for a completely new graphics card with a completely new driver, without reinstalling. That is, quite simply, out of the question for me, as I've made many customizations to Fedora, and I don't have the time to back them up and restore them.
I'm having a bit of trouble with my Lenovo thinkpad. Usually, on a fresh install, when I tell my computer to suspend (either by Fn-F4 or selecting it from the menu) it suspends itself. From time to time, however, the computer will lose the ability to suspend and will simply darken its screen and flash the little moon crescent indefinitely, upon which I have to hold down the power button to shut it off.
While this is the second notebook I've had the luxury of running Slackware on, I have never used the the suspend to RAM / swap functions so all of this is new to me. With this new notebook and new installation of Slackware 13.1 I decided to give it a shot as it's definitely a power sucker. The machine is a Lenovo W510 with an NVidia graphics card running KDE. When I tell KDE to go to Sleep (RAM suspension) it looks like it does so properly by blanking the screen and pushing things to RAM. Is there a way to verify that Sleep is working? Anyway after unlocking the system my mouse pointer is no longer visible, however it is still active as I can hover over items to reveal their popups.
At this point none of my conky displays are transparent anymore, nor are they actively displaying stats. The windows I have set to display with 88% opacity are no longer as such and are completely opaque. It is as if all the custom window settings are ignored. If I move the the mouse towards the bottom of the screen the screen starts to go crazy with this rainbow of colors across the top of the screen and the only way to get out of this is to press Ctrl-ESC to bring up a System Activity window. I have not tried Hibernate yet as I would like to get this resolved first. Is Slackware 13.1 supposed to be able to Sleep/Hibernate with no special configuration and creation of scripts provided that the system can handle these functions?
I'm experiencing an annoying issue since I upgraded from 9.10 to 10.4: when I try to put my Laptop to sleep, the control sign for suspension starts blinking and that's it: the system hangs and I've got to kill it with pressing the power button. Resuming doesn't work either, same symptoms.
I just updated my kernel to the latest version (2.6.35-24). Now my suspend function on my Thinkpad SL510 no longer works. The system simply hangs with a solid cursor in the corner of a black screen. USB devices remain powered on, HDD keeps spinning, and all indicator lights remain lit. When this happens, the only thing I can do is hold the power button down for a hard power off.My first thought would be to troubleshoot this with dmesg, but I don't know how to record dmesg after a power off. The message buffer is reset when I reboot.
A few months back, my Lenovo IdeaPad Y510 stopped connecting to my wireless network after coming out of Suspend (it had worked fine previously). Wireless networking is simply disabled, and I have to reboot in order to get it back. I tried upgrading my OS from Intrepid all the way to Lucid, but the problem persisted. I also tried changing my 00sleep_module as suggested in this thread, but to no avail.
I'm using a lenovo t530 laptop with debian testing. my suspend button combination (fn / f4) suddenly stopped working, from recent updates? How to get a terminal readout from what's happening when i push these buttons.
I am trying to install Ubuntu 10.10 on an Lenovo G560 laptop with Intel P6100. Everything seems to work fine except for the graphics. The screen goes blank when I enter startx from the console.
lspci shows the following for the graphics card : 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) In xorg.conf, I've tried drivers 'vesa' which gave me low resolution, and also 'intel' which blanked the screen again. How do I configure this graphics card ? Has anyone else faced similar issues when installing Ubuntu on this graphics card?
I just put Fedora 11 on my Lenovo Thinkpad t400. I selected the integrated (lousy, but Intel (supported)) graphics device in the BIOS, but I really hate the lower performance than the discrete graphics device. However, this device requires fglrx or radeonhd for DRI. RPMFusion has not released an (a)kmod-fglrx, so I can't use that. I have heard radeonhd has some stability issues though, and I don't know how to install. I was wondering how I could completely change my graphics configuration (change chipsets in the BIOS) and get the X Server in Fedora 11 working with the new driver and chipset. Is it a good idea to use radeonhd, or should I wait for the fglrx?
Even then, how would I completely change my graphics configuration so it would work with a different card & driver? I don't want to do a fresh install because I've done a lot of work & customization with the F11.I don't know anything about radeonhd, so any information about this kind of thing would be useful.Finally, should I just suck it up and deal with the Intel graphics? Is anything of this sort really worth my time? (I'm willing to spend quite a bit, trust me!)
This laptop has been in the mainstream news as the cheapest Windows laptop available. Unfortunately it has a 64-bit CPU with 32-bit UEFI that dumps to the grub shell before installation. In addition, the built-in keyboard does not work.
As far as the dump to shell problem, this seems like something is not setup correctly in the grub UEFI configuration. This "hybrid" notebook should be using the multi-arch as I understand the situation. I noticed there is no grub configuration file in the multi-arch netinst ISO when I mounted it and looked around. I also noticed the standard netinst ISO is not easily mountable: there are errors when I try to mount the individual partitions to inspect the grub configuration. Additionally, Kubuntu boots perfectly aside from the keyboard issue. Devuan also boots when I modify the netinst to bypass gummiboot and use grub directly. Finally, the multi-arch grub shell freezes up when autocompleting and searching through the drives for the grub config, leading to a forced reboot. As an extra note, I tried 2 different flash drives and CD install media with the same results.
I tried many, many grub kernel combinations to fix the keyboard issue. It works in grub, but not in Linux. I was ultimately going to try a newer kernel to fix it.I was in a hurry to get something set up so back to the store it goes.
I'm trying to install openSuSE 11.4 onto my brand-new Lenovo W520 laptop, using the Intel Rapid Storage Technology (FakeRAID?) controller, ROM version 10.1.0.1008. I have 2 physical 500GB disks configured in a mirror (RAID-1). Everything looks fine, the installation program comes up and asks if I want to use mdadm to manage the RAID, to which I answer yes. I go through the normal setup screens, and select the partition layout that I want (for sake of this post, I'll limit myself to the layout that the system itself recommends).
The problem comes when it becomes time to format the partitions. Somehow the partitioning program gets it into it's head that the root partition is 10TB, not 20GB, and the ext4 partitioning fails in various ways (short reads to sector zero, unable to map using 4096 byte sectors, etc, etc) depending on exactly which partitioning scheme I'm attempting. I pretty much get the same result no matter how I play the partitions, which file systems I use (XFS, ext4, etc [of course, I can't use XFS for /boot...]).
For now I've gone ahead and set myself up using software RAID, since this system is unlikely to become dual-boot with Windows for a few years at least. (As an aside, but as a hint to others, when the installation fails, I end up having to go back into the Intel RAID controller BIOS boot to clear out the entire RAID setup each time it fails - the disks are left in a completely useless state).
Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend. I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds." The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus). Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new. I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop. As you can see from the logs, I've been working on this for a month already!
Here's a typical error message:
Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
Here's an example log showing 2 tasks that fail to freeze:
Code:
Nov 9 01:25:09 MyComputer kernel: [16615.765114] PM: Syncing filesystems ... done. Nov 9 01:25:09 MyComputer rtkit-daemon[1738]: The canary thread is apparently starving. Taking action. Nov 9 01:25:09 MyComputer kernel: [16615.767512] PM: Preparing system for mem sleep
Ubuntu Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend.
I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds."
The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus).
Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new.
I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop.
As you can see from the logs, I've been working on this for a month already!
Here's a typical error message: Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
I recently installed Ubuntu 10.04.1 LTS and have it set to dual-boot with windows 7 on my gateway tablet PC. Since installing, sometimes when I suspend or reboot, my wireless does not work. To be more clear - it is working fine, then I either suspend/reboot, then I come back and no wireless networks show up at all. I can still connect with ethernet cable though. I can solve it by rebooting multiple times (usually around 1-5 times) and then it (magically) seems to work again. I have also tried switching from network-manager to wicd, but the problem persists. With both network-manager and wicd, I've tried simulating a reboot for the wireless by using the command 'sudo modprobe -r iwl3945 && sudo modprobe iwl3945' (network-manager) and 'sudo /etc/init.d/wicd restart' (wicd), but these do not seem to work.
I've had this problem two times before and solved it once by following a guide, the other time by formatting. It always happens when it fails to wake up from suspend. Usually I am unable to even mount the drive or access the files. This one is different in that now I can actually access my files for the most part but this comes up on boot. I backed up most of my files (except it still says I don't have permission to access some of them) but I would like to get it back up and running without formatting. If I boot in recovery mode it stops at this. I took a picture but I rewrote some of it here.
Firewire_core: created device fw0: GUID 00016c000061b4b4. S4??? in/sh: cannot open ro Kernel panic - not syncing: attempted to kill init! Call Trace: [<c05c8283>] ? printk+0x2d/0x32 etc Image posted here: [URL]
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.
My computer have ATI X600 graphics card installed, and I installed CentOS5.3.
Every time I suspend my computer and then resume it, it seem the graphics card can't resume and the monitor says 'no signal', but the system still responses, I can use keyboard.
Is there any configuration I can't do to make it resume normally? I've searched a lot in Google but can't find out any one else run into the same problem.
I have what I think is a somewhat different failure of standby than I've seen listed on other threads, and I'm stumped.The system hangs on this for a while, then comes back to the login screen without going into standby. This ONLY HAPPENS on a SECOND standby attempt--the first standby after booting ALWAYS succeeds.The standby log doesn't indicate any failures.I had made other changes previously that temporarily got standby working consistently:/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
I upgraded from 10.04 to 10.10 Worked fined, but suspend doesn't work anymore. When I click suspend, a tty1 terminal screen appears, exactly as you would hit ctrl+alt+F1, with the exception that no input is possible. I'm a newbie and an Ubuntu fan but I absolutely have no idea how to solve this...
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 (2.6.38.2 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), 2.6.37.0 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 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
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.
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.
I've been struggling with suspend to disk (hibernate if you prefer) for a while, it works after a fresh boot and for several days' worth of overnight hibernation as I go about my work, but eventually it stops working - it gets to the splash screen but the bar only makes it a little way to the left before stopping, and then after a timeout the system just returns to the "session locked" screen - no real error messages.
I've done my best to try to find out what's causing it to break but I'm really struggling, the suspend process doesn't appear to write anything helpful to the dmesg log or the /var/log/pm-suspend.log - the only thing that I've seen at about the right point in time is cifsd, but I can't be sure that it's a problem with cifs as hibernate continues to work immediately after mounting windows shares with cifs.
My hibernation was working out_off_the_box but now it has strange issue. This is debian testing with kernel 2.6.38.4 "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.