[SOLVED] Suspend to ram ( sleep) does not work on my Slackware64-current multilib
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Suspend to ram ( sleep) does not work on my Slackware64-current multilib
I use slackware-current 64bit multilib updated .
well ...
If I click on kde application launcher from sleep, sleep my pc starts and ends, but soon after it gets October It does not stay sleep! The screen goes black.
Interesting. When I boot up with a USB mouse plugged in, the system does not see it. If I plug in the USB mouse after booting up, it will see that. I wonder if your problem and mine are connected.
Interesting. When I boot up with a USB mouse plugged in, the system does not see it. If I plug in the USB mouse after booting up, it will see that. I wonder if your problem and mine are connected.
In my case it is something related to some of the latest updates, as previously this issue did not happen ...
I marked the topic as solved, but in fact it was actually solved by updating the bios.
thanks
Try to avoid updating your BIOS if you can. On one machine, I have lost the ability to boot ISOLINUX discs, I needed to update the BIOS in this case to support a new CPU, but there was a price to pay.
Try to avoid updating your BIOS if you can. On one machine, I have lost the ability to boot ISOLINUX discs, I needed to update the BIOS in this case to support a new CPU, but there was a price to pay.
Thanks for the warning, indeed serves as a warning that a bad BIOS update done, can prevent the motherboard to start.
Try to avoid updating your BIOS if you can. On one machine, I have lost the ability to boot ISOLINUX discs, I needed to update the BIOS in this case to support a new CPU, but there was a price to pay.
I would like to know who provided that BIOS. I wonder if that will break other boot loaders like EXTLINUX.
I would like to know who provided that BIOS. I wonder if that will break other boot loaders like EXTLINUX.
I hate to say that it was an ASUS motherboard. The damn tech just said that not enough people use Linux to justify a re-write of the offending code.
Here is part of one e-mail
Quote:
Originally Posted by Jack1 He (tsd AT asus.com.tw)
Re:<TSD> Motherboard M3A32-MVP DELUXE/WIFI-AP [ID=RWTM2011070509294825-713]
After updating BIOS, please load default the BIOS setting for a try.
If the issue still remains, please consider to re-install a new clear OS and test again.
As the motherboard does not support Linux formally, if possible, please install a Windows OS for a further check.
Otherwise, please try to downgrade the BIOS, but we could not guarantee that it would be successful. 100%
Last edited by andrewthomas; 10-22-2013 at 06:31 PM.
Reason: added motherboard info
I have been used Asus motherboard since 2008 and no Linux ( Slackware ) problem.
I am not saying ASUS is bad. My last 4 motherboards have been ASUS boards. It was just 1 bad update that I wish that I wouldn't have done. I would have been better off with the new CPU in a different mb. But oh well, live and learn. I have actually bought another ASUS board since this problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.