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

    redream not working

    Scheduled Pinned Locked Moved Help and Support
    dreamcastredreampi4
    28 Posts 6 Posters 4.4k 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.
    • C
      c0un7z3r0 @mitu
      last edited by

      @mitu

      Thanks again

      This is getting weird, it now gives this error

      Executing: /Opt/RetroPie/emulators/redream/redream "/home/pi/RetroPie/ROMs/Dreamcast/myromfile.chd"
      /Opt/RetroPie/emulators/redream/redream: line 9: /Opt/RetroPie/emulators/redream/redream.aarch64.elf: No such file or directory 
      

      But that file does exist.

      Damn this is frustrating. Sorry to keep coming back with this, I appreciate your help

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

        @c0un7z3r0 said in redream not working:

        This is getting weird, it now gives this error

        This seems to be something related to your system. /Opt/Retropie doesn't exist on a standard RetroPie installation, RetroPie is installed in /opt/retropie . Since Linux filesystems are generally case-sensitive, in this case the folders are not the same.

        C 1 Reply Last reply Reply Quote 0
        • C
          c0un7z3r0 @mitu
          last edited by c0un7z3r0

          @mitu sorry the capitalisation was mine. I manually typed it out on my phone

          It is lowercase as you said.

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

            Then I suggest you reinstall again redream. The package does contain the file not found in your error (/opt/retropie/emulators/redream/redream.aarch64.elf).

            C 1 Reply Last reply Reply Quote 0
            • C
              c0un7z3r0 @mitu
              last edited by

              @mitu

              It does contain redream.aarch64.elf, it's referenced in the redream script we were having problems with. See image for my directory structure and files

              alt text

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

                You say you installed RetroPie using the RPI Imager image, but your image shows a newer kernel and a 64bit system (?), which we don't include. Did you use rpi-update to update your system by any chance ?

                C 1 Reply Last reply Reply Quote 0
                • C
                  c0un7z3r0 @mitu
                  last edited by

                  @mitu

                  I don't specifically remember doing so but it's quite likely i have at some point done rpi-update.

                  I noticed an issue with the symlinks last night so I'm going to investigate that but I'm AFK right now. I'll come back with my findings.

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

                    @c0un7z3r0 said in redream not working:

                    I don't specifically remember doing so but it's quite likely i have at some point done rpi-update.

                    Why ? rpi-update is not meant to be used for regular updates, it even tells you so when you run it. Your bootloader and kernel have been upgraded to the latest beta and that's why your system is running a 64bit kernel, but with a 32bit system. it's most likely the reason redream doesn't work since it thinks the system is 64bit, but the aarch64 (64bit) executable cannot run on a 32bit userland.

                    You can either re-install the relevant packages to remove the beta kernel/bootloader or add arm_64bit=0 to the booloader configuration file (config.txt, in the /boot folder).

                    C A 2 Replies Last reply Reply Quote 0
                    • C
                      c0un7z3r0 @mitu
                      last edited by

                      Thanks @mitu

                      I'm going to check to see if the symlinks issue is the problem first (it seems as tho the bios files symlinks are not working, I've not fully investigated but it seems nothing happens if I try to 'cat' the bios files). If that's a red herring then I'll try to force 32bit mode as advised. I'll update the post as usual. Thanks again for your help.

                      Cheers.

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        c0un7z3r0 @c0un7z3r0
                        last edited by c0un7z3r0

                        @mitu

                        I finally got it sorted out thanks to you, the issue was indeed was the 64/32 bit mismatch. Forcing 32 bit mode with arm_64bit=0 and fixing the issue with the symlink that points to the bios fixed it. Thanks so much for your help and patience, im so releived to have finally got it fixed. I couldnt have done it without you! Cheers!

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

                          @c0un7z3r0 Glad you got it working. Also, don't use rpi-update again for regular updates.

                          C 1 Reply Last reply Reply Quote 1
                          • C
                            c0un7z3r0 @mitu
                            last edited by

                            @mitu Will do! Thanks!

                            1 Reply Last reply Reply Quote 0
                            • A
                              aftermath17 @mitu
                              last edited by aftermath17

                              @mitu This was the cause of my issues. More info here.
                              https://forums.raspberrypi.com/viewtopic.php?t=349070

                              My issue was also fixed by adding arm_64bit=0 to /boot/config.txt.

                              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.