Mouse does not work in 2.6.3

beajedi · 03-01-2004, 06:08 PM

Hello,

I am running slackware 9.1 and have a Logitech Optical wheel mouse.

I compiled the 2.6.3 kernel using the same options that were selected in the 2.4.22 kernel.

when I booted into the new kernel, I was shocked to find out that my internet, sound, and mouse did not work.

However, I discovered that the modules simply weren't loaded.

So I did

modprobe emu10k1
modprobe 3c59x

and I was able to get sound and network to work again.

But I'm still don't know how to get the mouse to work in 2.6.3! It worked perfectly fine in my 2.4.22 kernel...

Also, how do you set it up so that my sound/network modules load on startup?

DrOzz · 03-01-2004, 06:13 PM

maybe just try running xf86config and picking a generic mouse thats most closely related to your mouse from the list and see if you can get it to work that way ...
and then tweak it yourself to get other features like the wheel and side buttons or whatever else to work after the initial step ...

Code:

First specify a mouse protocol type. Choose one from the following list:

 1.  Microsoft compatible (2-button protocol)
 2.  Mouse Systems (3-button protocol)
 3.  Bus Mouse
 4.  PS/2 Mouse
 5.  Logitech Mouse (serial, old type, Logitech protocol)
 6.  Logitech MouseMan (Microsoft compatible)
 7.  MM Series
 8.  MM HitTablet
 9.  Microsoft IntelliMouse

If you have a two-button mouse, it is most likely of type 1, and if you have a three-button mouse,
iit can probably support both protocol 1 and 2. There are two main varieties of the latter type:
mice with a switch to select the protocol, and mice that default to 1 and require a button to
be held at boot-time to select protocol 2. Some mice can be convinced to do 2 by sending
a special sequence to the serial port (see the ClearDTR/ClearRTS options).

Enter a protocol number:

this is the step you'll be looking for ...

but i want you to notice one thing before you take the above into consideration ..
and that is ... is your mouse connected by USB ? maybe you need to do the same for USB and load the modules before the mouse will get picked up ...

beajedi · 03-01-2004, 09:27 PM

Yeah it is a USB mouse. And it works just fine in 2.4.22.

And shouldnt the xf86 configs simply carry over to the next kernel?

I did an "lsmod" and tried to write down all the modules installed so I could modprobe them all in 2.6.3.

Here's what my lsmod looks like:

Module Size Used by Not tainted
emu10k1 61064 3
ac97_codec 9512 0 [emu10k1]
soundcore 3332 4 (autoclean) [emu10k1]
keybdev 1952 0 (unused)
mousedev 4244 1
hid 21156 0 (unused)
usbmouse 2008 0 (unused)
input 3200 0 [keybdev mousedev hid usbmouse]
uhci 24496 0 (unused)
usbcore 58400 1 [hid usbmouse uhci]
emu10k1-gp 1352 0 (unused)
gameport 1452 0 [emu10k1-gp]
ohci1394 24200 0 (unused)
ieee1394 42436 0 [ohci1394]
3c59x 26832 1
pcmcia_core 40032 0
ide-scsi 9424 0
agpgart 39576 0 (unused)

Which one is the necessary one for USB?

I guessed it to be USBcore, usbmouse, and mousedev. Maybe hid too.

scottwest2 · 03-01-2004, 11:51 PM

for the auto module load on boot edit your /etc/rc.d/rc.modules and search for the modules you are looking for and uncomment them, if they aren't there then add "/sbin/modprobe 'module_name'" to the end of the file for each module.

DrOzz · 03-02-2004, 03:34 AM

Quote:

The names for the USB modules are different. This affects /etc/modprobe.conf (look for ``usb-controller'') and, once again, /etc/rc.sysinit. I had to rename all instances of ``keybdev'' into ``usbkbd'' and ``mousedev'' into ``usbmouse''. In addition, I replaced all instances of ``/proc/bus/usb'' with ``/sys/bus/usb''. (Also do this last part in /etc/init.d/halt.)

Look for ``needusbstorage'' in /etc/rc.sysinit. I changed that section into:

needusbstorage=
if [ $usb = "1" ]; then
needusbstorage=`LC_ALL=C grep -e "^I.*Cls=08" /sys/bus/usb/devices 2>/dev/null`
action $"Initializing USB HID interface: " modprobe hid 2> /dev/null
action $"Initializing USB keyboard: " modprobe usbkbd 2> /dev/null
action $"Initializing USB mouse: " modprobe usbmouse 2> /dev/null
fi

here is something that affects some, and this is quoted from another site ...
see if this is in relation to your problem ... the usb modules names changed in 2.6 .

tesauce98 · 03-04-2004, 01:05 AM

i'm having a similar problem. i've been fiddling with 2.6.3 all day. i have it running on my compaq presario laptop, and the 2.4.24 kernel worked fine. however when i went to 2.6.3, i had fun trying to fix a lot of the stuff. i was able to fix my sound, but i noticed my usb mouse wasn't working. after some investigationg, i found that none of my USB stuff was working. i think the renamed USB modules in 2.6.3 has something to do with it.

being that i'm on a compaq, the USB root drivers i need to use are OHCI (ohci-hcd). i have this module installed but when i try loading it, it says:
FATAL: Error inserting ohci_hcd (/lib/modules/2.6.3/kernel/drivers/usb/host/ohci-hcd.ko): No such device

any ideas on the problem, i feel i may be missing some important things i need to be compiled into the kernel, because i started with a completely blank kernel config file for this kernel, so i could hopefully leave out a lot of unnecessary stuff. (slackware just needs to come out with bareacpi.i kernel image and modules for 2.6

)

on a side note, i'm also getting fatal errors about agpgart, but i think i need this for 3D support. and apparently the new xfree 4.4 has 3D support for my radeon mobility U1 so i want try messing with that later.

S_Warlock · 03-04-2004, 02:11 AM

In 2.6.x they have change /dev/mouse to /dev/psaux.
So if you have a ps/2 mouse.
Change the follow line in XF86Config:
From :

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/mouse"
EndSection

to :

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxismapping" "4 5"
EndSection

Good luck !

/ Teo

beajedi · 03-09-2004, 04:24 PM

Thanks all, I got everything to work.

It was a matter of turning on all the USB devices I could find in my "menuconfig" and making sure that they were all loaded in my rc.modules startup script.

Looking_Lost · 03-10-2004, 02:28 AM

You should run generate-modprobe.conf aswell when you first compile and install it, something I forgot to do, although it never affected my usb mouse, /dev/input/mice still worked as normal. Then alsaconf for the sound.