openSUSE has problems detecting if the AC Adapter is plugged in or not. Say if it’s plugged in and I unplug it, it still thinks it’s plugged in and charging. (Or vice versa). The actual charging/discharging takes place normally and the percentage display is also accurate - it’s just that it doesn’t detect properly if it’s plugged in or not.
This is not a huge issue, but it gets annoying as it uses a wrong power profile - so it could be on Aggressive Powersave if I’m plugged in, or worse, on Performance when I’m running low on battery!
One thing to be noted though is it does detect the adapter status properly at bootup. Oh, and another thing to be noted that is also properly detects if the battery is being charged or discharged, but it can’t guess if it’s plugged in or not!
Check to see if udevd is running, using ‘top’ in a console, or CTRL-ESC and see if it’s there.
you can restart it from a console if needed:
sudo /etc/init.d/boot.udev restart
it’ll ask for a password and then should attempt to stop then start the udev daemon.
I’ve been having issues with udevd also, so keep an eye on this daemon. I tend to kill it when I’m ‘steady-state’ and not plugging things in and whatnot, then restart udevd when I’m using flash drives and such. It seems to be a cpu hog at the moment, giving my approx 40-60% load consistently. I’m testing and looking for a solution.
udevd seems to be running fine, although for me the CPU usage is around 2%. There are quite a few instances of it though - around 10ish… is this normal?
Anyways, I did try the command you posted but it doesn’t change the status. Oh and for me, other devices like flash drives plug-n-play just fine.
By chance, do you have a ‘noacpi’ entry in your boot entry? If I remember correctly (don’t worry, someone will correct me if I’m wrong… trust me…), the acpi subsystem has a hand in telling udev that something has changed in the power system (and other stuff too)
apm is the older interface for power events (and other stuff again). You should have a daemon named ‘acpid’ or ‘apmd’ running to handle the power change events. Although, if you’ve got a ‘apm=off’ or ‘noacpi’ or ‘noapm’ entry in the kernel command line, then neither would even start.
hmm, Kernel Command Line… just to check it, you can
cat /proc/cmdline
which will show you what command line was handed to the kernel from grub (or lilo)
To change it, generally you need to edit /etc/sysconfig/bootloader and verify the correct entries are in place. I imagine the YaST2 BootLoader GUI is a better place to be mucking with boot parameters.
Yast -> System -> BootLoader
Be careful, and only change ONE of the entries at a time. If you change BOTH, (ie, the failsafe TOO), then you might not be able to boot back into the system to fix a mistake. These things happen to the best of us… don’t invite trouble.
Actually, you generally don’t want to play with the ‘failsafe’ entry, it’s your saving throw against those ‘omg omg omg what did I do?!?’ moments…
Just posting to confirm it’s an issue with KDE (or something KDE related). (When I boot from the GNOME live CD it’s able to show the AC adapter status properly.) Reporting the bug.
