ok, I will try it these days and tell you what happens . I will make it again with the bare.i kernel

Excuse me, but I would like to ask you one final thing before re-installation. I notice that the error message "apm:BIOS not found" occurs right after the statement "Updating module dependencies:". Does this shed some light on the nature of the problem? Is it the apmd daemon that provides apm support in the group A packages that fails?

your getting errors for a bunch of modules that are all part of the

-kernel-modules-2.4.31-i486-1.tgz <- section A of disc 1

that's why i think if you went thru and tried to reinstall that package and it didnt work, your just better off to reload as your new and might be doing somehting wrong.

to reinstall is probably so much of a faster way to take care of your problem; and just write the experience off as a learning curve

ok, tomorrow I will have time to reinstall and i will tell you the result.

These days read some literature on advanced power management and it says that "APM support consists of two parts: kernel support and user-land support" [http://en.tldp.org/LDP/Mobile-Guide/...c1s8-apm.html]. The command "apm -v" prints information about the APM BIOS version and Linux APM driver version. When I type it, it says: "No APM support in kernel". When I go to
control center-power control-laptop battery-power control, I can read: "Your computer doesn't have the Linux APM (Advanced Power Management) or ACPI software installed, or doesn't have the APM kernel drivers installed - check out the Linux Laptop-HOWTO document for information on how to install APM." The book about apm says: "You need a kernel that has the APM driver compiled in using the appropriate kernel configuration options. Currently most distributions do not ship kernels with the APM driver enabled so you may have to enable the driver using a boot option or to compile a custom kernel." It seems to me that I will have to compile a custom kernel to have apm support? what do you think?

But be it so, there is something still that I do not understand: so long I have conceived an impression that am support is built in the compiled bare.i kernel that I am using? or for my version 2.4.31 that is not true?

the kde power laptop panel looks to see if the module apm is loaded. since you have no apm loaded because your modules are messed up, yeah, it's going to give that error.

if i were to freshly load my laptop up, no changes or anything just a clean install of slackware 10.2 with the bare.i kernel, and go into the battery center in KDE it would give that error. then if i went into console as root, and type 'modprobe apm' and then went back into the battery center, it would show I have apm.

you have module issues, and alot of them. that's why i think it best you reformat/reinstall with the full-noobie option.

you'd be done in under an hour

oh one last thing.

there are two ways to make a kernel for apm.

1. you can have the kernel made with apm built in. no modprobe required.
2. you can have the kernel made with apm as a 'module'. the 'modprobe apm' is therefore required to activate the 'apm' daemon.

Pat builds the bare.i kernel with option 1 above. Not everyone needs it. Some people may have issues with it. Hence the name, 'bare.i'

So I downloaded Slackware again from the Slackware site, verified all md5 sums, installed it and again when I type "modprobe apm" the result is:
/lib/modules/2.4.31/kernel/arch/i386/kernel/apm.o.gz: init_module: No such device
/lib/modules/2.4.31/kernel/arch/i386/kernel/apm.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.31/kernel/arch/i386/kernel/apm.o.gz: insmod /lib/modules/2.4.31/kernel/arch/i386/kernel/apm.o.gz failed
/lib/modules/2.4.31/kernel/arch/i386/kernel/apm.o.gz: insmod apm failed

(((
when I type "dmesg | grep apm" the result is:
apm: BIOS not found.
apm: BIOS not found.
Please, what should I do? Is my bios faulty? my motherboard is Intel D845GERG2 and my BIOS version is RG84510A.86.0022.P12

I really suggest you to install a 2.6 kernel and try both APM and ACPI with that 2.6 kernel. Maybe your mobo, bios, whatever is not supported in the 2.4 series. Really, just install one of Pat's 2.6 kernel then try with APM if it's not working, compile the 2.6 kernel with ACPI support as I said and try it like that.

I would be thankful if you tell me where to download the 2.6 kernel and tell me what installing a kernel involves. Does it require reinstallation, or as it is written in the slack book just copying the image to /boot? Would you be so kind as to tell me what to do to install the new kernel? I haven't done that so far...I am interested in installing the kernel in such a way that if it does not work, to be able to boot with the old kernel.
I think that the problem is with my BIOS. since the apm module is built in the bare.i kernel, and I have the apm module installed, but I am unable to load it, this means that the only option left is my BIOS, isn't it like that?

Probaly I should try the bareacpi.i kernel, it is compiled with ACPI support. What do you think? I would be thankful to you if you provide me some guidelines on installing a new kernel in such a way that in case of failure to be able to use the old kernel.

tramni:

the bare.i does not include ACPI support.

however, Pat did make a kernel called "bareacpi" that is included with Slackware 10.2

That kernel can get installed easier when you re-install all of slackware.

I believe it's when you are booting up it's the f2 or f3 key I forget exactly, but you can pick the 'bareacpi' kernel. Just take a look at the slackware tutorial at slackware.com it has photos showing you the various steps in pictures to install slackware.

Now your other question, the 2.6.13 kernel is on cd tool in a folder called testing.

You install the alsa, modules and kernel. I doubt that you require the 'headers' and Pat has a warning about instlling them.

You install these 3 tgz files with 'pkgtool' with root priveledges. Then as root you run 'lilo' then you reboot and that is it. This will overwrite the boot up for 2.4 kernel, it leaves the 2.4 kernel stuff in your pc. And it makes the 2.6.13 kernel the default.

You could to play it safe, take a look at the lilo in shilo's post at top of slack forum here, there is how you can add another section to the lilo for the vmlinuz-ide-2.4.31 and run lilo after that. Thus you can boot into 2.4.31 kernel or your newly installed 2.6.13 kernel just in case.

Personally, I think you might find it more usefull to boot up on cd 1 and go thru reformating and reinstalling everything, but linux is about playin, learning and tweaking so it may not be a bad excercise to try this to before you dump your entire drive.

ok, if I reinstall everything once again with the bareacpi.i kernel, what should I do to enable acpi support? What else should I do so that my PC gets really shout down when I type "shutdown -h now"? Where and what shall I uncomment after reinstalling with the bareacpi.i? And where do you think my problem is with the bare.i kernel, is it my bios as I think? I think there is no other alternative left since the bare.i has support for apm and I have apm module installed.

I scrutinized my BIOS this evening and I found out that there is nothing about apm mentioned there. In the power settings only ACPI is mentioned. Most possibly my BIOS does not support apm, and that is why I constantly get "apm: BIOS not found". Do you think so?
I would be thankful to you if you tell me whether reinstalling with the bareacpi.i kernel is worth, if there is something different from the installation with the bare.i kernel and what shall I do to enable acpi support, where and what should I uncomment after the installation of bareacpi.i, what should I add to my lilo section?