gravis elimator gamepad issues...

kalif · 08-27-2003, 10:52 PM

i am having issues with my gravis eliminator gamepad...
i tried to uncomment items in the /etc/rc.d/rc.modules file that i thought pertained to the gamepad but nothing has worked so far...

i am going to continue to try uncommenting lines but help would be greatly appreciated. maybe then i could enjoy some snes games instead of messing about...

kalif · 08-28-2003, 09:44 PM

still no luck with an answer?

kalif · 08-29-2003, 12:57 AM

alright.. i was able to make my gamepad work (with minimal fuss due to reading a post by footfrisbee). now i just need to know how to make the pad input to my zsnes emulator... do i have to recompile it... or can i just change some config?

kalif · 08-29-2003, 03:48 AM

update... recompiling zsnes had no success...

footfrisbee · 08-30-2003, 01:57 AM

I've had no problems getting zsnes to recognize my gamepad pro. Are your permissions set ok? When you run zsnes off the command line does it say that it sees any joysticks?

kalif · 08-30-2003, 04:13 PM

bash-2.05a# zsnes

ZSNES v1.36 (c) 1997-2002, ZSNES Team (zsKnight & _Demo_)

Be sure to check http://www.zsnes.com/ for the latest version.
Please report crashes to zsnes-devel@lists.sourceforge.net.

ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE' thoroughly before using it.

Use ZSNES -? for command line definitions.

MMX support found and enabled.

You are running in 24 bpp, but ZSNES is forcing 16 bpp.
You may experience poor performance and/or crashing.

mcop warning: user defined signal handler found for SIG_PIPE, overriding
mcop warning: user defined signal handler found for SIG_PIPE, overriding
ZSNES could not find any joysticks.

i am guessing by this that the answer is no, by it telling me it does not. what should i do to fix permissions? or is it something else?

footfrisbee · 08-30-2003, 09:59 PM

I though of this a bit later. Zsnes may be looking in the wrong place for your joystick. Try making a symlink from /dev/input/js0 to /dev/js0. Changing the permissions is probably not necessary.

kalif · 08-30-2003, 11:40 PM

the joystick that works is /dev/input/js0 and the one that does not is /dev/js0... so should i deleted /dev/js0 and make a link from /dev/input/js0 to replace it?

kalif · 08-30-2003, 11:41 PM

ps... i found this out after $ cat /dev/input/js0 and $ cat /dev/js0

footfrisbee · 08-31-2003, 01:45 AM

If you're uncomfortable deleting it just rename it to /dev/js0.old or something.

kalif · 08-31-2003, 06:16 PM

alright... now zsnes recognizes the joystick... but it will not let me configure the buttons for a game... here is the compile script updated:

bash-2.05a# zsnes

ZSNES v1.36 (c) 1997-2002, ZSNES Team (zsKnight & _Demo_)

Be sure to check http://www.zsnes.com/ for the latest version.
Please report crashes to zsnes-devel@lists.sourceforge.net.

ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE' thoroughly before using it.

Use ZSNES -? for command line definitions.

MMX support found and enabled.

You are running in 24 bpp, but ZSNES is forcing 16 bpp.
You may experience poor performance and/or crashing.

mcop warning: user defined signal handler found for SIG_PIPE, overriding
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Joystick 0 (2 Buttons): /dev/js0

ps... is there any way to change the "you may experience poor performance and/or crashing"? that does not sound good...

footfrisbee · 08-31-2003, 08:46 PM

It seems the "poor performance" thing is a bit of a disclaimer. It does mean that it may bring X down with it if it goes. I'm not sure why you're zsnes has this problem. My display is set to 24 bpp, and it runs without warning. Perhaps it's a compile switch?

As for configuring your joystick, it seems strange that zsnes only sees 2 buttons. Mine reports 10 as it should. What does your syslog say when you load the hid module?

kalif · 09-01-2003, 12:12 AM

how exactly do i go about finding out what my syslog says when i load the hid module?

footfrisbee · 09-01-2003, 05:03 PM

Well, you can just thumb through /var/log/syslog and see how the module loaded. For example here's the pertinent parts of my syslog with the commands that caused them:

Code:

# modprobe usb-uhci
/var/log/syslog:
Aug 31 20:40:14 Qbert vmunix: usb.c: registered new driver usbdevfs
Aug 31 20:40:15 Qbert vmunix: usb.c: registered new driver hub
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: $Revision: 1.275 $ time 13:03:19 Aug 19 2003
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: High bandwidth mode enabled
Aug 31 20:40:15 Qbert vmunix: PCI: Found IRQ 10 for device 00:07.2
Aug 31 20:40:15 Qbert vmunix: PCI: Sharing IRQ 10 with 00:07.3
Aug 31 20:40:15 Qbert vmunix: PCI: Sharing IRQ 10 with 00:0b.0
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 10
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: Detected 2 ports
Aug 31 20:40:15 Qbert vmunix: usb.c: new USB bus registered, assigned bus number 1
Aug 31 20:40:15 Qbert vmunix: hub.c: USB hub found
Aug 31 20:40:15 Qbert vmunix: hub.c: 2 ports detected
Aug 31 20:40:15 Qbert vmunix: PCI: Found IRQ 10 for device 00:07.3
Aug 31 20:40:15 Qbert vmunix: PCI: Sharing IRQ 10 with 00:07.2
Aug 31 20:40:15 Qbert vmunix: PCI: Sharing IRQ 10 with 00:0b.0
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 10
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: Detected 2 ports
Aug 31 20:40:15 Qbert vmunix: usb.c: new USB bus registered, assigned bus number 2
Aug 31 20:40:15 Qbert vmunix: hub.c: USB hub found
Aug 31 20:40:15 Qbert vmunix: hub.c: 2 ports detected
Aug 31 20:40:15 Qbert vmunix: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Aug 31 20:40:15 Qbert vmunix: hub.c: new USB device 00:07.2-1, assigned address 2
Aug 31 20:40:15 Qbert vmunix: usb.c: USB device 2 (vend/prod 0x428/0x4001) is not claimed by any active driver.


# modprobe joydev
# modprobe hid
/var/log/syslog:
Aug 31 20:40:22 Qbert vmunix: usb.c: registered new driver hiddev
Aug 31 20:40:22 Qbert vmunix: usb.c: registered new driver hid
Aug 31 20:40:22 Qbert vmunix: usb-uhci.c: interrupt, status 2, frame# 867
Aug 31 20:40:27 Qbert vmunix: usb_control/bulk_msg: timeout
Aug 31 20:40:27 Qbert vmunix: usb-uhci.c: interrupt, status 3, frame# 1775
Aug 31 20:40:27 Qbert vmunix: input0: USB HID v1.00 Gamepad [Gravis GamePad Pro USB ] on usb1:2.0
Aug 31 20:40:27 Qbert vmunix: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
Aug 31 20:40:27 Qbert vmunix: hid-core.c: USB HID support drivers

As you can see the modules correctly recognize my Gamepad Pro as such. What I am wondering is if this is working for your setup.

kalif · 09-01-2003, 07:29 PM

Sep 1 00:08:25 fallen kernel: Freeing unused kernel memory: 228k freed
Sep 1 00:08:26 fallen kernel: PCI: Enabling device 00:07.2 (0000 -> 0001)
Sep 1 00:08:26 fallen kernel: usb-uhci.c: Detected 2 ports
Sep 1 00:08:28 fallen kernel: usb-uhci.c: interrupt, status 3, frame# 1004
Sep 1 00:08:30 fallen kernel: usb_control/bulk_msg: timeout
Sep 1 00:09:09 fallen modprobe: modprobe: Can't locate module char-major-10-134
Sep 1 00:09:11 fallen kernel: mtrr: no more MTRRs available
Sep 1 00:09:11 fallen last message repeated 11 times

does not say anything about the gravis pad... so i would assume that it does not, but that is strange because like i said previously... when i cat /dev/input/js0 all the buttons work fine.