On 2022-10-21 16:29, cagsm wrote:

Support,

apparently utter and total noob here understanding or making use of power saving methods on laptop on current leap here.

major brand rather current generation laptop hardware here. default leap with kde install. when i sleep (technical name: suspend?) the laptop from via kde menu or close the lid, it still eats away huge amounts of the battery of this laptop. also it plays sounds and clickery effects from the speaker when for example i turn off my power outlet (switch off power) for example. the laptop apparently doesnt sleep at all or i have very different understanding and reasoning what sleep would mean.

coming from a windows world, my (older) laptops back ages ago really went still, powered down the cpu and memory and disks, would not cause heat at all, or barely eat away the battery at all.

i am not talking memory-saving-to-disk here at all (technical term: hibernation) thats what I am trying to avoid, as it really writes away so much amount of ram completely to SSD these days, and still takes like a lot of time.

i am first trying to make use of normal sleep (suspend). i wonder if linux is so incapable of saving power to begin with, or if this is a configuration issue, or an opensuse leap issue or kernel issue or whatever.

for example: when i put the system to sleep via kde menu, the close the lid only after that, i have the feeling that the system still reacts to the lid even as if it would unsleep the machine again, like a switch button, sleep from kde menu = suspend swith pressed. lid closing = suspend switch button pressed once again thus un-suspend waking it again.

when having the lid closed and i turn off the laptops power then (unplug it from ac socket etc.) then the laptops creates sound in reaction to that, showin the user (me) that some power event happened or once again suspend switch pressed once more figuratively.

this all dont make sense to me, how can an already sleeping laptop in the fist place react to closing the lid. in my universe that would only acknowledge the wanted sleeping suspend state by the user, but apparently it is not. then pulling the ac power after that even creates for another contradicting event on addition on top of that.

i am really confused. my windows machine once put to sleep, does not generate sounds, and does not re-ware up or change its state when i pull the plug, or reconnect the ac plug and more.

i am seriously missing the KDE configuration gui what happens when i close the lid and when i pull the power etc apparently there is only three major categories as a state of things, running on ac, running on battery and running on low battery. but this does not reflect my true reality of things.

what am I getting wrong here? ty.

It may be that your laptop is capable of some intermediate sleep mode, and Linux is using that. For instance, my tiny laptop on sleep mode leaves one of the USB sockets powered. This can be disabled in the UEFI (aka bios). Apparently it is of use to charge a phone. I don't remember if it also does this in hibernation mode. Your machine may use this mixed mode for some "documented" reason. Or, sleep simply failed. There is a well known hybrid sleep mode, in which memory is dumped to disk, same as in hibernation, but at the final moment the machine goes to sleep instead; the idea is instant wakeup, but if you leave the machine too long in sleep and the battery runs down you can connect the power and wake up from the disk image. The system logs should give you information about what happened, so you should read them. And of course, try to sleep via command: sudo /usr/bin/systemctl hibernate Possibilities (man systemctl): suspend Suspend the system. This will trigger activation of the special target unit suspend.target. This command is asynchronous, and will return after the suspend operation is successfully enqueued. It will not wait for the suspend/resume cycle to complete. hibernate Hibernate the system. This will trigger activation of the special target unit hibernate.target. This command is asynchronous, and will return after the hibernation operation is successfully enqueued. It will not wait for the hibernate/thaw cycle to complete. hybrid-sleep Hibernate and suspend the system. This will trigger activation of the special target unit hybrid-sleep.target. This command is asynchronous, and will return after the hybrid sleep operation is successfully enqueued. It will not wait for the sleep/wake-up cycle to complete. suspend-then-hibernate Suspend the system and hibernate it after the delay specified in systemd-sleep.conf. This will trigger activation of the special target unit suspend-then-hibernate.target. This command is asynchronous, and will return after the hybrid sleep operation is successfully enqueued. It will not wait for the sleep/wake-up or hibernate/thaw cycle to complete. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)