JInput needs /dev/input/event* - How do I get them

hi

For JInput needs /dev/input/event* device nodes, I need them to use JInput. I’m running Mandriva 2005 LE with standard kernel. In /dev/input/ there are just two files “mice” and “mouse0”, if I remember correctly. Maybe I have turned off a responsable daemon. I don’t know. Can anybody tell me how to get these f***ing nodes?

Or maybe I don’t need them to use JInput; even better.

Please help me

Qudus

Hi

Those are the nodes needed to used the devices, It looks to me like your distribution doesn’t have the event interface modules built in.

My kernel config has this in it.

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_MOUSEDEV_PSAUX_ENABLE=y
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_TSDEV=m
CONFIG_INPUT_TSDEV_SCREEN_X=240
CONFIG_INPUT_TSDEV_SCREEN_Y=320
CONFIG_INPUT_EVDEV=m
CONFIG_INPUT_EVBUG=m

Those nodes will also only appear when you have a device plugged in, but with the right modules, even just a mouse/keyboard will count and create /dev/input/event* nodes

Unfortunatly your distribution doesn’t seem to have much info online that people who don’t have it can get at. You’ll have to register your product and ask on there unless you are familiar with kernel building.

Endolf

On my platform (SUSE9.3) I currently get a list of event nodes that dont exist that all seme to be related to rumble code.

However it runs fine and hears my KB and mouse :slight_smile:

Hi

Don’t know about suse, but redhat always used to create hundreds of dev nodes for every device under the sun, I think it created something like 5 js nodes even if non were plugged in, gawd knows how many hdd nodes it created :slight_smile:

Endolf

Ok, got that fixed. I just plugged my mouse to the usb port. Before it it was plugged to the ps2 port. After I did that there were three event nodes and after I changed the rights jinput found my mouse and my keyboard. Why did it find the keyboard after that and not before?

Anyway, the problem is fixed for me.

Hi

Not sure whats going on there, it still sounds like a kernel config/compile issue. The good news is it’s working though :slight_smile:

Endolf