Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, if you're using a stock default kernel with your distro, they've probably compiled most of the kernel features as loadable modules. I'd try modprobe acpi or modprobe apm (acpi is apm's more advanced twin, as far as I know, and the two are both probably supported, but can't be enabled simultaneously). You can use rmmod to remove a module from memory if you don't think it's for you.
If loading that module seems to fix your problem, you'll have to check your distribution for instructions on how to make it load by default on bootup. In debian, you add the module name to "/etc/modules".
I tried the rmmod to get rid of acpi, and it didn't work. I did however do some additional searching based on what you had posted. Basically I found that acpi is the culprit, and by removing it apm should work.
I added 'acpi=off' to my /etc/grub.conf file and rebooted. I could now suspend without problem, however a couple of issues have arrisen from this:
1) my notebook makes an odd sound with the acpi off . It's tough to explain, but almost has the sound of an overloaded capacitor for you electronics guys. When I put acpi back on, the sound goes away. (no, this isn't coming from my speakers)
2) when I resume from a suspend, my USB is gone. I'm not sure how to reset it. I found a similar thread at this link, however the explanation given isn't really that clear to a newb like me.
That's really odd. As for #1, if I were you, I'd try searching on google or linuxquestions for your specific model of laptop (in quotes), and linux. Try adding ACPI too. See if anyone else talks about this problem, you might find someone who's already found a solution.
As a general solution, the first thing that comes to mind is make sure you're using the newest kernel you can. I believe ACPI is an area that is pretty heavily worked on right now, so if you're using a relatively old kernel version, that could explain it. Try to get 2.6.x, 2.6.11 is most preferable.
As for #2, what they're saying is that we need to tell linux to, when suspending your computer, unload the module for your USB (that will effectively shutdown USB support), and when resuming from suspend, load that module (that will effectively enable USB properly).
This is probably an area you should go to your specific distribution for, as I don't know of a standard way to do this. Basically you want to:
figure out the module names that covers all your USB support, and figure out how to uninitialize and reinitialize it using rmmod and modprobe. This might be something like :
Once you have this down, figure out where you can tell Fedora to run a script before suspending, and figure out where to tell Fedora to run a script when resuming from suspend, and put your commands to unload and load the modules in those appropriate scripts.
I hope this makes more sense - tell me if that worked, or if it at least makes sense to you!