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

    Keyboard input loss: tty1

    Scheduled Pinned Locked Moved
    Help and Support
    keyboard tty tty1 terminal cli
    4
    7
    644
    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.
    • EfriimE
      Efriim
      last edited by Efriim

      I have been having this issue for a while, and realizing I'm never going to figure it out on my own finally will ask for help.

      • Raspberry Pi 3 B+ w/ Generic Power Supply & MegaPi Case
      • RetroPie 4.4 image updated to 4.4.11
      • Logitech Unity Nano Transceiver w/ keyboard and mouse

      The thing is exiting to tty1 via f4; the terminal will stop taking input from the keyboard, unable to type or switch to tty2.

      This happens sometimes I don't know what causes it. Exiting ES via F4, using dosbox or some other non-libretro emulators sometimes the runcommand will bug out.

      Resetting the Transceiver or keyboard doesn't help, plugging in a usb keyboard doesn't help either.
      What should I do?

      1 Reply Last reply Reply Quote 1
      • EfriimE
        Efriim
        last edited by

        Similarly different.

        When a controller gets disconnected in most sdl apps and other emulators there will be no more response when it is reconnected. Is there a way to get the controls to persist? Is this an error?

        mituM 1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator @Efriim
          last edited by

          @Efriim said in Keyboard input loss: tty1:

          When a controller gets disconnected in most sdl apps and other emulators there will be no more response when it is reconnected

          Not quite true - just unplug the gamepad while you're in Emulationstation, then plug it back, it will work again without needing to restart the application. ES uses SDL exclusively for gamepad/joystick control.

          EfriimE 1 Reply Last reply Reply Quote 0
          • EfriimE
            Efriim @mitu
            last edited by

            @mitu
            Then the problem is somewhere else. What I am trying to describe is in a game like reicast or scummvm, after my controller times-out or disconnects and when I reconnect it the input won't work again. I can't use the shortcut hotkey to exit and there is no way to save my game, but I can press the reset button on my case to exit.

            quicksilverQ 1 Reply Last reply Reply Quote 0
            • quicksilverQ
              quicksilver @Efriim
              last edited by quicksilver

              @Efriim I have noticed this behavior as well. Seems to happen only with non-retroarch emulators. Mupen64plus and Reicast I have noticed specifically. If my wireless xbox 360 controller goes to sleep, upon turning it back on, all hotkeys are no longer functional and I have to use a keyboard to exit the game.

              hostolisH 1 Reply Last reply Reply Quote 0
              • hostolisH
                hostolis @quicksilver
                last edited by hostolis

                If you connect with VNC, does it let you type?

                EfriimE 1 Reply Last reply Reply Quote 0
                • EfriimE
                  Efriim @hostolis
                  last edited by

                  @hostolis
                  Yes, vnc works, I just tried.

                  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.