If buttons and axis are not showing up, is it joystick or joydev.ko problem?

Asked by Hans Deragon

If buttons and axis are not showing up, is it a problem with the 'joystick' package or the kernel module 'joydev.ko'? I have a Logitech Driving Force GT wheel and running kernel 3.5.0-44-generic, I have 11 axis and buttons showing up with 'joystick', but many buttons are missing.

I can help out to figure out what is missing to get all buttons working.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu joystick Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What is the output of:

lsb_release -a; lsusb

Thanks

Revision history for this message
Hans Deragon (deragon) said :
#2

As requested:

# lsb_release -a; lsusb
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:qt4-3.1-amd64:qt4-3.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise
Bus 003 Device 002: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port
Bus 003 Device 003: ID 0a5c:21e8 Broadcom Corp.
Bus 004 Device 002: ID 046d:c20a Logitech, Inc. WingMan RumblePad
Bus 004 Device 003: ID 046d:c294 Logitech, Inc. Driving Force
Bus 005 Device 002: ID 046d:c207 Logitech, Inc. WingMan Extreme Digital 3D
Bus 008 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3
Revision history for this message
Hans Deragon (deragon) said :
#4

LTWheelConf is not required anymore with the new kernels; the project has been abandonned since. So the problem lies somewhere else. I suspect 'joydev.ko' since I assume that 'joystick', like games, is only reading data provided by the kernel module. But I would like to have a confirmation before issuing a bug report against 'joydev.ko'.

BTW, I tried LTWheelConf and it did not work.

See comment at:

https://github.com/TripleSpeeder/LTWheelConf

Revision history for this message
Stephen Kitt (steve-sk2) said :
#5

Hi,

The tools in the joystick package, as you suspect, only use the information provided by the kernel. There might be a trace somewhere in your dmesg output (/var/log/dmesg) from joydev giving the number of buttons detected.

The evtest tool (in the package of the same name) can also be useful when investigating this type of problem.

Regards,

Stephen

Can you help with this problem?

Provide an answer of your own, or ask Hans Deragon for more information if necessary.

To post a message you must log in.