Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I read through this thread again and now a little bit confused to what the actual problem is. Do you want to use a mapper program for games that don't have gamepad/joystick support? Or are you trying to use a mapper for games that have support?
I read through this thread again and now a little bit confused to what the actual problem is. Do you want to use a mapper program for games that don't have gamepad/joystick support? Or are you trying to use a mapper for games that have support?
I'm trying to find any solution at all for getting games to work. A good mapper for keyboard emulation would be good, but then there are some games that clearly *do* support joysticks that also aren't seeming to recognize them. If possible, I'd strongly prefer a solution that will work across distros and doesn't require a mapper even, but again, a mapper that'd work universally would solve most or perhaps all of my joystick issues.
Let me know if you need more info on my system or anything. Thanks.
As long as your joystick/gamepad (brand? model?) is recognized by the kernel (dmesg output when plugging it in will be helpful) it should work out of the box in games that support a gamepad. I never have used a wrapper, so I can't comment on that.
As long as your joystick/gamepad (brand? model?) is recognized by the kernel (dmesg output when plugging it in will be helpful) it should work out of the box in games that support a gamepad. I never have used a wrapper, so I can't comment on that.
Yeah, and for sure in Ubuntu it DOES seem to work out of the box at least some of the time. Arguably the biggest problem here is that it keeps emulating my mouse and controlling the cursor, and this seems to be independent of whether or not a mapper program is running. If I could get that part fixed I'd probably be more than halfway there.
Please post the messages of the dmesg output related to that device when plugging it in. May it be possible that the controller itself has some kind of emulation mode activated?
Please post the messages of the dmesg output related to that device when plugging it in. May it be possible that the controller itself has some kind of emulation mode activated?
Hi TobiSGD,
Sorry for the delay in recognizing what you said earlier about dmesg. Your mention of it had slipped my mind and I didn't mean to ignore it.
The output of merely typing "dmesg" is HUGE, and I wanted to ask if I should add any parameters that would lessen the output and/or narrow its output down entirely to USB devices or maybe even USB joysticks specifically. I'm not very familiar with the command, but I have my Ubuntu terminal ready now if there's a way to get less output so I can paste it here.
No idea if the controller has any emulation mode activated, but I do know it works fine in Windows upon plugging it in without any further adjustments needed. This is one of few bits of hardware I have that have had fewer problems in Windows than in Linux.
I assumed I do run systemd, though I didn't know how to check. Upon running the journalctl command, I got this output:
Code:
-- Logs begin at Tue 2015-06-09 16:02:04 CDT. --
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: f.Callbacks/n@http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js:2:14779
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: f.Callbacks/o.fireWith@http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js:2:15553
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: w@http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js:4:11393
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: .send/d@http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js:4:17218
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: pbs<@resource://unity/observer.js:38:71
Jun 09 16:04:32 kaiji-desktop gnome-session[1103]: Observer.prototype.observe@resource://unity/observer.js:77:24
Jun 09 16:05:48 kaiji-desktop kernel: usb 10-3: USB disconnect, device number 3
Jun 09 16:05:48 kaiji-desktop systemd-udevd[302]: error opening USB device 'descriptors' file
Jun 09 16:07:44 kaiji-desktop gnome-session[1103]: WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
Jun 09 16:07:44 kaiji-desktop gnome-session[1103]: pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
Jun 09 16:07:44 kaiji-desktop gnome-session[1103]: pbs<@resource://unity/observer.js:38:71
Jun 09 16:07:44 kaiji-desktop gnome-session[1103]: Observer.prototype.observe@resource://unity/observer.js:77:24
We can see the disconnect (you unplugged the device), but relevant are the lines that appear when you plug the device in again.
Oh! I missed the re-plugging part. It did detect it, and I think these are the relevant lines:
Code:
Jun 09 16:25:43 kaiji-desktop kernel: usb 10-3: new low-speed USB device number 5 using ohci-pci
Jun 09 16:25:43 kaiji-desktop kernel: usb 10-3: New USB device found, idVendor=0079, idProduct=0006
Jun 09 16:25:43 kaiji-desktop kernel: usb 10-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 09 16:25:43 kaiji-desktop kernel: usb 10-3: Product: Generic USB Joystick
Jun 09 16:25:43 kaiji-desktop kernel: usb 10-3: Manufacturer: DragonRise Inc.
Jun 09 16:25:43 kaiji-desktop mtp-probe[3593]: checking bus 10, device 5: "/sys/devices/pci0000:00/0000:00:12.0/usb10/10-3"
Jun 09 16:25:43 kaiji-desktop mtp-probe[3593]: bus: 10, device: 5 was not an MTP device
Jun 09 16:25:43 kaiji-desktop kernel: input: DragonRise Inc. Generic USB Joystick as /devices/pci0000:00/0000:00:12.0/usb10/10-3/10-3:1.0/0003:0079:0006.000B/input/input29
Jun 09 16:25:43 kaiji-desktop kernel: dragonrise 0003:0079:0006.000B: input,hidraw8: USB HID v1.10 Joystick [DragonRise Inc. Generic USB Joystick ] on usb-0000:00:12.0-3/input0
Jun 09 16:25:43 kaiji-desktop kernel: dragonrise 0003:0079:0006.000B: Force Feedback for DragonRise Inc. game controllers by Richard Walmsley <richwalm@gmail.com>
So the kernel recognizes the device as a generic joystick device, not as a mouse or similar device.
This all looks OK to me, at this point I am out of clues why this device would act as a mouse (unless your DE has something like that enabled, but I wouldn't know where to search for that in Ubuntu, since I am not a Ubuntu user).
OK. It looks like you use Arch. Might you know where to look in there? I use Manjaro a lot, especially for work, and it might lead to me figuring out other distros' solutions to this as well. Thanks.
That would depend on which DE you use, for KDE I would look in your System Settings panel under Hardware/Input Devices, though I am not quite sure if KDE offers such an option. I run a strange mix of KDE and LXQt applications/services ontop of the i3 window manager, so my setup is far from default.
That would depend on which DE you use, for KDE I would look in your System Settings panel under Hardware/Input Devices, though I am not quite sure if KDE offers such an option. I run a strange mix of KDE and LXQt applications/services ontop of the i3 window manager, so my setup is far from default.
Thanks. I'll see what I can do with this with Manjaro in the future.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
