Resolved (sorta): Omega2+ ignores reboot command (on latest firmware 0.1.10 b160)



  • I've tried everything I can think of, including downgrading and upgrading back and forth between 0.1.9 and 0.1.10 several times, firstboot -y, so on and so forth. After my latest fresh firmware flash, I can do this:

    Using username "root".
    root@192.168.3.1's password:
    
    
    BusyBox v1.26.2 () built-in shell (ash)
    
       ____       _             ____
      / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
     / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
     \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
     W H A T  W I L L  Y O U  I N V E N T ? /___/
     -----------------------------------------------------
       Ω-ware: 0.1.10 b160
     -----------------------------------------------------
    
    root@Omega-0AC3:~# oupgrade --check
    > Device Firmware Version: 0.1.10 b160
    > Checking latest version online...
    > Repo Firmware Version: 0.1.10 b160
    > Comparing version numbers
    > Device firmware is up to date!
    root@Omega-0AC3:~# df -h
    Filesystem                Size      Used Available Use% Mounted on
    /dev/root                 5.5M      5.5M         0 100% /rom
    tmpfs                    61.4M     88.0K     61.3M   0% /tmp
    /dev/mtdblock6           25.1M      2.0M     23.1M   8% /overlay
    overlayfs:/overlay       25.1M      2.0M     23.1M   8% /
    tmpfs                   512.0K         0    512.0K   0% /dev
    root@Omega-0AC3:~# reboot
    root@Omega-0AC3:~# Why am I still running?
    -ash: Why: not found
    root@Omega-0AC3:~#
    

    Any help would be greatly appreciated.



  • Mine on same fw works:-

    '# which reboot
    '/sbin/reboot
    '# dir /sbin/reboot
    'lrwxrwxrwx 1 root root 14 Feb 2 2017 /sbin/reboot -> ../bin/busybox*
    '# md5sum /bin/busybox
    'ea6470f444af811d7866f825e27bfb54 /bin/busybox



  • @Paul-Beach
    Please try
    busybox reboot
    or
    /bin/busybox reboot



  • Thank you all for the replies. I've tried your suggestions and everything checks out ok, but it still will not reboot.

    Additionally, if I run "reboot -f" it will reboot the system, however there's a tendency for any changes I've made that session to be lost if I do that (e.g., if I run "opkg install python-light" and then "reboot -f", when it comes back up that package is no longer installed!).

    Using username "root".
    root@192.168.3.1's password:
    
    
    BusyBox v1.26.2 () built-in shell (ash)
    
       ____       _             ____
      / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
     / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
     \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
     W H A T  W I L L  Y O U  I N V E N T ? /___/
     -----------------------------------------------------
       Ω-ware: 0.1.10 b160
     -----------------------------------------------------
    root@Omega-0AC3:~# which reboot
    /sbin/reboot
    root@Omega-0AC3:~# ls -la /sbin/reboot
    lrwxrwxrwx    1 root     root            14 Feb  2  2017 /sbin/reboot -> ../bin/busybox
    root@Omega-0AC3:~# md5sum /bin/busybox
    ea6470f444af811d7866f825e27bfb54  /bin/busybox
    root@Omega-0AC3:~# busybox reboot
    root@Omega-0AC3:~# /bin/busybox reboot
    root@Omega-0AC3:~# Nope, still running.
    -ash: Nope,: not found
    root@Omega-0AC3:~#
    


  • Annoyingly, I think I've resolved this by noticing another issue that was resolved in this thread: http://community.onion.io/topic/1902/wifimanager-over-90-cpu-usage-omega2p/5

    I saw that wifimanager was using a lot of CPU. After disabling it, the CPU is normal and the reboot command operates normally.


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.