GPIO controller gives me a sh: can't access tty; job control turned off
-
Run latest Recalbox v4 Beta on a Raspberry Pi 2 Had the pins already prepared, meaning connected with short cables. Soldered some extension cables to make it long enough to reach the joystick and buttons in my bartop. Now if I boot, it gives me a "sh: can't access tty; job control turned off". Adding disablesafemode in recovery.cmdline gives me at least the possibility to boot into recalbox. But running jstest gives me this picture: jstest /dev/input/js0 Driver version is 2.1.0. Joystick (GPIO Controller 1) has 2 axes (X, Y) and 9 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnThumbL, BtnThumbR, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 Buttons: 0:on 1:off 2:off 3:off 4:off 5:off 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:off 3:off 4:off 5:off 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:off 4:off 5:off 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:off 5:off 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:off 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6: Axes: 0: 0 1: 0 Buttons: 0:on 1:on 2:on 3:on 4:on 5:on 6:on 7:on 8:off Connecting a button gives no signal, meaning it does not switch from on to off or versa. What I already tried: Different SD card SD reformated an put on new NOOBS from Raspberry Site All GPIO connection unplugged Any ideas? Greetings Schnirpf
-
So if I got you right, you are wiring the buttons straight to the GPIO controller? Does it boot without anything connected to the GPIO and only not boot with the GPIO cables connected? Did you edit the recalbox.conf to enable the GPIO driver? Follow the wiring diagram and configuration protocols found here? https://github.com/recalbox/recalbox-os/wiki/Gamecon-controllers-(EN)
-
You are correct, I am wiring the buttons straight to the GPIO Controller. It does not boot anymore without or with anything connected. It did boot earlier with just a couple of cables connected to the Joystick and one button - and the button and Joystick worked. So this Situation is after I Extended the cables. I did edit the recalbox.conf and with jstest it shows up. Because it did work before with Joystick and one button, the Driver must be activated. I followed this Manual: https://github.com/recalbox/recalbox-os/wiki/GPIO-controllers-(EN). One more Thing. If I put disablesafemode in recovery.cmdline, then the pi boots into recalbox, but the Controller still does not work. Would it be possible, that only the GPIO part breaks?
-
Can you take a picture of how you wired it up? I think i might know what is going on. Is it permanently soldered into the GPIO or are you using a ribbon cable? Can you make sure your wiring matches this http://www.davesclassicarcade.com/vpinball/pics/switches.JPG I am curious because what I think is happening is you are soldered to the wrong connection on the microswitch telling the button it is always on which could mess with boot. But regardless let me just see a few pictures of how it is wired up. Possible to check for shorts? Do you have an extra sd card you can try putting a fresh copy of RBox on I would imagine something happened that messed up the config. Or you could try to recover it with noobs but I do not know how successfull that would be. A few buttons working, does not mean the driver was enabled unless your sure that you edited the system file c<span style="font-family: Consolas, 'Liberation Mono', Menlo, Courier, monospace; font-size: 13.6px; line-height: 21.76px; background-color: rgba(0, 0, 0, 0.0392157);">ontrollers.gpio.enabled=1 </span>
-
Big thanks for your help. But I gave up on this and will send the raspberry pi back. The cables weren't soldered directly to the pins and the actual problem is, that I even can not start up without connected GPIOs. I also checked any possible shorts on the GPIOs directly, but couldn't find any. Btw. after a while, the cpu gets really hot - that wasn't before. For me it seems to be defective. Again thank you very much for your help.
-
Great time to order a Raspberry Pi 3 then
-
Can you read minds?
