Waymark FAQ

My gamepad doesn't work

If you are using UNIX-like operating system, it is possible that you don't have permission to read input from the gamepad. In this case, your gamepad is recognized, but the device cannot be read. For example, on some GNU/Linux systems you can list input devices by issuing the following command:

ls -l /dev/input

As a result you will see a listing of the available input devices:

drwxr-xr-x 2 root root       140 2009-01-08 21:05 by-id
drwxr-xr-x 2 root root       180 2009-01-08 21:05 by-path
crw-rw---- 1 root root    13, 64 2009-01-08 18:46 event0
crw-rw---- 1 root root    13, 65 2009-01-08 18:46 event1
crw-rw---- 1 root root    13, 66 2009-01-08 18:46 event2
crw-rw---- 1 root root    13, 67 2009-01-08 18:46 event3
crw-rw---- 1 root root    13, 68 2009-01-08 18:46 event4
crw-rw---- 1 root root    13, 69 2009-01-08 18:46 event5
crw-rw---- 1 root root    13, 70 2009-01-08 18:46 event6
crw-rw---- 1 root root    13, 63 2009-01-08 18:45 mice
crw-rw---- 1 root root    13, 32 2009-01-08 18:45 mouse0
crw-rw---- 1 root root    13, 33 2009-01-08 18:45 mouse1

Now, plug in your gamepad and give the command again:

ls -l /dev/input

In this case, you will see, that event7 is the gamepad, because it wasn't on the previous listing. You will also see, that root owns the gamepad and if you aren't logged in as root-user, you do not have permission to read the device:

drwxr-xr-x 2 root root       140 2009-01-08 21:05 by-id
drwxr-xr-x 2 root root       180 2009-01-08 21:05 by-path
crw-rw---- 1 root root    13, 64 2009-01-08 18:46 event0
crw-rw---- 1 root root    13, 65 2009-01-08 18:46 event1
crw-rw---- 1 root root    13, 66 2009-01-08 18:46 event2
crw-rw---- 1 root root    13, 67 2009-01-08 18:46 event3
crw-rw---- 1 root root    13, 68 2009-01-08 18:46 event4
crw-rw---- 1 root root    13, 69 2009-01-08 18:46 event5
crw-rw---- 1 root root    13, 70 2009-01-08 18:46 event6
crw-rw---- 1 root root    13, 71 2009-01-08 21:05 event7
crw-rw---- 1 root plugdev 13,  0 2009-01-08 21:05 js0
crw-rw---- 1 root root    13, 63 2009-01-08 18:45 mice
crw-rw---- 1 root root    13, 32 2009-01-08 18:45 mouse0
crw-rw---- 1 root root    13, 33 2009-01-08 18:45 mouse1

You should find out the best way to solve this issue on your specific system, but here is quick (and dirty) way to access the gamepad. This method is only temporary, you must reissue this command again every time if you have unplugged your gamepad or logged out. This command is executed as root (the sudo command), so use it on your own risk, and be careful. If you decide to use it, do not just copy-paste the command, but instead replace values with the correct ones for your specific system. In this case, the gamepad is event7, so to add to everybody a right to read the device:

sudo chmod +r /dev/input/event7

Now, if you list the input devices again, you will see, that everybody can read the gamepad:

drwxr-xr-x 2 root root       140 2009-01-08 21:05 by-id
drwxr-xr-x 2 root root       180 2009-01-08 21:05 by-path
crw-rw---- 1 root root    13, 64 2009-01-08 18:46 event0
crw-rw---- 1 root root    13, 65 2009-01-08 18:46 event1
crw-rw---- 1 root root    13, 66 2009-01-08 18:46 event2
crw-rw---- 1 root root    13, 67 2009-01-08 18:46 event3
crw-rw---- 1 root root    13, 68 2009-01-08 18:46 event4
crw-rw---- 1 root root    13, 69 2009-01-08 18:46 event5
crw-rw---- 1 root root    13, 70 2009-01-08 18:46 event6
crw-rw-r-- 1 root root    13, 71 2009-01-08 21:05 event7
crw-rw---- 1 root plugdev 13,  0 2009-01-08 21:05 js0
crw-rw---- 1 root root    13, 63 2009-01-08 18:45 mice
crw-rw---- 1 root root    13, 32 2009-01-08 18:45 mouse0
crw-rw---- 1 root root    13, 33 2009-01-08 18:45 mouse1

Now the gamepad should be usable for non-root-users too. Notice, that when using gamepad as an input device, for best performance you should use the directional pad, not the stick for input. If nothing happens when pressing the directional pad, press mode-button so that the red led starts to glow, and try directional pad again.