* Daniel Bruno -- Friday 04 March 2005 23:45:
> I have a similar problem with joystick connection.
... except that in your case the joystick doesn't work in *any* application,
right?
> I have a G-Force Plus
> connect to the gameport but it refuses to be detected.
[...]
> $ls -l /dev/input/js0
> crwxrwxrwx 1 root root 13, 0 2001-06-14 03:25 /dev/input/js0
The device is there and readable/writable for all.
> $ groups
> knoppix sudo
This would only be important if the js belonged to a special group and
weren't world-readable/writable.
> $ strace -fF -eopen js_demo /dev/input/js0
For the archive: the device doesn't do anything here. It't only the result
of a copy/paste accident. This is enough:
$ strace -fF -eopen js_demo
[...]
> open("/dev/input/js0", O_RDONLY) = -1 ENODEV (No such device)
It's the kernel which doesn't know anything about your joystick. Don't know
about Debian, but you either have to load a few modules, or even to recompile
the kernel. Something like this should work:
# modprobe input gameport joydev ns558 analog
If I got the order wrong, you have to issue the command a few times. Check
with /sbin/lsmod if all modules are loaded. Try $ jstest /dev/input/js0.
And if it works, edit your /etc/modules.conf or /etc/modprobe.conf, or
whatever is the style of the time. I had this in my /etc/modules.conf
when I still used a gameport js:
pre-install ns558 modprobe "-k" "joydev"
pre-install analog modprobe "-k" "ns558"
alias char-major-13 analog
options analog js=chf
... but I think that this file is obsolete now(?).Today I have a USB js
and all modules are compiled in the kernel.
m.
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
