@Zerog As you know before v0.1.7 b142 reboot did not work at all. For example @Mikael-Djurfeldt wrote on 7 Jan 2017, 18:25 When I try to reboot the system using the command reboot, I get a shutdown instead, and have to use the physical switch to power-cycle in order to start the Omega2 again. @Lazar-Demin wrote on 13 Jan 2017, 05:30 in Omega2 reboot Reboot is fixed as of b142, changelog coming soon Since then reboot works but halt or poweroff also reboots Omega2(+). @Lazar-Demin wrote on 17 Jan 2017, 23:22 The nature of the kernel patch to enable rebooting seems to have this side-effect... How essential are the halt or poweroff commands for your workflows? Btw, I will be submitting a Pull Request to LEDE for the reboot kernel patch soon, will update you when it's in. I think he has already done this... [Resolved] ?! PS. reboot works on 0.1.10 b160 - please check it again.

@Igor-Silenock I have observed the same behavior with several Omegas2+. That is incomplete, halted boots when powered by 3.3V, then a successful boot when the power was increased to 3.4V. I did wonder if the digital meter on my bench power supply is accurate ... my VOM says it is, but in both cases this is measure of the least significant digit.

For anyone having the same issue, I believe I solved the issue after some tweaking. The issue seems to be that I wasn't setting pin 3 to be input before trying to read from it. Adding the line os.system("gpioctl dirin 3") solved the crashing issue. Alternatively you could replace gpioctl dirin 3 with fast-gpio set-input 3. I'm a little concerned that the error wasn't handled better. I don't know if that fault is on Python or my Omega2, though. Anyways, happy coding everyone!

The hardware simply does not have any poweroff capability, nor would any system based on a router chipset be likely to unless additional parts were added specifically for that purpose. What would be possible at some point is a halt - there are ways in which the flash access mode reset bug on the 2+ can sort of resemble one.