View Full Version : FC2 usb Mouse does not work; only stupid touchpad
tomforce
30th May 2004, 09:42 AM
Hi
i upgraded to FC2 but now my USB Mouse does not work anymore
I have a Laptop with a touchpad, which never worked in FC1
but that was not a problem because i didn't want to use the touchpad, i always used my mouse
and now in FC2 the mouse does not work anymore, but the touchpad works
so, can someone help me with this
i tryed #setup and changend the mouse from ps/2 to usb, with different buttons
but it didn't help
i have an optical mouse and the red light is always off
tomforce
31st May 2004, 10:42 PM
i give you more information
in my modprobe. conf i have these entrys with usb in them
alias usbdevfs usbcore
install usbmouse /sbin/modprobe --first-time --ignore-install usbmouse && { /sbin/modprobe hid; /bin/true; }
remove usbmouse { /sbin/modprobe -r hid; } ; /sbin/modprobe -r --first-time --ignore-remove usbmouse
alias usb-uhci uhci-hcd
alias usb-ohci ohci-hcd
and these are the ones with the word mouse in them
alias char-major-10-2 msbusmouse
alias char-major-10-3 atixlmouse
alias char-major-13-32 mousedev
install usbmouse /sbin/modprobe --first-time --ignore-install usbmouse && { /sbin/modprobe hid; /bin/true; }
remove usbmouse { /sbin/modprobe -r hid; } ; /sbin/modprobe -r --first-time --ignore-remove usbmouse
i hope now someone can help me
in an other post someone said this
lspci -v | grep HCI
gave him the modules which he needed
but lspci does not work on my system, the bash does not know the command
or does the XKB Configuration has something to do with this, because on startup i get an error box which sais, "there is an error on activating the XKB Configuration, maybe there is an problem with the X Server......"
so please help me
thanks
and by the way in ->Systemtools->Hardwarebrowser
there is an USB entry with
VT82xxxxx UHCI USB 1.1 Controller
from Via, with the driver: uhci-hcd
tomforce
4th June 2004, 04:56 AM
well nobody really helped me here so i just tryed something
i added this two lines, which i found in another thread, just changed them a little
alias usb-controller uhci-hcd
alias usb-controller1 ohci-hcd
into my modprobe.conf and rebooted the pc
and now my mouse works
don't know what the 2 lines do, or if 1 line would be enough, but who cares, it works
so next thing the %&x§# sound, lets go
wohooo
Thetargos
4th June 2004, 08:15 AM
:lol: the problem was the naming of the USB drivers. The 2.6 kernel (such as FC2's) uses a different name for the different USB hub types, what was called in 2.4 usb-ohci, in 2.6 is ohci-hcd (for hub controller device, I think), so forth and so on for the uhci hub type. ehci however has always been called ehci-hcd.
The alias thing is just an internal name really, so you can load the correct module by just calling the alias (more descriptive) instead of the actual driver name. In Red Hat and FC, these modules are loaded via the /etc/rc.d/rc.sysinit script, and this script loads the usb-controller* aliases rather than the device drivers themselves. So this is why it worked (you my have also gotten it to work if in /etc/rc.d/rc.local you had added a line like modprobe ohci-hcd uhci-hcd)
klik
25th July 2004, 12:28 AM
I had the same problem. After viewing in the modprobe.conf, there already stood
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
I changed the first line to uhci-hcd, and it worked fine.
KLiK
Viro
25th July 2004, 04:47 AM
ehci-hcd is for a USB2 controller. If you don't have a USB2 controller, you can safely comment that out.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.