Hi All,
I have a device connected to USB (A guitar pedal board, Mooer GE200) that allows, among other things, new amp sims to be installed from a computer. I’ve plugged it into a USB port and lsusb shows it is there as STMicroelectronics GE200), but I can’t figure out where (or if) its’ mounted.
ian@Susian:~> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1c6b:a223 Philips & Lite-ON Digital Solutions Corporation DVD Writer Slimtype eUAU108
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 005: ID 12c9:1025 Newmen Tech.,LTD 2.4G Wireless Set
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 0483:5703 STMicroelectronics GE200
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 1058:25a1 Western Digital Technologies, Inc. Elements / My Passport
Bus 002 Device 003: ID 1058:2623 Western Digital Technologies, Inc. Elements SE 2623
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 1bcf:2cb4 Sunplus Innovation Technology Inc. AAPDQT-0622-W
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
The software is unfortunately Window$ only (or Mac) but it seems happy to run under wine, except that it cannot detect the device even though it’s plugged in. So I guess the issue could be wine related too.
I’ve searched for similar issues and found that the device is on /dev/snd/controlC2. I’ve tried mounting that to /mnt but the software doesn’t find it. I’ve tried using winecfg to allocate /dev/snd/controlC2 to drive D:, but that didn’t work either.
I’m stumbling around in the dark here as I really don’t know much about how this stuff all works. All advice gratefully received.
One other thing I discovered by accident, is that I can select the Mooer as an output audio device in the audio settings, and audio magically comes out of my guitar amp. So It seems linux doesn’t have a problem recognising it. It must be something to do with wine? I’ve read there are all sorts of problems getting wine to talk to a usb device, and other posts that say it’s easy. Just add a disk drive (i.e. D:) and point it to the device using winecfg. Problem is, /dev/snd/controlC2 doesn’t appear in the list of drives that can be allocated to a drive in winecfg. And mounting it on a drive that IS in the list, i.e. /mnt, doesn’t seem to work either. Another post suggested making a symlink to a com port in ~/.wine/dosdevices/com34. Tried that, still the s/w can’t find it. Maybe I should go and try something easy, like brain surgery. :-\
then plug the device in, and capture the output. That might provide more detailed information including the input device. Not sure what might be needed from a wine perspective though.
[ 233.578480] usb 1-2.4.1: new full-speed USB device number 7 using xhci_hcd
[ 233.698013] usb 1-2.4.1: New USB device found, idVendor=0483, idProduct=5703, bcdDevice= 0.c8
[ 233.698039] usb 1-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 233.698051] usb 1-2.4.1: Product: GE200
[ 233.698059] usb 1-2.4.1: Manufacturer: MOOER
[ 233.698066] usb 1-2.4.1: SerialNumber: 00000000001A
[ 233.725153] input: MOOER GE200 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.3/0003:0483:5703.0003/input/input15
[ 233.725450] hid-generic 0003:0483:5703.0003: input,hidraw2: USB HID v1.10 Device [MOOER GE200] on usb-0000:00:14.0-2.4.1/input3
Well, I think I’ve proved that it’s a wine problem. I have another window$ app, that I haven’t used for ages, that also talks to a usb device (this time a programmable touch screen device), and it couldn’t find the device either. Linux could find it and connected it to /dev/ttyUSB0, which is correct. And a linux app I have that talks to usb devices recognised it. So it’s looking like wine is the culprit. I’ll have to do some more digging into that.
Yes, somehow you need to get the HID input device (/dev/hidraw2 ?) available to wine somehow. Not sure if this is just treated as a character device linked to a com port, or more complex than that.
This may be of interest to you with respect to setting r/w access to the appropriate group. The user running wine would then need to be a member of this group eg ‘lp’ group.