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.
Distribution: Slackware: in progress, Mandrake 9.2, Libranet, Vector
Posts: 373
Rep:
Which kernel do I need?
At the end of slack installation, it asks which kernel that I would like to install in my system. But none has a description. How do I know which kernel I need?
I have CD RW, high speed internet / lan, usb printers. Which kernel do I need?
you should probably select the default one (bare.i) unless your motherboard uses ACPI, in which case you'd want the acpi-enabled kernel (bareacpi.i)...
Distribution: Slackware: in progress, Mandrake 9.2, Libranet, Vector
Posts: 373
Original Poster
Rep:
Quote:
Originally posted by win32sux acpi is the "modern" interface for power management functions...
if you install bare.i, you'll know if you should have used bareacpi.i if your computer isn't able to turn itself off, for example...
what i mean is that, when using "bare.i", having your computer not able to shut-itself down (it does it's shutdown sequence but the power remains on, forcing you to manually turn the computer off) is a classic symptom of the "you should have used bareacpi.i" syndrome...
=)
of course, if it's shutting-down properly, then the board was happy with "bare.i"...
if it doesn't shut-down properly with "bare.i", make sure the apm daemon (apmd) is running:
ps aux | grep apmd
apmd needs to be running for apm to work, just like acpid needs to be running for acpi to work...
what i mean is that, when using "bare.i", having your computer not able to shut-itself down (it does it's shutdown sequence but the power remains on, forcing you to manually turn the computer off) is a classic symptom of the "you should have used bareacpi.i" syndrome...
I wouldn't go by that, since by default, the APM module for the bare.i kernel is disabled. So the machine isn't going to turn itself off, even if bare.i was the right kernel for your hardware.
You have to edit "/etc/rc.d/rc.modules" then uncomment the line to load the APM module.
by "classic symptom" i didn't mean "determining factor"...
that's why i suggested to check that apmd was running:
Quote:
if it doesn't shut-down properly with "bare.i", make sure the apm daemon (apmd) is running
are you sure the "/sbin/modprobe apm" isn't uncommented by default??? i use acpi mainly, but i've installed a couple slackware boxes with apm and i can't rememeber needing to do that... i might be trippin', though... my memory sucks... lol...
so, nukem... did you get that box running??? how'd the power management work-out for you???
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.