Hi people!!

I have a problem, my laptop IBM 390E doesn't switch off with Slackware 10.

By the way, is there any way to startx before than logging, I mean logging through KDE?

thanks a lot!!

atreo--

I always have that problem with Slackware. The problem is for some reason or another ACPI support (ACPI controls that sort of thing) isn't compiled into the generic kernel (from the A) package.

To circumvent this problem, I'm afraid you're going to have to recompile the kernel. (or try to find one to install that's compiled with ACPI support). Anyway, compiling it is an interesting adventure and any Linux power-users going to want to learn how to do it, so you may as well learn now.

There are two options...you can go fancy and get a 2.6.X kernel (i think the latest as of my post date is 2.6.19.1 obtained from kernel.org).or you can go not so fancy and stick with the kernel source for the kernel you've already got.

If you did a full slackware install, the source will be in /usr/src/linux (which is actually a symbolic link to /usr/src/linux.2.4.X) [x being whatever version you have]

you go into that directory and type
make mrproper
(which basically runs a script that ensures all necessary files are in their correct states)
then type:
make menuconfig
this will make a menu based program that you go through selecting various things to enable in the kernel. It's somewhat daunting so you may want to frequently push the help button or read through documentation in the /usr/src/linux/Documentation directory.

Plan on messing up a few times and getting kernels that don't quite work with your PC (or forgot to enable certain file system support/framebuffering/ACPI =) /etc).

Part of the planning is ensuring that you can boot with, say, the slackware CD in case your kernel is unbootable. Be sure to save the original kernel by copying /vmlinuz to /vmlinuz.bak or some other such routine. Also save the original /boot/System.map

Once you're done configuring options in the menuconfig
if you've got a 2.4.X kernel then you have to type:
make dep which makes dependencies
if you have a 2.6.X kernel you can skip it.
Then type:
make bzImage which will compile the kernel.

you'll notice a million weird statements will all sorts of crazy -Flags set in the 2.4.X series but in the 2.6.X series the kernel compilation is quite simple. Either way it takes a LONG time depending on the machine.

When that's done type:
make modules to make modules
and then install them with
make modules_install (PS. I have no idea whether the _ is necessary but that's the way I initially learned and I haven't tested it out

Now you've got to copy the bzImage (stored in /usr/src/linux/arch/i386/boot/bzImage) don't ask me why... to the /boot/ as well as the System.map stored in /usr/src/linux ). Now update the /etc/lilo.conf to make sure that the image= line points to /boot/bzImage

FINALLY AND MOST IMPORTANT...EVERYTIME NO MATTER WHAT YOU DO YOU HAVE TO RUN /sbin/lilo
Even if you just compile one little teency weency thing or change. If you forget you're likely to encounter a machine that doesn't boot with a message "out of input" or something to that end. So don't forget to run it. If you do forget it, life goes on if you've got a handy boot disk so that you can get into your drive and type /sbin/lilo with the /etc/lilo.conf stored on your harddrive.

Hope this helps. I'm still figuring out a lot of things too so if you need help someone else may be of more service. But this power off thing I've finally worked out...

How exactly doesn't it swich off, it doesn't power down ? Did you try:

Hi there!

I'm going to try first the second suggestion and if it doesn't work I'll try the first one.
Although I should think in update from kernel 2.4 to 2.6, don't you think so?

Thank you so much for your attention and help dudes!!

I'll give you feedback.

I forgot to mention...

look in /proc
and see if you have a directory called "acpi"

if you don't then you're going to need to add support for acpi. If you do, something else is amiss.

try doing the following
run
to look for a program running called "acpid" which is what monitors acpi events from the kernel.

if nothing is returned try running the program
and see if it loads. If it does, then try
or

Thanks, I'll try today.

Atreo - if you are using Slack 10 with the 2.4 kernels, you have load the apm kernel module.

I had the same problem you had, but I edited /etc/rc.d/rc.modules to load apm on bootup. With 2.4 kernel and apm module loaded, an "init 0" will shutdown the OS and power off the computer.

But now that I'm using Slack 11 with the stock 2.6.18 kernel (from /testing), it's compiled with acpi and acpid starts from bootup.

Hi all!!
I tried mr.v. suggestions and I think I don't have acmp installed.
I'm trying to install acpm package.
I'm using KPackage for installing ospmd-20021122.tar.gz .

The thing is that something is not working properly. I have these two problems when I press 'install':

Problem 1:
installpkg //root/descargas/ospmd-20021122.tar.gz ;echo RESULT=$?
Cannot install //root/descargas/ospmd-20021122.tar.gz: package does not end in .tgz
RESULT=0

Problem 2 (if I press install again):
Cannot install //root/descargas/ospmd-20021122.tar.gz: package does not end in .tgz
RESULT=3

How can I solve these problems for being able to install the package?

PD: same problem with lirc-0.8.1.tar.gz

A quick idea, try
'modprobe apm'
and then
'halt'
the first will load the Advanced Power management module which is present in the default kernel. Your computer should shutdown succesfully.

@Atreo:

if you want to install a slackwarepackage on slackware you do this with the command installpkg that is true.
but not every archive is a slackwarepackage! archives with the ending .tar.gz or .tar.bz2 are never slackwarepackages!
slackwarepackages have allways the ending .tgz
so what you have there (i.e. lirc-0.8.1.tar.gz) is probably source.
you have to compile this in order to get your program.

so to start the whole thing again maybe tell us what you use.
do you use slackware 10.2? what kind of kernel do you use (you can find that out with the command uname -a you get some thing like "Linux darkstar 2.6.18 [...]")
i think to get your probs solved you do not have to install anything, you just have to configure your system ...

Hey,
I have the same problem . My comp doesn't halt.
Right now I have to do shutdown now -r and then poweroff manually when the comp has just restarted.

shutdown now -h , doesn't halt the system. It only shows "power down" and then hangs there.
I have 2.6.18 kernel , with acpi enabled. acpid is running.
My lilo is :
I had an earlier thread on this topic, but didn't quite manage it there. So trying again over here!
The append part above is from the earlier thread.

Atreo...are you sure you searched for acpi and not acmp. ACPI stands for Advanced Configuration and Power Interface (but make sure you search for the lower case "acpi"). "acmp" stands for...???

Both Atreo and duryodhan, can you run the following commands exactly and post the output for each one here in the forum.

The first command is:The second is:The third is:

Here goes the output :

Thank you all!!

I'll try tonight.

duryodhan--

First obvious question is, will another 2.6.X linux distribution allow you to turn off your computer. Try, say, an Ubuntu or Knoppix live-cd's to see if the shutdown powers the computer off.

Second, I noticed in your OP that you put
All I know is that I do not append these lines and my computer turns off so they aren't strictly necessary. Try removing that line from your /etc/lilo.conf and then update it using /sbin/lilo

Also be sure to look at the /var/log/dmesg to make sure that append line hasn't caused any errors. But still, I don't think you'll need it. You may, however, have to recompile the kernel. Did you enable all the options like Button, Processor, Thermal Zone, etc when you built the kernel? And if so, did you compile them as modules or statically?