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

    RPI no controls work and freezes if I launch a game immediately after boot (mame2003 or advmame1.4)

    Scheduled Pinned Locked Moved Help and Support
    mame2003advmame 1.4freezingblack screen
    5 Posts 3 Posters 793 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.
    • stoney66S
      stoney66
      last edited by stoney66

      Pi Model or other hardware: 3 model B
      Power Supply used: Canakit 5v 2.5a
      RetroPie Version Used : 4.3 and 4.4
      Built From: Pre made image
      USB Devices connected: mini-pac
      Controller used: only mini-pac
      Error messages received: map: v102 => fb0
      Log found in /dev/shm/runcommand.log (if relevant): Nothing out of the norm
      Emulator: So far just mame2003 and advmame 1.4
      How to replicate the problem:
      This has been a problem for a while, both on 4.3 and 4.4 (both pre-made image). When I boot up the system if I launch a game immediately none of the buttons work (coin, start etc), once I press the combo keys to exit the game the screen goes black, there is a message in top left corner map: v102 => fb0. I can hear the game playing but the screen is still black, if I try and exit again then all is silent and no keys work. (I can still ssh in and reboot it though the reboot hangs). If I wait about 15 seconds once the system boots before starting a game, its always fine. So far I only see this with mame2003 and advmame1.4, I tried Atari2600 (lr-stella) and it's fine. I will try some others later.

      I notice that when I launch a game and the Retropie screen shows up, thats means it's not going to work. When I see the normal screen "Launching XXX (advmame1.4) then I know it's going to work. For the last year or so I've just waited to launch after bootup, finally getting around asking for help :) Maybe the fix is just to keep waiting, or put a delay for ES on startup, seems like the system hasnt fully booted when I launch a game.

      mediamogulM mituM 2 Replies Last reply Reply Quote 0
      • mediamogulM
        mediamogul Global Moderator @stoney66
        last edited by

        @stoney66 said in RPI no controls work and freezes if I launch a game immediately after boot (mame2003 or advmame1.4):

        I notice that when I launch a game and the Retropie screen shows up, thats means it's not going to work.

        Can you elaborate on what this "RetroPie screen" is? Also, was your pre-made image obtained from this website or a third party?

        RetroPie v4.5 • RPi3 Model B • 5.1V 2.5A PSU • 16GB SanDisk microSD • 512GB External Drive

        1 Reply Last reply Reply Quote 0
        • stoney66S
          stoney66
          last edited by stoney66

          @mediamogul it's the same retropie screen that you get on first bootup with the controller pie logo. It's the pre-made image from this website.

          It looks like its only specific roms, e.g. 1941/1942 do not have an issue but Berzerk and Galaga do. 1941/1942 still show the retropie bootup screen like berzerk/galaga but then they will switch to showing the normal Launching 1941 screen right after. Berzerk and Galaga never show that (unless I wait 10-15 seconds before launching after bootup).

          It's really really odd.. It's not a huge deal, I'm accustomed to just waiting a few seconds... usually I'll bootup, grab a beer and it's good to go by then :)

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

            @stoney66 Are you running your ROMs from an external driver or a mapped network share ? What screen are you using ? The map: v102 => fb0 message is not an error, just an info message.
            Have you modified the default config.txt and enabled the experimental OpenGL driver ?

            1 Reply Last reply Reply Quote 0
            • stoney66S
              stoney66
              last edited by

              @mitu na all roms are running on the sd card, 32GB sandisk. I have a few of them that I cycle through during updates etc. All of them have shown the same behavior. I haven't changed default config.txt.

              I'm using an LCD monitor with hdmi, not sure if that was the screen question :)

              Also the map message only happens with Galaga so far, Berzerk does not show that it just completely freezes, screen does not go black like Galaga does.

              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.