-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PS2] RetroArch does not start connected to HUB device #14569
Comments
Do you have only one device connected to the USB hub? |
Yes, I tested one at a time. |
I'm not 100% sure, but maybe this #14724 will solve the issue. |
I will test later again, but the least devices I have is 8 GB I will also test later still today when I have time. |
@fjtrujy I just tested all my devices and so far it only works with the internal HDD and USB 8 GB, and it doesn't even work with the 64 GB USB exfat and without being on the HUB none of the others worked only with the Vinik HUB-USB and another exbom Hub-usb 8 in 1 and the same thing happens. I start raboot.elf in wLanchelf or opl in the apps tab, and it just opens a black screen and loads my FMCB 1.966 and goes to opl, I tested with another memory card and same thing happens. |
It is strange, because these HUBs all working in opl open my games, but in retroarch they don't even start and boot up the raboot. |
To be honest, no idea…. as I said before I also suffered that issue in the past with a 64 GB USB 3.0 device. |
Even in MX4SIO retroarch it will not boot with 16 GB SD in fat32. |
RA doesn’t have M4SIO driver so it will never boot there. |
I understood how it uses the new irx drives from the SDK in its custom drive repertoire, I thought the BDM already contained the function for MX4SIO support as I recently purchased it, but still, thanks, good to know it is not supported yet, but I will be waiting for when it is supported. |
@fjtrujy It has to have some problem in the raboot, because I bought a 256 GB USB stick in the promotion it arrived yesterday, with other things like MX4SIO is the strange thing, because it is working the retroarch while the other devices, will not understand the meaning.:( |
RetroArch is composed by RAboot and all the cores. This behavior will happen if you try to launch for instance RA from the MX4SIO. As said before, based on my experience PS2. doesn’t work well with huge memories and/or USB 3.0. Cheers |
I've been testing Retroarch, but for some reason it starts raboot normally, but if I try to start the cores manually they result in a black screen Edit: Not all cores do this |
RA is thought to be started by using RAboot.elf and having the core and info folder. |
I purchased a simple SD card adapter without being hub and some of the genres, however with it now my 8 GB, 16 GB and 32 GB cards are working, just not on the usb hub it doesn't work yet nor devices above 32 GB at least with me. |
I have done an improvement on the wait for USB to be detected, could you just try latest nightly and check if it now works better? |
@fjtrujy I finally managed to start raboot.elf on the HUB and other devices, like USB stick and SD, but unfortunately the settings are not being saved. When I try to load the core or the roms, it goes back to the browser. |
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
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].
Environmental Information
The text was updated successfully, but these errors were encountered: