• 0 Votes
    4 Posts
    260 Views
    S

    @mitu I ran an update last night and the issue of the in-game menu causing the controller to become unresponsive until the select button is pressed has been fixed. I can now pull up the menu, take screenshots, save states, and return to the game without any problems.

    The issue with running the setup from within the RetroPie OS still remains. The workaround is to sudo ./retropie_setup.sh from the terminal.

  • 0 Votes
    1 Posts
    256 Views
    No one has replied
  • 0 Votes
    6 Posts
    2k Views
    E

    Hi, this also happens to me. No problems with Pi 3B+, but I just got a new Pi Zero W, and freezes all the time with RetroPie.

    I've tried this versions:

    Retropie 4.5.1 -> when it freezes I stil can do F5 in Web Manager and see the temperature, or sometines reboot with Putty if I already had one session opened. And one of those times, Putty threw this when it froze:

    pi@retropie:~ $ Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.163849] Internal error: Oops: 837 [#1] ARM Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167201] Process emulationstatio (pid: 681, stack limit = 0xcebb6188) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167355] Stack: (0xcebb7fa8 to 0xcebb8000) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167463] 7fa0: be82d520 00000001 be82d520 00000001 00000000 00000003 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167653] 7fc0: be82d520 00000001 00000004 000000a8 00000000 00000000 00000005 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167844] 7fe0: 00000000 be82d518 00000000 b66ea124 80000010 be82d520 00000000 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.168038] Code: f10c0080 e5992008 e35204bf 1b000de1 (e5991000)

    RetroPie 4.5 -> Also freezes randomly.

    RetroPie 4.4 -> Also freezes, but exits EmulationStation and shows "Segmentation Fault". I have and screenshot if you need it.
    And Putty threw this:

    pi@retropie:~ $ Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.770533] Internal error: Oops: 805 [#1] ARM Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773455] Process emulationstatio (pid: 444, stack limit = 0xc0e68188) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773619] Stack: (0xc0e69e48 to 0xc0e6a000) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773741] 9e40: 00000010 00000000 00000020 00000030 00000030 00000020 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773942] 9e60: 00000200 c0e69e8c c0e69edc c0e69e78 bf078ba0 c015a1e4 cd592b60 c0e69ea0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774148] 9e80: c1eaec00 0000b00a 00000001 be9481d8 c0e69ea8 00000000 00000000 00000ff0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774353] 9ea0: 020a4371 00000ff0 c13b8de0 cd5dc660 c0e69eec c0e69ec0 c004c3a0 c0623aec Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774556] 9ec0: c004c99c c0040a14 00000000 c13b8de0 00000001 cea06f00 c0e69f1c c0e69ee8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774755] 9ee0: c0046b2c be9481b4 cf2edd88 c9627320 00000004 00000004 c0e68000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774956] 9f00: c0e69f7c c0e69f10 c016c824 c05025c4 c0e69f74 c0e69f20 c063068c c0046adc Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775156] 9f20: c0e69f44 c006fae0 c0e69f6c c0e69f38 3cbc4f68 c01773f8 cb6ef900 b5feb564 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775358] 9f40: be9481b4 be9481d8 400cc404 00000004 c0e69f6c c9627321 be9481b4 c9627320 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775562] 9f60: 400cc404 00000004 c0e68000 00000000 c0e69fa4 c0e69f80 c016cf20 c016c794 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775762] 9f80: 0000b00a b5feb564 be9481b4 be9481d8 00000036 c000ffa4 00000000 c0e69fa8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775963] 9fa0: c000fe00 c016cee8 b5feb564 be9481b4 00000004 400cc404 be9481b4 0000b00a Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776164] 9fc0: b5feb564 be9481b4 be9481d8 00000036 00000000 be948374 003be5cc 02164608 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776365] 9fe0: b5feb240 be9481a4 b5fd8c08 b66ef80c 80000010 00000004 00000000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.777184] Code: e51f1528 e24b207c ebffea8d e1a09000 (eafffc25)

    RetroPie 4.3 -> Also freezes

    NOOBS_v2_8_2 -> Raspbian Ok, update everything..., until I install RetroPie manually, then it freezes right away!

    I have to try Recalbox...

  • 0 Votes
    74 Posts
    18k Views
    I

    I know this is SUPER old, but after parsing through possible ways/threads to get a trackball working on MAME2003, I was finally successful (after 3 attempts where I gave up and just went with advancemame)

    A) in retroarch-core-options.cfg, add:

    mame2003-dialsharexy = "enabled" mame2003-mame_current_mouse_enable = "enabled"

    I didnt verify if you actually need mame2003-dialsharexy = "enabled" but Im glad it is working

    B) in /opt/retropie/configs/arcade/retroarch.cfg, add:

    input_player1_mouse_index = "MOUSEINDEX"

    Where:

    MOUSEINDEX is the index for your mouse /dev/input/mouse*. I needed to test through a couple as what I needed to enter above, wasnt the same as the device's index. Unclear how these correlate Your retroarch config (in this case arcade) may be different for your emulator. Easiest way I know to determine the config is when its running ps -aux | grep retro and look for the program and its referenced config file
  • 0 Votes
    2 Posts
    1k Views
    S

    Anybody having these issues with other controllers? Read that some people having issues with version .12?

    Mostly annoying is that when pressing start to start a rom, it throws me back to the games screen and that most buttons, even properly configured in es and am, dont work anymore. Even the connected bluetooth controller is first joy0 and later on joy1 when rebooting. Its very annoying.

    Anybody knows what i should or can do? Thanks!

  • 1 Votes
    1 Posts
    676 Views
    No one has replied
  • 0 Votes
    4 Posts
    2k Views
    jonnykeshJ

    @jazzsunn Or failing that, not even your theme. Check your ROM names for non ASCII characters. Remove anything odd or unusual from the file names.

  • 0 Votes
    20 Posts
    6k Views
    G

    @mediamogul This did the trick for me thank you!
    sudo rm /home/pi/RetroPie/roms/genesis/megadrive
    I got the issue when I launch the setup update script from retropie, now is all working again!

  • White bar at the top of the screen

    Help and Support
    4
    0 Votes
    4 Posts
    1k Views
    DeadStretchD

    I too am running into this issue and I can't seem to pinpoint what's actually causing it. I am also a complete noob to Linux. This is actually the very first time I have ever used linux. So please be as simple as you can with you explanations. If need be I am a sucker for studying Glossary's. :D

    Pi Model: 3
    RetroPie Version Used: 3.8.1
    USB Devices connected: 1 keyboard, 1 Xbox 360 wired fightstick controller, 1 Microsoft wireless dongle
    Controller used: MadCatz Xbox 360 BrawlPad
    Error messages received: N/A
    Guide used: Followed 2 guides. One was a

    about the xbox 360 wireless controller configuration The other was on wiki for adding PSX BIOS and ROMS.
    File: N/A
    Emulator: N/A
    Attachment of config files: Not sure which config. are actually needed?
    How to replicate the problem: Basically I have my Retropie in a state the it runs and works flawlessly. Now when trying to add anything to it upon reboot it seems like the whole screen is shifted down except for the UI. Also besides there being the white bar at the top none of my usb devices seems to work and the only way to fix it is by removing the files and rebooting using the terminal from my PC