Wireless ImtelliMouse problem

2007-10-16 Thread Vadim Jukov
Hello all.

Due to different reasons I bought MS Wireless Desktop (keyboard + mouse).
While keyboard works fine, mouse produces headache. I'll skip simptoms,
going straight to information gathered.

I tried to used new mouse both alone and with Logitech UltraX Optical
in pair. Logitech works OK in both cases (it suffers from, err,
hardware problems:), which were the reasons to buy new mouse).
IntelliMouse going wrong in both cases too.

Snip from dmesg (full version later):

uhidev0 at uhub1 port 1 configuration 1 interface 0 Logitech USB-PS/2 Optical 
Mouse rev 2.00/20.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 4 buttons and Z dir.
wsmouse0 at ums0 mux 0
uhidev1 at uhub1 port 2 configuration 1 interface 0 Microsoft Microsoft 
Wireless Optical Desktop\M-. 2.10 rev 2.00/0.41 addr 3
uhidev1: iclass 3/1
ukbd0 at uhidev1: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev2 at uhub1 port 2 configuration 1 interface 1 Microsoft Microsoft 
Wireless Optical Desktop\M-. 2.10 rev 2.00/0.41 addr 3
uhidev2: iclass 3/0
uhidev2: 23 report ids
uhid0 at uhidev2 reportid 1: input=7, output=0, feature=0
uhid1 at uhidev2 reportid 2: input=2, output=0, feature=0
uhid2 at uhidev2 reportid 3: input=1, output=0, feature=0
uhid3 at uhidev2 reportid 4: input=1, output=0, feature=0
uhid4 at uhidev2 reportid 5: input=3, output=0, feature=0
uhid5 at uhidev2 reportid 6: input=0, output=0, feature=1
ums1 at uhidev2 reportid 17: 5 buttons and Z dir.
wsmouse1 at ums1 mux 0
uhid6 at uhidev2 reportid 18: input=0, output=0, feature=1
uhid7 at uhidev2 reportid 19: input=1, output=0, feature=0
uhid8 at uhidev2 reportid 20: input=1, output=0, feature=0
uhid9 at uhidev2 reportid 21: input=3, output=0, feature=0
uhid10 at uhidev2 reportid 23: input=0, output=0, feature=1

xev(1) output for mouse clicks are different: while Logitech
produces single mouse down and mouse release events as
it should, IntelliMouse produces mouse down and mouse up
on each move too, which yields many strange things. I can send
exact logs (enter window, mouse move, mouse down, mouse move,
mouse up, mouse move, exit window) if anyone is interested in
them.

One more thing: xmseconfig(1) tells me that X server doesn't
handle Protocol option in xorg.conf, always setting it to
microsoft instead of wsmouse (or, at least, intellimouse,
which is compatible, instead of microsoft). After reverting
protocol to something more closer to reality, some bugs
disappear, but xev(1) still says there are mouse down and
mouse release events on each move with pressed button.

Even more: when I try to move objects like scrollbars by
dragging using any mouse button, they began to move up, like
mouse wheel tell is being scrolled.

But mouse wheel doesn't work. At all. It worked many days,
and some days ago it sopped working. I thought that was due
to hardware problems (some juice over it) with Logitech
mouse, and I went to buy new mouse... And now I'm stuck.

It's more likely OpenBSD-related problem because all is OK on
a fresh (Mandriva 2008.0) Linux distribution which I pulled in.

Today I'm going to test this mouse on another OpenBSD machine,
which is CURRENT too. If I'll find something more than I'll
post it here, of course.

Thank you for any tips.

-- 
  Best wishes,
Vadim Jukov


OpenBSD 4.2-current (GENERIC) #431: Sun Oct 14 22:00:04 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Sempron(tm) Processor 2600+ (AuthenticAMD 686-class, 128KB L2 
cache) 1.61 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3
cpu0: AMD erratum 89 present, BIOS upgrade may be required
real mem  = 1072459776 (1022MB)
avail mem = 1029238784 (981MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/28/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS 
rev. 2.3 @ 0xf0530 (55 entries)
bios0: vendor American Megatrends Inc. version 1008.013 date 
06/28/2005
bios0: ASUSTeK Computer Inc. K8V-MX
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf58a0/224 (12 entries)
pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT8237 ISA rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xd000 0xcd000/0x2000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 VIA K8M800 Host rev 0x00
pchb1 at pci0 dev 0 function 1 VIA K8M800 Host rev 0x00
pchb2 at pci0 dev 0 function 2 VIA K8M800 Host rev 0x00
pchb3 at pci0 dev 0 function 3 VIA K8M800 Host rev 0x00
pchb4 at pci0 dev 0 function 4 VIA K8M800 Host rev 0x00
pchb5 at pci0 dev 0 function 7 VIA K8M800 Host rev 0x00
ppb0 at pci0 dev 1 function 0 VIA K8HTB AGP rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 ATI Radeon 9600 Pro rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: 

Re: Wireless ImtelliMouse problem

2007-10-16 Thread Vadim Jukov
P QPPP1QP5P=P8P8 PQ Wednesday 17 October 2007 Vadim Jukov
P=P0P?P8QP0P;(a):
 Even more: when I try to move objects like scrollbars by
 dragging using any mouse button, they began to move up, like
 mouse wheel tell is being scrolled.

Sorry, I'm bit asleep now, so said something wrong. Scrollbars works OK
after using xmseconfig(1), but when I, for example, try to select text
in the terminal client, it begins to move selection upper and upper. No
crashes still (yet?).

And xmseconfig(1) says following right after startup (when mouse first
time enters it's window):

Error in Tcl Script

Error: invalid command name tk::ScreenChanged

A copy of stack trace has been saved in the file
/tmp/X.err

If you think this error has not been reported before blah-blah-blah

X differs on each run, of course. Stack trace consists following:

invalid command name tk::ScreenChanged
while executing
tk::ScreenChanged :0.0
(changing screen in event binding)


--
  Best wishes,
Vadim Jukov