You are not logged in.
I tried to follow this Archlinux wiki: https://wiki.archlinux.org/index.php/PS … _Bluetooth
in using my DualShock 3 controller as a gamepad for linux. It works via cable, but when I want to use it via Bluetooth, I would have to add a udev rule, as the wiki states:
Create a new udev rule (usually 99 or 98-dualshock.rules into /etc/udev/rules.d/) with the following content
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{uniq}=="device_addr_you_got_on_pairing", SYMLINK+="input/dualshock3"
I did setup this rule, but the devicefile is not created, and I dont know why.
My udev rule looks like this:
KERNEL=="event*", SUBSYSTEM=="bluetooth", ATTRS{uniq}=="00:26:5C:17:DC:1F", SYMLINK+="input/dualshock3"
I also asked on Stackoverflow and in different IRC channels: http://stackoverflow.com/questions/2632 … th-gamepad
Here are different results from udevadm info, test and monitor:
@notebook-arch:~$ sudo udevadm info -p /devices/pci0000:00/0000:00:14.0/usb3/3- 3/3-3:1.0/bluetooth/hci0/hci0:256
P: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:256
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:256
E: DEVTYPE=link
E: SUBSYSTEM=bluetooth
E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0:256
E: SYSTEMD_WANTS=bluetooth.target
E: TAGS=:systemd:
E: USEC_INITIALIZED=10884187430
@notebook-arch:~$ sudo udevadm test /devices/pci0000:00/0000:00:14.0/usb3/3-3/3- 3:1.0/bluetooth/hci0/hci0:256
calling: test
version 216
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
load module index
timestamp of '/etc/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
timestamp of '/etc/udev/rules.d' changed
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
...
Reading rules file: /etc/udev/rules.d/98-dualshock.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 49152 bytes tokens (4096 * 12 bytes), 17579 bytes strings
3261 strings (38563 bytes), 2275 de-duplicated (21971 bytes), 987 trie nodes used
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:256
DEVTYPE=link
SUBSYSTEM=bluetooth
SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0:256
SYSTEMD_WANTS=bluetooth.target
TAGS=:systemd:
USEC_INITIALIZED=10971258079
unload module index
Unloaded link configuration context.
@notebook-arch:~$ sudo udevadm monitor --properties
monitor: unrecognized option '--properties'
@notebook-arch:~$ sudo udevadm monitor --property
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[12523.921496] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3- 3:1.0/bluetooth/hci0/hci0:256 (bluetooth)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:256
DEVTYPE=link
SEQNUM=3112
SUBSYSTEM=bluetooth
UDEV [12523.922080] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3- 3:1.0/bluetooth/hci0/hci0:256 (bluetooth)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:256
DEVTYPE=link
SEQNUM=3112
SUBSYSTEM=bluetooth
SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0:256
SYSTEMD_WANTS=bluetooth.target
TAGS=:systemd:
USEC_INITIALIZED=523921525
Last edited by berz3rk (2014-10-12 17:28:42)
Offline