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

    On Pi 3 If N64 roms folder has contents then accessing setup or rasp-config gives black screen

    Scheduled Pinned Locked Moved Help and Support
    n64 folderblack screenpi3 model b
    10 Posts 2 Posters 2.1k 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.
    • S
      spacemonkey
      last edited by

      Pi Model: ( B, 3 )
      RetroPie Version Used: md5sum: 4bf44fa37bb9db72b9d7c6dfab6fe015
      Built From: (RetroPie website https://retropie.org.uk/download/)
      USB Devices connected: wireless x360 adapter, wireless keybord
      Controller used: wireless x360
      Error messages received:
      How to replicate the problem:
      If you add roms to the n64 folder that work,
      you test the roms and everything works then try going back to emustation and choose anything that triggers the terminal menu, choose either raspi-config or retropie-setup or wifi... the screen goes black. no error is shown.
      If you press ctrl+c you go back to emustation menu.

      Thanks

      1 Reply Last reply Reply Quote 0
      • S
        spacemonkey
        last edited by

        I forgot to say that i have retropie installed on a 64gb sdcard..and if i delete all the roms from the n64 folder then everything works, scripts , wifi terminal

        1 Reply Last reply Reply Quote 0
        • S
          spacemonkey
          last edited by

          it seems to be some corruption with script ...but i can not find any relevant log. Somehow i do not see any image whenever i want to do something in the console, if i press ctrl+z i a am back in the emustation.
          I checked the logs but i can not find anything ...anyone has an idea in what log should i look ?

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

            Please ssh in (https://github.com/retropie/retropie-setup/wiki/ssh) and give me the output of

            git -C ~/RetroPie-Setup/ log -1
            

            So I can tell what version of RetroPie-Setup you are on.

            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
            • S
              spacemonkey
              last edited by BuZz

              Author: Jools Wills <buzz@exotica.org.uk>
              Date:   Sat Dec 3 03:17:21 2016 +0000
              
                  Merge pull request #1773 from joolswills/retroarch_hotkey_hack
              
                  retrarch - rework hotkey enable hack for upstream retroarch and re-enable patch - fixes #1772
              
              1 Reply Last reply Reply Quote 0
              • BuZzB
                BuZz administrators
                last edited by BuZz

                are you booting into Kodi before Emulation Station ?

                Please post the output of cat /boot/cmdline.txt Please put in a code block - see http://commonmark.org/help/ - I have formatted your previous post.

                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
                • S
                  spacemonkey
                  last edited by spacemonkey

                  yes

                  dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet loglevel=3 consoleblank=0 plymouth.enable=0

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

                    @spacemonkey That would have been a good detail to mention in your original post.

                    The issue is to do with the screen reset code in the Kodi launch script, and is a known problem.

                    as a temporarily workaround you can edit /opt/retropie/configs/all/autostart.sh and add between kodi and emulationstation the line sleep 1; fbset -depth 8; fbset -depth 32

                    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 1
                    • S
                      spacemonkey
                      last edited by

                      Worked thank you very much

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

                        @spacemonkey I assume you worked out I got the path wrong - I meant /opt/retropie/configs/all/autostart.sh - glad it's working.

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