I'm new at this and would like the battery monitoring abilities available in 8.2 to work. I found the part in the Kernel to turn on, but am unsure as to the procedure to 'make' after turning it on Could someone post the procedures and syntax I need to preform to do this correctly. Or... is it not worth the effort? Thanks in advance
A las 08:21 del 23 de Sep de 2003, William Westfall dijo:
I'm new at this and would like the battery monitoring abilities available in 8.2 to work.
I found the part in the Kernel to turn on, but am unsure as to the procedure to 'make' after turning it on
Could someone post the procedures and syntax I need to preform to do this correctly.
Or... is it not worth the effort?
Depending on your laptop configuration you are better off APM or APCI. check which one goes better with you and compile _only that one_ in your kernel. AFAIK if it is a new laptop you have more chances be better using ACPI I am with APM and everything works fine out of the box , and yes, it is worth it, Sergio -- pubic hair, n.: Organic dental floss.
On 2003.09.24 04:21 William Westfall wrote:
Or... is it not worth the effort?
Right, it is not :-) You can use acpi or apm, to be enabled at boot time. Both options are compiled on the suse kernels. By default, acpi will be used, but disabling it wil automatically enable apm. Documented - search the SDB, for example. -- Cheers, Carlos Robinson
On Wednesday 24 September 2003 08:44 am, Carlos E. R. wrote:
On 2003.09.24 04:21 William Westfall wrote:
Or... is it not worth the effort?
Right, it is not :-)
You can use acpi or apm, to be enabled at boot time. Both options are compiled on the suse kernels. By default, acpi will be used, but disabling it wil automatically enable apm.
Documented - search the SDB, for example.
-- Cheers, Carlos Robinson
With my laptop (which uses ACPI) I discovered that in order to see battery usage and power status I had to manually run the command "modprobe ac && modprobe battery" as root. I added them to start up by placing that command in /etc/rc.d/boot.local HTH, Mike Sacco
Michael, Michael Sacco wrote:
With my laptop (which uses ACPI) I discovered that in order to see battery usage and power status I had to manually run the command "modprobe ac && modprobe battery" as root. I added them to start up by placing that command in /etc/rc.d/boot.local
HTH, Mike Sacco
This also worked on my laptop except I started experiencing lockups at random intervals under SuSE 8.2 / KDE. Took it back out and all is fine again :o( Damian
On Wednesday 24 September 2003 22:23, Damian O'Hara wrote:
Michael,
Michael Sacco wrote:
With my laptop (which uses ACPI) I discovered that in order to see battery usage and power status I had to manually run the command "modprobe ac && modprobe battery" as root. I added them to start up by placing that command in /etc/rc.d/boot.local
HTH, Mike Sacco
This also worked on my laptop except I started experiencing lockups at random intervals under SuSE 8.2 / KDE. Took it back out and all is fine again :o(
Damian
Random? Nothings random in computers - not even the random number generator. ;-) Typically you will get kernel panics (blinking keyboard lights) when removing some of these modules. (Usually processor and thermal). Excluding these from being removed at run-level changes is the job of /etc/sysconfig/powermanagement file. -- _____________________________________ John Andersen
On Wednesday 24 September 2003 16:35, Michael Sacco wrote:
On Wednesday 24 September 2003 08:44 am, Carlos E. R. wrote:
On 2003.09.24 04:21 William Westfall wrote:
Or... is it not worth the effort?
Right, it is not :-)
You can use acpi or apm, to be enabled at boot time. Both options are compiled on the suse kernels. By default, acpi will be used, but disabling it wil automatically enable apm.
Documented - search the SDB, for example.
-- Cheers, Carlos Robinson
With my laptop (which uses ACPI) I discovered that in order to see battery usage and power status I had to manually run the command "modprobe ac && modprobe battery" as root. I added them to start up by placing that command in /etc/rc.d/boot.local
HTH, Mike Sacco
Mike: Did you forget to load the acpid in the Boot run-level? This is the script responsible for loading those modules, and many users forget to use the run-level editor to enable it. It should be enabled for the "B" column only. It will then load all the acpi modules that are not excluded by the /etc/sysconfig/powermanagement file. Yes, your way works, but its not the SuSE way. ;-) -- _____________________________________ John Andersen
On Thu, 2003-09-25 at 08:34, John Andersen wrote:
On Wednesday 24 September 2003 16:35, Michael Sacco wrote:
On Wednesday 24 September 2003 08:44 am, Carlos E. R. wrote:
On 2003.09.24 04:21 William Westfall wrote:
Or... is it not worth the effort?
Right, it is not :-)
You can use acpi or apm, to be enabled at boot time. Both options are compiled on the suse kernels. By default, acpi will be used, but disabling it wil automatically enable apm.
Documented - search the SDB, for example.
-- Cheers, Carlos Robinson
With my laptop (which uses ACPI) I discovered that in order to see battery usage and power status I had to manually run the command "modprobe ac && modprobe battery" as root. I added them to start up by placing that command in /etc/rc.d/boot.local
HTH, Mike Sacco
Mike: Did you forget to load the acpid in the Boot run-level? This is the script responsible for loading those modules, and many users forget to use the run-level editor to enable it. It should be enabled for the "B" column only.
It will then load all the acpi modules that are not excluded by the /etc/sysconfig/powermanagement file.
Yes, your way works, but its not the SuSE way. ;-)
-- _____________________________________ John Andersen
Hi Can you explain which is the SuSE way ? I have the same problem with my laptop and I still don't know how to solve it. EJ
John
Did you forget to load the acpid in the Boot run-level? This is the script responsible for loading those modules, and many users forget to use the run-level editor to enable it. It should be enabled for the "B" column only.
It will then load all the acpi modules that are not excluded by the /etc/sysconfig/powermanagement file.
Yes, your way works, but its not the SuSE way. ;-)
Why does it have to be run level B. It is 2, 3 and 5 by default in the run level editor. Is this an error? Ulrich
On Thursday 25 September 2003 01:04, Ulrich Leopold wrote:
John
Did you forget to load the acpid in the Boot run-level? This is the script responsible for loading those modules, and many users forget to use the run-level editor to enable it. It should be enabled for the "B" column only.
It will then load all the acpi modules that are not excluded by the /etc/sysconfig/powermanagement file.
Yes, your way works, but its not the SuSE way. ;-)
Why does it have to be run level B. It is 2, 3 and 5 by default in the run level editor. Is this an error?
Ulrich
You want to start these mods at boot time and not delete them ever, because on many machines, attempting to take these modules out causes a kernal panic. SuSE is smart enough to not unload them if the next runlevel also uses them, so most of the kernal panics happen at shutdown. Setting them to B means start them at boot and don't delete them ever, just let the kernel shutdown with them still running. I believe this is in the suse knowledgebase somewhere. There are also settings in the file mentioned above (and available thru yast) where in you can list those modules you know cause problems when removed. In my Sony machine, rmmod'ing thermal or processor leads to a kernal panic in less than 1 second, preventing a clean shutdown. -- _____________________________________ John Andersen
Yes, your way works, but its not the SuSE way. ;-)
Why does it have to be run level B. It is 2, 3 and 5 by default in the run level editor. Is this an error?
Ulrich
You want to start these mods at boot time and not delete them ever, because on many machines, attempting to take these modules out causes a kernal panic.
Not on mine :o) John, I know you're trying to help but this is definately a YMMV. I followed your advice above and not only did I get lots of errors in messages but I also seemed to suddenly have 3 CDRW/DVD devices instead of the one. I took it back out and I'll live without it. SuSE 8.2 & HP/Compaq nx9005 (Athlon XP 2400) Damian
participants (8)
-
Carlos E. R. -
Damian O'Hara -
Ernesto Jardim -
John Andersen -
Michael Sacco -
Sergio Dominguez -
Ulrich Leopold -
William Westfall