+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: Resume from suspend not working after flashing Tow-Boot to SPI (/showthread.php?tid=17539)
Resume from suspend not working after flashing Tow-Boot to SPI - xp19375 - 10-30-2022
I recently flashed Tow-Boot to the SPI and now my Pinebook Pro won't resume from suspend. According to journalctl, it enters suspend just fine but it never resumes and I need to reboot. Has anyone else encountered this? If I have to, how would I go about flashing the SPI to what was there before?
RE: Resume from suspend not working after flashing Tow-Boot to SPI - wdt - 10-30-2022
> If I have to, how would I go about flashing the SPI to what was there before?
AFAIK,, from the factory, pbp SPI is blank
install mtd-utils OR there are, IIRR, 2 other programs to write nor flash
----
Just what kind of suspend? there is ordinary S2,, S2ram (STR, S3) and hibernate
I have not heard anyone make hibernate work
ordinary S2 is barely better than screen blanking
S3ram is quite good, but there are 5 !!! caveats
no nvme,,, 5.7 or 5.8 manjaro kernel,,, a working uboot (with s2ram capability),
setting in sleep.conf,, settings in systemsettings5, power
I have had the failure to wake lots, trying to see if a distro supported s3ram, I have no answer
Only 2 or 3 distros will do s3ram, FWIW.... If you know more, please post
---
BTW, to wake from STR, a quick tap on pwr button, everything else (but lid magnet sensor) is dead
If lid magnet is misplaced, as so many are, you have to either turn if off or move it (the magnet)
RE: Resume from suspend not working after flashing Tow-Boot to SPI - xp19375 - 10-31-2022
Thanks wdt! I'm running the latest Manjaro that comes on the PBP eMMC, kernel 6.0.2-MANJARO-ARM. Previously suspend/resume had worked for this kernel and lid magnet.
/etc/systemd/sleep.conf is all defaults
Quote:[Sleep]
#AllowSuspend=yes
#AllowHibernation=yes
#AllowSuspendThenHibernate=yes
#AllowHybridSleep=yes
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
#HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=120min
Before I flashed Tow-Boot to the SPI flash, suspending looked like (output of 'journalctl | grep -C 4 suspend').
Quote:Oct 29 08:58:10 neptune systemd-sleep[2735]: Entering sleep state 'suspend'...
Oct 29 08:58:10 neptune kernel: PM: suspend entry (deep)
Oct 29 08:58:14 neptune kernel: Filesystems sync: 0.109 seconds
Oct 29 08:58:14 neptune kernel: Freezing user space processes ... (elapsed 0.005 seconds) done.
Oct 29 08:58:14 neptune kernel: OOM killer disabled.
Oct 29 08:58:14 neptune kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 29 08:58:14 neptune kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 29 08:58:14 neptune kernel: LDO_REG2: No configuration
Oct 29 08:58:14 neptune kernel: LDO_REG1: No configuration
Oct 29 08:58:14 neptune kernel: ieee80211 phy2: brcmf_fil_cmd_data: bus is down. we have nothing to do.
Oct 29 08:58:14 neptune kernel: ieee80211 phy2: brcmf_cfg80211_get_tx_power: error (-5)
Oct 29 08:58:14 neptune kernel: PM: suspend devices took 2.160 seconds
Oct 29 08:58:14 neptune kernel: Disabling non-boot CPUs ...
Oct 29 08:58:14 neptune kernel: psci: CPU1 killed (polled 0 ms)
Oct 29 08:58:14 neptune kernel: psci: CPU2 killed (polled 0 ms)
Oct 29 08:58:14 neptune kernel: psci: CPU3 killed (polled 0 ms)
--
Oct 29 08:58:14 neptune kernel: OOM killer enabled.
Oct 29 08:58:14 neptune kernel: Restarting tasks ... done.
Oct 29 08:58:14 neptune kernel: random: crng reseeded on system resumption
Oct 29 08:58:14 neptune kernel: mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Oct 29 08:58:14 neptune kernel: PM: suspend exit
Oct 29 08:58:14 neptune systemd-resolved[375]: Clock change detected. Flushing caches.
Oct 29 08:58:14 neptune wpa_supplicant[496]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 29 08:58:14 neptune systemd-logind[430]: Lid opened.
Oct 29 08:58:14 neptune wpa_supplicant[496]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Now journalctl shows the following when trying to suspend:
Quote:Oct 30 15:12:20 neptune systemd[1]: Starting System Suspend...
Oct 30 15:12:20 neptune systemd-sleep[1017]: Entering sleep state 'suspend'...
Oct 30 15:12:20 neptune kernel: PM: suspend entry (deep)
Oct 30 15:12:20 neptune wpa_supplicant[503]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 30 15:12:20 neptune wpa_supplicant[503]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Erasing Tow-Boot off of the SPI flash and rebooting worked. Now resume from suspend works as expected. I installed the mtd-tools package and ran
Code:
flash_erase /dev/mtd0 0 0RE: Resume from suspend not working after flashing Tow-Boot to SPI - wdt - 10-31-2022
My experience with tow-boot is mixed
The 1st version worked OK, S3ram sleep was about 1/2 as long (as BSP uboot)
version 2 did not wake from sleep
IDK what version it is now