Can only press "a" to enter Runcommand menu one time per boot
-
@rrdein a isnt correct. It says press a button not the a button. You need to press whatever button is button 0 on your controller and x is the correct button on the keyboard. It may have changed adding other buttons on the keyboard but x should work correctly.
-
Dude I don't know what to tell you, but I have a Rii controller and a Logitech K400r, and the correct input is "a" on both keyboards. 0 does not work. These are standard keyboard layouts. "a" works, and "0" does not, so that is clearly not the solution. I cannot account for any different impressions other people have of what the key should be, but the correct key on both of my keyboards is "a", and it only works once, as described in the OP.
-
So, I want to be real clear on this. The correct key for both of my keyboards is "a". If someone wants to go around saying the Pi interprets this is a zero or something that is fine by me. I've tried it with "0" and it has never ever worked. On my system it is "a". This is not relevant to the problem. My problem is that, after entering runcommand once, I am not able to enter it again without rebooting. I am hoping that there is someone who understands runcommand enough to advise me on why this is happening. Anyone who reads the OP can see that my problem is not one of "pushing the wrong button".
-
@rrdein no. 0 works fine - it responds to any normal keyboard character press.
Please use a standard RetroPie image rather than the BerryBoot images - There are various problems using berryboot and the images are not supported. eg for example the screen blanker kicking in.
-
This reminded me a video @obsidianspider posted recently:
-
Ok so, I guess I was wrong and 0 does work (as well as "a"). My problem is the same though. So there's no way to diagnose this, I just have to try another image? What would you tell me to try if I wasn't using Berryboot?
-
@rrdein said in Can only press "a" to enter Runcommand menu one time per boot:
So there's no way to diagnose this, I just have to try another image? What would you tell me to try if I wasn't using Berryboot?
Not sure I like that attitude.
I would help debug it - I want to rule out something related to Berryboot first.
-
I'm downloading the image, but once I install it the opportunity to diagnose the issue is gone, because the Berryboot rom does not have this issue out of the box.
-
@rrdein I won't diagnose it on Berryboot - I don't want to support it. It says that on the Download page. The Berryboot images were provided on request, but it's not something I support directly.
I cannot reproduce your set-up on Berryboot to verify an issue. I don't use it and don't have it set up. Also since berryboot shares a Kernel between the various OSes it makes it harder to replicate an issue than on a set RetroPie image.
If this is a problem, I am happy to leave this and help other users instead.
-
I understand, thank you. Sorry for being rude.
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.