installing kernel bareacpi.i (2.4.26) in Slackware

[chillz]

Hi

I installed Slack recently using two unofficial Slack Current ISO's and specifically selected the bareacpi.i kernel (version 2.4.26). I wanted to see how the ACPI would work on my laptop. The "config" file which came with that kernel shows that ACPI has been enabled. However, upon installation and a check at the kernel configuration in the KDE Control Center, shows ACPI to be disabled. The abscence of a /proc/acpi directory confirmed that fact too.

A subsequent installation choosing the bareacpi.i kernel again and another set of ISO's gave the same result. Can someone please explain what is going on here. Is it that the kernel is just named bareacpi.i but expects a user to recompile it to enable acpi support using the config file supplied???

Any help will be deeply appreciated

Cheers

[JohnT]

From the terminal issue the command..."lsmod" do you see it listed? No? Then run "modprobe acpi". Now run "lsmod". Is it listed? No? Then you'll have to enable it in the kernel, which means recompiling.

[XiaoKJ]

I run acpi even with bare.i -- acpi is not needed...

But compiling yourself a 2.6 kernel with acpi and devfs and all those cool stuff inside is much better an option, and worth it.

[bwkaz]

PLEASE, not devfs!

The devfs maintainer is gone, and nobody's maintaining that codebase anymore. Besides, it has bugs (some fixable, most not). I would guess that it's going to get ripped out of the kernel pretty much as soon as 2.7 development starts...

If you need automatic device node management, udev is what you want to be using for 2.6 kernels. It does everything devfs used to do, except automatically loading modules when a name in /dev is opened (but that's useless anyway, because what you SHOULD be doing is loading all the modules at boot time or when the hardware is hotplugged). Plus, it's implemented entirely in userspace.

If you don't require dynamic devices, just use a static /dev. It's not that big of a deal.