Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have upgraded from ubuntu 10.4 to 10.10 and the issue seems to be that when I close my lid I have set the computer to suspend. When I open my lid I get a black screen with the login but keyboard is not working. I am using a Toshiba Satellite U400, and didn't manage to find something suspicious at my log files. Any ideas?

share|improve this question

migrated from Feb 7 '11 at 23:01

This question came from our site for system and network administrators.

Not sysadmin related. I voted [belongs-on-SU], but you may want to check out also/instead. – jscott Nov 17 '10 at 11:58
@jscott You are totally right, is it possible someone to migrate it to – topless Jan 27 '11 at 1:11
@Chris it is likely this question will get migrated to SU, as there is no migration path from SF to askubuntu. If you want and answer there, you will need to repost your question. – Sam Jan 27 '11 at 17:26
up vote 3 down vote accepted

I have a Toshiba U-400, and Maco's answer here is similar to Pitto's.

In our case, it's the bluetooth module that prevents the laptop from resuming from suspend. You need to add this line to /etc/default/acpi-support.

MODULES="toshiba_bluetooth bluetooth btusb"

That should get you running again. Despite this change, perhaps 1 in every 25 or so suspends (not resumes) will fail for me. When it fails, it cycles the CPU and fanspeed up pretty high. Do not trust this laptop to suspend correctly. It suspends very quickly, so when you close the lid, keep your eye on it for the 3 or 4 seconds it takes to complete (the amber light under the trackpad should go off).

If it doesn't, you're looking at a fire hazard!

share|improve this answer

As was mentioned this was repaired with a kernel upgrade to >= 2.6.36

share|improve this answer

I have the same problem and yet I couldn't test a solution I've found... As soon as I get back home I'll post back results.

"You can try to put the name of your proprietary module (nvidia or fglrx (for ATI) are most likely) in the quotes in MODULE="" in the /etc/default/acpi-support file and reboot.

sudo nano /etc/default/acpi-support

This'll make that module unload before suspend and reload after suspend. It sometimes works, but it's also possible that you have just plain buggy drivers somewhere and need to file a kernel bug.

EDIT: It's also very possible that you've just plain found a bug. If you think that's the case, please file it: ubuntu-bug linux"

share|improve this answer
it looks like an upgrade of kernel to 2.6.36 from here resolved the suspend issues for me. – topless Nov 17 '10 at 14:30
@Chris Can you make your comment an answer if that fixed the problem? – Jorge Castro Feb 7 '11 at 23:07
Upgrading my kernel might have fixed the issue (I didn't test), but I had so many issues with VirtualBox after upgrading that I went back to stock and with my ACPI-support modification, suspend/resume works okay. – Scaine Feb 8 '11 at 8:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.