Suspend/Hibernate Toshiba M-45-S169

After all the technical help you've received, this noob comment may be less than useless. But...

I've run Mepis 6.0 on a Dell laptop and never set it up to hibernate. For snappier perfomance, though, I installed the Xfce window manager, which has a hibernate option on the log-out screen. The hibernate worked fine, except (as we know) when waking up. Opening the lid gave me a brief splash screen and then darkness. But contr+alt+backspace brought the session back quickly.

Now I'm not sure that restoring the session this way is the same as your having to restart. Maybe others can clarify the difference, if any. But if hibernate is important to you, and if a window manager would make your laptop peppier, you might consider Xfce. Or at least find out more about it before installing through synaptic.

Just a thought...

I read a couple of pieces about the Xfce Windows M-. Can someone else comment about it, highlighting the contrasts between it and KDE. Also, would it provide a fix for my suspend issue or would I still left to configure the system, that is, left where I am now. Thanks.

Others can supply more technical information. The gist is that when you boot into Xfce, a minimal set of KDE applications is loaded for use--but the rest of the KDE menu is available. The only difference in terms of applications (that I noticed) is that Thunar becomes the default file manager unless you activate Konq. Otherwise, there's no "difference" between Xfce and KDE--Xfce is only a way of "managing" KDE more efficiently (by preventing all of KDE from loading when you boot). You can tell Xfce to launch only the applications you want to have running--thus peppier performance.

There was no configuration involved getting "suspend" to work. There may, however, be a way to make it automatically wake up when you open the laptop lid. I didn't bother to find out since cont+alt+backspace was a tolerable fix.

I continue to wrestle with the suspend/hibernate feature. I noticed I did not have ACPI package installed. I installed it this morning, thinking it would fix my woes. I mades some of the changes to the etc/default/apt...file as recommended by one of the posts. Still, however, when I resume from the suspend to disk, I have a small blank square (about 1" x 2") at the bottom, right of the screen, right above the system monitor and I do not have sound. However, now, my mouse and everything works. The computer does not lock up. When I try and restart, however, the machine moves slow, taking 3-4 minutes to shut down X and then it locks up on a black screen with my mouse cursor in the middle. I hit ctrl, alt, and b-space which seems to push me over the hump.

I know by now the forum is more than tired of hearing about all my woes, especially this one. But I feel like I'm closer now to solving the problem.

I know some have wondered about the ATP driver issue, that is, if I have same symptons and I do, regardless of what driver I have installed (i.e., FGLRX or default raedon). I cannot think of any other symptons. I hope this will be enough to trigger a solution in someone's mind.
Thanks.

I had issues with suspend to ram on a toshi. I found out though that installing MEPIS onto a reiserFS partition instead of ext3 DID allow me to suspend to ram (to disk already worked).

If you have free space,you can try installing to a new partition and format it as reiser. Or you can just suspend to disk instead of suspend to ram. It is safer and does not use power....

Newbie or not Newbie, there's always a question

Hi Carlops,

I'd love to suspend to disk so I could just shut my lid and pick up where I left off when I get back to working. The problem, however, as I have mentioned, is something goes haywire. If it worked for you, surely it will work for me, right? Maybe I just need to hold my tongue just right. What file do I not have configured right?

What happens when you select suspend to disk by right clicking the battery symbol in the taskbar??

Newbie or not Newbie, there's always a question

That is how I suspend it. I right click, select susp-disk. It begins to to copy pages to the hda6 and then shuts down. Without closing my lid, I turn the machine back on. It goes through Grub and then to Mepis. I see a black screen for several seconds. Then, I see text in the upper left portion of the screen. It reloads the system. My screen blinks a time or two with frazzled graphic appearance then goes black with the unlock box appearing in the center. I password myself in and there is the rectangle box. Everything appears fine, as is like I left it. However, now I do not have sound. When I restart, it freezes and yada, yada, yada.

Try adding 'acpi_irq_balance' to the boot line (edit /boot/grub/menu.lst as root and add to the line that starts with 'kernel´):

Newbie or not Newbie, there's always a question

I already added it. Here is the file:

title MEPIS at hda7, kernel 2.6.15-26-386
root (hd0,6)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/hda7 nomce quiet vga=791 resume=/dev/hda6 acpi_irq_balance
boot

there must be some interrupts messed up when you resume.... This is going to be difficult. Do you not have room for a fresh install on a reiser partition?? 4 Gb would be enough....

Newbie or not Newbie, there's always a question

What will that look like? Right now I have:

hda1 NTFS
hda2 Extended
- hda5 FAT 32
- hda 6 EXT3
- hda 7 SWAP

Too, can you highlight the differences between the two file types? Is one better than the other?

When you fire up qtparted, does it not show anything as 'Free'? From this list I could not tell. A posibility would be to fire up the live CD and shrink the ext3 partition (hda6). Then use the free space to install MEPIS in reiser. You can use the existing swap partition for the new install

Newbie or not Newbie, there's always a question

MajorCedar, there is a package called convertfs that can be loaded from the repositories. It is able to convert a partition from one file system to another. I have used it to convert to/from reiserfs in the past but it is extremely dangerous. Even with its utility, it is still very easy to completely destroy valuable information. So I only recommend it if it's also possible for you to copy data to a safe place. Do you have a spare hard drive that you can use as a test?

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless

I too have a toshiba laptop that doesn't want to play ball with hibernate, but I do not have any concerns for my system as I'll be using the original 60Gb hard drive with a fresh install of SM6.04 Beta1. I have been considering changing my root partition to reiserfs for its speed, so this exercise will have a dual purpose if it is successful, when I will backup my root partition, format it to reiserfs, and copy back the data with an altered fstab file, which is all I think I will need for the change.

Hope to post back before the new year, which is exactly 10 hours away for me here in NZ.

Minor Edit - Mine is a Toshiba M30 ORE002 and to date, I have never had a successful suspend, mostly because I have not had the time to do it with this being a working machine.

9h15 minutes to go - First hurdle I have encountered is a resume partition is not set up.

Mike P

--------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis

Local time is 10.55pm, 31st Dec 2006, 1hr10mins to the new year and I can confirm the suspend to disk requires nothing other than the reiserfs and a kernel parameter command on the grub bootline

title MEPIS at sda1, newest kernel
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda4 nomce quiet vga=791 acpi_irq_balance
boot

I tested on a different hard disk, then went the whole hog and overwrote my stable SM6.01 system and tried it again, once I had applied all the tweaks and changes, additional packages etc.

Suspend to disk works flawlessly using the right click from the kpowersave tray icon. I have my intel pro Wireless pinned to ath0 by its mac address using a udev rule in /etc/udev/rules.d/010_netinterfaces.rules

KERNEL=="eth*", SYSFS{address}=="xx:xx:xx:xx:xx:xx", NAME="ath0"

That's all I had to do. So far, my sound works, display is clean and clear, (using latest nvidia driver through synaptic) and my network interfaces do not switch back and forwards.

Overall, I'm quite happy with the outcome, though I have not fully tested suspend to ram.

Mike P

--------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis

Well done Mike. Seems that reiser is indeed a better choice for laptops so far. I accidentally installed on ext2 once, and suspend worked OK, but the file system would get corrupted if I so much as sneezed at it.

You can get suspend to disk working by closing the lid by editing /etc/powersave/events and changing EVENT_BUTTON_LID_CLOSED="screen_saver" to
EVENT_BUTTON_LID_CLOSED="suspend_to_disk"

So far there is one thing I have not found out yet. I would like to force an unmount of all SMB shares. Suspending with an SMB share mounted works OK, but the share cannot be accessed afterwards. If you feel like spending the 1st day of the year on this...

Oh, and of course: HAPPY NEW YEAR!!!

Newbie or not Newbie, there's always a question

Gosh, I hate to have to whack my machine and start over. If I must, however, I'll just wait to the 6.04 is released in a stable version. Let me ask this. I went to Toshiba's page to look and see if there was an update for my Bios and discovered there is. The update is as follows:
Title: ACPI Flash BIOS version 1.50 for Satellite M40/M45 (PSM43x)
Version: 1.50
Size: 2,728,448 bytes
Posted: 08/24/05
Released Date: 08/23/05
Operating System: BIOS
Description:

Change History

Version 1.50 08-23-2005
o A change was made to correct an issue where the screen backlight would stay off when the lid switch was pressed and released quickly.
o A change was made to correct an issue where the Shift key would respond like the Enter key.
o Updated the Brightness Table for the LTN154X3-L06-G.

Do you think this might be the reason I'm having difficulty getting the suspend to disk to work? Should I upgrade - or flash? I'm nervous about doing it I suppose, a bit reluctant, not wanting to add an expensive paper weight to my collection.

Also, when you download the ACPI package, do you have to configure any files or does it automatically configure during the install.

While I'm having a difficult time with this, I really like Mepis. Commenting to my wife just yesterday, I said I liked going to the Synaptic store to get lots of free goodies to try out. Too, there's wonderful tech support that not only helps resolve problems, but, because you have to wait for answers, teaches patience, a virtue I need to learn and practice.

I tried installing the reiserfs yesterday. I think I messed up and did not install the GRUB loader. I circumvented the problem by editing my menu.list in my working Mepis (I hope that was alright to do!). When it loaded, I went to suspend to disk. It said something about the kernel in the menu.list not matching but said I could by pass it if I changed something in my powersave file. I did. It suspended to disk. When it restarted, I had the same issues as before. Maybe my install was faulty, but I whacked it, deciding that was not the fix.

I'm a pastor so as I sit in my study preparing for Sunday worship, I am reminded of the importance of community - assistance, support, accountability, etc. So I say thanks to all those who've helped me and others out along the way. Blessings and Happy New Year (which actually began with Advent!).

for the hint on the lid button. I do use it sometimes while I'm at work and I have to pack up and do an emergency callout.

For MajorCedar, yes, I would flash the bios. The fixes are no doubt for power management issues and your problem is directly related to power management.

Bios updates will only damage a system if you flash yours with the wrong bios, but provided you have double and triple checked that you have the right one, and you have the peace "that surpasses all understanding" about it, go ahead. If you want to have a fall-back, see if you can download a copy of the original bios along with the update.

Mike P

--------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis

I was wrong, my machine does not have a bios update. Hmm, it seems as if I am back to square-one with my suspend problem. As I continue to mess around and learn the system, I notice that I should be able to adjust the screen brightness during 'powersave' mode. I tried to and it said my system did not support this feature. I bet I just do not have my machine configured right. Any takers???

this depends on the bios and acpi hooks. I can dim the screen with the hotkeys, but kpowersave does not recognize it either (Toshiba satellite A110).

Have you tried installation to reiser FS yet??

edit:
nevermind, I read your post later....

It really is frustrating that we cannot get this to work....

could you please post the file /etc/powersave/sleep again?

Newbie or not Newbie, there's always a question

Yes, indeed, it is frustrating. I'm encouraged however. Thanks for the help! (By the way, the ip commands worked great.) Each time I have to go back to windows, I find it slowly, not as snappy, or efficient. I'm becoming quite the advocate of Mepis. If only I can get my sleep/suspend to work. It's become a kind of eschatological hope, well, not really, but I am desirous of it. Enough babbling, thanks for helping, I sure appreciate it. Here is the contents of the file. Too, let me add that I downloaded the acpi pack in synaptics. I've not done anything with it at this point due to ignorance. Thanks again!

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Description: Configuration of all three sleep modes (S2 is not supported):\n \
## S1 sleep (only ACPI) low wake-up latency, \n \
## S3 (ACPI) suspend to ram or (on APM systems) standby and \n \
## S4 (ACPI) suspend to disk or (on APM systems) suspend. \n \
## \n \
## For some hardware, modules have to be unloaded before entering the \
## sleep state. You can configure these in this section. These modules \
## will be unloaded in the specified order. Modules which depend on one \
## of the specified modules, will also be unloaded. If not all modules \
## can be unloaded, entering the sleep state will fail. \n \
## After resuming, the modules that have been unloaded will be reloaded \
## in reverse order. \n \
## The same applies for the "SERVICES_TO_RESTART"-variables which define \
## services which have to be stopped before entering a sleep state.

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2RAM=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_STANDBY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: "slmodemd irda upsd apcupsd"
#
# All services that have to be stopped before entering a sleep mode
# and restarted after the machine resumes.
# If you notice problems of some services that may be related to
# suspend/standby, restarting the service may solve the problem.
# The names to enter here are simply the filenames of the init scripts
# in /etc/init.d. The services are stopped in the order entered here.
# They are restarted after resume in the reverse order.
# Entering "NONE" disables restarting of services ("" means default).
SUSPEND2DISK_RESTART_SERVICES=""
SUSPEND2RAM_RESTART_SERVICES=""
STANDBY_RESTART_SERVICES=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "yes"
#
# Should FAT and NTFS filesystems be unmounted before entering
# a sleep mode and remounted after the machine resumed?
# You should do this for suspend to disk if you want to boot
# Windows while Linux is suspended to avoid severe data corruption
# on the Windows filesystems.
# Note that suspend will fail if the partitions cannot be unmounted.
# This may cause problems with external storage media connected during
# suspend.
# Defaults to yes for suspend to disk, no for suspend to RAM / standby.
SUSPEND2DISK_UNMOUNT_FATFS=""
SUSPEND2RAM_UNMOUNT_FATFS=""
STANDBY_UNMOUNT_FATFS=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should PCMCIA cards (CardBus and PC-Card) be ejected before entering
# a sleep mode and reinserted after the machine resumed?
# This should not be necessary for most CardBus cards, PC-Cards seem to
# need this more often.
SUSPEND2DISK_EJECT_PCMCIA=""
SUSPEND2RAM_EJECT_PCMCIA=""
STANDBY_EJECT_PCMCIA=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# Set this variable to yes to disable suspend to disk.
DISABLE_USER_SUSPEND2DISK=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# Set this variable to no to enable suspend to RAM.
# If the /usr/sbin/s2ram binary is available, it will be used to detect
# if the machine is capable of suspend to RAM. You can override this
# detection with SUSPEND2RAM_FORCE below.
DISABLE_USER_SUSPEND2RAM=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# If /usr/sbin/s2ram is installed but does not know about your machine,
# you can force suspend to RAM for unknown machines by setting this
# variable to yes.
# Be careful, this might crash your machine.
# See also the SUSPEND2RAM_ACPI_SLEEP, SUSPEND2RAM_VBE_POST and
# SUSPEND2RAM_VBE_SAVE variables.
SUSPEND2RAM_FORCE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer(0:3)
## Default: "0"
## ServiceRestart: powersaved
#
# If SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can set
# the acpi_sleep parameter here. This is a number, 1 means "s3_bios",
# 2 means "s3_mode" 3 means "s3bios,s3mode".
# These parameters are explained in the kernel sources under
# Documentation/power/video.txt
# Leaving this empty or setting it to 0 means "don't touch this setting",
# you might still have one of the options set from the kernel commandline.
# Be careful, this might crash your machine.
SUSPEND2RAM_ACPI_SLEEP=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable
# the equivalent of "vbetool vbestate save/restore" before/after suspend to
# RAM with this variable. This does restore the state of the graphics chip
# on many machines.
# Be careful, this might crash your machine.
SUSPEND2RAM_VBE_SAVE="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable
# the equivalent of "vbetool post" after suspend to RAM. This reinitializes
# the graphics chip on many machines.
# Be careful, this might crash your machine.
SUSPEND2RAM_VBE_POST="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "yes"
## ServiceRestart: powersaved
#
# Set this variable to no to enable standby (also needs BIOS support!)
DISABLE_USER_STANDBY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer(0:1000)
## Default: 0
#
# Specify the time in seconds a sleep state should be delayed. This can
# be used to delay a power-button-induced suspend for some seconds to
# be able to power off the machine hard.
#
SUSPEND2DISK_DELAY=""
SUSPEND2RAM_DELAY=""
STANDBY_DELAY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string(platform,firmware,shutdown,reboot)
## Default: "platform"
#
# Specify the shutdown method the kernel uses after suspend-to-disk.
# "shutdown" is known to work on most machines, "platform" may work,
# too. "firmware" will most likely not work, "reboot" is for
# debugging only. Use only if you know what this is for.
#
SUSPEND2DISK_SHUTDOWN_MODE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should the system clock be reset from the hardware clock after
# suspend-to-disk or suspend-to-RAM? This may be unneccessary depending
# on kernel version and SUSPEND2DISK_SHUTDOWN_MODE, but will not hurt.
SUSPEND2DISK_RESTORE_CLOCK="yes"
SUSPEND2RAM_RESTORE_CLOCK="yes"
STANDBY_RESTORE_CLOCK="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should we suspend to disk even if it seems the kernel in /boot
# is not matching the running kernel? This is very dangerous, if
# the kernels don't match, resume will not work. Use only if you
# absolutely need to (e.g. you are compiling a custom kernel).
#
SUSPEND2DISK_IGNORE_KERNEL_MISMATCH=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should we switch to a text console _in userspace_ before entering
# a sleep mode? The kernel usually does this anyway, but if you need
# to run some initialization code before switching back to X, this
# might be handy. Also on ppc, the kernel does not switch, so this needs
# to be "yes" there.
SUSPEND2DISK_SWITCH_VT="yes"
SUSPEND2RAM_SWITCH_VT="yes"
STANDBY_SWITCH_VT="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer
## Default: 500
#
# The size of the image in MB that will be written to disk upon suspend.
# A bigger image will make your system feel more responsive after resume,
# but take additional time for writing and reading your data.
# This value specifies the maximum image size to use. The image can be
# smaller if not enough swap is available or memory usage is low, it also
# can be bigger if the size is not enough for suspending the machine.
# setting it to "0" will restore the old behaviour and always create the
# smallest possible image.
SUSPEND2DISK_IMAGE_SIZE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: ""
#
# to make sure that there is enough swap available, you can configure an
# additional swap partition, which will only be used for suspend. This
# partition should not be in /etc/fstab and should not normally be used.
# Its size should be the amount of physical RAM the machine has, or at
# least SUSPEND2DISK_IMAGE_SIZE.
# Enter the device node of this partition here to have it activated before
# suspend and deactivated after resume.
# You also need to make sure that the resume= boot parameter points to
# this partition.
SUSPEND2DISK_RESUME_DEVICE=""

... but you can try either of these:

SUSPEND2RAM_VBE_SAVE="yes" set this to "no"
SUSPEND2RAM_SWITCH_VT="yes" set this to no

Change the 1st and test. If it is no good, revert and change the 2nd.

If none works, a manual test:
after suspending and resuming, go to a console and do
'xset dpms force off'. This will switch off the screen. Move the mouse and see how it comes back

Newbie or not Newbie, there's always a question

Well, I was able to suspend to disk successfully. The changes you suggested, however, did not make this happen. I made them and then tried and the system crashed. I changed them back and was going to try the second and it worked. I did not have the square. I do, however, think I have an idea about the little square. You know when you sign on and the square from your ath0 pops up and says you are connected? That is the size and location of the square. Anyway, today (and for the past couple of days) I have been plugging in to the LAN instead of using the w-less connection. Each time I sign in, I go to the terminal (becasue both the LAN and the w-less are connected pulling IPs) and ifdown the ath0 (which, if there is away to fix this so that if a LAN is present the w-less will take backseat I'd love to know). Maybe this had something to do with it, I've not tried to the suspend-disk while I"m still connected to the w-less yet.

I tried the suspend to RAM (feeling lucky!) and it crashed in a big way. I tried to restart the system after taking the battery out, etc. and there were errors, it said, on the /dev/hd5 (boo!). I ran the fix and it repaired them all.

When I tried to resume from RAM I had no monitor whatsoever. Black, yet the computer seemed to be working for several seconds.

Well, I'm excted that the suspend to disk works. Any ideas about the RAM?

You're making progress!

Suspend to ram is less likely to work correctly. Don't ask me why, but linux can suspend to disk quite well, but due to hardware idiosyncracies suspend to ram seems to be more difficult.

If you do lsmod, you get a list of loaded modules. One of those is for the wireless card. If you can't figure that out: which card do you have? We'll google for it.

Anyway, in the file /etc/sleep there is a section to enumerate the modules to be unloaded before suspend to disk (or suspend to ram, two different entries). Copy the default list in the comment section above to the variable and add the module for your wireless card. If you're lucky, the card will be deactivated upon suspend and activated upon resume, so you won't have to do that manually.

There is BTW a way (or more) to make the wired lan take precedence over the wireless. However, I suggest you create a different post for that.

Newbie or not Newbie, there's always a question

When I add a resume= to the grub command my system completely shuts down automatically unexpectedly after about 1/2 hour, and an intended suspend to disk fails.

I do have root as reierfs and home as ext3 and a standard swap partition. The reiserfs, ext3 mix was a mistake at installation.
Rich

I'm not terribly sure about the problem you mentioned, of course, I'm not one to ask about problems and their fixes in linux. However, I can say I have not had that issue. I have the 'resume=..." line in my menu.list and have not had symptons like the ones you're describing.

Here's a glitch to my solved problem, maybe the one causing me the problems from the beginning. Yesterday, before I left the office, I unplugged my USB mouse. Then I suspended to disk, excited about it working. Later that night, I tried to resume, you know, open the lid and watch the machine work like the machine is supposed to work. However, after it booted, everything looked fine but the mouse (now using the TOUCHPAD) would not work. I restarted; the machine shutdown like it should. I tried it again and had the same issue. Now, I'm back at work. I plugged the USB mouse in and started up. I then suspended to disk and everything worked well. I think the issue is that the TOUCHPAD MOUSE is not reloading when I resuem from suspend. How can I fix this?

try unloading the module psmouse in the /etc/powersave/sleep file.

Newbie or not Newbie, there's always a question

Forgive my ignorance, but I'm not entirely sure I understand what you're telling me to do. What is the module for the psmouse? I searched the sleep file for psmouse and found nothing. I will paste it below. Too, what would "unloading the module" look like? What can I say, I'm a newbie? Thanks!

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Description: Configuration of all three sleep modes (S2 is not supported):\n \
## S1 sleep (only ACPI) low wake-up latency, \n \
## S3 (ACPI) suspend to ram or (on APM systems) standby and \n \
## S4 (ACPI) suspend to disk or (on APM systems) suspend. \n \
## \n \
## For some hardware, modules have to be unloaded before entering the \
## sleep state. You can configure these in this section. These modules \
## will be unloaded in the specified order. Modules which depend on one \
## of the specified modules, will also be unloaded. If not all modules \
## can be unloaded, entering the sleep state will fail. \n \
## After resuming, the modules that have been unloaded will be reloaded \
## in reverse order. \n \
## The same applies for the "SERVICES_TO_RESTART"-variables which define \
## services which have to be stopped before entering a sleep state.

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2RAM=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_STANDBY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: "slmodemd irda upsd apcupsd"
#
# All services that have to be stopped before entering a sleep mode
# and restarted after the machine resumes.
# If you notice problems of some services that may be related to
# suspend/standby, restarting the service may solve the problem.
# The names to enter here are simply the filenames of the init scripts
# in /etc/init.d. The services are stopped in the order entered here.
# They are restarted after resume in the reverse order.
# Entering "NONE" disables restarting of services ("" means default).
SUSPEND2DISK_RESTART_SERVICES=""
SUSPEND2RAM_RESTART_SERVICES=""
STANDBY_RESTART_SERVICES=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "yes"
#
# Should FAT and NTFS filesystems be unmounted before entering
# a sleep mode and remounted after the machine resumed?
# You should do this for suspend to disk if you want to boot
# Windows while Linux is suspended to avoid severe data corruption
# on the Windows filesystems.
# Note that suspend will fail if the partitions cannot be unmounted.
# This may cause problems with external storage media connected during
# suspend.
# Defaults to yes for suspend to disk, no for suspend to RAM / standby.
SUSPEND2DISK_UNMOUNT_FATFS=""
SUSPEND2RAM_UNMOUNT_FATFS=""
STANDBY_UNMOUNT_FATFS=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should PCMCIA cards (CardBus and PC-Card) be ejected before entering
# a sleep mode and reinserted after the machine resumed?
# This should not be necessary for most CardBus cards, PC-Cards seem to
# need this more often.
SUSPEND2DISK_EJECT_PCMCIA=""
SUSPEND2RAM_EJECT_PCMCIA=""
STANDBY_EJECT_PCMCIA=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# Set this variable to yes to disable suspend to disk.
DISABLE_USER_SUSPEND2DISK=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# Set this variable to no to enable suspend to RAM.
# If the /usr/sbin/s2ram binary is available, it will be used to detect
# if the machine is capable of suspend to RAM. You can override this
# detection with SUSPEND2RAM_FORCE below.
DISABLE_USER_SUSPEND2RAM=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# If /usr/sbin/s2ram is installed but does not know about your machine,
# you can force suspend to RAM for unknown machines by setting this
# variable to yes.
# Be careful, this might crash your machine.
# See also the SUSPEND2RAM_ACPI_SLEEP, SUSPEND2RAM_VBE_POST and
# SUSPEND2RAM_VBE_SAVE variables.
SUSPEND2RAM_FORCE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer(0:3)
## Default: "0"
## ServiceRestart: powersaved
#
# If SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can set
# the acpi_sleep parameter here. This is a number, 1 means "s3_bios",
# 2 means "s3_mode" 3 means "s3bios,s3mode".
# These parameters are explained in the kernel sources under
# Documentation/power/video.txt
# Leaving this empty or setting it to 0 means "don't touch this setting",
# you might still have one of the options set from the kernel commandline.
# Be careful, this might crash your machine.
SUSPEND2RAM_ACPI_SLEEP=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable
# the equivalent of "vbetool vbestate save/restore" before/after suspend to
# RAM with this variable. This does restore the state of the graphics chip
# on many machines.
# Be careful, this might crash your machine.
SUSPEND2RAM_VBE_SAVE="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
## ServiceRestart: powersaved
#
# if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable
# the equivalent of "vbetool post" after suspend to RAM. This reinitializes
# the graphics chip on many machines.
# Be careful, this might crash your machine.
SUSPEND2RAM_VBE_POST="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "yes"
## ServiceRestart: powersaved
#
# Set this variable to no to enable standby (also needs BIOS support!)
DISABLE_USER_STANDBY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer(0:1000)
## Default: 0
#
# Specify the time in seconds a sleep state should be delayed. This can
# be used to delay a power-button-induced suspend for some seconds to
# be able to power off the machine hard.
#
SUSPEND2DISK_DELAY=""
SUSPEND2RAM_DELAY=""
STANDBY_DELAY=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string(platform,firmware,shutdown,reboot)
## Default: "platform"
#
# Specify the shutdown method the kernel uses after suspend-to-disk.
# "shutdown" is known to work on most machines, "platform" may work,
# too. "firmware" will most likely not work, "reboot" is for
# debugging only. Use only if you know what this is for.
#
SUSPEND2DISK_SHUTDOWN_MODE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should the system clock be reset from the hardware clock after
# suspend-to-disk or suspend-to-RAM? This may be unneccessary depending
# on kernel version and SUSPEND2DISK_SHUTDOWN_MODE, but will not hurt.
SUSPEND2DISK_RESTORE_CLOCK="yes"
SUSPEND2RAM_RESTORE_CLOCK="yes"
STANDBY_RESTORE_CLOCK="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should we suspend to disk even if it seems the kernel in /boot
# is not matching the running kernel? This is very dangerous, if
# the kernels don't match, resume will not work. Use only if you
# absolutely need to (e.g. you are compiling a custom kernel).
#
SUSPEND2DISK_IGNORE_KERNEL_MISMATCH=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: yesno
## Default: "no"
#
# Should we switch to a text console _in userspace_ before entering
# a sleep mode? The kernel usually does this anyway, but if you need
# to run some initialization code before switching back to X, this
# might be handy. Also on ppc, the kernel does not switch, so this needs
# to be "yes" there.
SUSPEND2DISK_SWITCH_VT="yes"
SUSPEND2RAM_SWITCH_VT="yes"
STANDBY_SWITCH_VT="yes"

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: integer
## Default: 500
#
# The size of the image in MB that will be written to disk upon suspend.
# A bigger image will make your system feel more responsive after resume,
# but take additional time for writing and reading your data.
# This value specifies the maximum image size to use. The image can be
# smaller if not enough swap is available or memory usage is low, it also
# can be bigger if the size is not enough for suspending the machine.
# setting it to "0" will restore the old behaviour and always create the
# smallest possible image.
SUSPEND2DISK_IMAGE_SIZE=""

## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: ""
#
# to make sure that there is enough swap available, you can configure an
# additional swap partition, which will only be used for suspend. This
# partition should not be in /etc/fstab and should not normally be used.
# Its size should be the amount of physical RAM the machine has, or at
# least SUSPEND2DISK_IMAGE_SIZE.
# Enter the device node of this partition here to have it activated before
# suspend and deactivated after resume.
# You also need to make sure that the resume= boot parameter points to
# this partition.
SUSPEND2DISK_RESUME_DEVICE=""

Check out this section:
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK=""

What you need to do is copy the default modules in between the quotation marks and add psmouse. It should therefore look like this:
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper"
## ServiceRestart:
#
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper psmouse"

Newbie or not Newbie, there's always a question