Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

NES controller not working with New ControlBlock2 build



  • I am now able to compile and install the driver, however I do not get all buttons functionable anymore. I tried this on two different units that has been functioning with the exact same wiring before, so I am confident it's not a problem with wiring.

    pi@retropie:~ $ jstest /dev/input/js0
    Driver version is 2.1.0.
    Joystick (ControlBlock SNES Gamepad) has 2 axes (X, Y)
    and 8 buttons (BtnA, BtnB, BtnX, BtnY, BtnTL, BtnTR, BtnSelect, BtnStart).
    Testing ... (interrupt to exit)
    Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:off 4:on 5:on 6:on 7:off

    This is the output I get from jstest, and as seen here only button 3 (B on a NES controller) and 7 (Start on a NES controller) as well as the axes are responsive. The rest is in a constant "on"-mode.

    The /etc/controlblockconfig.cfg is edited to interpret the controllers as SNES-controllers and both units worked before trying to upgrade.

    It seems like the unit is also very slow in reaction but that could be the jstest command not registering very fast. I haven't moved forward to installing any games before the control-issues are solved. :)



  • @hravnkel said in NES controller not working with New ControlBlock2 build:

    I am now able to compile and install the driver, however I do not get all buttons functionable anymore. I tried this on two different units that has been functioning with the exact same wiring before, so I am confident it's not a problem with wiring.

    pi@retropie:~ $ jstest /dev/input/js0
    Driver version is 2.1.0.
    Joystick (ControlBlock SNES Gamepad) has 2 axes (X, Y)
    and 8 buttons (BtnA, BtnB, BtnX, BtnY, BtnTL, BtnTR, BtnSelect, BtnStart).
    Testing ... (interrupt to exit)
    Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:off 4:on 5:on 6:on 7:off

    This is the output I get from jstest, and as seen here only button 3 (B on a NES controller) and 7 (Start on a NES controller) as well as the axes are responsive. The rest is in a constant "on"-mode.

    The /etc/controlblockconfig.cfg is edited to interpret the controllers as SNES-controllers and both units worked before trying to upgrade.

    It seems like the unit is also very slow in reaction but that could be the jstest command not registering very fast. I haven't moved forward to installing any games before the control-issues are solved. :)

    Hi, I have exactly the same issue. The Controlblock worked perfectly until I upgraded my build with a Pi 3b+ and used the 4.4 Image (Previously Pi 3b & 4.3).


  • Global Moderator

    Strange, I will test this on my side with a complete hardware setup and fresh RetroPie 4.4!



  • Hi,
    Im using a old SNES case with Pi3 and Controlblock version 2.1 some time without any Problems.
    Now i also has a similar problem after updating Retropie from 4.3 to 4.4.

    After setting the controblock config to "SNES" Button 1 and 6 on controler port one (js0) are always "on". Controler port two (js1), Power switch and reset button works fine.

    Im made a few tests:

    • I've also testet it with a new Retropie 4.4 Image without update. Exact the same issue.
    • I'm also getting exact this signals without any wires on the controlblock beside the power switch.
    • I'm set the controlbock config to "arcade" according to the Tutorial to check all pins seperat - with success. The Hardware seems fine.

    I'm also noticed that the default controlblock.cfg has no "genesis" entry like the readme on github.

    I hope you can fix this problem.
    Thanks for all the great work.



  • I am having the EXACT same issue as Herzog.
    I actually performed the exact same tests as well before checking this thread, and had the exact same results.


  • Global Moderator

    There was a bug with a recently added additional virtual keyboard button, which is fixed now (finally). Sorry for this bug!

    You can attach any momentary buttons on Player 1 A or B. Pressing the buttons will lead to a simulated press of the ESC or the F1 key.



  • Thanks for your fast response! I will test it the next few days.



  • Thank you for the amazing turn around time! I reinstalled the driver, and everything is working perfect again.



  • Nope...
    After reinstallation of the driver I still have the same problem like Hravnkel.
    Setting: RPI 3b+, 4.4 Image, Controlblock2, SNES Controller.
    Gamepadtype is configured as "snes".
    The powerswitch function works well but if I want to configure the input just the "B" button is recognized...


  • Global Moderator

    Ok, I was able to reproduce your observation with NES controllers. I have fixed it a few minutes ago.

    There is now a dedicated NES gamepad type in the configuration: Use "nes" as gamepad type in /etc/controlblockconfig.cfg.



  • My problems are also gone. Thanks a lot!
    By the way, this time I used the Retropie-setup script to install the driver. Works fine.



  • Original poster here.

    I was able to install the latest driver using:
    wget -O - https://raw.githubusercontent.com/petrockblog/ControlBlockService2/master/install.sh | sudo bash

    I took me a while to understand the difference between US & UK keyboards to make the "|" (pipe) symbol. For those w/ US keyboards, use the lower right ALT + "~" (next to #1).

    I am struggling again w/ having and empty /ect/controlblockconfig.cfg file which is preventing me from setting the controller as NES or SNES.
    cd ControlBlockService2
    sudo nano /ect/controlblockconfig.cfg

    I can run jstest /dev/input/js0 and it shows driver 2.1.0 (same as before) and being set as arcade (I had switched it to SNES w/ the old driver back when I could open the config file).

    How do I get the /ect/controlblockconfig.cfg file to open again so I can edit it to NES now?


  • Global Moderator

    You can restore the original configuration file by running the install script again, e.g., by running sudo ./install.sh from within the ControlBlockService2 directory.


  • Global Moderator

    Also, the config file is located in the folder supplementary within the driver folder ControlBlockService2.



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.