Running build 10 on a raspberry pi 2 no overclocking harddisk connected for 'share' Changed to a new raspberry pi 2 and booted like my "old" one, but couldn't get the harddisk to work. The harddisk showed up in the system setting, but with 0GB. The harddisk is listed as share in /boot/recalbox-boot.conf as: sharedevice=DEV a95f5d3d-4678-4d04-946d-ae9f7b57e680 I added 'sleep 5' to the /etc/init.d/S31emulationstation, so the harddisk has enough time to spin up. The weird thing is, most of the time it is not starting from the harddisk. So 'share' is on the sd card, but system setting still shows the harddisk as storage device. I can access the harddisk as /media/usb0. If I change something in the system settings it boots an starts from harddisk and everything is fine. After another reboot or two, again the same problem. Any suggestion? Thanks in advanced. Update: Had to rename the folder /recalbox on my harddisk, otherwise the system gets messed up. So just moved all the roms to the newly created folder /recalbox and everything is up and running like it should:-)
Latest posts made by schnirpf
-
[solved] [4.0.0] Booting from harddisk doesn't always work
-
RE: More than 20 minutes to turn off Recalbox
Had the same problem (not 20 minutes, rather 10 minutes) with Recalbox 4.0 beta, alot of roms and external HD. Delete images folders and gamelist.xml and let emulationstation create the gamelist.xml or wait the amount of time to shutdown. I couldn't find another solution.
-
RE: GPIO controller gives me a sh: can't access tty; job control turned off
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.
-
RE: GPIO controller gives me a sh: can't access tty; job control turned off
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?
-
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