| Summary: | the mouse-wheel on the device sysmouse does not work | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Andrew Muhametshin <inspirra> |
| Component: | Input/Mouse | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | high | ||
| Version: | 6.8.99.902 (6.9 RC2) | ||
| Hardware: | x86 (IA32) | ||
| OS: | FreeBSD | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Andrew Muhametshin
2005-12-02 19:48:57 UTC
Ran into the same problem on DragonFly BSD, upgrading up to 6.9.0. My old, perfectly working config just stopped working, and no matter what different options I try, I can't get xev to show more than 3 mouse button events. The first problem I had was that it was autodetecting the MouseSystems protocol, instead of the SysMouse protocol. I did some research, and it appears that the sysmouse drivers operate in two levels: 0: MouseSystems 5 byte protocol which handles x, y, and 3 buttons. 1: SysMouse protocol, which has 3 more bytes for z, and buttons 4-10. My mouse has been running in leve 1 before I upgraded. I can be pretty sure of this by the fact that z was working. I can even have moused direct z to x, and that works. So my "ums" USB mouse driver is certainly working. I also know that the level can be changed via ioctl. I tried to force the protocol to SysMouse, and it was doing crazy stuff, so perhaps it was stuck in level 0, trying to interpret it in level 1 when I did that. I am going to research this more, and do some more controlled tests now that I know more about what is going on. Hmm. SetSysMouseRes forces level to 1 when the protocol is SysMouse, so my first theory is probably wrong. The code that reads the protocol appears to have not been changed in ages, too. This is interesting. When: (**) Mouse1: Device: "/dev/ums0" (**) Mouse1: Protocol: "SysMouse" Works But when: (**) Mouse1: Device: "/dev/sysmouse" (**) Mouse1: Protocol: "SysMouse" Doesn't work. Only change. The differences that I can see between them is that the ioctl() calls return different information (just more generic for sysmouse), so it likely has to do with code that branches based on that information. http://leaf.dragonflybsd.org/mailarchive/kernel/2006-02/msg00006.html Looks like a fix was found. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Andrew Muhametshin Do you still experience this issue with newer soft ? Please check the status of your issue. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-input-mouse/issues/6. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.