Hi. I could use some help tackling the task of getting a joystick to work with
my system. I've been working on this for a few days and have not made much
headway. The short question is: Has anyone successfully gotten a joystick to
work on the game port of a Sound Blaster AWE 32 card? If so, what line
is used in your isapnp.conf file for the game port configuration?

More detail is given below:

I'm running kernel 2.2.9-27mdk. It came with the 1.2.13 joystick modules.
Here's my configuration and what's happened so far.

I have a Sound Blaster AWE 32 sound card with the midi/game port that a
joystick attaches to. [I know the card's not defective because when I ran
Windows a year or two ago, I could use a joystick on this port fine.] The
card is correctly configured to play sound, but I'm not sure if the game port
is correctly configured in my isapnp.conf file.

I attached the joystick I have (a Thrustmaster Phazer Pad) to this port and
then I created the joystick devices (/dev/js0 through /dev/js3) using 

mknod /dev/js0 c 15 0
...
mknod /dev/js3 c 15 3

>From there I loaded the joystick.o module by running "insmod joystick". This
seems to run fine and checking with "lsmod" I find that the module is indeed
loaded.

Module          Size    Used by
joystick        7140    0

However, when I try to load the hardware specific joystick module by running
"insmod joy-thrustmaster" (or any of the other joy-* modules) I get the
following error

init_module: Device or resource busy

Checking dmesg I get

joy-thrustmaster: probe - can't read packet
joy-thrustmaster: no joysticks found

The most likely reason for this seems to be that the card is not being
correctly initialized by isapnp. The lines in my isapnp.conf file for
configuring the game port are:

(Configure CTL009c/374679 (LD 1
(IO 0 (SIZE 8) (BASE 0x200))
(NAME "CTL009c/374679[1]{Game                }")
(ACT Y)
))

My booklet that comes with the SB AWE32 card indicates that the io address for
the game port is indeed 0x200. This step doesn't seem to be accepted though
since a look at /proc/ioports reveals

...
00f0-00ff : fpu
01f0-01f7 : ide0
0220-022f : soundblaster
02f8-02ff : serial(auto)
...
0620-0623 : sound driver (AWE32)
0a20-0a23 : sound driver (AWE32)
0e20-0e23 : sound driver (AWE32)
...

I've edited the /proc/ioports contents above to show the range where 0x200
should be but nothing is listed and also to show all entries that are shown
relevant to the card. Again, sound is working; the game port is not (and I
don't have an IDE device attached to the card).

If anyone can help me figure out how to get the game port working (by perhaps
making an appropriate modicication to the isapnp.conf file, I would appreciate
it.

Any questions or advice, feel free to write.

Tyson.
-------------------
[EMAIL PROTECTED]

Reply via email to