On Tue, 2003-11-11 at 05:53, Mof wrote: > On Tue, 11 Nov 2003 04:59 pm, James Sparenberg wrote: > > On Mon, 2003-11-10 at 22:02, Mof wrote: > > > The "rpm -e -nodeps suspend-scripts" didn't work, so it became obvious > > > that it was a kernel problem, so I thought I'd upgrade to the latest > > > kernel, and see what happens, but as I was doing that I noticed something > > > odd in lilo.conf : > > > > > > append="quiet devfs=mount hdb=ide-scsi acpi=ht resume=/dev/hda5 > > > splash=silent" > > > > > > First off I really don't know what acpi=ht means. > > > What is ht ?? > > > So I changed it to "on" > > > But wait!!!!! Look right next to that and you'll see the "causer of all > > > pain" "resume=/dev/hda5" > > > But /dev/hda5 is my bloody swap partition!!!! > > > After removing the resume=/dev/hda5, it works fine now! > > > > Yep, it was using the same partition of the suspend as it was for > > swap. Whereas suspend to swap does use a swap partition to suspend, it > > doesn't use one that is mounted and when you use swap it really mucks > > with what swsuspend writes there. In other words if you had a second > > swap not in fstab (partitioned in size to about 20% over ram) That isn't > > listed in fstab then suspend to swap should work right for you. > > It's up to you if you want to experiment with this or not but if you > > have the disk you might want to use this. > > Hmmm.... > I reinstalled, this time creating a 768M & a 1G swap partition, I intended to > use the 1G partition as the software suspend partition. > It works great when I run 'pmsuspend2' from the command line. Ie it suspends, > and in a matter of seconds it can come back up. > If I shut the lid though, it still hangs!! > Once again it works if I change the following in lilo.conf : > > "acpi=ht resume=/dev/hda7" > to > "acpi=on" > > So it seems there is still a problem..... > > And yes I did remove /dev/hda7 from /etc/fstab. > > So does anyone have anymore suggestions ? :-) > > Mof.
See what I get for reading the FM *grin* The last one I can't test because my laptop doesn't do ACPI or the lid close feature. and my desktop doesn't have a lid *grin* One question here. Is there anything being written to /var/log/messages when this happens? If there is too much noise to be able to tell you could do a tail -f /var/log/messages > somefilename.txt Then close the lid. and see if it gives you any useful info. James > > > > ______________________________________________________________________ > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
