RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    ControlBlock service won't start with v1.6 board

    Scheduled Pinned Locked Moved ControlBlock, PowerBlock & Co.
    controlblockinstall error
    15 Posts 2 Posters 1.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      petrockblog Global Moderator
      last edited by

      Also, you can call controlblock service from within the build directory directly. That should also give you an error output.

      1 Reply Last reply Reply Quote 0
      • E
        EmbeddedMan
        last edited by

        OK, those are great suggestions. The commands "make", "sudo make install", "sudo make installservice" all run just fine with zero errors or warnings of any type.

        The I2C interface was not enabled (at least according to raspi-config), so I enabled it, and then rebooted. Still "service --status-all" showed that controlblockservice was not started. So that didn't work. (Note that "sudo make installservice" reported : "Making sure that the ARM I2C Interface is enabled via /boot/config.txt . . ." even though the I2C interface was not turned on when I ran it.

        When I ran "sudo controlblock" from the build directory I got no error messages of any type. I just got the following:

        [ControlBlock] Gamepadtype = ARCADE gamepads
        [ControlBlock] Single gamepade mode DEACTIVATED
        [ControlBlock] Shutdown is ACTIVATED

        Any other ideas?

        E 1 Reply Last reply Reply Quote 0
        • E
          EmbeddedMan @EmbeddedMan
          last edited by

          @EmbeddedMan @petrockblog Any other ideas for what things to check? I'm an embedded C guy, and Linux isn't my primary environment so I'm not exactly sure what to check next.

          1 Reply Last reply Reply Quote 0
          • P
            petrockblog Global Moderator
            last edited by

            Sorry for this delayed reply.

            I would start and step-by-step go through the non-quick installation steps that are described at https://github.com/petrockblog/ControlBlockService/blob/master/README.md

            it would be interesting to see at which of the step something goes wrong.

            E 1 Reply Last reply Reply Quote 0
            • P
              petrockblog Global Moderator
              last edited by

              Thinking about it — if you can start the controlblock service manually with ‘controlblockservice &’, you should be able to see test the controlblock with the jstest tool as described at https://github.com/petrockblog/ControlBlockService2/blob/master/README.md#troubleshooting (that also works works with the ControlBlock 1.x).

              E 1 Reply Last reply Reply Quote 0
              • E
                EmbeddedMan @petrockblog
                last edited by

                @petrockblog said in ControlBlock service won't start with v1.6 board:

                Sorry for this delayed reply.

                I would start and step-by-step go through the non-quick installation steps that are described at https://github.com/petrockblog/ControlBlockService/blob/master/README.md

                it would be interesting to see at which of the step something goes wrong.

                And, unfortunately, when I do this, I get the exact same result as what I've listed above and in the GH issue. There are no error messages until the very end when I get

                [ERROR] The ControlBlock service is not running

                That's it.

                *Brian

                E 1 Reply Last reply Reply Quote 0
                • E
                  EmbeddedMan @petrockblog
                  last edited by

                  @petrockblog When I type "controlblockservice &" on the command line, I get "-bash: controlblockservice: command not found" error. Is there some specific directory I need to be in to run the service that way?

                  E 1 Reply Last reply Reply Quote 0
                  • E
                    EmbeddedMan @EmbeddedMan
                    last edited by

                    @petrockblog I found the controlblockservice script : in /etc/init.d/controlblockservice. When I do "sudo /etc/init.d/controlblockservice &", I don't get any error message (just "[1] 690") but then the next command that I type (no matter what it is) I get "[1]+ Done sudo /etc/init.d/controlblockservice" which I think means that the service started but then immediately exited?

                    1 Reply Last reply Reply Quote 0
                    • E
                      EmbeddedMan @EmbeddedMan
                      last edited by

                      @petrockblog Well, I think I've found something : /usr/local/bin is completely empty. The service script (controlblockservice) exits immediately after executing this line:

                      [ -x "$DAEMON" ] || exit 0

                      And since $DAEMON is /usr/local/bin/controlblockservice, it exits.

                      So why does the 'install' process not generate any errors for me (either using the install.sh script, or doing it all manually) but yet it doesn't copy anything over into /user/local/bin?

                      1 Reply Last reply Reply Quote 0
                      • E
                        EmbeddedMan
                        last edited by

                        @petrockblog It appears that I can get the service running by commenting out the line "[ -x "$DAEMON" ] || exit 0" and then starting the service. This also allows the service to run on boot.

                        So, why does this line need to be commented out? I'm confused why this would work for everyone else and not my setup (even though I started from a completely fresh RetroPi 4.5).

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                        Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.