libretro / libretro/RetroArch

[PS2] RetroArch does not start connected to HUB device

Open
#14,569 17 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 testing my USB device, HD or SD card on a USB hub and trying to start RetroArch from the list of wLauchelf or OPL applications, a black screen will simply occur, and then go back to the browser or start FMCB in my case, this does not happen if not using the hub, but may well be fixed to work]

Expected behavior

[That homebrew will start instead of returning to the browser or starting the FMCB]

Actual Behavior

[When trying to load the homebrew from wLauchelf or OPL some debug colors will occur, then start a black screen will start the browser, or FMCB]

Steps to reproduce the bug
  1. [Connect to console start OPL or Wlauchelf]
  2. [Load Raboot.elf].
  3. [Debug screen then black won't start homebrew]
Bisset Results

[Tests were performed on October 26, 2022, with Vinik HUB-USB, WD Blue 1 TB HD, Hontek 64 GB USB pendrive and SanDisk 16 GB SD with everything, the device, being in fat32].

  • RetroArch: [1.11.1 and 1.12.0]
Environmental Information
  • OS: [PS2 platform]
  • Compiler: [USB]

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

Start by reproducing the failure on the PS2 with a USB hub, wLauchelf or OPL, and Raboot.elf, comparing it with a direct USB connection. Review the reported RetroArch 1.11.1 and 1.12.0 behavior and the debug colors before narrowing down the affected startup path. Done means the homebrew starts from the listed applications while connected through the hub.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.