On Wednesday, March 14, 2012 15:19:16 Chris Turner wrote: > This is probably overkill. Also, moused has an '-l' flag for this > > For reference - alot of the mouse documentation is somewhat 'cruft' > from the MS/DOS PC-AT era and various nonstandard serial port drivers - > for the most part things just 'work' for 'modern' (e.g. Pentium+/win95+ > era) ps2/USB mice in my experience. > > However, some KVM's do 'interesting' things with port data, so you'll > probably want to post a dmesg to see if anything obvious stands out, > and try running from the console with -f and -d flags will probably > be of use here as well - for example - a test session for me > shows 'Z' axix activity in the 'dz' field here: > > $ grep 'dz.*1' /tmp/mouse-log > moused: activity : buttons 0x00000000 dx 0 dy 0 dz -1 > moused: activity : buttons 0x00000000 dx 0 dy 0 dz 1
I ran it in debug mode and saw no activity at all when I turned the wheel. Varying the level, I got three-byte packets at levels 0 and 2 and eight-byte packets padded with zeros at level 1. > I misadvised earlier in this thread r.e. the '-z' flag and apologize - > at the time I was not using moused & have switched back for testing here - > > my setup (moused, ps2 mouse, scroll OK) is as follows: > > $ dmesg |egrep '(psm|ums)' > psm0: current command byte:0065 > psm0.atkbdc0.acpi0.nexus0.root0 > psm0: <PS/2 Mouse> [tentative] irq 12 on atkbdc0 > psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons > psm0: config:00000000, flags:00000008, packet size:4 > psm0: syncmask:08, syncbits:00 > psm0: <PS/2 Mouse> [attached!] irq 12 on atkbdc0 I got just this: psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 The mouse is a Compaq MO42KC. Pierre -- Don't buy a French car in Holland. It may be a citroen.