BBB + debian-8.4-iot-4gb + battery = SHUTDOWN

49 views
Skip to first unread message

peppeiron

unread,
Jul 26, 2016, 10:40:01 AM7/26/16
to BeagleBoard
Hello everybody,

root@beaglebone:/# uname -a
Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux

My board is powered by 5V and is connected to a battery for use by backup/ups/safe_shutdown. When I take off the power supply, the board goes off in a few seconds,
without switching to battery.
I can not understand why not switch to battery.
I note that the board works perfectly if powered only by a battery.
the problem arises only when there is no 5V.
I can not find the service that manages the shutdown.

Is there a way to avoid this behavior by software??

Thanks

William Hermans

unread,
Jul 27, 2016, 1:02:44 AM7/27/16
to beagl...@googlegroups.com
$ sudo apt-get remove acpid should do the trick.

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3f60e9aa-9d22-4a11-b37e-10efbc3182c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

peppeiron

unread,
Jul 27, 2016, 3:40:50 AM7/27/16
to BeagleBoard
I thank you for the answer,
unfortunately in this kernel version and this version of debian,
the acpid service is no longer running, so the problem remains.
It will be due to some other service.
any other ideas?

William Hermans

unread,
Jul 27, 2016, 3:46:48 AM7/27/16
to beagl...@googlegroups.com
So, if you're running Jessie, there may be some other kind of service I'm currently unaware of handling these same duties. Which exactly, I'm not sure. But this could also be another difference between the *TI*, and *bone* kernels.

There was some discussion on this a few month back, it's possible someone from TI decided to implement new code within the kernel to handle this ?

Reply all
Reply to author
Forward
0 new messages