Battery Monitoring + SUSE
Hi All,
I've spent a few hours reading through some of the threads on here about people with laptop battery monitoring problems, but I didn't find anything pertaining to my problem (nor did I understand much of it, to be honest. I'm still very new at this...). I'm confused. Quite confused! I've tried several different distributions of Linux out in the past week since I got my laptop and I basically decided that I'd use the one that had the least amount of problems, mainly because I need to get some work done and wanted to spend the minimum amount of time configuring things. I'm currently running SUSE 10.0 and it detected everything, installed everything without a glitch. There's still two things not right about it though and one of those is the battery monitoring (the other is the wireless, but it's not really a priority now, so I can look at it next week or something). I just can't for the life of me understand why the monitoring of the battery would work "out of the box" for Ubuntu and Mandriva, but not for Fedora Core and SUSE. I've decided on SUSE, so I'd really like to ask for anybody's advice on where I could get started. I've read a lot about "recompiling my kernel", however, this sounds a nightmarish situation that I don't really have time for. If there's no other way, then I suppose I'll get round to learning how to do that eventually, but ideally, I'd just like to be able to run a patch or install something, or find out where to put things in config files to make this work. Anyone have any ideas specific for SUSE? I've looked in /proc/acpi, but actually, no such directory exists on my system. Where would I start to get some basic info and understanding of this? Oh, also, I have the Gnome Battery Charge monitor in my system tray, which is showing a red exclamation mark next to the battery, a completely empty battery and 0:00 time next to it. This is while the laptop is plugged into the wall. Unplugging the laptop does nothing to change this monitor. Any help to get me started would be greatly appreciated! I know I can do this stuff, since I have a sweet 1280x800 resolution now after reading a lot last night, but the battery is next :) Cheers in advance, Lioncoeur |
It sounds like SUSE didn't install with ACPI support. How did you come about with your SUSE disks? Did you burn them yourself, or did you get them from a friend, magazine, or book. I guess what I'm getting at is if you have a current version.
|
I downloaded them a few days ago and burned them myself. Is there any way to check if I have ACPI support or not?
The ones I got were: SUSE 10.0 EVAL DVD i386 GM. Also, I just checked the dvd and there is a program called acpid-1.04 in it. |
Perhaps its installed but the module isn't loaded. Can you post the output of lsmod
|
Sorry I took a few days to respond to this thread, thanks for your offer to help. Here is my lsmod:
Code:
Module Size Used by |
Also, would this all be solved if I simply reinstalled my system with ACPI support? How do I go about doing that? On a related note, I noticed that the SUSE installation doesn't do some things automatically, like other installations do. For instance, I spent about 10 minutes scratching my head completely boggled at why the CD-Rom was reading so slowly. I then checked hdparm to see if dma wasn't enabled, and noticed that indeed it wasn't. I rebooted, started installation from the beginning, and was able to Alt+F2 into a shell where I could enable dma on the drive before I started installing things.
What else should I do while I'm in this shell? Thanks in advance. |
Hi, I've been doing some playing around and I've got some results!
If I pass 'apm=off acpi=force' to the kernel at boot, I can get the module loaded and working. If I try 'apm=off acpi=on', then it doesn't work at all. Here are relevant lines from dmesg: Code:
ACPI: Subsystem revision 20050408 Code:
FATAL: Error inserting acpi_cpufreq (lib/modules/2.6.13-blah blah): Device or resource busy What is the difference between acpi=force and acpi=on and should I care? Thanks :) |
acpi
your problem is most probably caused by a non-functioning acpi dsdt-table in your bios (which is the case for the most bios versions I know). since windoofs e.g. is not a really exact guy usually this problem doesn't matter for this kind of operating system. linux on the other hand is very exact and does not like corrupted dsdt-tables. search the web (google) for your laptop (which kind of laptop do you have?) and "dsdt table". I am sorry, but I forgot the exact link to a site in the net which has thousands of dsdt tables for several laptops (I got mine also from there and it worked!). Follow the instructions (as far as I remember you have to compile the dsdt for your specific laptop with the Intel acpi driver (which you also get in the net). then you have to put your compiled "dsdt.aml" (or something like that) in your /boot directory and tell linux, that it has to load it during the boot process (in /etc/sysconfig). That's it!
|
All times are GMT -5. The time now is 08:09 PM. |