-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Doesn't work on Western Digital Elements SE Portable (WDBABV) #12
Comments
@drizzt Thanks for reporting this issue. I'll look into it as soon as I get back home. It seems to be related to the Mode Sense (6) SCSI command either having issues or being unsupported. SX OS driver most likely works because it doesn't issue Mode Sense commands. Would it be possible for you to get a USB packet dump (e.g. via Wireshark) using a PC with partition automounting disabled? |
@drizzt Nevermind, further inspection of the packet dump suggests that these drives don't support I'll try to come up with a solution. |
@drizzt I'm back home. I've already pushed some changes to the On the other hand, even though these changes help mitigate the freezes experienced with some drives, I've been unable to find a proper solution to your specific issue. If you're using a PC with a Linux distro, please use sg_modes on your drive to see if it can effectively retrieve Mode Sense data from it. The suggested command lines are:
|
Hi, Mode Sense (6):
Mode Sense (10):
|
@drizzt Thanks for your input on this matter. It seems we definitely can't use any Mode Sense commands on these drives - raw sense data from both command outputs confirms this fact. I'll change some stuff around and provide you with a test build with logging enabled. |
@drizzt Just as I promised, here's the new test build with logging enabled. Please test it whenever you can and let me know how it goes. |
@drizzt (sorry for pinging you) Have you been able to test the build from my previous comment? |
@drizzt Please test this new build and send me its logfile. |
Same crash and I also updated atmosphere to 0.17.1 (and no logfile is generated) |
@drizzt Alright then, please try this one. It won't fix the issue but it should generate the logfile. |
If you have a Discord handle, we can continue these tests over there - real time communication isn't very optimal here. |
@drizzt Someone else was able to reproduce this very same crash using a drive that supports Mode Sense commands. I took a closer look at the problem, and turns out there was an issue with my You see, available usb:hs documentation states that an unsigned 64-bit integer with an unknown purpose must be passed to the I was setting this value to Thus, adae94c fixes the crash. I'd still like to know if it fixes the freeze you were originally experiencing with Mode Sense commands, though. Whenever possible, please test this new build. |
Describe the bug
Applications hangs with Western Digital Elements SE Portable (WDBABV). I tried both 500GB and 1TB variants
To Reproduce
Steps to reproduce the behavior:
Connect a Western Digital Elements SE Portable (WDBABV) hard disk to the Switch (I tried also by using an Y cable with external power supply) and launch libusbhsfs-example (released one and a debug-rebuilt one)
Please fill the following information:
Logfile
Make sure you're using an application that's linked against the debug version of the library, and upload your logfile located at
sdmc:/libusbhsfs.log
.libusbhsfs.log
Additional context
The hard disk(s) used to work with SX OS libusbfs
The text was updated successfully, but these errors were encountered: