slackware 9.1 USB mouse and other usb devices not working
 

Hello, i have recently installed slackware 9.1, and my optical USB mouse does not work.

The mouse is: optical USB wheel mouse, the brand name appears to be "Val Gear". there are 2 buttons and wheel that can be depressed and act as a third button as well as a wheel.

When booting up there are oodles of messages concerning usb devices that say things like "bulk timeout". These messages fly by and i cant read them all.

lsmod reveals the following modules are loaded (there are others laoded but i dont think they are related to USB):

usbmouse 2008 0 (unused)
mousedev 4244 0 (unused)
hid 21156 0 (unused)
input 3200 0 [usbmouse keybdev mousedev hid]
uhci 24496 0 (unused)
ehci-hcd 16872 0 (unused)
usbcore 58400 1 [usbmouse hid uhci ehci-hcd]

I cut and pasted this while using a PS2 mouse.

I used the bare.i distro kernel, although i think that should be fine.
I dont think this is an Xfree86 issue, since my mouse is supposed to work before i "startX", and it does not.

when i reconfigured and pointed the /dev/mouse file to a PS2 mouse, the PS2 mouse worked fine before starting X and after. I think this is a matter of finding the correct modules for this USB mouse.

I realy want this USB mouse to work, because my PS2 mouse is garbage. thanks for any help.

This might work

Unplug the USB mouse then as root run the coomand tail -s 3 -f /var/log/syslog

Now plug in the mouse and it should show on the console where the mouse is, ie sd1 or whatever.

Then link that to /dev/mouse

Hope this works

usb still does not work
 

thank you for the suggestion.
I tried your suggestion, and this was the result:
from syslog:
Jan 23 20:51:25 nc kernel: usb_control/bulk_msg: timeout
Jan 23 20:51:43 nc last message repeated 150 times
Jan 23 20:52:32 nc kernel: usb_control/bulk_msg: timeout
Jan 23 20:52:32 nc kernel: usb.c: USB device not accepting new address=3 (error=-110)
Jan 23 20:52:37 nc kernel: usb_control/bulk_msg: timeout
Jan 23 20:52:37 nc kernel: usb.c: USB device not accepting new address=4 (error=-110)
Jan 23 20:54:31 nc kernel: usb_control/bulk_msg: timeout
Jan 23 20:54:31 nc kernel: usb.c: USB device not accepting new address=5 (error=-110)
Jan 23 20:54:37 nc kernel: usb_control/bulk_msg: timeout
Jan 23 20:54:37 nc kernel: usb.c: USB device not accepting new address=6 (error=-110)

it seems my usb mouse doen not want to cooperate.
any other ideas?
has anyone else seen this before?

i would like to get usb working, as i have other usb devices as well.
i have tried to change my usb modules from uhci to one of the others (usb-uhci, usb-ohci) but this only spat insmod errors:

bash-2.05b# modprobe usb-ohci
/lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: init_module: No such device
/lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: insmod /lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz failed
/lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: insmod usb-ohci failed
bash-2.05b#

I am running low on ideas. suggestions?

What usb chipset do you have?
The command "lspci -vv" will tell, just post the usb info.
Also the command "lsusb" will tell us if the mouse is detected correctly.

some more information:
I tried this command that I saw elsewhere while trying to figure this out:
>lspci -v | grep HCI
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])

more specificaly:
>lspci -v (verbose with usb sections)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e000 [size=32]
Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at e400 [size=32]
Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e800 [size=32]
Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at dffffe00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2


tired of reading yet?
could this be some power management thing? are my usb devices turning themselves off before they can be used?
again, i would appreciate any help.

bash-2.05b# lsusb
Unknown line at line 1809
Duplicate HUT Usage Spec at line 2650
Bus 004 Device 001: ID 0000:0000 Virtual Hub
Bus 004 Device 002: ID 124b:4d01
Bus 004 Device 003: ID 046d:c20b Logitech Inc.
Bus 003 Device 001: ID 0000:0000 Virtual Hub
Bus 002 Device 001: ID 0000:0000 Virtual Hub
Bus 001 Device 001: ID 0000:0000 Virtual Hub

00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin A routed to IRQ 11
Region 4: I/O ports at e000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin B routed to IRQ 5
Region 4: I/O ports at e400 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin C routed to IRQ 10
Region 4: I/O ports at e800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin D routed to IRQ 5
Region 0: Memory at dffffe00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

OK; I just hooked up a usb mouse and it worked with Slack 9.0.
If these directions don't work your past my knowledge.

Plug the mouse in

As root run mouseconfig and pick usb for usb connected mouse

Reboot

Wel, that tells us that modprobe usb-ohci won't do any good because you don't have an ohci chip, what you do have is an uhci usb 1.1 controller and an ehci usb 2.0 controller. There are two modules for uhci controllers, uhci and usb-uhci and you have uhci loaded, you need to try the usb-uhci module. Did toy install hotplug? If yes then look at /etc/hotplug/blacklist, make sure it says uhci and not usb-uhci, if it says neither then add uhci to it and reboot.

Thank you sharper, but i have already tried that :)
In fact that was my choice at setup when i installed. the mousconfig uses this for gpm:

gpm -m /dev/input/mice -t imps2
or something very much like it.
I have however tried to do this again after loading the other type of usb support. see below.

I have since tried to load the other type of usb support, as suggested by changing the line in my blacklist file to be "uhci" instead of "usb-uhci". now the loaded modules are:

mousedev 4244 0
hid 21156 0 (unused)
usbmouse 2008 0 (unused)
input 3200 0 [keybdev mousedev hid usbmouse]
usb-uhci 22188 0 (unused)
ehci-hcd 16872 0 (unused)
usbcore 58400 1 [hid usbmouse usb-uhci ehci-hcd]
amoung modules that dont appear to be usb related.

i have tried to use the mouse again. no luck. here is some of the output from using the command: >tail -s 3 -f /var/log/syslog
Jan 23 22:39:51 nocode kernel: usb.c: USB device 3 (vend/prod 0x46d/0xc20b) is not claimed by any active driver.
Jan 23 22:39:51 nocode kernel: usb-uhci.c: interrupt, status 2, frame# 1125
Jan 23 22:39:51 nocode kernel: usb.c: error getting string descriptor 0 (error=-75)
Jan 23 22:39:51 nocode kernel: usb_control/bulk_msg: timeout
Jan 23 22:39:53 nocode last message repeated 99 times
Jan 23 22:43:39 nocode modprobe: modprobe: Can't locate module char-major-10-134Jan 23 22:48:51 nocode kernel: usb_control/bulk_msg: timeout
Jan 23 22:48:51 nocode kernel: usb.c: error getting string descriptor 0 (error=-110)
Jan 23 22:48:56 nocode kernel: usb_control/bulk_msg: timeout
Jan 23 22:48:56 nocode kernel: usb.c: error getting string descriptor 0 (error=-110)
Jan 23 23:00:21 nocode kernel: usb_control/bulk_msg: timeout
Jan 23 23:00:21 nocode kernel: usb.c: USB device not accepting new address=3 (error=-110)
Jan 23 23:00:26 nocode kernel: usb_control/bulk_msg: timeout
Jan 23 23:00:26 nocode kernel: usb.c: USB device not accepting new address=4 (error=-110)

thank you again for the help and directions.

the pesky mouse still does not work. i know it is functional since i use it in windows. it had no required software, just plaugged it in and it was working.

hmmm, I have a logitech MX300(USB) and it works fine in slackware9.1. Even though yours is plugged in the USB, run mouseconfig and select PS/2 mouse. For some reason my mouse still worked when it was setup as ps/2 but plugged in to USB. Do you have an adapter to plug it in to the ps/2 port? You might have to sacrifice a little responsitivity to get it to work in linux and windows.

i purchased a usb-to-ps2 adaptor, so my usb mouse is now a ps2 mouse. however the wheel part of it does not work. This is not realy a solution to my problem, and my other usb devices still dont work. (32MB mass storage device, and an airflo game controller.) but at least i can use a halfway decent mouse now. I am optimistic about the wheel part.

I used the mouseconfig program to set up my mouse as a ps2.
I would still like to get USB working properly. I will be compiling the kernel and modules soon, so perhaps that will fix the problem.

thanks for the help thus far, i have learned a few things.http://www.linuxquestions.org/questi...readid=137767#
any more suggestions / help is welcome.