Power consumption and suspend to ram

[z4v4l]

So it seems that suspend to disk isn't trivial on ARM.

as anything not done. ARM as an architecture brings zero complication to that.

And indeed it seems that suspend to ram / sleep is not putting the cpu to sleep...

then it's not suspend to ram. all S states do put all CPUs off. not idle, not deep sleep, not anything but full off.

and honestly, again, until Rockchip jumps ACPI, this won't change. because all these efforts (manjaro) are mimicking. for STR, a capable firmware is needed, on PCs, this is done by the BIOS,UEFI/ACPI and the OS. manjaro here, hardly would do anything. for hibernation, it could be made by the OS purely, but eh, you do see how it goes.

[robt]

Ok, so no real STR. But if others can get 7% battery loss in 24 hrs, and I get about 10x that, what can I do?

[robt]

Just tried again, 12 hrs and battery went from 91% to 37%, so a 54% drain in 12 hrs standby, not very usable...

I also tried charging with the supplied power adapter on the barrel port, instead of via the USB-C port - I figured it might actually have something wrongly configured, so I charged that way, then did a reboot off the charger. Alas, still very high battery drain for only half a day on suspend to ram.

I just checked the tablet (which doesn't get use since I now use the PBP), it was at 100% on the 15th, got a couple of hours of use and is now at 66%... Also ARM based, so much more should be possible,...

[wdt]

If you have manjaro (and perhaps mrfixit's uboot)
https://forum.pine64.org/showthread.php?...48&page=19
, & page before and after may give some help

[xmixahlx]

use bsp uboot
use kernel 5.6+
configure /etc/systemd/sleep.conf with SuspendState=mem and disable hibernation.

[robt]

Ok, that's very helpful, thanks!

uname tells me I have kernel 5.7.0-1-MANJARO-ARM, and I installed bsp uboot: uboot-pinebookpro-bsp (1.5-7), which tells me this at the end of the installation:
A new U-Boot version needs to be flashed our install drive. Please use lsblk to determine your drive, before proceeding.
You can do this by running:
# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblkX seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblkX seek=24576 conv=notrunc
Transaction successfully finished.

lsblk outputs this:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk2 179:0 0 58.2G 0 disk
├─mmcblk2p1 179:1 0 213.6M 0 part /boot
└─mmcblk2p2 179:2 0 58G 0 part /
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
zram0 252:0 0 5.6G 0 disk [SWAP]

So I figure I should move on to this (as root):
# dd if=/boot/idbloader.img of=/dev/mmcblk2boot0 seek=64 conv=notrunc

which unfortunately results in this:
dd: writing to '/dev/mmcblk2boot0': Operation not permitted
1+0 records in
0+0 records out
0 bytes copied, 0.00123433 s, 0.0 kB/s

?
What am I missing?

I have read lots of pages, mostly to be sure which device to dd to... but this is unclear to me.

[JasonG-FR]

# dd if=/boot/idbloader.img of=/dev/mmcblk2boot0 seek=64 conv=notrunc

You should dd to `/dev/mmcblk2` not `/dev/mmcblk2boot0`:

Code:

# dd if=/boot/idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc

[xmixahlx]

also, i would use mrfixit bsp-based uboot. i have a script that does this for you in pbp-tools.

[robt]

Thanks a million, that helped. I just triggered the suspend and it managed to wake up again (after pressing the power button, not just opening the lid as it was before - which is perfectly fine with me).

Since it's late, I only did the correct dd commands as Jason mentioned.

xmixahlx, what would the mrfixit bsp-based uboot bring to the table that I don't have now? I'm on Manjaro, 3 week old pbp, software up to date. Thanks.


Edit: just checked, after 10 hours of sleep (the laptop, I got fewer), the battery went from 56% to 54%...!
:-D

[termac]

Thanks a million, that helped. I just triggered the suspend and it managed to wake up again (after pressing the power button, not just opening the lid as it was before - which is perfectly fine with me).

Since it's late, I only did the correct dd commands as Jason mentioned.

xmixahlx, what would the mrfixit bsp-based uboot bring to the table that I don't have now? I'm on Manjaro, 3 week old pbp, software up to date. Thanks.


Edit: just checked, after 10 hours of sleep (the laptop, I got fewer), the battery went from 56% to 54%...!
:-D

Does sound work for you after waking up from suspend? Deep sleep is working for me, but I can't get sound working after a resume. Anyone else seeing this issue?