You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I try to connect to my EMS Cartridge with ems-qart on Arch Linux, after a couple of seconds, the GUI opens up however not connected to the cart. In the Terminal the error reads:
Failed to open device, libusb error: LIBUSB_ERROR_IO
It is definitely unrelated to the udev-rules or the like, because without the udev rule the error message reads LIBUSB_ERROR_ACCESS.
How to solve this? My cart usually worked with the official Windows tool and the PCB reads "GB64USB-12".
The text was updated successfully, but these errors were encountered:
How recently did you try to use the cart with the official Windows tool? Can you try with that?
LIBUSB_ERROR_IO makes me think of a problem at the cart level (which is not so uncommon with EMS Carts, even the ones that were working fine until they don't).
Right now I tested the Windows Tool and it at least also didn't show stored games and couldn't dump the savegame.
However, I also found out, that ems-qart runs perfectly fine under Windows. So if that is a unique bug only happening with my cart, this could be closed. I will at least test ems-qart again under Linux when I rebooted next time.
Whenever I try to connect to my EMS Cartridge with ems-qart on Arch Linux, after a couple of seconds, the GUI opens up however not connected to the cart. In the Terminal the error reads:
It is definitely unrelated to the udev-rules or the like, because without the udev rule the error message reads
LIBUSB_ERROR_ACCESS
.How to solve this? My cart usually worked with the official Windows tool and the PCB reads "GB64USB-12".
The text was updated successfully, but these errors were encountered: