"buttons" process on stock Tomato 1.28?

Discussion in 'Tomato Firmware' started by nsap, Dec 4, 2011.

  1. nsap

    nsap Addicted to LI Member

    Does this process simply monitor for the SES/AOSS button to be pushed? Is it safe to kill?
  2. nsap

    nsap Addicted to LI Member

  3. tueftl

    tueftl Serious Server Member


    I had the same question this week and found (in /proc/*PID*/fd/) that the "buttons" process also had a handle to /dev/nvram, so I decided it would be to much risk to kill it.

    Also this process several times logged someone had pushed the SES button - which is physically not there... So I began to search how to get rid of this process.

    The source code ("buttons.c" etc.) turned out that there are some bugs. My nvram always has the two variables "btn_override=" and "btn_reset=", but without values (check by "nvram show|grep btn"). This is not interpreted correctly by "buttons" in a way that GPIO bit 0 was the reset button. But there is a condition at the process initialization where it terminates because it thinks there is nothing to do. This way it is safe to get out and optimal if there is neither a SES nor a reset button on the router.

    What to do:
    1. Open a console session (perhaps enable SSH in admin interface prior).
    2. Check the existing values in nvram regarding buttons: "nvram show|grep btn"!
    3. "nvram set btn_override=1"
    4. "nvram set btn_reset=16"
    5. "nvram commit"
    6. Reboot the device, next time there will be no more "buttons" process.
    The value 16 (generally all values that have any bit of 0xffffff70 set) is interpreted as "invalid", so "there is no reset button". The "btn_reset" variable is read only if "btn_override" !=0.

    nsap likes this.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice