Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Using Linux (Redhat 8.0) on my laptop, hibernation or suspend to disk where the OS writes everything in RAM to disk and then shuts completely off, is an important feature. I've searched the web, this forum, linux-laptop.net and several other resources, and I'm still stumped.
Main questions are:
Does hibernation/suspend2disk require a supend-partition (primary?) or is a hibernation file (like Windoze uses) sufficient?
I've read that it's not possible to hibernate linux if your bootloader (grub in my case) is located in MBR (also my case), and only possible if it's located on /boot. Is this the case, and if, how do I move my bootloader from MBR to /boot?
Assuming the above problems are solved, what exactly do I have to do to make my linux hibernate? Is there a utility available to make all the appropriate arrangement?
As you've probably understood by now, hibernation/suspend2disk is something I really want to make work, and if anyone have any input at all, it'll be greatly appreciated.
Sorry about the bad english (not my native language), and thanks for reading!
Forgot to metion, but suspend and apm works fine, I can suspend the machine manually, automaticly or by closing the lid.
The difference between suspend and suspend to disk is that suspend never shut down the entire machine, i.e keeping information in ram (draws power), while suspend to disk copies everything to disk and shuts down completely.
I am looking to do a "hibernate" feature with linux so i can dump winxp (right now its just so conveninent to be running in 15sec). can i do this with Red Hat 7.3?? If so, how? If not, how can i do it in Red hat 8 .. .which I could download :-)
True, checked it out som time ago. But I got the impression that it wasn't One good solution, but more tweaking and tuning to get it to work. And it isn't clear whether it's necessary to have a hibernation partition or not. That's why I'm still searching
I've read about "swsusp" patches for the Linux kernel, which is "suspend to disk", I think is the same as hibernate (?).
One thread says (I quote):
>>On many laptops, the suspend-to-disk feature is controlled by the BIOS and requires a FAT partition as the first partition on the disk. A DOS utility or its Linux equivalent "phdisk" writes a file ~ the size of the machine's RAM that's composed of contiguous sectors to this partition, then writes the location of the start and end sectors to some secret place in the NVRAM. Then you can trigger the suspend-to-disk feature with a special key sequence regardless of what OS you're running, often Fn-F12.
>>If that doesn't work, the "swsusp" patches for the Linux kernel add similar functions that take slightly longer to complete, but work everywhere.
but being a Linux newbie, I'm pretty intimidated by this. And I'd rather work on my laptop than have to repartition and start over.
It has been a while since this thread was touched, and I never got around to installing Linux because of this issue.
Now that Red Hat Linux 9.0 is out, is there any ACPI support? What about the original issue of suspend-to-disk, where the RAM contents are written to the harddrive so that the machine boots faster by restoring everything?
gig103, to get ACPI in RH 9, one needs to compile it afterwards, there is no generic ACPI support in RH 9.0 (at least to my knowledge). The next RH release will be based on kernel 2.4.21 (I think), which has much better ACPI support (most of the ACPI work done for kernel 2.5 and 2.6 have been inkluded in 2.4.21). Think I got that correct
Anyways, if ACPI is a key issue, and you don't vant to compile the lot on your own, it would be wise to either wait for the next RH release or consider another distro.
just as a reminder, the swsusp patch needs a plain vanilla kernel; it won't work with the RH9 kernel source.
A really brief howto:
1. download a vanilla kernel source from www.kernel.org.
2. su to root.
3. cd /usr/src
4. tar -zxvf kerelxxxxx.gz or tar -jxvf kernelxxxxx.bz2
5. ln -s /usr/src/the_new_kernel /usr/src/linux
6. download the current swsusp patch from http://sourceforge.net/project/showf...group_id=25964.
7. bzip2 -dc < /path_to_the_swsusp_patch | patch -p1
8. make xconfig, enable the software suspend in the general setup section. (plus properly configuring ur kernel, you can find more help from the forum)
9. make dep clean bzImage
10. install the new kernel.
11. download the suspend script from http://sourceforge.net/project/showf...group_id=25964.
12. install the script.
13. append "resume=your swap partion" to ur kernel parameters in grub or lilo.
This is just a very brief summary. For more information, please refer to the swsusp's doc.
1. There might be some risk trying that out.
2. before applying a patch, it's a good idea to run with --dry-run option to see if the patch applied cleanly.