RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    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

    Can only press "a" to enter Runcommand menu one time per boot

    Scheduled Pinned Locked Moved Help and Support
    runcommand
    11 Posts 4 Posters 1.4k 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.
    • R
      rrdein
      last edited by rrdein

      I just started with RetroPie 4 days ago, and have reinstalled it 5 times so far. Every time I have a different problem, which is weird as I haven't really done all that much. On this current install I have installed Kodi, Desmume, Iceweasel (which CANNOT play Netflix), FreeCiv, and Quake 3. I've solved a lot of problems on this install and I'm really loathe to reinstall and do it all over again after having wasted so many free days on this.

      My problem is very simple. I boot, go to any game, run it, and press "a" to enter runcommand. Then I launch the game, exist, and try to repeat. However, on repeat pressing "a" does nothing and it boots to the game. It doesn't matter which game I try first or second, the first one always works and the second one always doesn't. This always worked in every previous attempt up until now, both in this install and previous installs.

      I want to add that I've read you are supposed to press '0', but I think this is probably someone's imagination or something, because I was told to press 'a', and 'a' is what works on my keyboard.


      Pi Model or other hardware: Pi 3 Model B
      Power Supply Used: 2.5A power supply
      RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): Linux retropie 4.4.47v7-aufs (release info from uname -a)
      Built From: BerryBoot
      USB Devices connected: 500GB Clickfree USB HDD (working find)
      Controller used: Rii keyboard/touchpad
      Error messages received: none
      Log found in /dev/shm/runcommand.log (if relevant) (I SHOULD MENTION THIS LOG WAS EMPTY UNTIL THIS BOOT WHEN I STARTED MESSING AROUND WITH IT SOME MORE):

      Parameters:
      Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-v$


      | / |_ _ _ __ ___ _ __ / /_ | || | | _ | |_ _ ___
      | |/| | | | | '_ \ / _ \ '_ | '_ | || || |) | | | | / |
      | | | | || | |) | / | | | (_) | | __/| | || _

      || ||_,| .
      / _|| ||_/ || || ||_,|/
      |
      | http://code.google.com/p/mupen64plus/
      Mupen64Plus Console User-Interface Version 2.5.0

      UI-Console: attached to core library 'Mupen64Plus Core' version 2.5.0
      UI-Console: Includes support for Dynamic Recompiler.
      Core: Goodname: 1080 Snowboarding (E) (M4) [!]
      Core: Name: 1080 SNOWBOARDING
      Core: MD5: 632C98CF281CDA776E66685B278A4FA6
      Core: CRC: 58FD3F25 D92EAA8D
      Core: Imagetype: .v64 (byteswapped)
      Core: Rom size: 16777216 bytes (or 16 Mb or 128 Megabits)
      Core: Version: 1449
      Core: Manufacturer: Nintendo
      Core: Country: Europe (0x50)
      UI-Console Status: Cheat codes disabled.
      UI-Console: using Video plugin: 'GLideN64' v2.0.0
      UI-Console: using Audio plugin: 'Mupen64Plus OMX Audio Plugin' v2.0.0
      Input Error: Couldn't find config file 'InputAutoCfg.ini'
      Input Warning: missing 'plugged' parameter from config section AutoConfig0. Set$
      Input Warning: missing 'plugin' parameter from config section AutoConfig0. Sett$
      Input Warning: missing config key 'DPad R' for controller 1 button 0
      Input Warning: missing config key 'DPad L' for controller 1 button 1
      Input Warning: missing config key 'DPad D' for controller 1 button 2
      Input Warning: missing config key 'DPad U' for controller 1 button 3
      Input Warning: missing config key 'Start' for controller 1 button 4
      Input Warning: missing config key 'Z Trig' for controller 1 button 5
      Input Warning: missing config key 'B Button' for controller 1 button 6
      Input Warning: missing config key 'A Button' for controller 1 button 7
      Input Warning: missing config key 'C Button R' for controller 1 button 8
      Input Warning: missing config key 'C Button L' for controller 1 button 9
      Input Warning: missing config key 'C Button D' for controller 1 button 10
      Input Warning: missing config key 'C Button U' for controller 1 button 11
      Input Warning: missing config key 'R Trig' for controller 1 button 12
      Input Warning: missing config key 'L Trig' for controller 1 button 13
      Input Warning: missing config key 'Mempak switch' for controller 1 button 14
      Input Warning: missing config key 'Rumblepak switch' for controller 1 button 15
      Input Warning: missing config key 'X Axis' for controller 1 axis 0
      Input Warning: missing config key 'Y Axis' for controller 1 axis 1
      UI-Console: using Input plugin: 'Mupen64Plus SDL Input Plugin' v2.5.0
      UI-Console: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP Plugin$
      Core Warning: Fallback for Video plugin API (02.02.00) < 2.2.0. Resizable video$
      Input: 0 SDL joysticks were found.
      Input: N64 Controller #1: Forcing default keyboard configuration
      Input Error: Couldn't find config file 'InputAutoCfg.ini'
      Input Warning: missing 'plugged' parameter from config section AutoConfig0. Set$
      Input Warning: missing 'plugin' parameter from config section AutoConfig0. Sett$
      Input Warning: missing config key 'DPad R' for controller 1 button 0
      Input Warning: missing config key 'DPad L' for controller 1 button 1
      Input Warning: missing config key 'DPad D' for controller 1 button 2
      Input Warning: missing config key 'DPad U' for controller 1 button 3
      Input Warning: missing config key 'Start' for controller 1 button 4
      Input Warning: missing config key 'Z Trig' for controller 1 button 5
      Input Warning: missing config key 'B Button' for controller 1 button 6
      Input Warning: missing config key 'A Button' for controller 1 button 7
      Input Warning: missing config key 'C Button R' for controller 1 button 8
      Input Warning: missing config key 'C Button L' for controller 1 button 9
      Input Warning: missing config key 'C Button D' for controller 1 button 10
      Input Warning: missing config key 'C Button U' for controller 1 button 11
      Input Warning: missing config key 'R Trig' for controlGenerated a 884 x 18 (15 $
      /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 292: 2215 Segmentation fault SDL_VIDEO_RPI_SCALE_MODE=1 "$rootdir/emulators/mupen64plus/bin/mupen64plus" --noosd --windowed $RES --rsp ${RSP_PLUGIN}.so --gfx ${VIDEO_PLUGIN}.so --audio ${AUDIO_PLUGIN}.so --configdir "$configdir/n64" --datadir "$configdir/n64" "$ROM"

      Guide used: (Mention if you followed a guide) (DIDN'T USE A GUIDE, BUT USED FORUMS FOR TROUBLESHOOTING, CAN'T REMEMBER)
      File: N/A
      Emulator: ALL
      Attachment of config files: I do not know which ones you want, but let me know specifically and I will provide them. Possibly worth noting I am using overclock settings in config.txt, but that is not what caused the problem (at least, it was working afterward, until last night).

      How to replicate the problem: I am not sure how another person could replicate the problem.

      edmaul69E meleuM 2 Replies Last reply Reply Quote 0
      • edmaul69E
        edmaul69 @rrdein
        last edited by

        @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.

        R 1 Reply Last reply Reply Quote 0
        • R
          rrdein @edmaul69
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • R
            rrdein
            last edited by

            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".

            BuZzB 1 Reply Last reply Reply Quote 0
            • BuZzB
              BuZz administrators @rrdein
              last edited by BuZz

              @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.

              To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

              1 Reply Last reply Reply Quote 0
              • meleuM
                meleu @rrdein
                last edited by

                This reminded me a video @obsidianspider posted recently:

                • Useful topics
                • joystick-selection tool
                • rpie-art tool
                • achievements I made
                1 Reply Last reply Reply Quote 2
                • R
                  rrdein
                  last edited by

                  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?

                  BuZzB 1 Reply Last reply Reply Quote -1
                  • BuZzB
                    BuZz administrators @rrdein
                    last edited by

                    @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.

                    To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                    1 Reply Last reply Reply Quote 0
                    • R
                      rrdein
                      last edited by

                      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.

                      BuZzB 1 Reply Last reply Reply Quote 0
                      • BuZzB
                        BuZz administrators @rrdein
                        last edited by

                        @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.

                        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                        1 Reply Last reply Reply Quote 0
                        • R
                          rrdein
                          last edited by

                          I understand, thank you. Sorry for being rude.

                          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.