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

    Command line unresponsive after exit Emulationstation

    Scheduled Pinned Locked Moved Help and Support
    raspianemulatistationcommand line
    7 Posts 4 Posters 1.5k 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.
    • Meneer JansenM
      Meneer Jansen
      last edited by

      • Pi Model: Pi 1B+
      • RetroPie Version Used: 4.3.11
      • Built From: script atop on Raspbian 9 Stretch
      • Error messages received: none
      • Log found in /dev/shm/runcommand.log (if relevant): link pastebin
      • Guide used: this here topic and the doc from the Retropie website and the compatibility list
      • Emulator: all N64 emu's tried (gles, rice, you name it)

      As everybody knows, one can exit Emulationstation w/ the F4 button on your keyboard. However, after certain emulators crashed (N64, PSX, Macintosh) then I cannot do anything anymore on the command line. I can see the prompt on my television and I can reboot the Pi via SSH but the Pi does not take any input from the command line. Is this a problem of Raspbian or of Emulationstation??

      Avid Linux user.

      rbakerR mituM 2 Replies Last reply Reply Quote 0
      • rbakerR
        rbaker @Meneer Jansen
        last edited by

        @meneer-jansen Is stretch fully supported yet? or is it still in beta?

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

          @meneer-jansen More likely a Raspbian/config issue. Stretch support is still in testing, so bugs could still creep in. Can you post your config.txt file ? Do you run any commands within the onstart/onend scripts that change the resolution/framebuffer settings ?

          1 Reply Last reply Reply Quote 0
          • Meneer JansenM
            Meneer Jansen
            last edited by

            @RBaker and @Mitu: I didn't know that Debian Stretch wasn't fully supported yet Bummer. I installed it the "official" way via https://www.raspberrypi.org/downloads/raspbian. The only Rasbpian version one can download there is the Debian 9 Stretch version. According to https://www.debian.org/releases it's the current Stable release.

            My /boot/config.txt file:

            # For more options and information see
            # http://rpf.io/configtxt
            # Some settings may impact device functionality. See link above for details
            
            # uncomment if you get no picture on HDMI for a default "safe" mode
            #hdmi_safe=1
            
            # uncomment this if your display has a black border of unused pixels visible
            # and your display can output without overscan
            #disable_overscan=1
            
            # uncomment the following to adjust overscan. Use positive numbers if console
            # goes off screen, and negative if there is too much border
            #overscan_left=16
            #overscan_right=16
            #overscan_top=16
            #overscan_bottom=16
            overscan_left=-20
            overscan_right=-20
            overscan_top=-20
            overscan_bottom=-20
            
            # uncomment to force a console size. By default it will be display's size minus
            # overscan.
            #framebuffer_width=1280
            #framebuffer_height=720
            
            # uncomment if hdmi display is not detected and composite is being output
            #hdmi_force_hotplug=1
            
            # uncomment to force a specific HDMI mode (this will force VGA)
            hdmi_group=1
            hdmi_mode=1
            
            # uncomment to force a HDMI mode rather than DVI. This can make audio work in
            # DMT (computer monitor) modes
            #hdmi_drive=2
            
            # uncomment to increase signal to HDMI, if you have interference, blanking, or
            # no display
            config_hdmi_boost=4
            
            # uncomment for composite PAL
            #sdtv_mode=2
            
            #uncomment to overclock the arm. 700 MHz is the default.
            #arm_freq=800
            
            # Uncomment some or all of these to enable the optional hardware interfaces
            dtparam=i2c_arm=on
            dtparam=i2s=on
            dtparam=spi=on
            
            # Uncomment this to enable the lirc-rpi module
            dtoverlay=lirc-rpi
            
            # Additional overlays and parameters are documented /boot/overlays/README
            
            # Enable audio (loads snd_bcm2835)
            dtparam=audio=on
            gpu_mem_256=128
            gpu_mem_512=256
            gpu_mem_1024=256
            overscan_scale=1
            

            Only thing I changed in that config file it setting my pi to Overscan because other wise dispmanx games crash (topic) and I've set my Pi to VGA mode because then SNES games run at an acceptable rate.

            Avid Linux user.

            1 Reply Last reply Reply Quote 0
            • ClydeC
              Clyde
              last edited by

              I'll quote myself from here:

              Sometimes, I can free the keyboard by pressing Alt+PrtScr/SysRq+R simultaneously. It's a Linux Magic SysRq key combination that switches the keyboard from raw mode, which graphical programs tend to use, to XLATE mode. May be worth a try.

              Note that on some keyboards, Laptops etc. the key combination is slightly different. See the link above for the variations.

              Meneer JansenM 1 Reply Last reply Reply Quote 0
              • Meneer JansenM
                Meneer Jansen @Clyde
                last edited by

                @clyde said in Command line unresponsive after exit Emulationstation:

                I'll quote myself from here:

                Sometimes, I can free the keyboard by pressing Alt+PrtScr/SysRq+R simultaneously. It's a Linux Magic SysRq key combination that switches the keyboard from raw mode, which graphical programs tend to use, to XLATE mode. May be worth a try.

                Note that on some keyboards, Laptops etc. the key combination is slightly different. See the link above for the variations.

                Bloody hell! Hat trick here! Found me a keyb. w/ a print screen button, pressed alt + pr.scr. + r and bingo! Thanks man. :-)

                Avid Linux user.

                ClydeC 1 Reply Last reply Reply Quote 0
                • ClydeC
                  Clyde @Meneer Jansen
                  last edited by

                  @meneer-jansen My pleasure. :)

                  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.