You are not logged in.
Pages: 1
Has anyone been able to get this gamepad working on Arch? There doesn't seem to be anything in the wiki about Bluetooth gamepad.
Offline
Pluggig gamepads in Kde is pretty much as easy as it gets... Cannot really explain it better than "just do it". If you want something more "command-line", google a bit further, this stuff is pretty much generic, so any linux works the same.
Offline
@Vipermaseg what makes you think phunni uses KDE?
@phunni Does the gamepad get recognized by your bluetooth adapter? What bluetooth manager are you using?
Offline
I'm not using KDE - openbox provides my UI. @emeres If I run bluetoothctl it lists a "Moga Pro" and a MAC address which suggests it can find my device. The issue is that I simply don't know what to do next. Connecting via bluetooth doesn't seem to give me a working gamepad...
Offline
I think you have to pair it, I never used bluetooth for that though, so I am guessing. Check if there are any devices after pairing in /dev/input (or maybe somewhere else?):
tree /dev/inputThe procedure should be similar to a bluetooth keyboard.
Last edited by emeres (2014-07-15 18:03:15)
Offline
OK, I have the controller paired and trusted, but, for some reason, it simply won't connect. With bluetoothctl, if I run info 00:1E:B5:8C:5F:14 I get:
Device 00:1E:B5:8C:5F:14
Name: Moga Pro HID
Alias: Moga Pro HID
Class: 0x000508
Icon: input-gaming
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v20D6p0DADd0001but if I run connect 00:1E:B5:8C:5F:14 it eventually fails with:
Failed to connect: org.bluez.Error.FailedI've tried googling that error, but it's a bit too generic so I can't find anything useful. Are there any logs I could look at, or is there a way to get bluetoothctl to run in verbose/debug mode?
Offline
After the device is paired does anything new show under /dev/input? Did you try using hcitool for connecting? Dmesg should show bluetooth information.
Offline
MOGA controllers require some additional "drivers" to be able to use them on Android, nothing would show up in /dev/input when pairing.
Bumping thread to see if someone would work on something similar to ZeeMouse, but for arch/linux in general
Last edited by M4R10zM0113R (2015-01-07 23:52:52)
- "I summoned Cthulhu and Satan trying to fix my interxternet. How I'm gonna fix it now??"
- "We can't fix it either"
Offline
There should be no need for additional drivers in HID mode (AKA "orange" or "B" mode). I have a Moga Pro Power and it works just fine OOTB with Blueman. This should be the same for the older model (non-power), so my suggestion is you try with Blueman, and if it works and you still want to use cli tools only, try to find out what it does exactly that you are missing.
I also have to say that although it worked just the same once it connected, my old bluetooth adapter (Intel WiFi+BT card) was a bit more stubborn getting the connection up than my current one (Atheros WiFi+BT card), so it may depend on your adapter or default adapter settings (read: module options) too, IDK.
Good luck!
Semi-Offtopic: I also have a config for xboxdrv already set up, if anyone wants it! You may have to tweak it for the non-power model, but it could be a start once you are able to connect. Many games nowadays expect an xbox controller layout or at least have a preset for it, so once set up you usually don't have to worry about mapping anymore.
Offline
Pages: 1