HI All,

I see that this has been posted a bunch but i cannot find anything that is concrete.. i have however found the things i should be looking for but still stumped
Slackware10.1 kernel 2.6.15 / Dell 700m Laptop (integrated synaptics touch
Mouse: Logitech wireless USB

SO what are the things i need to check?
I have tried running 'mouseconfig' and selecting USB and 'Yes' to GPM with no change.
I have tried the above and said 'No' and then #'d out the line for GPM.

I have tinkered around with the Xorg.conf file and tried various settings with no change. Currently it is set tpo 'PS/2' for into and 'auto' for protocol.

All this said, the PS/2 (touchpad) works fine pre - Xwindows.
So i can move the 'touchpad' mouse around on the first login screen.

the device that is being loaded when KDE starts is /DEV/Mouse
Which i think currently points to /DEV/psaux -

Where should it point for USB?
I notice while booting the snaptics touchpad driver loads but it goes too fast for me to see whether USB Probing is active.
SHould it be?

When i go into 'control centre' in KDE it can see the USB port and appears to be fine. unsure if it can see a device connected since kernel upgrade. I am sure i selected all the USB options prior to compiling.

** At no point during boot or in KDE' does the RED OPTICAL light on a NORMAL intellimouse light up either (I have 2 x USB mice to test).... sounds like a problem right?

Pls dont say i need to recompile kerel
I have everything on this puppy working a charm incl ipw2200 wifi driver/networking tools/patch for video 1200x800/great eye candy in KDE but i am totally lost here...

Something to do with this PROC business i bet

Thanks!!

Maybe one of those SW on your lappy google references will have xorg.conf file to help setup 2 mice. Your touchpad(one mouse) is configured and works as mouse or whatever you labelled it and the 2nd mouse wound be mouse1 for example. Then the server layout section should have mouse as "CorePointer" and mouse1 with "SendCoreEvents"along with keyboard. But that Logitech mouse and the wireless whatever-you-call-it that connects to lappy usb2 port have buttons to turn power on that may not be easily seen. Check for those. lsusb with mouse connected should show the mouse. lsmod would show right modules. My usb MSIntellimouse with IntelliEye works with /dev/mouse, auto protocol, and ZAxisMapping "4 5" on SW10.2. Some use /dev/input/mouse or mice and IMPS/2 protocol. No gdm. Congrats on 2.6.15 config! And good luck.

HI Lestoil,

Thanks for the info!

Yes, the touchpad works fine (a lot of the compaq and dell gear use synaptics touchpad/drivers) <-- i think thats the whatever you call it

I did not know about the mouse and mouse1 thing either.. i will have to look at this.

OKay so i should disable the GDM then? That seems to be what i have been reading to get it to work properly in KDE.. Thing is the USB mouse doesn't work before loading KDE anyway.
My mouse is similar to your's, just logitech.. has a USB receiver that looks a lot like a memory key.

How do i go about checking whether USB Probing is active when booting?
Is there a log file that shows all the steps during boot and outcome?
If so, where can i find it usually//
Im sure it has something to do with this..
Especially as if i plus a regular USB Optical mouse in, the RED light does not come on... this seems strange?

The port does have power though as a externl USB HDD spins up fine (but i cannot seem to read that iether)

Thanks again

Well I bit the bullet and re-compiled kernel 2.6.15 again.

After looking through my .config i noticed what the problem was - reading what OHCI was all about, thats what i had left out.
I did not include OHCI or UHCI in the original config.
Both are included as Modules now and Logitech Wireless USB Mouse is working a real treat!! (And the Synaptics touchpad works simulateously no problems)

# USB Host Controller Drivers
CONFIG_USB_EHCI_HCD
CONFIG_USB_OHCI_HCD
CONFIG_USB_UHCI_HCD

# USB support
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m

/DEV/MOUSE used as device in xorg.conf
Protocol set to 'Auto' in xorg.conf

Thanks for your help lestoil, your suggestions made me realise what must be going on.. cheers

Graz!

Thank you so much! I have been suffering the same problem since I compiled my 2.6.15 kernel. I wasn’t able to get my mouse working for so long I actually rebuilt Slack and recompiled a clean kernel, still no luck. I finally came across this thread and did what you did, recompiled with OHCI module support (I already had the other one) and copied the kernel installed modules and works great! It made my night. : ) Now to the next thing to pull my hair out!

Hey Kazt,

Excellent! Thanks for the note..
Yeah i was sooo stoked when i got it working.. I then had problems with the scroll on my mouse which has since been fixed too..
Unsure if your having the same issue.. If so, i had to add the below to the Xorg.conf file in /etc/x11

I added the below in Xorg.conf

Identifier "Mouse1"
Driver "mouse"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

Yes I also had that issue. thankfully its fixed. no its just problems with compiling the 2.6.15.3 kernel now : ). I upgraded from 2.4.31 which was the stalk that came with slack 10.2. yah after I compiled it and did everything I needed to do(i think) I got a lot of -mcpu try is deprecated -mtune or -march warning when compiling kismet. I thought maybe it was GCC so I updated that with no change. I have read almost every post not only on this site but also what ever google found and
nothing seems to have helped. some of the things are about making sure I have the kernel source, but I downloaded and extracted in the /usr/src directory. then I did a make xconfig then I saved the .config file did a make, then make modules_install, then cp the bzImage to /boot/vmlinuz-2.6.15.3 and also cp the System.map. also configed lilo and ran /sbin/lilo.

I dont know i'm going to blow everything away and start fresh and see.

ok so I blew everything away : \ I started with the 2.4.31 kernel and I tried to compile the program (kismet) I was trying after the 2.6.15 upgrade, same problem! I could have sworn I have compiled kismet before with out those warnings.. I wonder if I just let it go threw and then install madwifi after the kernel upgrade if it will work, will see!

Oh okay, yes i have since got kismet working perfectly as well. since upgrading to 2.6.15
I also had to get special driver and firmware from my nic (ipw2200).. is working perfect though,. I also compiled from /usr/src