sebastien
Participant
Post count: 10

Thank you for your reply.

/etc/udev.rules.d/ The folder does not exist in my version.

I have 2 file /etc/udev/rules.d/:
40-scratch.rules and 99-input.rules

I tried to edit these files in all directions but nothing…

Here is the beginning of udevadm:

pi@RPI-CONSOLE ~ $ sudo udevadm info -a –name=input/event5

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input55/event5’:
KERNEL==”event5″
SUBSYSTEM==”input”
DRIVER==””

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input55’:
KERNELS==”input55″
SUBSYSTEMS==”input”
DRIVERS==””
ATTRS{name}==”Nintendo Wii Remote Classic Controller”
ATTRS{phys}==””
ATTRS{uniq}==””
ATTRS{properties}==”0″

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D’:
KERNELS==”0005:057E:0306.000D”
SUBSYSTEMS==”hid”
DRIVERS==”wiimote”
ATTRS{devtype}==”gen10″
ATTRS{extension}==”classic”

……………………………………….
js0 :

pi@RPI-CONSOLE ~ $ sudo udevadm info -a –name=input/js0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input52/js0’:
KERNEL==”js0″
SUBSYSTEM==”input”
DRIVER==””

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input52’:
KERNELS==”input52″
SUBSYSTEMS==”input”
DRIVERS==””
ATTRS{name}==”Nintendo Wii Remote”
ATTRS{phys}==””
ATTRS{uniq}==””
ATTRS{properties}==”0″

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D’:
KERNELS==”0005:057E:0306.000D”
SUBSYSTEMS==”hid”
DRIVERS==”wiimote”
ATTRS{devtype}==”gen10″
ATTRS{extension}==”classic”

………………………………………………
js1 :

pi@RPI-CONSOLE ~ $ sudo udevadm info -a –name=input/js1

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input55/js1’:
KERNEL==”js1″
SUBSYSTEM==”input”
DRIVER==””

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D/input/input55’:
KERNELS==”input55″
SUBSYSTEMS==”input”
DRIVERS==””
ATTRS{name}==”Nintendo Wii Remote Classic Controller”
ATTRS{phys}==””
ATTRS{uniq}==””
ATTRS{properties}==”0″

looking at parent device ‘/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:42/0005:057E:0306.000D’:
KERNELS==”0005:057E:0306.000D”
SUBSYSTEMS==”hid”
DRIVERS==”wiimote”
ATTRS{devtype}==”gen10″
ATTRS{extension}==”classic”