Power Management - Suspend

Robert_Fisher · January 17, 2015, 4:35am

Hi all.

I have been trying to find a way to put my BBB into a suspend or sleep state. I found out that power management was not incorporated into the 3.8 kernel, however several posts suggested that it would be working in later kernel (3.14+). I have installed several versions of 3.14 through 3.18 and still have not been able to find one that will allow me to enter a suspend mode.

On some versions I could issue “echo ‘mem’ > /sys/power/state” and nothing would happen. On 3.18 with Debian, I receive “Permission denied”. I’ve seen a few posts about recompiling firmware from TI with custom cape configurations. Unfortunately this is a bit over my head at the moment.

I was hoping someone had some experience with this and could provide a step-by-step for how to get it working. If we could make this more straightforward for the BBB community, I think we would see an increase in the number of people using BBBs for battery-powered applications.

Thanks in advance!

RobertCNelson · January 17, 2015, 4:45am

Well, this is a feature that is currently "only" in the 3.14.x-ti kernel:

sudo apt-get update
sudo apt-get install linux-image-3.14.26-ti-r44
sudo reboot

Based on patch status, it "should" enter mainline during v3.20-rcX (so
the next kernel merge cycle)

Regards,

Robert_Fisher · January 18, 2015, 5:26pm

Mr. Nelson, thank you very much for clearing that up for me. I will try that today.

Robert_Fisher · January 18, 2015, 11:26pm

Quick question…I see that you’re suggesting that I use apt-get to install the kernel, but I don’t seem to have a repository with knowledge of that kernel.

Should I be using git instead?

Thanks.

Robert_Fisher · January 19, 2015, 12:08am

OK, I found your apt repository. I got that set up and the installation seemed successful, but upon reboot I’m still running my original 3.18 according to uname -a.

Any thoughts?

RobertCNelson · January 19, 2015, 1:46am

Sorry, it's not that simple on the older rootfs.. it only works with
rootfs from around Sep 2014 and later..

You have to manually update /boot/uboot/* with the files that are now
under: /boot/

Regards,

Axel_Barkow · January 29, 2015, 7:51am

Hi,

I’m trying to suspend/resume my BBB based on GPIO input. I’m using Kernel 3.14.29-ti-r46 and suspending with “echo mem > /sys/power/state” works. I can also wake up the BBB via the serial console. From what I found on the internet it should be possible to wake the BBB also from GPIO0, but a level change on GPIO0_x (I tried 7 and 26) doesn’t show any effect.
Does anybody know what I need to configure to wake up the BBB from GPIO?

Regards

Axel

mjmcclary · April 28, 2015, 1:34am

OK, I found your apt repository. I got that set up and the installation seemed successful, but upon reboot I’m still running my original 3.18 according to uname -a.

I am trying to install that kernel and have not found the repository. Could you tell me where it is?

I though I’d found and added it. My /etc/apt/sources.list is currently:

deb Index of /ubuntu-ports trusty main universe multiverse
deb-src Index of /ubuntu-ports trusty main universe multiverse

deb Index of /ubuntu-ports trusty-updates main universe multiverse
deb-src Index of /ubuntu-ports trusty-updates main universe multiverse
deb [arch=armhf] Index of /debian wheezy main
#deb-src [arch=armhf] Index of /debian wheezy main

but this gives me:

E: Unable to locate package linux-image-3.14.26-ti-r44
E: Couldn’t find any package by regex ‘linux-image-3.14.26-ti-r44’

So I’m wondering if I installed the wrong repository or if it just got broken
as part of the EOLing.

michael

RobertCNelson · April 29, 2015, 1:39pm

OK, I found your apt repository. I got that set up and the installation
seemed successful, but upon reboot I'm still running my original 3.18
according to uname -a.

I am trying to install that kernel and have not found the repository. Could
you tell me where it is?

I though I'd found and added it. My /etc/apt/sources.list is currently:

deb Index of /ubuntu-ports trusty main universe multiverse
deb-src Index of /ubuntu-ports trusty main universe
multiverse

deb Index of /ubuntu-ports trusty-updates main universe
multiverse
deb-src Index of /ubuntu-ports trusty-updates main universe
multiverse
deb [arch=armhf] Index of /debian wheezy main
#deb-src [arch=armhf] Index of /debian wheezy main

Umm... trusty is available..

github.com

rcn-ee/repos/blob/master/README.md

Debian 10: (buster): http://repos.rcn-ee.com/debian/
```
deb [arch=armhf] http://repos.rcn-ee.com/debian/ buster main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ buster main
```

Debian 11: (bullseye): http://repos.rcn-ee.com/debian/
```
deb [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main
```

Ubuntu 18.04 lts: (bionic): http://repos.rcn-ee.com/ubuntu/
```
deb [arch=armhf] http://repos.rcn-ee.com/ubuntu/ bionic main
#deb-src [arch=armhf] http://repos.rcn-ee.com/ubuntu/ bionic main
```

Ubuntu 20.04 lts: (focal): http://repos.rcn-ee.com/ubuntu/
```

This file has been truncated. show original

deb [arch=armhf] Index of /ubuntu trusty main
#deb-src [arch=armhf] Index of /ubuntu trusty main

but this gives me:

E: Unable to locate package linux-image-3.14.26-ti-r44
E: Couldn't find any package by regex 'linux-image-3.14.26-ti-r44'

So I'm wondering if I installed the wrong repository or if it just got
broken
as part of the EOLing.

It's a space issue with weekly kernel image updates, i only keep "10"
kernel release per channel.. So today use:

sudo apt-get update ; sudo apt-get install linux-image-3.14.39-ti-r61
; sudo reboot

Regards,