I know it is super complicated to fix this because it is hardware dependent, but most people take this features for granted and it is very annoying to find out that hibernate/standby in Ubuntu are equivalent to shutdown/restart.
The number of Laptops is growing and will continue to grow so good working stand by and hibernate are really needed.
I've been having a terrible time getting my wireless working when coming back from a suspend or hibernate on my m1330n any time I change classes or put my computer in my bag when I come back it's 50/50 whether I'm going to be able to get my wireless working again :(
This is a big bother for me. I try to suspend my laptop when I go to and from class, and roughly half of the time when resuming from suspend I just get a black screen and have to hold the power button and reboot, losing everything that I had open. Sometimes, it won't even suspend, but the screen turns black for a minute before coming back, but I usually find this out after it has been in my backpack coming too and from class, and the laptop is nearly overheating.
This would definitely improve the experience for many mobile users. I find mac laptops tend to suspend and resume very gracefully, Ubuntu should mimic that. I find my new eee pc running Ubuntu dies when suspended with a full initial battery charge in what seems like 8 hours or so. My macbook seems to last days. Also my eee takes a really long time to resume from suspend, I sometimes lose the machine as I can't get the display back, though most of the time I just get a black background for 10-15 seconds before X seems to come back.
The intel driver is definitely not configured well on my machine.
I have way more problems than with suspend and hibernate.
1. Suspend usually works, but not always. Often the mouse won't move after coming out of suspend.
2. Every time I've tried hibernate, my computer doesn't come back to life.
3. When I connect to a VGA (external monitor), horrible things happen. I have to change resolutions manually (something that ought to be done automatically, really). I don't know if this is a television problem, but when I connect VGA to my television, everything but the eject button stops working until it's unplugged and plugged in again (probably is an Insignia television issue).
What also needs to be fixed is the speed of hibernate and wakeup! Aside from the fact that I had to install a hardy kernel on gutsy to get suspend to work at all, suspending and resuming is actually much slower than a full reboot.
This could be fixed by switching to suspend 2, when I was using this on my debian box, suspend and wakeup was an order of magnitude faster.
Nowadays sleep/hibernate is given for granted. That it doesn't work at all in many laptops makes ubuntu look very bad.
This is a must have just to be in the race.
the only way I can get hibernate to work reliably on feisty and gutsy is to manually compile a kernel with the tuxonice patches, and even then it hibernates and resumes much slower than the Windows XP partition on the same Laptop :(
Suspend/Hibernate support seems to be getting worse. I used to be able to suspend and hibernate my AMD/ATI desktop, but that support broke sometime in Feisty with updates. Then my intel video laptop broke all suspend/hibernate with Gutsy.
Suspend/Hibernate is a fundamental feature that should be supported where at all possible. With this working, there is also much less pressure to improve boot times.
Suspend and hibernate working fine normally, but it'll cause my laptop unable to recover from suspend and hibernate when the mplayer application is running.
In that case, I've no choice but to press the power button to force reboot.
Hugh issue, even with desktops. My desktop burns 200 watts; 5000 such machines left on because suspend/resume doesn't work wastes a megawatt. It is much more important than eye candy.
Suspend/resume worked with Fiesty, but is a crap shoot on Gutsy. On my machine every thing works on resume but the usb-keyboard until I restart the x server using my usb-mouse. My machine is a Dell XPS 410 with proprietary nvida drivers.
I've worked for a Linux distro myself. I understand how complicated this is, but it's a really big deal - or dealbreaker for many. I own an IBM/Lenovo T60 laptop and I have not been able to suspend or hibernate for almost a year now. This is simply not acceptable. I get it - the fault lies with ATI and their fglrx driver, but the problem is that this series of laptops is one of the most popular in the world. It's just plain embarrassing that Linux in general, and Ubuntu do not correctly support this hardware. Ubuntu, and other distros, should be front and center loudly proclaiming that ATI's closed-source video drivers _do not work_ If they cannot get things right, then open source them so that you, and other open source proponents can.
The Ubuntu responses to the endless posts about this issue on the bug-tracking system are not acceptable. This issue is a showstopper and must be fixed, no matter how painful. If the distro won't run on mainstream, business hardware used by millions around the world - well, it's dead at the starting gate.
Please - speak for us end-users and get in the face of ATI (now AMD) and others to get this fixed.
Many, many thanks for creating a truly impressive distro.
rozen is right on this one. The amount of power wasted each year because laptop *and* desktop users are not able to suspend and instead just leave their machines on has got to be HUGE.
This is the fault of INTEL for refusing to open the BIOS or to provide sufficient documentation for the chipset and processor.
The reason that Intel doesn't open up the BIOS is that it has agreed with Phoenix Technologies and American Megatrends to protect their markets from competition from open source.
I know this because I own a company that manufacturers computers. I tried to get from Intel technical documentation to solve this problem. Intel's engineers candidly told me that they were prohibited from releasing the information because the company had agreed to protect Phoenix.
I don't know "why" this works, but it does for my Thinkpad X60s. I suspect its something that will work for others, since its a bios level thing, and that relates to the previous post.
1. sudo gedit /boot/grub/menu.lst
2. find the grub menu line that is the ubuntu default .. the first one that appears, that will look like this:
title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel ....... etc
3. Add the following to the end of the "kernel" line:
acpi_sleep s3_bios
Here is my "kernel" line.
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=b6e33b4a-d2ec-4107-9aaa-8956ed669d82 ro quiet splash acpi_sleep s3_bios
This is the biggest problem for Ubuntu at the moment. Power saving issues are really important for many users, and it is really annoying that they don't work. A minimal workaround would be to include a diagnostic tool, which gives a warning when the user tries to suspend/hibernate the system, if it fails, or something.
I'm having huge issues with it as well, especially since I'm using nVidia restricted drivers (via Envy), and I have a dual-core AMD64 processor, so I'm doubly screwed. These days I just shut my computer down every night, when I'd rather leave it in suspend or hibernate so that it will come back on more quickly.
This is a huge issue with windows as well from what I have seen. So don't be disheartened, realistically though, I have seen less issues with my ubuntu than I have with clients Windows, even Vista.
For this reason I don't think it is as big an issue as others that are out there.
This is important for notebook users. One mode does not let the computer wake back up. The other sometimes does, but seems to run the CPU full out the whole time the lid is closed. Could be a fire hazard or equipment hazard that way if it's packed away in an air tight case or amongst flammables.
Agreed that this is a major problem. Must note that the problem mostly lies with proprietary drivers, which people seem to turn on for 3D and compiz. Doesn't mean that should hang back and let ATI and NVIDIA slowly fix at their own pace. Either support 3D in open drivers or make hibernate work.
However, even with hibernate problems, I'm running Ubuntu on fglrx with compiz-fusion full as it gives me an awesome user experience. Guess that kills off my battery life, so I'm stuck to a/c power.
It has nothing to do with proprietary drivers for video cards: because I have this problem on two systems with Intel video cards, which run on the usual open source drivers.
I know that fglrx causes problems in some cases, so yes, it does have to do with proprietary video cards. The problem is not *only* with proprietary video cards, but it certainly affects them adversely.
but unfortunately I'm sure that it is not only kernel or ubuntu problem. I have an ATI X1300 Mobility card in my HP nc6400 and it doesn't work at all. ATI shoud commit it's patches as well.
HP 6510b and 6710b (both with intel x3100) suspend&hibernation doesn't work neither :(
amen sister (or brother)! this issue is show stopper enough for the average joe. i installed gOS on my wife's laptop and she can't have her laptop unplugged (if she's using it or not) for longer than the battery will last or it dies.
why is this happening? why is it related to video drivers? honestly, i don't care if a proprietary driver is necessary or not - this just needs to be solved.
Two Dell laptops; two different sets of problems with power management; no solution has worked with any consistency. And another "me too" for Gutsy being more broken then Feisty.
A resounding endorsement of fixing that. #1 for sure.
My first experience with Linux a few years ago was trying to install it on an IBM T20, which I found out in the course of my frustration and research, was an exception and did not play nice with Linux at all on the issue of suspend and resume while being one of the most popular laptops of its day. It seemed to me at the time that there was something fundamentally wrong with Linux because even Windows 98 could suspend a T20. This left me with a negative impression that has lasted for some time even though I am a Linux fan and dual boot every machine I own. Since then I've learned more but nearly every computer I've tried to use it on has had an issue with it not working without having to address some issue. To use a MS phrase, it leaves a bad "OOBE" (out of box experience). The failure of Linux to do something fundamental like that produces its own "FUD" due to the logic that "there's never just one cockroach"
Like others, I find this to be an important issue. I have a Dell D620 laptop and Feisty worked fine with it. Suspend was wonderful. Upgraded to Gutsy and this, among other things, is broken. I would really like a fix for this issue.
Yes! I am using ubuntu 7.10 on laptop and desktop and have issues about Hibernate on laptop yet.
I just realize this issue is about nvidia (restrict) driver. After active this driver hibernate does not works.
What happens:
- When pressed hibernate button the system is successful hibernated, but... when resuming the screen got stuck on a "white" panel filling all the screen. After a few seconds it show some "blurs" on the screen and the system freezes.
daigorocub:
Thanks for your comment. The Ubuntu environment will then for sure help us saving the _real_ environment.
And no, I'm not an activist. At all.
+1 vote. This issue is so annoying that I have spent a VERY good deal of the time since I half-switched to Ubuntu trying to fix this (first on a Thinkpad R50e, where I discovered that I had to somehow break - dunno how still, it was serendipity - 3d support of the intel i810 driver to get it working; and now Dell Inspiron 6400, where intel wireless and nvidia video card drivers gave me lots of problems).
One thing, though. In this year fiddling around I found out that to fix or at least improve the problems with closed drivers it was sufficient to add some lines to the acpi, saying to leave some modules in the kernel or stop some services. My question then becomes, why when I install one of these drivers does the system NOT take care of this work which I have to do manually? I do not think it would be that hard to add some minor script so that restricted manager takes care of this, using the huge feedback already existing to create the base database of necessary hacks to the acpi-support (or any other file, I am not knowledgeable enough to tell where else one must act).
It seems to me that Ubuntu has mainly targeted the Desktop pcs. There Ubuntu rocks (ever put a desktop pc into suspend? yeah, me neither). But as laptops are continuously spreading in the user-base, IMHO Ubuntu should focus more on those to be a runner in the mid to long term.
I had tried so hard to find solutions to fix this only got to nowhere.
And this Suspend and Hibernate have never been stable in term of one day I can get it working; usually after system was setup the way I wanted it, then failed the next day. So sometimes I would decide to reinstall the OS again only to lose all the settings and software I would have installed.
I am using a HP DV9xxx laptop. And what I have found so far, is that when I need to use special parameters at the boot time, like apm=off noapic and etc, then this function usually fail.
At one time, I found i386 edition can be loaded without using any of these parameters and the AMD64 one would always required.
But in summary, please have this function to be fixed perhaps in the near release.
Yes, this is a big one. Here's my experience on my averatec 2300 (amd turion); in feisty sleep/hib/etc worked fine. I upgraded to gutsy and that action completely broke. After the screen saver timed out and control was passed to hibernate the x server would go *snap* and leave the screen all white and strange, requiring a reboot. I went back to feisty, which didn't resolve the problem. I re-installed fiesty one more time doing a complete wipe of the hard drive. This finally got me back to a working situation. Other than this experience however my time with ubuntu has been really great.
Neither Suspend or Hibernate work on my installation of Gutsy. It did not work on Feisty or Edgy either. I am on a Dell Inspiron 8600. It seems like X fails because there is no video, but I have not done much to research. In my mind, this is there for convenience and should work "out of the box". I'm a Linux admin and do not mind tinkering with it myself, but if Ubuntu wants to convert more winders users, this will have to just work.
I would like to mention explicitly that this is as PC issue too, not just a laptop. From a green perspective and also from a money perspective. I don't want my PC burning extra energy even though it's plugged into the wall. Currently both hibernate AND suspend lock up my desktop computer, so I end up having to wait for it to boot every evening when I come home and then shutting it down before bed time.
Adding to this -
Suspend which I use(d) daily worked perfectly on Feisty with my Lenovo v100. This was the one thing that Gutsy broke on my system. Fixing for Hardy is an absolute priority.
Suspend/Hibernate is a one big pain I'm living with when using Ubuntu. I have Acer Travelmate 8204. The system never comes up from suspend mode. It would be nice if Ubuntu can fix this regardless of laptop/desktop.
woohooo thanks cappy, now my suspend seems to be working pretty much without a hitch. I can't thank you enough for the tip (nor can I believe that I looked for so long and it ended up being something so simple). I still do think this is the most pressing issue with ubuntu. Once people see my laptop running compiz they flip at how cool it looks. But when they see it struggling to make it out of suspend they're normally a bit taken back.
This is one big issue for me. Everything seems to come back up expect for the video, the screen on my laptop is blank. With Ubuntu 7.04 I was able to hibernate and it worked fine but with Ubuntu 7.10 lost that ability.
Oh man, I would kill to see this problem fixed. When my laptop with an ATI Radeon x1200 card hibernates or suspends, I can't awaken it at all and have to reboot.
ACPI S3 is the holy grail of suspend and hibernate. When they work they are just plain awesome. However they are kernel and acpi support related. The acpi standard was poorly designed (Google for Linus'es comments if you want to see some quite bitter text) and the vendors keep changing things constantly.
What would really be required to "fix suspend and hibernate" are three things. First of all, the rare breed: C wizards that are able to work with Linux kernel. Second, hardware donations (motherboards and/or complete systems) to the developers. This could however be substituted with giving SSH access to your computer - major trust issue but sometimes doable. Third, support from the vendors. (docs etc)
This would be great to have working out of the box. I drag my laptop between home and work and then from one office to another for various projects and having to actually power down every time is a serious pisser.
Hibernate/resume works great for me (Dell Inspiron 5100) except for the fact that when I hibernate, I get a screen full of USB debugging information instead of something telling me the system is in the process of hibernating.
For a user new to Linux, hibernating bringing up a screen full of techo-babble is a Bad Thing, and they may never hibernate again.
With that said, the core issue is making sure hibernate works at all. Making it user-friendly is just icing on the cake.
I would really like this feature to be working on my laptop. I read somewhere that it has something to do with the ATI restricted graphics drivers. Next time i'll go for a Nvidia card..
rawsausage raised good points. There are challenges, but with all this interest, there should be things that can be done. I'd suggest:
* Promote a standard test procedure and related tools to probe the hardware and try out the different methods of suspending.
* Develop a reporting procedure where people can report the behaviour of their systems to the different tests
* Perhaps a suspend-test package that will automate some of this, and try out the suspend options, sending back the debugging information to a database.
The test/debug tools package would probably need to change regularly (and require re-testing) as developers gain new ideas about how to fix specific computers, and what different things to probe.
Basically, rather than (or in addition to) developers getting donation PCs or SSH access, if the testing procedure is automated, they can do the tests in parallel on thousands of PCs at once, and all developers can benefit from the tests others have made.
Both work (most of the time) on my Compaq Presario V6402CA, but sometimes it will refuse to suspend/hibernate (goes black screen, but then "wakes back up" immediately.
Also annoying, I tell power manager to leave the PC on when plugged in but it goes to sleep anyway.
With a lot of effort I got my Dell D830 to suspend properly most of the time. Even now I can't really "trust" it, you have to watch it carefully to make sure it really suspends when you close the lid. Occasionally the mouse and keyboard don't work when you unsuspend.
I never got it to work on my T60 Laptop and it's one of the things I really miss a lot. I hate having to reboot completely every time - so this would be indeed a great fix!
hibernate has been working on my sony vaio (s260) since 6.10 - at that only the trackpad scrolling functionality would dump on resume. not a major concern for me.
I can understand a lot of people find this is a major issue, but this isn't something that ubuntu can do much about.
For me, when using the opensource ATi driver, suspend works like a charm. Using the closed source driver, it doesn't work at all. I bet the same goes for 90% of the people talking about this 'bug'. The issue here isn't suspend resume per-say, but rather the closed source drivers. Get those fixed, and it's all fixed.
i recently succeded in configure suspend2 on my hp dv6146 laptop with nvidia proprietary drivers, ndiswrapper for broadcom wireless ecc.. it was kinda hard but possible.
I can tell suspend2 is light-years fastest than default suspend and hibernate shipped with ubuntu...
Why don't you think to include that in future releases?
i think suspend and hibernate should be also quick in going and coming back, default system takes more time than a normal reboot... otherwise they're kinda useless.
I agree this idea , not only as a better experience in the user way , also very much important for support a sustainable
world ecologically talking ...
Yeah, seriously. Continue to improve Suspend/Hibernate and don't break what already works. When I test an Ubuntu beta, alpha, or release candidate and there's a regression please fix it. My older laptop had suspend working in dapper and feisty, but was broken in Gutsy even though I am using opensource video driver. The Hardy alpha i was asked to check still didn't work.
This idea does *NOT* defend the use of proprietary drivers to enable a perfect suspend/resume...
... it defends a perfect suspend/resume using open source kernel code, that works everytime, even if the user is using some proprietary drivers (like nvidia) that have problems sleeping nowadays.
It might be just me, but it seems a lot of people have read this entry wrong.
Most definitely a bit issue for people moving to Linux.
I don't think it should be considered a Ubuntu problem more of an general Linux problem.
I guess Ubuntu developers can do something about it to a certain extend. What I see as the complex issue is not only what should be done to fix, but how much time Ubuntu should spend on it.
I am not sure how Ubuntu and other distribution / kernel people keep record of what is broken / what works when it come to Suspend.
What I can see is Ubuntu as a big active community, if there was a big Suspend issue database or the-like that would open up, I am sure quite a lot of people to help to provide useful information.
Well it's just one idea... I don't know what the developer need the more for fixing those suspend issue.
this is THE number one reason I have not yet switched to Ubuntu. Hibernate just doesn't work (suspend kinda does nwo). That's the major showstopper. A laptop OS without proper working laptop features is just not possible. Please Ubuntuaniacs, fix this.
Regarding the posts that this isn't something that Ubuntu can do much about, I don't think that completely true. It partly is packaging and documentation, because currently there are several different suspend methods, each with different options. Currently Ubuntu pushes just one of those with one set of options via the graphical suspend/hibernate buttons.
There is also Suspend2, tuxonice, and other suspend methods. However, currently there isn't much current documentation about what is available, and the differences between those.
A package could be developed for people willing to fiddle more that simply click "hibernate" and observe it does/doesn't work. - instead trying the different options, with/without X, with different X driver etc..
It 'kind of' works for me on my laptop, but not flawlessly.
Suspend/standy works when I select it manually from the menu. Even though klaptopdmanager/daemon is set up to suspend when closing the lid, this only works occasionally. Most of the times, it just starts the screensaver.
Hibernation works, but takes extremely long when comparing eg to Windows.
In both cases, when coming back up, it happens quite often that I see my desktop and then it goes into suspend mode again, so I have to start it one more time before I can actually use the laptop.
No big issues but it would be nice if this could be better.
On my laptop suspend to ram and hibernate works fast and without any problems with vista. With Ubuntu so far it does not work at all. (although maybe the fglrx drivers are to blame, but there is no other solution for it so far) If you want people to use Ubuntu / Linux instead of Windows, then suspend must work.
This question: easy and reliable suspend and hibernate has been the main reason why I did not dump my Macbook for a Ubuntu machine that I would better appreciate. With suspend working as good, I would switch back to Ubuntu tomorrow. (On my wife's windows xp coputer, suspend does not work well either !). THanks for the work
and I have problems suspending to ram, mainly the major problem is that the screen goes blank and it doesn't come back. I wish there was a per laptop model wiki because of the way each one has different settings for propper suspend.
Since Ubuntu is targeted as a "friendly" desktop linux distro, suspend and hibernate need to work out of the box (or in this case fresh off the cdrom.iso). Could certainly win more converts.
I agree it is important, but you have it all backwards. The problem as others have said is that each laptop model is different and supporting them all reliably is impossible. Someone has to be paid to make it work, and generally the development work and tweaking is included in the purchase price, but only in a few cases is Ubu the target.
So what needs to happen? The Linux community needs to forward a hardware standard for which Linux is guaranteed to work. Make a "Guaranteed to work with Linux" logo and certification process. This is bigger than Ubu/Canonical and probably needs to be addressed by the Linux Foundation and broader community. Unfortunately, the Linux Foundation has limited pockets and at least one of their major employees (rhymes with highness) appears not to use a laptop (or at least has stated he's only really interested in desktop hibernate).
Short of that, the only bandaid solution is to have laptop-model specific packages that are maintained by the community. Installing these packages would do a "best practices" tweaking of the system.
Maybe some of these may be able to help some situations. Apparently there are some kernel patches to be done to use tuxonice (suspend2) - but I haven't seen how this is done on Ubuntu yet.
When I was using gentoo, I would update vanilla kernel every new release. I never had issues with any particular kernel releases.
However gutsy would not work on lappy. Hardy does I'm pleased to say :).
I'm running Gutsy on a T61p and the overall user experience is phenomenal -- except for the failure of Hibernate. It just doesn't feel like my OS is taking its job seriously if it can't do this simple task.
Agree with tirade - having two buttons (suspend and hibernate) that a user sees every time they log out, both of which cause the computer to crash looks cheap.
At the very least, if it doesn't reliably work, they should be removed from the menu.
Sometimes I feel like ubuntu takes one step forward and two steps back.
In feisty on my laptop, a Gateway MT3707, wireless and suspend and hibernate worked out of box. There was sound as well.
Now, in gutsy, wireless causes a kernel panic upon connect (so I'm forced to use ndiswrapper), sound doesn't work and I needed to compile Alsa from source and apply a patch that isn't going to go upstream, and suspend and hibernate doesn't work.
Interestingly enough, every time I fix sound, after every kernel update they push, I have to recompile alsa.
I really just want suspend and hibernate to work. The other problems I can deal with, but this is ridiculous. I'm actually thinking of switching to another distro.
Taking that there is a working solution for this, I just cannot understand how long Ubuntu can ignore this. Suspend2 or TuxOnIce (http://www.tuxonice.net/) as it is called nowadays solves this most requested feature easily. Why not implement it then?
Focus on speeding up booting and shut down times. Remove hibernate and suspend buttons for default.
Hibernation takes ages to be done when you have a lot of RAM anyways. And suspend does not really save energy.
If booting and shut down times could be halved we wouldn't even need these things.
If you really want to keep hibernate and suspend, improve them but please, avoid proprietary drivers, I don't want to see people's freedom reduced for such unnecessary features.
vexorian: S3 suspend does save a lot energy. On the desktops I've tested, S3 suspend power supply draw is only slightly above the "off" power leakage. Don't confuse it with S1 suspend - which indeed doesn't save energy.
If suspend and hibernate were working, then we wouldn't need to worry so much about boot times.
The idea is not talking about using proprietary drivers to do it. It is talking about making it work even when people are using proprietary video drivers. If anything, if you wanted to remove proprietary driver dependency, you would be better off encouraging suspend - because it is one of the things that is driving people to the open source video drivers.
Ya, the next ubuntu need to hav the fix, its bad think in a Debian Baseed OS w/ this problem. Original Debian dont hav it.
amitk(Ubuntu developer)
wrote on the 3 Mar 08 at 22:34
Thanks for all your comments. We strive to improve Ubuntu with every release and this feedback is important to us. Here are a few thoughts in getting suspend and hibernate to work:
1. It is very complex to get working because it depends on every peripheral driver on the system behaving correctly. And sometimes there are just buggy drivers.
2. The single biggest culprit preventing suspend/hibernate is the video driver.
3. With binary drivers (mainly ATI and Nvidia), we do not have _any_ control over making these drivers behave - so users are left to choose between better 3D support or hibernate.
4. Suspend2 suffers from lack of support upstream (Linus') tree. Coupled with the fact that the patch is very intrusive, it makes maintenance of the patch harder for Ubuntu.
5. As has been shown recently on LKML and various talks [1], both the swsusp and suspend2 (tuxonice) suffer from significant design drawbacks, so that they may never work correctly. There is new work ongoing on using a kexec-based approach that is being currently seen as the successor to the current design.
6. Using open drivers has a better chance of success. If that doesn't work, I urge you to file bugs on launchpad.net so that we might try to fix those.
7. References [2] and [3] are pointers to further debugging your suspend/hibernate issues. Help us in fixing your machines.
No mather how complicated it is to fix, this is a show stopper for most people. It is required to work out of the box like it does in any modern respectable OS. I used ubuntu with proprietary Graphic driver because these are the one that allow me to use my graphic adapter to its full potential. Using my graphic adapter to its full potential is the main reason why I did by a graphic adapter, so it should not be a reason for not having the possibility to suspend and resume. it is much more important imho than having a desktop cube. It can mean 150$/year in economie when used overnight instead of leaving it always on. This is for me the most anoying bug that there is in ubuntu.
amitk(Ubuntu developer)
wrote on the 5 Mar 08 at 00:31
Hi Julien,
I am willing to hear suggestions on how we can get proprietary drivers vendors to co-operate with us. Most of the Linux and *BSD communities would be interested in finding a solution to this problem.
One solution that is encouraged by these communities is to ask users to vote with their wallets - buy hardware that ships with open drivers (or atleast open specifications). Most Intel graphics chips[1] and many ATI ones[2][3] now have open drivers or are working towards open drivers. So the expectation is that these problems will go away, but it will take some time.
In the meanwhile, if there is something that works on another Linux distros but not on Ubuntu, we want to hear about it.
Last weekend i upgraded to hardy alpha5 and although I was aware of the meaining of "alpha" and I want to contribute, I can't understand why things break that worked before in gutsy....
Hardware:
Samsung P35 notebook, ATI Radeon 9700 Mobility (r300) with free drivers, ipw2200 WLAN
Before:
Gutsy, s2ram (suspend) works like a charm (needs only vbe restore)
*suggestion*:
Wouldn't it be possible to help the user migrating a working setup to the new pm-tools based infrastructure? Like asking
- "Does suspend/resume work for you?" Y/n
- "Shall I try to migrate the old settings?" Y/n
Additionaly after a resume the user is asked, if the resume worked as expected. In case of a failure either the default settings may be loaded or some probing script may be started to evaluate a working setup AND publish the results.
I think if this could be fixed it would be amazing as currently I tell people who's machines I install it on just to not tuch those options. I think this is a kernal issue and to get it to work for all chipsets will be quite a challenge and accomplishment if it were resolved.
I like the way a MacBook goes to 'sleep' when you close the lid. It instantly writes everything to RAM and only uses a tiny fraction of power. Upon reopening the lid, you can resume your work instantly.
From a usability perspective, this is better than hibernate. Current huge amounts of RAM (up to 4 GB) take almost as much time to write to disk then plain old rebooting.
The only 'drawback' of Macbook sleep being that you can't swap batteries, because it would purge RAM. But why not find an adapter instead? I have heard reports of Macbooks that can be in the sleep state for days and still be used.
That MacBook behaviour described is "S3 suspend", also known as "suspend to RAM" to differentiate against hibernate, which is also known as "suspend to disk". There is also a mode that keeps the data in RAM, as well a writing it to disk - and the disk image only used on resume if the power was lost.
S3 Suspend is good on desktops too, where the current draw is typically very little more than the "off" leakage current.
S3 Suspend is theoretically implemented in Ubuntu, but the problem is there is just so much hardware that doesn't work properly with it, and there isn't much coherent documentation about how to get it going when it doesn't "just work" .. hence the demand here for it to be fixed.
For me, both suspend and hibernate are slow, jerky, not as aesthetic as shutting down (screen pixellates and blinks), and disrupt services like the volume manager. These bugs really make suspend and hibernate useless to me at this point; shutting down is just much more convenient.
Well, that quick fix doesn't really work for gutsy, because the s2ram has been deliberately removed because apparently we don't need it and it would be confusing to us to have it available.
On the other hand, for me the following works on my Dell D400,
sudo apt-get install pm-utils
now the pm-suspend does s3 suspend correctly, and it seems to also work through the graphical option on the shutdown menu
One way to fix this:
1. Ask the user "Is this a Laptop?" during installation.
2. If yes as user "What brand laptop is it?"
3. Taylor installation of APM to fit the laptop
4. If it is an unrecognized brand inform the user that suspend/hibernate may have problems
Though being a laptop or not isn't all that relevant - it applies equally to desktops and laptops. Also the question of which is the right way to "taylor" the installation isn't clear. There seems to be a bit of a power-play going on between three different suspend/hibernate projects, and each think they are the right way to go. Ubuntu has chosen its way, and so would recommend that as the best solution in all cases.
For each method, it's also an issue of knowing what is the right way to do it for each model. That is the hard part. Once that's known, then the model that the user has can pretty much be auto-detected.
I think what really needs better support are the users with some technical know-how to do some level of debugging. That's less than 1% of users, who can then do directed debugging on their own hardware to better gather and incorporate that information. The results of that would then flow on to all users. The problem for that 1% is that the documentation is rather haphazard, and much is out of date. It would be good if there were an official ubuntu wiki that kept up to date with how things should be done for those users prepared to do a bit of debugging and information-gathering.
That's an interesting talk. It leaves me a confused about s2ram though, given that it's presented as the state of the art, but yet the s2ram user interface binary has been compiled out of the recent Ubuntu uswsusp packages. Maybe pm-utils replicates the same userspace functionality, but with the HAL whitelist instead of the s2ram whitelist??
But then neither uswsusp or pm-utils packages are installed by default it Gutsy ... why's that?
This is a deal breaker for many. My girlfriend was loving Ubuntu on her laptop until we found out it would not support suspend. She actually quit using her laptop because of it. This must be fixed or Ubuntu will not be a viable solution for laptops!
@amitk: I appreciate seeing a developer come in and help explain things and why they are difficult. I was wondering why there is such an issue with the X3100 Intel drivers using suspend/hibernate if they're open source drivers? As I just bought a new laptop, I found a LOT of newer laptops that use this gpu, all of which (it seems) will have no suspend/hibernate on the LTS Hardy. That's no good...
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/164974
Since the main problem is closed drivers for Video cards, it's the choice you have to make at the moment.
Use open source drivers (with minimal/bare 3D accel, think old ATi cards, intel cards etc) and have suspend/hibernate working pretty much fine, but expect slow 3D performance (on my 9600 mobile the open source drivers work well enough for wobbly windows etc, but obviously can't do heavy 3D). Or use closed source drivers, but don't expect suspend/hibernate to work. It's a choice atm you'll have to make.
You cannot blame ubuntu for this, it's driver makers fault. Some are doing there best (intel for example) some are changing their old ways (ATi). And as mentioned before, even windows has plenty of problems with suspend/hibernate. Though I absolutely agree, Suspend/hibernate is very important to us all.
I installed Hardy on my HP Compaq 8510p and was pleased to see that suspend works with the radeonhd driver. However sometimes it still crashes, I think this is maybe related to the radeonhd driver which is developed by Ubuntu.
But if it does not work correct, Ubuntu needs to care about it. Otherwise users will run away from Ubuntu. I don't know where exactly the problem is, but maybe the Ubuntu developers need to collaborate more with Novell and the radeonhd developers (radeonhd is sponsored by Novell, afaik)
"
If suspend and hibernate were working, then we wouldn't need to worry so much about boot times. "
But then, if (re)boot was made faster then we wouldn't need to worry about suspend and hibernate either.
From the devs' point of view it looks like working on speeding those up is more viable than hoping for everyone to use hardware with open source 3d graphics cards.
As of your clarification about proprietary drivers, I stand corrected.
"No mather how complicated it is to fix, this is a show stopper for most people."
And I want a pony.
"It is required to work out of the box like it does in any modern respectable OS."
You mean, like in no OS? Even windows doesn't offer that out of the box and has issues.
"I used ubuntu with proprietary Graphic driver because these are the one that allow me to use my graphic adapter to its full potential."
Buy one that doesn't require that sort of driver.
"Using my graphic adapter to its full potential is the main reason why I did b*u*y a graphic adapter, so it should not be a reason for not having the possibility to suspend and resume."
You are just saying it is not a valid reason because you don't agree with it.
"it is much more important imho than having a desktop cube."
As long as the kernel devs work in compiz, this statement is relevant, else it isn't.
"It can mean 150$/year in economie when used overnight instead of leaving it always on."
Ubuntu does allow you to turn the computer off.
"This is for me the most anoying bug that there is in ubuntu. "
That's a matter of opinion.
-
I insist, remove those buttons, speed up (re)boot and just pretend these things never existed, if you want you computer to go green, turning it off saves more energy...
aidave: What you are saying about having gnome restarting , is not hibernate, it is power off + session restoration, and it is already implemented. Does this mean you agree with me about the idea of just disabling those buttons and let people shutdown the PC if they want to save energy?
I use Ubuntu for 3 years, and I tested it on 2 laptops and 1 desktop. I have NEVER had problems with hibernating/suspending these computers. What I am doing wrong?
vexorian: suspend is useful. I use it on my laptop all the time (where suspend and hibernate work just fine). It saves more power than being turned on (in suspend, batteries will last about 1.5 days), and is much faster. I can close the lid, pull the power, and by the time I've put the laptop in my bag, it's asleep. Open it up, and 3 seconds later it's woken up. It's incredibly handy. I'll use hibernate if it's going to be a while before I use it next, but 99% of the time it's not on, it's in suspend. Hibernate is too slow to be practical for people doing things like going between classes, moving 2Gb between RAM and disk just isn't a fast operation, and you have to be careful when it's doing that or you risk damaging the disk.
My point is, just because you don't think it useful, doesn't mean others shouldn't use it.
I have read the comments of amitk (Ubuntu Developer) and is right in many respects. However, as said PreviousN is very often to see in (k)Ubuntu things that works in one version and stops to works in the next version as suspend/hibernate in my case.
I think ubuntu should do updates with more care and not in a crazy way.
I'm just a newbie at Linux but i find that if i open a terminal and type this: sudo s2disk that my thinkpad r40 will hibernate. if someone could point me in the right direction to modify hal-system-power-hibernate-linux then this might help to fix the problem.
No I complete disagree vexorian. Suspend/Resume is not about saving power. Maybe it is to some people... who knows.
The point is being able to turn your laptop off and on quickly. NO ONE in everyday life of a laptop thinks "Hey I want to wait 5 minutes between on/off every time to save a teeny bit of power". Thats simply absurd. Someone forgot to add that last line to their resume, or whatever, they need to quickly open/close their laptop to do quick things.
Fact is people will not use Ubuntu if it cant handle a basic task like suspend/resume. I have seen the frustration first hand and I'm willing to bet Ubuntu has lost countless users to this unfortunate messup. Windows provides suspend/resume, so they return to what works.
Yeah well, I doubt those users matter that much, if they leave at the first moment of unfamiliarity they will eventually leave for another reason anyways.
I insist, speed up boot and reboot, imagine if it took 15 seconds to do either of them (which seems possible since right now it is taking 45 seconds) , for the very same reason you have stated you like to use suspend, you would be able to power off the computer that fast. And it will save energy as well.
So, after reading your statement, I would say that if boot/reboot took much less time, you would agree with the idea of removing suspend and hibernate, and that's what I am saying, since , according to the devs it is currently unfixable, the best approach would be to begin working on improving boot/shutdown times to make them a viable alternative to suspend and hibernate.
I have an HP Pavillion dv6558ea. Wish it could Suspend and Hibernate, so thanks for suggesting this. I don't recall any problem with my old Acer and Ubuntu 6.10. Gutsy has been a real pain for me on the HP, actually, but this problem is the one I'm most concerned about right now - now that there's proper sound management coming in 8.04.
With my desktop at work running windows, I suspend it at the end of each day, and each morning it wakes up within a couple of seconds, with applications already running where I left off the day before. even a 10 second boot isn't getting close to that convenience.
If we can get full boot, including gnome desktop, and sessions started plus files loaded for emacs, firefox, and Matlab all within 5 seconds, then I'd say there's no need for suspend.
I agree that hibernate isn't such a big thing to get excited over though.
hibernate still not really working in hardy beta. what's happening here. is this so hard to fix? can somebody explain what's holding back this great operating system from working like 8 year old windows?
Suspend/Resume does not even work out of the box! According to Dell this is Ubuntu's fault... if so, why would they sell a defective laptop in the first place?
This is incredibly embarrassing, one of the fundamental features of laptops, doesn't work with a pre-equipped Ubuntu machine.
The real problem with suspend and hibernate is that its hard to discover whether its going to work on particular hardware or not. Results are often anecdotal and in reports it isn't clear which methods were tried or whether there are other ways of getting it working.
Couple with that the fact that its a moving target, and for me for a given piece of hardware, it has generally gone backwards. My old laptop used to suspend fine all the time a few years ago, but then around dapper or so it stopped. Then my desktop used to suspend reliably, until a kernel update that shipped somewhere in fiesty .. and since then I've never been able to get it to do it.
The problem that Ubuntu can address is getting the right information more readily available, rather than relying on hunting through out-of-date forum posts to find out (a) whether some hardware works, and (b) the right methods to try in order to get it working.
Ok, well should a consumer trust a computer preinstalled with Ubuntu to work properly? Some people seem to think not, if you buy a laptop from Dell for example, and suspend/resume doesnt work, somehow that is the fault of the consumer for not doing research. Come on...
Also, to say that Ubuntu should get rid of suspend/resume and replace it with a quicker reboot, is not solving the problem, but trying to cover it up. The fact is that Suspend/Resume is a fundamental feature of laptops.
I have a Dell Inspiron 1520. Despite all the forum posts I've read, Suspend is still not reliable. It works sometimes, but about 40% of the time my computer freezes and I have to force-shutdown, which is not-so-good for my HD.
this guy nails the problem. this whole suspend/hibernate issue needs fixing, I agree with the author in saying that it is mindboggling why this still doesn't work right, it just can't be.
That was a ridiculous article. Have you read any of the responses in this thread or in the comments to that post? The fact remains that if suspend and hibernate are not working on your machine, it is almost always due to proprietary information (from companies like nVidia) being unavailable to Ubuntu developers. If they will not share accurate specifications on their video cards (so devs can create open-source drivers) or provide bug-free proprietary drivers (not likely), there is NOT A WHOLE LOT UBUNTU DEVELOPERS CAN DO, "show-stopper" or not. Got a problem with it? Get a graphics card that has open specifications (like Intel's do) or START GETTING PISSED OFF AT NVIDIA, NOT UBUNTU. As it is, the open-source drivers are trying to reverse-engineer the video card drivers. That's never going to work very well.
It's also very annoying to hear people insist that things work fine on Windows, therefore Windows is doing a better job. That's complete BS. Even if nVidia cards suspend/resume perfectly in Windows (a very debatable point), that says nothing about Windows. Any reason it's working on Windows is because nVidia made their proprietary drivers work right specifically for Windows, but they didn't take the time or effort to do the same for Linux AND they won't make their specifications available so that we can do it ourselves.
This is not just about the proprietary drivers. Even on fully open hardware there are problems that don't need to be there. With even Intel graphics, I've found cases where suspend stops working after updates or upgrades to new versions. These are kernel level and driver problems. A lot of kernel and driver development seems to go on without regard to suspend/hibernate, and it only considered as an afterthought. This could be considered a shortcoming of Ubuntu in trying to use a server-oriented OS in a desktop market.
There are also problems in the packaging and configuration of the available suspend tools. I found my laptop started suspending successfully after installing an additional package. I only knew to look for that package after seeing it mentioned in an obscure reply to a obscure post in an obscure forum somewhere.
Then there's documentation - It's hard to get authoritative current information about the way it's supposed to be done and what alternatives can be tried. Even for people willing to debug different hardware, its hard to find where to start. Doing a search on ubuntu suspend yields a whole lot of older pages with various attempts and anecdotes, many of which are outdated and don't represent the "right" way of doing things now - and also apply only for some unknown types of hardware
Then also yes, it does make sense to compare to Windows. If Windows will suspend and Ubuntu won't then Windows (as an operating system) is doing a better job in that aspect. Sure, it may be harder for Ubuntu to do it due to its development model and popularity, but that doesn't change the facts about which is actually working better for the user.
I voted for this issue a bit too fast, cause right after voting I saw that:
"even with proprietary drivers."
Sorry but this is not the solution. Work is being done upstream with free software (the kernel, HAL,...), why would we want to short-circuit them and despise their work by using proprietary drivers when we could work with them and help them fix this issue only with free software ?
The "proprietary drivers" remark means getting suspend+hibernate to work through open source code, but even when using the Nvidia or ATI proprietary video drivers. It's relevant because the presence of those drivers on a user's system is often taken as an excuse for why suspend shouldn't be expected to work.
So it isn't about short-circuiting the open-source developers. At worst, its making life harder for them by getting them to test against systems with binary video drivers installed. Perhaps there's also some pressure there to get more dialogue going on with the video card companies to get their driver bugs with suspend sorted out.
"The "proprietary drivers" remark means getting suspend+hibernate to work through open source code, but even when using the Nvidia or ATI proprietary video drivers. It's relevant because the presence of those drivers on a user's system is often taken as an excuse for why suspend shouldn't be expected to work."
That makes a lot more sense :)
The only problem with that is that it will be kind of difficult to ask the devs of "suspend / resume" to support those binary drivers.
In fact with FOS drivers, the devs of "suspend / resume" can say "hey, your driver is broken so suspend / resume won't work. You should fix it this way, here is a beginning of a patch. Thanks in advance for fixing it."
With binary drivers, those same devs have the choice between:
1. "We do all the work to try and make those binary work, without even knowing how they work, without knowing if their next release won't break all that we did."
2. "Suspend / resume won't work with those drivers"
Oh, and we all know that it soon won't be a problem as every graphic card vendor will open its specifications and so free drivers will appear (look at Intel, AMD, VIA). :)
just for the record, I don't have an nVidia card but a "regular" intel graphics chip.
it's just that when you claim "for human beings" you can't exclude the human beings who like to use laptop computers ;-) I love Ubuntu, but the popularity of this issue on Brainstorm proves how dissatisfied lots of people are about the state of laptop support in Ubuntu. I just hope all those cool programmers are working on it, while I hoped that they were working on it ever since I first tried it 2 years ago. 2 years is a long time to get something done that WinDumb has done almost since the inception of XP....
I was unlucky to become an nVidia user and suspend/hibernate has always been a HUGE pain-in-the-neck. I has haunted me for many many years. Once, I was thrilled when I struggled getting the suspend-to-disk working by setting NvAGP=1 (on Gusty), but now after upgrading to Hardy, my miserable life came back again: whatever you do, you simply can not get the system back from suspend.
Suspend and Hibernate are the *most* important features for mobile computing, I really hope that Ubuntu team can pay a serious attention to these issues and play a key role to improve the situation, either by collaborating with the manufactures, or developing their own robust ACPI support. Wish these painful experiences with suspend/hibernate go away, forever.
I don't know if this problem still exists, but standby/hibernate used to work on my laptop in gutsy (now using hardy with no problems), but then gutsy started acting up, and would act like it was going into hibernate, but then bring the desktop back up and not do anything.
I hear lots of people complaining power saving and suspend/hibernate worked fine in feisty but now the quality is reduced or it just breaks in gutsy. WTH is up with that?
I hope hardy or at least intrepid ibex fixes this!
There was a change in a kernel memory allocator that exposed a bug in the binary ATI driver - which to my knowledge ATI still haven't fixed. Then around the same era IIRC there was a change to a different Intel driver which seemed less suspend-friendly.
It's hard for Ubuntu to do much about those sort of issues, but where they can help as packagers is to make the most of what code and options are available, and harness the power of their userbase for debugging and dissemination of up-to-date methods for getting it working.
BUMP - because I know this is an issue for many users. On one occasion I had an issue with suspend/hibernate; the mouse locked up and the system froze. I had to re-seat the memory in order to re-boot the computer, in the process I also had to fix a few errors on the HD that most likely occurred as a result of the hibernate/suspend process.
Btw, how come nobody's claiming to do anything about this issue; it has been at #1 position for weeks now.
I think it's - to put it mildly - shocking, that another, even LTS, release is being finalized without this issue being fixed.... very sad and disappointing. I understand those hardware related issues are hard to fix, but it can't be THAT hard, I suggest a community-funded hardware testing center for linux, also funded by Canonical, Red Hat etc, just buy every laptop model out there and do tests..... would also cut down on the (somtimes) less useful (for the devs) bug reports in that area
As far as I am concerned, it is fixed for me! My computer, which would previously always freeze upon waking up (or just completely fail to sleep) now works with Hardy! It sleeps and wakes up just fine :-). Dell E1505 w/ ATI Radeon Mobility x1400
This underlies the problem. Here we have two pieces of hardware that are basically the same: one works and the other doesn't. It's almost certainly possible to get the Toshiba working as the Dell does, but will require some slight configuration changes. But nowhere is there suitable up-to-date documentation to say what tests should be tried to work out what configuration is needed.
It's in the "too hard" basket, waiting for upstream kernel developers to fix things there. Ubuntu figures that once (if) it's improved there to work out of the box, then they won't need to document how to debug the Ubuntu implementation.
i got a new nvidia card for my workstation (running gutsy) and was surprised how easy it was to make it work with gutsy (i think i had to click, install restricted drivers and that was it)
HOWEVER sometimes when i suspend the machine and i try to wake it up again, the screen remains black. This seems to happen randomly and not very often. These are the problems that need to be fixed under windows it never like this.
Suspend & Hibernate WORK FLAWLESSLY on Fedora 9 (Pre-Release, on IBM/Lenovo Z61m). So, this is definitely fixable. I'm seriously considering going back to Fedora because of this issue.
I am also concerned that this is not marked as "being worked on". Also, those pointing to non-open source drivers and 3D cards, I don't see how that explains hibernate/suspend being jerky on laptops with generic intel graphics. as many have pointed out, this is a feature that just has to work on a laptop, or you can't use it as you would use a laptop. Also, by claiming "linux for human beings" Ubuntu has set a standard for itself that is "slightly" higher than that of other distros, and I can very well say no to fancy Compiz effects if I get a linux I can finally switch to for it. I have waited many Ubuntu releases already, and I still can't dump my XP because of this issue....
I am really concerned about this.
I own an HP tx1215nr laptop and suspend doesn't work at all. I really need it when I am in between classes. It saves a lot of time when you don't really need to fully shut down your computer. For example, in between classes or when you leave school and take a short bus trip home and you know you'll use it again when you get home.
Cheerfully, hibernate does work... sometimes.
I have an Acer Aspire 5100 laptop. No major problems with it using 7.10. Upgraded to 8.04. Now suspend and resume don't work. (neither did the trackpad at first but thankfully that fix was fairly simple). Another vote for this being a very important if not vital area for fixing!
What I dont get, personally, is how there is no problem "booting" up graphics cards. Yet to "resume" a graphics card it is a problem. Why not, instead, "boot" the graphics card on resume?
Put some kind of wrapper around it so that it thinks it is booting. That seems to me like the solution to these proprietary driver problems. Just a thought!
Just saw Amitk's comments from March (above). Unfortunately (s)he seems to have swallowed some ancient FUD. Suspend2/TuxOnice was once intrusive (before the freezer was merged), but here's a diffstat of changes to existing files from today:
Most of that is adding support for freezing fuse filesystems, exporting swsusp functions so we can use them and adding an improved (finer grained) method of freeing memory.
TuxOnIce generally applies cleanly (or at worst with minor rejects) against Ubuntu kernels. Git trees with it already applied to Feisty, Gutsy and Hardy are available from kernel.ubuntu.com.
That said, I agree that I should be seeking to get it merged into vanilla. Unfortunately I don't have a lot of time to work on that now, and it seems that too many people have swallowed FUD to even consider it anyway.
This is what worked for me. I am usinga Toshiba Portege M200 with an Nvidia GeForce FX 5200 display. For me, Suspend/Hibernate would work, but it would not resume properly. I did some research on the Internet and I figured out that I needed to edit /etc/acpi-support in gedit. So I went into Terminal and entered in "sudo gedit /etc/apci-support". Ubuntu opened up a gedit window with acpi-support in it. I then changed the type of suspend to the other type (not the default.) I tried suspend again and voila! It worked! If somebody knows a fix for hibernation, please post it.
here's a clarification. In /etc/default/acpi-support, I changed ACPI_SLEEP_MODE to standby instead of the default (i think it was mem). I restarted the laptop and voila! Standby now works like a charm!
Personally I agree with those who say we should just scrap suspend and speed the hell up out of boot and reboot. If someone wonders why there isn't a suspend, we'll be able to tell them turning the computer off or hibernating (hibernating will still be there in order to keep a session)is just as fast as suspending on another OS, then it will be even better because guess what it does:
1) It reduces complication to the user, which increases work efficiency and makes computing a pleasure for the user
2) It saves EVEN MORE power because now ABSOLUTELY NO power is used when the computer is off. Sure, it takes power to turn on the computer, but first we can make boot up extremely fast and also make it power-efficient or even have an energy-saver boot up style in the power options that should be coming in a future release of Ubuntu.
To reiterate, scrap suspend, speed up boot and shutdown, and make hibernate really good.
One of my desktops suspends ok with Ubuntu (athlon XP with ATI 9200se video), and the power draw is:
On: 68W
S3 Suspend: 3.3W
Off: 3.1W
So the power needed for S3 suspend is negligable compared to the power supply leakage current. For modern computers, the only way to get absolutely no power draw is to pull the power plug out, and most people don't do that.
I don't see how having to re-start applications and find context again increases work efficiency and makes computing a pleasure for the user.
S3 Suspend is just expected to be available these days, and is strongly demanded. Having it working poorly in Ubuntu is an embarrassment, and the lack of debugging documentation is a shame.
Cutting corners has never been a way to become a leader of the distro.
Suspend and hibernate MUST ABSOLUTELY work. On my system it does not since one year and an half !!!
It does not matter who's fault it is. I used to have MS W and it worked, now with Ubuntu it does NOT work.
The final word is the quality of the service rendered to the users.
Ubuntu (and other Linux distro) is failing miserably on that topic, and as an old software GM, my answer is always the same, the developers (we) are not good enough, sorry guys...
But this poor performance is costing us 2 Nuclear Reactors of 1.000 MWatt/h each per year....On the other hand, I thrown away my Win and I am ecstatic about Ubuntu in general.
This isn't an idea it is a problem. I would like to see ideas linked to this problem and vote on those as is described in http://brainstorm.ubuntu.com/idea/9907/
Suspend is still useful for laptops, is faster if they just close the lid and it suspends, a few mins later the user open it again and in second everything is how it was left.
I recently switched back to an old Dell Inspiron 5100, temporarily.
Admittedly it's old, but it's really common, suspend/hibernate should work for it. I reverted to the 7.10 kernel, which has both suspend and hibernate support for it.
Even my 2 year old custom built system that has always worked with suspend (never tried hibernate on it) Does not work with 8.04 now. I guess I'll have to try reverting it's kernel as well.
But this sad... why exactly is the ability of Ubuntu to suspend/resume getting WORSE instead of better?
Neither one works with with or without using proprietary drivers.
this is one of the reasons why I think Brainstorm is to a large part busy-therapy for complaining whiners like us users. We spend hours voting for cool ideas, lament the bugs that prevent it from really being "for human beings", but at the end of the day, no matter how many votes this gets, it is not the metaphorical bullet to the programmer's head. But I agree with most of what's been said above, this "idea" should really be marked as "in development", and since it isn't, I have a BAD feeling about Intrepid
Post ideas on how to fix this Suspend and Hibernate problem and I will be glad to vote for them.
This "idea" (problem) should be marked as "not an idea" before everyone starts posting their pet peeves and not including ideas to solve their pet peeves.
We are looking for ideas to solve the Suspend and Hibernate problems. Does anyone have any ideas on how to solve that?
Here's few:
1. Provide an experimental kernel with the debugging features enabled and the latest suspend and hibernate patches to make it easier for mass testing.
2. Patch Apport to mark the bug reports that a certain application crashed after a suspend or hibernate.
3. Create a wiki that list known working and non working suspend and hibernate hardware.
4. If we need hardware specs, petition the manufacturer.
5. If the bugs have been identified and no one is working on them, create a bounty.
These are just at the top of my head and that is what we should be voting on as well.
yes flammon, I agree that it is not an "idea", but I am not a programmer, so I certainly don't have a "real" idea on how to fix it, other than saying the big idea is to fix this somehow, if you consider the amount of votes this almost "non idea" gets, it should be telling how urgent and important this "issue" is to users/people.... let's call them Human Beings, after all that's what Ubuntu claims to be, and the sort of human being I know, wants to hibernate, or at least suspend his or her laptop without suspecting alien activity going on while witnessing all the weird stuff that's visible on the screen while trying....
I'd go as far and say every other issue/feature out there for intrepid isn't even half as important as this one..... maybe the Ubuntu makers, and I applaud them because I really like Ubuntu a lot and so much is happening, really, aside from my ranting, Ubuntu is really great, but maybe the Ubuntu makers don't suspend/hibernate enough to see how broken this is on many laptops? just an assumption. or people involved in making Ubuntu pick an Ubuntu-compatible laptop in the first place?
Yes fixing Suspend and Hibernate is critical.
In my PC, Suspend is OK, though a little slow but acceptable but works most of the time but Hibernate does NOT work half the time.
Fixing Suspend and Hibernate should be of topmost priority.
Wouldn't it be possible to blackmail Nvidia, in order to get them release an open source driver?
"If you won't release an open source driver Ubuntu won't support display green colors with a nvidia card detected, when Ubuntu reached 20 % market share."
These things don't work for me either, on either laptop I have at home (one P3 and one P-m based, both Ati graphics). This isn't a showstopper for me but it does suck, and I can completely understand it is a showstopper for others. I fully understand how Canonical cannot just fix this as there are too many external dependencies: the kernel devs and Ati/AMD and Nvidia. However, this IS your operating system which does present this reasonably serious flaw so I hope you'll try your best to put a little pressure where necessary to have this fixed. It's not your fault but it doesn't make Ubuntu look very good and that isn't beneficial to anyone (well, except for Microsoft maybe).
I would disagree with Auzy that Nvidia don't need us. 6 months ago I had a choice between Acer laptop with Nvidia and Fujitsu-Siemens with Intel. Finally I bought the second one and now have Suspend function working! I do not really need Nvidia...
Well, Gutnov, if an integrated chipset like intel was good enough for you anyway, you would have gone for it probably more because of price (they are horribly slow). But. what you need to understand Gutnov, is that Nvidia changed everything for us. They didn't have to offer any linux drivers from the beginning (lets face it, we would have come up with our own, and at the time, linux has no penetration whatsoever).
Except, the drivers at the time we produced wouldn't have been as good... Not nearly as good. And their drivers showed many users they were serious about linux. And in turn, those drivers were used to prove to users, that Linux was good, which spurred a whole new segment of development.
If the nvidia drivers are causing problems, it may be a result of too much competition actually. Both ATI and Nvidia have to sacrifice some stability in the drivers department for much better optimisation of drivers (like doing dodgy clipping in benchmarks or lowering graphics quality). The best thing we could do is improve the bug reporting systems, so that we can report back exact systems that don't suspend/hibernate properly, so we can isolate which hardware configurations have issues so they can fix it (this would be the case normally anyway!)
Like it or not, consistent driver support from Nvidia is a beating pulse in our Linux timeline, and we should respect the effort they put in. Whilst something we coded might be a bit more stable, they probably wouldn't have been near as fast as Nvidia's official drivers.
But anyway, due to the changing environment (AMD swallowed ATI), this might change soon anyway. After all, Nvidia's purchase of 3DFX, probably contributed significantly towards their fight with ATI for so long.
+1 I've never had any luck with any kind power saving on any os.
@ rorymccann, purpleidea, gcc and others
So "free software" should not allow me to choose proprietary drivers over open source and have them work? Doesn't sound so "free" to me. I reserve the right to choose which ever drivers I want to use, not you or anyone else. This is freedom of choice.
Anyway that's not what this is about. Its about the problems lots of people are having with suspend and hibernate irrespective of what being used to drive it.
The Ubuntu developers can't do much about proprietary drivers which are the responsibility of the driver developer, but they can assist where possible.
I'm not sure this is a Linux problem. I've never had hibernate or suspend work, in any computer, not even with the original OS (usually a flavor of Windows). I've long since just given up on these "features", assumed they weren't available, and managed to get by without them.
Sure, it would be nice to have them, but... if Ubuntu manages to make them work, they've boldly gone where no (wo)man has gone before... +1
Just to offer a counterpoint to those that say they haven't seen suspend / hibernate work properly...
I routinely see suspend and hibernate work properly around here, on various flavors of Windoze and Linux.
In fact, the only os I cannot get hibernate to work right is on Hardy using a Dell Latitude D610. I seem to be in good company, as there is no shortage of hibernate threads for Hardy. Actually, it appears to hibernate correctly, it just cannot resume from the image and merely reboots.
Strangely, standby/resume works fine on my laptop (Dell Latitude D420) but not at all on my desktop (Dell Dimension 8400). I've tried a few of the configuration file tricks as recommended by the forums, but no dice on the desktop -- get the blank screen every time I try to resume.
Getting it to work reliably would be fantastic. Booting takes to long, and leaving it on is just not an environmentally friendly solution when these computers have these nice low power standby modes which work fine with Windows.
I'm fairly new to open source but love the idea and the feeling I've gotten for the Ubuntu project is a good one, but I've had a few hardware problems besides this, though this one is driving me crazy! I'm an IT student at Uni and I can't even get this fixed on my Desk top, yet alone laptop. My desk top is 64 bit AMD based MSI motherboard with NVIDIA PCIe graphics card. All that seems to happen when I suspend is an improper shutdown, and I have to restart as if I've just had a power cut! I do love Ubuntu, but I hope this is sorted soon (especially considering I just had to dump my xfi soundblaster extreme audio PCIe card for a more lowly model so as to have a working duel boot system - dedication, hey?)! I also so think it would be in Ubuntus interests to have a listing dedicated to informing users about confirmed hardware compatibility.
We should actually get a Safe Suspend mode too (which keeps everything in ram still, but also backs it up to the HDD, so if the power runs out, it takes longer to restart, but at least then you never lose any data).
Hi, its probably not the best place to post this, but i just wanted to say that i retryed the suspend fonction today just for the sake of it since it was like 3-4 months since i last tryed it and at my biggest surprised it worked perfectly. :D
this is on a new pc wich as a asus m2n-e motherboard and a asus nvidia 8600gt vid card using the proprietary drivers.
i am very surprised at that successfull result and even more that i did not even need to do anything to be able to achieve it.
Wow good job devellopers this is another step closer to the absolute perfect OS for me.
I used to have this problem consistently with Feisty and Gutsy, intermittently with Hardy, but I tested Intrepid and it was perfect. I am on an older, less popular laptop (Dell Precision M20) but this is a godsend. Personally, I think it was the open sourced from proprietary ATI Drivers. That's what I was told was stopping Suspend and now it works and they're OpenSource.
So I thought... what the hell, suspend would be nice, lets give it another go!
My setup is Hardy 8.04.1 with updates and backports and proposed and several PPAs and envy-ng with nvidia drivers: 173.14.12
Abit NF7-S mobo (NForce 2 Ultra)
Geforce 5900XT AGP
Never suspended correctly before in Windows XP
So I set the option in xorg.conf in Section "Device"
Option "NvAGP" "1"
And I changed the 2 options in /etc/default/acpi-support
SAVE_VBE_STATE=false
POST_VIDEO=false
AND guess what!! it F@#$#@king works for the first time ever!!! I'm so happy I could cry!!
Previously it would sleep ok.. then it would just beep continously with a blank screen until reset when you tried to wake up.
Any disadvantage to NvAGP "1" I should know?
If not, this should seriously be the default!
Option "NvAGP" "1"
was trying to load the NvAGP part of the nvidia driver, and failing, falling back to PCI mode, which made it equivalent to Option "NvAGP" "0" which I'm using now... it's a bit slower then actually having AGP support, but suspend is better then no suspend, I save so much time booting it's worth it... especially since the nvidia driver is so slow in 2D acceleration anyway.
On my Dell XPS M1330 Suspend and hibernate work great in Intrepid. Thanks to everyone involved! Hibernate is slower than a regular reboot though. Hehe. Just the way I like it. ;-D
i voted for this idea a few months ago (hardy). now i switched to intrepid ibex and hibernate works out of the box - i love it and want to thank you very much for your work on this issue!
It's funny, my friends seem to have this problem, but I don't (I don't really use ubuntu on my system) nor do I really see this on any of the ubuntu/kubuntu systems I've set up for people.
I love Ubuntu and have installed it on at least eight different computers, from netbook to desktop to mini-server, from brand new to slightly dated to really old, mostly without any serious hardware problems. BUT not on a single one of these machines does suspend/hibernate really work, i.e., work consistently and reliably each and every time.
Some of my machines won't suspend at all, some will just freeze when trying to wake up, and the remainder will lose at least some essential functionality after waking up, like Bluetooth, the touchpad, the keyboard, display backlight, or two or more of these in varying combinations.
Please do something about this and make suspend/hibernate one more area where Ubuntu is far superior to Windows!
Linus and the guys just dived into this long standing problem, and fixed it.
i'm kind of confused, if the blog post is really related to this very huge general bug in the suspend/hibernate functionality, isn't that the news of the year for the linux community?
Lets get some actual alternative solutions proposed for this idea so that if anyone listens to it, they have a broad base of places to start, and also to provide resources for -us- in the process of making sure that suspend/hibernate works for us as well.
This issue is the only reason I haven't switched from MS. I might look into another version of Linux that can go into hibernate/standby, but I'd really like to keep Ubuntu!
Fixing suspend is not just for laptops. Broken suspend on Linux wastes power and costs users.
Unfortunately it's broken in many ways- permissions, drivers, poorly written acpi, etc. It works fine for example on my laptop running Xubuntu, by my desktop will just return me to the GDM login screen. Why? I have no idea.
We need better tools to understand why suspend does not work, and how to fix it.
cender's idea , posted earlier here, fixed the problem on my IBM t42. I am reposting it word by word(thanks man)
I don't know "why" this works, but it does for my Thinkpad X60s. I suspect its something that will work for others, since its a bios level thing, and that relates to the previous post.
1. sudo gedit /boot/grub/menu.lst
2. find the grub menu line that is the ubuntu default .. the first one that appears, that will look like this:
title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel ....... etc
3. Add the following to the end of the "kernel" line:
acpi_sleep s3_bios
Here is my "kernel" line.
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=b6e33b4a-d2ec-4107-9aaa-8956ed669d82 ro quiet splash acpi_sleep s3_bios