Il 01/07/2014 18:05, Malcolm ha scritto:
On Tue, 01 Jul 2014 17:42:57 -0300 Marco Calistri <marco.calistri@yahoo.com.br> wrote:
Il 01/07/2014 17:10, Patrick Shanahan ha scritto:
- Marco Calistri <marco.calistri@yahoo.com.br> [07-01-14 16:03]: [...]
You are in control: systemctl disable upower
ps: running on one of my four desktops and not on either laptop
[...]
marco@linux-turion64:~> upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: (null) power supply: no updated: mer 31 dic 1969 21:00:00 BRT (1404244550 seconds ago) has history: no has statistics: no unknown warning-level: unknown icon-name: '(null)'
upower.service - Daemon for power management Loaded: loaded (/usr/lib/systemd/system/upower.service; enabled) Active: active (running) since mar 2014-07-01 09:25:26 BRT; 7h ago Docs: man:upowerd(8) Main PID: 783 (upowerd) CGroup: /system.slice/upower.service └─783 /usr/lib/upower/upowerd
sudo systemctl status upower.service
lug 01 09:25:25 linux-turion64 systemd[1]: Starting Daemon for power management... lug 01 09:25:26 linux-turion64 systemd[1]: Started Daemon for power management. lug 01 09:25:26 linux-turion64 upowerd[783]: (upowerd:783): UPower-Linux-WARNING **: energy_full (43.772400) is greater than energy_full_design (41.990400)
@Patrick:
At the end have I to disable upower from Yast or not?
no but I imagine that you can. Also: systemctl stop upower systemctl disable upower
You *do* read the responses you get ???
Is it a problem with my battery or probably with something else insided
AGAIN: appears an incompatibility between your system and the software, ie: support for your system is not there. Which you were told earlier in the thread.
w/o systems availabile for testing, much can be missed. And if you do not submit bug reports, unlikely to *ever* be fixed. Really, free software is not enitrely free. You are expected to help, ie: with bug reports.
All OK, I accept your blames but certainly I'm not alone with this not supported hardware problem, then do not base the overall issue still not resolved just upon the fact that myself have not been a good free-software user and has not contributed with opening of bug reports because many others are complaining about same not working power-management in Linux.
I red the responses from you and Malcolm and these are not in sync about upower enabling, for this reason I'm asking confirmations, beside this it could be possible I miss something because I'm not Anglo-Saxon then some words or concepts can even escape from my understanding.
Regards,
Hi On my systems upower is not enabled, yours is for what ever reason? I'm not running 3.12 only 3.10.
On this HP 4440s I run with the following boot option (for brightness control);
acpi_osi="!Windows 2012"
Maybe adding this will help with newer hardware?
Hi Malcolm! I don't know why it is enabled I was just checking into Yast and found it that way. I installed 3.12 a couple of days ago just to see if with this new release the problems go away (suggestion of giving a try to 3.12 by Richard Brown to one of my previous post). I have the following boot option on my laptop, it is not new hardware at all: Lenovo Z470 Command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-17-default root=UUID=d7862dd1-e694-4817-9fe4-adb352109a9f resume=/dev/disk/by-id/ata-SAMSUNG_HM501II_S2PMJ56B607218-part7 splash=silent quiet i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 showopts I wont add something if not specific to resolve my particular issue. Thanks for your reply. Cheers, -- Marco Calistri (amdturion) -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org