libretro / libretro/RetroArch

Retroarch asset folder causing Switch Boot Failure

Open
#14,627 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

When installing/loading Retroarch to the SD card, once the assets folder is added, startup fails.
Adding retroarch to the switch without the asset folder, allows the switch to startup and opening the application can startup (missing assets).
If the asset (/retroarch) folder is added to the SD, startup of HOS is prevented.

I'm not sure if there is a way to enable logging on the HOS to collect more data. If someone knows how, please let me know and I can add.

Expected behavior

Switch powers on, load hekate payload, and startup atmosphere to HOS. Loads HOS normally. Retroarch is able to startup and use the assets present in the /retroarch folder.

Actual behavior

Switch powers on, load hekate payload, startup atmosphere to HOS. Black screen, startup hangs here.

Steps to reproduce the bug
  1. Format SD card, FAT32
  2. Startup Hekate, and format SD card for emuMMC
  3. Add Atmosphere, sig patches to sd. Verify that startup is working as expected
  4. Load contents of Switch Retroarch download to root directory of SD card.
  5. Startup Atmosphere/HOS
  6. Notice black screen that does not startup
Version/Commit

You can find this information under Information/System Information

  • RetroArch:
    Downloaded from site Nov 14 2022
Environment information
  • OS:
    Switch OS: 15.0.1
    Fusee: 1.4.0
    Hekate: 5.9.0
    Switch V1, using rail based RCM

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified. Start by reproducing the FAT32 and emuMMC setup with the listed RetroArch, Switch OS, Fusee, and Hekate versions, then compare startup with and without the /retroarch asset folder; done means identifying a reproducible cause and verifying that HOS starts normally with the assets present.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.