LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   USB mouse on a new 2.6.5 kernel (https://www.linuxquestions.org/questions/linux-hardware-18/usb-mouse-on-a-new-2-6-5-kernel-166999/)

dulles 04-06-2004 04:01 PM

USB mouse on a new 2.6.5 kernel
 
I just installed a 2.6.5 kernel on my fresh Debian (woody) system and I can't get gpm to see my usb mouse.

I don't use X and have yet to see if X does it. I suspect not, because:

cat /dev/input/m* (mice, mouseX) yields "No Such Device"
cat /dev/usb/mouse* (mouseX) yields "No Such Device"

I did load all the usb modules (with the new module-init-tools), and tried various combinations. They all seem to work just fine.

I did not, however, set CONFIG_USB_MOUSE to Y because the help text (I use make menuconfig) seemed to very strongly recommend against it. Apparently it is used for special (eg, non-desktop systems).

Is this true? Do I need this module? What else could be the trouble?

Also: /dev/bus/usb does not exist. Is this deprecated?

update: If you're running a 2.6 kernel with a USB mouse, can you please post an 'lsmod' for me to see?

Thanks!

waster 04-06-2004 05:09 PM

My system has evdev and hid (human interface devices in the config) kernel modules compiled and loaded, and then the mouse events are on /dev/event something or other, as well as /dev/input/mouse1 (and /dev/input/mice )

vectordrake 04-06-2004 10:23 PM

evdev 9504 0
tsdev 7168 0
usbmouse 5216 0
hid 53312 0
uhci-hcd 29104 0
usbcore 99132 5 usbmouse,hid,uhci-hcd


That's what's loaded on my box with 2.6.3-7mdk. Not sure what tsdev is (seems to have to do with x,y-resolution - perhaps to do with the mouse)

waster 04-07-2004 02:46 AM

tsdev will be touch screen device - remove this to be on the safe side. Maybe your usb mouse is incorrectly detected? does 'dmesg' give any information. I get a lot of loggin output for USB devices , even without the extra debugging info option in the kernel configuration.

If you know how, you can recompile your kernel with extra debugging info. In the meantime, try this:

cat /dev/input/mouse0

then wiggle your mouse
try this for each of the possible devices, and dev/eventxxx , and /dev/psaux as it could be mirrored here from the real source. Personally, I've never used gpm and don't see the point.

dulles 04-07-2004 07:23 AM

Ah.... I see you didn't read my post:

cat /dev/input/mice (and all the variants thereof, such as mouseX)
gave "No such device". /dev/input/mouseX as well.

Anyway, I seem to have gotten it working. I tried evdev with usbmouse and it kicked in instantaneously. Now it works withouh evdev too! Some weirdness is going on, I tell you: it didn't used to work with just ohci_hcd, usbcore, and usbmouse, but now it does. Oh the finicky ways of the kernel.

So thanks everyone for ya'll's help!


All times are GMT -5. The time now is 10:05 AM.