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.
that doesn't seem to work. I kind of expected it. The tutorials all say there should be something like "mem and some other thing" coming out when you do
(look at the second one on the list about "Write Error.")
As far as I can tell, the regular Slackware kernels do not have "CONFIG_HOTPLUG_CPU" enabled so I recompiled my kernel and enabled that option and then acpi suspend to ram worked fine (with the appropriate acpi event and handler scripts, of course). I emailed Pat about this during the RC testing and he replied and said he would try to put this in the final 12.0 kernels but I have not had a chance to see if it was added.
As far as I can tell, the regular Slackware kernels do not have "CONFIG_HOTPLUG_CPU" enabled so I recompiled my kernel and enabled that option and then acpi suspend to ram worked fine (with the appropriate acpi event and handler scripts, of course). I emailed Pat about this during the RC testing and he replied and said he would try to put this in the final 12.0 kernels but I have not had a chance to see if it was added.
well, I'm using the 2.6 series since 2.6.7 was out, always custom compiled.
Though, it would have been nice to run a official slackware kernel once again...
Edit:
On the other hand, it is a nice excuse to patch it for bootsplash support
Finally it works!
The bootsplash stops people from asking
Quote:
should your laptop do that? I've got the same and that one doesn't do that
I added the CONFIG_HOTPLUG_CPU (aka SUSPEND_SMP) option.
I also compiled in all the acpi modules.
Now I'm using klaptop_acpi_helper to take care of the suspend.
BTW to work in kde, klaptop_acpi_helper needs chmod +s .
The dialog to do that in KDE complains about klaptop_acpi_helper not having the same size and checksum as it had when it was compiled. It also did that under 11.0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.