Jump to content

USB GamePad Problems


Lärs
 Share

Recommended Posts

Well, it seems that I'm having more trouble with USB devices. I think this one would take a different measure to correct.

The other day, I bought a Logitech Dual Action USB GamePad. I plugged it in my USB port and ran HardDrake. But for some reason, HardDrake won't load, lest detect it, and my comp crashes when I boot up and autodetection takes place.

I've tried several things. What I did first is disabled supermount, as USB devices seem to slow down my system when it's enabled. I modprobed joydev (in konsole and in the pure X-less console), and it seemed to work out fine. Then I ran ZSNES to test if the joystick would work. Apparently not.

I've given up since then. I'm running KDE 3.2 with Mandrake 10.1 Official. What must I do to get HardDrake to properly detect it and *maybe* load the Module on boot, without hanging? Any suggestions?

Link to comment
Share on other sites

it's a USB device so it uses the usbhid module, IIRC, which you'll have loaded already if you have a USB mode. It should show up in /dev/input ; look for /dev/input/js0. If it exists, the joystick's been picked up. zsnes may just be looking for /dev/js0 or something else that's not /dev/input/js0 , see if this can be configured.

Link to comment
Share on other sites

Well, it did not show up. It doesn't exist in /dev either. Is there a way I can copy it from one of the Mandrake CDs and put it in /dev/input temporarily? Or some kind of workaround like that?

Link to comment
Share on other sites

/dev/js is a device. It's not something you can copy from the CDs. It gets created when the the module (=driver) gets loaded (installed). :)

 

Open a console, log in as root and type lsmod. Is joydev in the list? If not do modprobe joydev and look again. If it is in the list look in /dev for a js0, js etcetc again.

Link to comment
Share on other sites

Yeah, I figured such, and when I modprobe for the joystick everything seems to go fine, but no js* in /dev/input. Joydev is somewhere in /lib, I know that for certain... Hmm. I'll try some more of what has been said.

Link to comment
Share on other sites

Hi everyone, I have been following the thread and I have the exact same problem. So i have attached the output of the dmesg when run on my PC, hope you can help my as well

Regards TLEdmesgoutput.txt

Link to comment
Share on other sites

I don't see the gamepad mentioned in the output. Can you unplug/plug in the gamepad and run dmesg again?

 

usb 1-2.2: USB disconnect, address 3

usb 1-2.2: new low speed USB device using uhci_hcd and address 8

input: USB HID v1.00 Joystick [Microsoft Microsoft SideWinder Precision Pro (USB)] on usb-0000:00:1f.2-2.2

 

You need to see something like this (this is for my sidewinder)

Link to comment
Share on other sites

Oh sorry, i missed the huge USB part of the headline, I have been reading a lot of thrads and just saw that the problem was that there is no device detected, and that is the same thing i am seing. But my problem is actually about a joystick and with the old kind of connection, (read NOT USB). So I'm not sure this is the same thing, sorry for the misunderstanding

Link to comment
Share on other sites

Ok I apologize for the delay, but I haven't had net access for a while, and my Linux box doesn't have net access either (which is no help) :D . Ok so basically my dmesg (at the end) said this.

usb 1-2: new low speed USB device using address 2

 

It didn't recognize what the joystick was though.

I modprobed for joydev, and nothing happened, according to dmesg. However I do know the joydev driver went into memory.

I unplugged and plugged in the gamepad again.

Basically dmesg said that the low speed device was removed, and it didn't detect it the second time.

Alsa and harddrake (the module harddrake) are reacting oddly to the gamepad. If I boot up the computer with the gamepad in, harddrakes convenient "detecting new hardware" freezes, and when I boot out after trying to get the gamepad to work (and unplugging it properly), alsa won't shut down.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...