Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3858 - udev fails to create joystick device

Attached to Project: Arch Linux
Opened by Simon Morgan (sjmorgan) - Sunday, 29 January 2006, 16:09 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I plug my SmartyJoy PlayStation controller adapter in I get the following but no joystick devices:

usb 3-1: new low speed USB device using uhci_hcd and address 3
input: Gamtec.,Ltd SmartJoy PLUS Adapter as /class/input/input4
input: USB HID v1.00 Joystick [Gamtec.,Ltd SmartJoy PLUS Adapter] on usb-0000:00:10.1-1
usbcore: registered new driver yealink
drivers/usb/input/yealink.c: Yealink phone driver:yld-20050816

$ ls /dev/input/js*
ls: /dev/input/js*: No such file or directory

As you can see it also incorrectly loads the yealink driver.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 31 January 2006, 09:00 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Sunday, 29 January 2006, 18:48 GMT
you aer using udev 079 or 083?
Comment by Simon Morgan (sjmorgan) - Sunday, 29 January 2006, 19:42 GMT
079.
Comment by Tobias Powalowski (tpowa) - Monday, 30 January 2006, 07:09 GMT
could it be that this joystick is now handled by evdev?
Comment by Simon Morgan (sjmorgan) - Monday, 30 January 2006, 13:04 GMT
I have no idea. I searched and couldn't find any decent info. All I know is that under a different Linux distribution a js0 device was created in /dev/input. Now it seems no new device is created at all even though a rule exists in udev.rules. Also, the fact it is loading the yealink drive can't be good. I've just tried manually loading joydev and a js0 device is created and works as expected.
Comment by Tobias Powalowski (tpowa) - Monday, 30 January 2006, 22:43 GMT
yes i can confirm it here, joydev is not loaded by udev automatically.
the question is should it be loaded? if yes then only usbhid can trigger it the module itself doesn't provide anything usefull, that we can use it as trigger.
Comment by Tobias Powalowski (tpowa) - Tuesday, 31 January 2006, 08:59 GMT
fixed in udev 084

Loading...