login
Search
I'm having a weird problem: I upgraded to the 2.6 kernel this weekend. I have two computers, both desktops, and a KVM switch. Now, mousewheel and all works great until the first time I switch to the second PC - after switching back to my 2.6 box, mouse and keyboard still work, but the mousewheel is gone. This did not happen with the 2.4 kernel (yeah, I know, different input model, that's why I highly suspect the kernel - that and no other significant update since then).
Did anybody else have this problem? Any pointers (or good google phrases - mine didn't seem to work).
Thanks,
Anno.
compile in evdev
compile in evdev
thanks, but...
I did so. I even pointed my X mouse to the correct event device. Unfortunately, no go. If I do a cat on /dev/input/event0 (mouse) and move the mouse or click buttons, junk appears on the screen (as expected), but no reaction with the scroll wheel.
*cries*
Further ideas would be very welcome. TIA.
I feel your pain too
I have tried kernel 2.6.5 and 2.6.7 compiled until my cpu's cried from overload. I too can not get my usb scroll mouse (logitech) to scroll. However the mouse works flawlessly in every other fashion.
my xf86config has been set up to use ZAxisMapping 4 5.
I have tried several mouse protocols from "auto", "imps/2" ,etc, etc
I have also tried changing the device it uses to /dev/input/mouse0, /dev/psaux, etc, etc.
I have several other working xf86configs that I have been working and troubleshooting off of. I still can not figure it out.
Ditto
have the same thing. one switch to another box and scroll down is gone,. scroll up makes all kinds of strange things happening.
try this
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
hotplug?
I feel your pain. :(
I did find that unplugging the mouse and plugging it back in re-enabled the mouse wheel. I get something like this.
Jul 19 11:57:21 storm input.agent[3511]: evdev: already loaded
Jul 19 11:57:21 storm input.agent[3529]: evdev: already loaded
Jul 19 11:57:21 storm input.agent[3547]: evdev: already loaded
Jul 19 11:57:21 storm kernel: input: PS2++ Logitech Wheel Mouse on isa0060/serio1
Any ideas if there is a way to force this event without having to physically unplug the mouse?
Simmilar problem (but worse)
I have Two machines (both running debian unstable) and a KVM switch, but the mouse is serial (not USB). Switching to another machine under kernel 2.6.5 caused problems until I used the "mouse.proto=bare" parameter upon boot.
However, with 2.6.7 kernel, after a switch the mouse is just dead. It does not move, at all. Under 2.4 kernels (yeah, different even model, I know) switching to a non-X virtual console and back worked to "restart" the mouse. It does so no longer. Right now, my KVM switch is completely
uselsess to me - since if I switch to a machine I have to reboot it before I can use it.
I don't understand exactly why this would happen. Are the mouse events numbered? Is it a long time without any messages from the mouse that confuses the driver? I'm open to any suggestions on what I could try to remedy the situation.
kernel option anyone it fixed mine
Add this to your kernel cmdline in grub or lilo
psmouse.proto=imps
It fixed mine
uname -r 2.6.7-1.459.
Plus this in your x config
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
Grub and Lilo command line
Sorry I'm newbie,
where do I insert these lines fro Grub (my actual bootloader) or in Lilo (Suse 9.1 doesn't wants to install it for the moment).
What should I do if I choose to avoid using the bootloader?
Thanks
Roberto
kernerl option worked
psmouse.proto=imps
That worked, thanks.