-
Notifications
You must be signed in to change notification settings - Fork 279
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
[ISSUE]: OPL v1.1.0 and over doesn't recognize my Crucial BX500 SSD #709
Comments
I have also noticed this and went back to see if I could figure out when this directly breaks, And it seems to be around the this change #423 Unfortunately I can't quite find a build of the build directly before it, so I sadly had to use a build from ps2-home, But the harddrive works fine on that 1.10 beta build.. I will see if I can find a build not from that person to see if it still works. But something about the partition checking breaks the BX500 being detected. For reference I have a Crucial BX 500 500Gb Update: After testing and conferencing with discord, it might be PR #474 that may have caused this regression, I am no expert, just a guy who really wants his brand new drive to work with latest opl. Update 2: after reverting this change it still didn't work. So Likely not OPL at fault at all. Likely due to changes in HDD drivers in PS2SDK, Posted an issue there with my findings. |
I have this exact same issue. Crucial BX500 1TB. I also tested bitfunx 2.0 adapter fitted to the official PS2 network adapter and also the gamestar sata HDD adapter with the same result. I can test various builds or anything if that helps, let me know. |
30k3 R Chassis Crucial MX500 500GB I'm not saying there's no problem, most likely there is, but it's more device-specific it seems. |
Additional info. Update 28/11/22 |
Hello all who work to improve and maintain this awesome project. I am very happy to report that I have just tested the latest beta and this appears to now be resolved. Thank you for doing what you do! |
Hey, sorry to bump this old issue! I'm using this SSD myself (2TB), and I'm encountering the same issue. I'm using the build from this Action: https://github.com/ps2homebrew/Open-PS2-Loader/actions/runs/5359760866 Is it possible that another change occurred that broke support for this model of drive within OPL? (I'm actually not sure if this issue was fixed at all, looking at the comments. People with it working seem to use the MX500, so maybe the BX500 was never fixed? |
Hey, what exactly is not working for you? I’d like to try to help |
Should be fixed in the last beta. |
Checks
Describe the issue
I recently got my Crucial BX500 250Gb SATA SSD connected to the official Network Adapter with the Bitfunx SATA adapter. I've configured the HDD OSD 2.0 with krHACKen's SUDC 4 disc. Everything is properly configured and the PS2 Browser successfully displays the HDD. I've even managed to get wLaunchElf to launch as an icon on the Browser.
The issue I'm having is that whenever I launch OPL through wLaunchElf the following happens:
I've been using HDL Batch Installer to put my games on the SSD with OPL Launcher. OPL itself is located on the +OPL partition. After launching OPL no folders are created. I've tested some versions of OPL, and v1.0.0 opens just fine and even recognizes the games I've injected.
What sucks is that OPL Launcher is only supported in v1.1.0 and over, so right now I'm stuck with an older version of OPL that can only be launched through wLaunchElf.
The weirdest part in all of this is that with the exact same partition layout, OPL works just fine on my older 2.5inch 250GB SATA HDD.
Another point I'd like to add is that OPL Launcher seems to inherit the same behaviour of regular OPL, that is whenever I try to launch a game through the PS2 Browser on the SSD the HDD activity light remains "on" for 10~20 seconds and I'm booted back into the PS2 Browser after more or less 1 minute (sometimes less).
Console model
SCPH-30004 (Launch model C Chassis)
OPL version / revision
OPL stable 1.1.0 | OPL beta 1.2.0 builds
In which device(s) have you experienced this issue?
HDD
Context and extra information
No response
The text was updated successfully, but these errors were encountered: