Dolphin won't recognize GC controller on Debian
|
Dolphin won't recognize GC controller on Debian
|
 (06-15-2015, 09:27 AM)skid Wrote: There is some debug logging which can be enabled by selecting the SerialInt category in the logs. Nothing gets logged at all from the SerialInt category. I've got the logging level set to Notice, so I should at least be seeing messages like "GC Adapter scanning thread started", right? What am I missing? (06-15-2015, 12:19 PM)udqm Wrote: Nothing gets logged at all from the SerialInt category. I've got the logging level set to Notice, so I should at least be seeing messages like "GC Adapter scanning thread started", right? What am I missing? Any ideas about why I wouldn't be getting log messages? I've got all three logging destinations enabled, and I've checked all of them.
I don't think Dolphin is hitting the GC adapter detection code. Maybe try plugging the adapter into a USB 2.0 or USB 3.0 port. Does this patch help?
https://github.com/dolphin-emu/dolphin/pull/2510 https://github.com/dolphin-emu/dolphin/pull/2510.diff 06-17-2015, 03:49 AM
(06-16-2015, 09:38 PM)skid Wrote: I don't think Dolphin is hitting the GC adapter detection code. Maybe try plugging the adapter into a USB 2.0 or USB 3.0 port. Does this patch help? No, I already have a similar udev rule set up. The device is definitely connected and accessible; I wrote a little C program to enumerate devices with libusb and it does find one with idVendor 0x057e and idProduct 0x0337. I was able to call libusb_open on that device successfully, too. What's confusing me is that I'm not getting any logging at all from the SerialInt category. From my reading of the code I should at least be getting messages like "GC Adapter scanning thread started", yet I get nothing at all. 06-25-2015, 10:56 AM
|
|
« Next Oldest | Next Newest »
|
