• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
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

lr-pcsx-rearmed not detecting bios

Scheduled Pinned Locked Moved Help and Support
bioslr-pcsx-rearmed
12 Posts 3 Posters 3.0k 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.
  • M
    mitu Global Moderator
    last edited by 27 Dec 2020, 21:41

    Disable the Boot logo in the Core Options, it's known to cause issues with games.

    F 1 Reply Last reply 27 Dec 2020, 22:20 Reply Quote 1
    • F
      Forthias @mitu
      last edited by Forthias 27 Dec 2020, 22:20

      @mitu

      Thanks for the compatibility tip, but now the game just boots to a black screen with 0 fps and exits lol. Disabled it for future reference, though. I did, however, get a readable dump this time though. I've had a few games with this, and I couldn't figure out what it means by using Google.

      Parameters:
      Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/pcsx_rearmed_libretro.so --config /opt/retropie/configs/psx/retroarch.cfg "/home/pi/RetroPie/roms/psx/Echo Night.cue" --appendconfig /dev/shm/retroarch.cfg
      selected sound output driver: libretro
      ari64_reset

      I'm not sure what the ari64_reset means, but I've had a few games that just have that repeated over a few times after a black screen. Like, half my psx games don't work for some reason now and I was assuming it's from using the hle bios, but no matter what I do I don't get anything except auto and hle choices in the bios select option. Launching with verbose logging still gives me an unreadable file, for whatever reason.

      1 Reply Last reply Reply Quote 0
      • M
        mitu Global Moderator
        last edited by 28 Dec 2020, 05:55

        Without any detailed info (from the verbose log), it's difficult to determine the cause. You should leave the BIOS to 'Auto' (instead of HLE).
        Did you reset your RetroArch configuration from the RGUI, by any chance ? This will change the location where the emulator looks for the BIOS files.

        F 1 Reply Last reply 28 Dec 2020, 20:22 Reply Quote 1
        • F
          Forthias @mitu
          last edited by 28 Dec 2020, 20:22

          @mitu I'll look up how to do that, I haven't, but I also haven't changed anything since updating. Still, some times updates can cause strange problems.

          I do have the bios set to auto, it's just using the hle bios for some reason. The only reason I knew was because I had the bios on boot turned on and it shows the PCSX logo under the Playstation logo.

          I tried to delete and reinstall the emulator, as well, and no dice. I did recently get an external hard drive for my roms, I'm assuming I can just do a fresh install and plug my external drive back in to recover my roms and memory card files? If I have to do that, I can. I just don't want to reatart the 15 or so PSX games I have going, I finally got an S rank on Resident Evil 2 before updating and don't want to redo it lol

          1 Reply Last reply Reply Quote 0
          • M
            mitu Global Moderator
            last edited by mitu 28 Dec 2020, 20:43

            Post a verbose log if you want to get diagnose the issue, there's little changes happening upstream in pcsx_rearmed. There was a recent change that impacted controllers, but I don't remember anyone reporting anything similar to this issue.

            F 1 Reply Last reply 28 Dec 2020, 21:52 Reply Quote 1
            • F
              Forthias @mitu
              last edited by Forthias 28 Dec 2020, 21:52

              @mitu I still can't get a verbose log, just says unreadable file. I deleted the conf files and nothing seemed to change, and I hadn't figured there was any huge changes in PCSX, as it seemed pretty stable, before. That's why this has got me so confused, I posted here as a last resort. I've no idea what's going on and without a log there's no real reason to tell, my guess is that maybe something got corrupted during the update? I'll just have to reimage my OS whenever I want to go back to playing PSX, I guess. It was worth checking just to see if anyone else had similar issues. Thanks for the help, though.

              Just to double check, the conf files are the ones in /opt/retropie/configs/ right? I deleted both the one in all and the one is psx, nothing changed, and I restored them via backups.

              I tried a few other games and it seems some of them are using the bios and some aren't, this doesn't make any sense to me at all. Resident Evil 2 and 3 both work fine and are using the correct bios. Echo Night and all of the Clock Tower games are using the hle bios and I'm not sure how to force the correct one, if that's even possible.

              M 1 Reply Last reply 28 Dec 2020, 21:54 Reply Quote 0
              • M
                mitu Global Moderator @Forthias
                last edited by 28 Dec 2020, 21:54

                @forthias said in lr-pcsx-rearmed not detecting bios:

                I still can't get a verbose log, just says unreadable file

                How are you trying to open the file ?

                Just to double check, the conf files are the ones in /opt/retropie/configs/ right? I deleted both the one in all and the one is psx, nothing changed, and I restored them via backups.

                Deleting the configuration file(s) is not recommended and it's possible this is why your BIOS is not found. Without a log file though, it's difficult to speculate.

                F 2 Replies Last reply 28 Dec 2020, 21:59 Reply Quote 0
                • F
                  Forthias @mitu
                  last edited by 28 Dec 2020, 21:59

                  @mitu I'm using RaspController on my phone. Any other time if I long press on it I can open it via text editor, that's how I got it before on my previous post. When I launch a PSX game and it black screens it just says unreadable file, I can try and navigate to it via the file explorer in the Retropie menu but it might take me a bit as I'm not used to the UI.

                  How should I reset the files? Is there a spot in the retroarch gui to reset everything?

                  1 Reply Last reply Reply Quote 0
                  • F
                    Forthias @mitu
                    last edited by 28 Dec 2020, 22:04

                    @mitu not sure if double post is against the rules or not, but I got the log to open that time and now I'm getting an invalid CD image notification. Which is odd, because it's the same image I was playing before the update.

                    But, I did get my external hard drive right after I updated and recently found out it's a 3.1 USB SSD, but the cable it came with isn't 3.1 even though it's blue. So, my guess is that the shoddy cable has corrupted a bunch of my isos during the transfer from the SD card. A head ache, but now I know what's wrong and feel like I wasted your time lmao. Thanks again, I think I know what's going on, now. Maybe that the corrupt images are making the emulator default to the hle bios

                    D M 2 Replies Last reply 29 Dec 2020, 04:58 Reply Quote 0
                    • D
                      dankcushions Global Moderator @Forthias
                      last edited by 29 Dec 2020, 04:58

                      @forthias a corrupted ISO would likely not work at all. i doubt it will have any affect on the used BIOS. we would need to see the verbose log in full to help you diagnose further.

                      1 Reply Last reply Reply Quote 0
                      • M
                        mitu Global Moderator @Forthias
                        last edited by 29 Dec 2020, 04:59

                        @forthias said in lr-pcsx-rearmed not detecting bios:

                        A head ache, but now I know what's wrong and feel like I wasted your time lmao. Thanks again, I think I know what's going on, now. Maybe that the corrupt images are making the emulator default to the hle bios

                        It's not a waste of time if we find out what's the cause.
                        Regarding the SSD issue, it might not be the cable, but the USB/SSD controller. There is an extensive topic in the Raspberry Pi forums about it, including workarounds and ways to diagnose it.

                        1 Reply Last reply Reply Quote 0
                        • F FraIgna referenced this topic on 26 Feb 2023, 11:15
                        12 out of 12
                        • First post
                          12/12
                          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.

                          This community forum collects and processes your personal information.
                          consent.not_received