On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
On Monday 22 February 2010 17:52:25 Chris Hedley wrote:
On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
Hi,
What is printed to dmesg when you enable debugging?
sysctl hw.usb.ums.debug=15
Is the attached information okay? I tried it twice, first after a switch
using the KVM (where the mouse didn't work) and second when unplugging the
receiver and plugging it back in. Both traces are identical except for
the sc=0xf... etc bit.
Do you want me to get the boot-time messages too, or is this okay for now?
What is printed when you move the mouse?
When I disconnect & reconnect it, I get lots of stuff like this as the
pointer moves about the screen:
ums_intr_callback: sc=0xffffff00015ae800 actlen=8
ums_intr_callback: data = 00 00 00 00 ff ff 00 00
ums_intr_callback: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback: sc=0xffffff00015ae800 actlen=8
ums_intr_callback: data = 00 00 00 00 fc ff 00 00
ums_intr_callback: x:0 y:4 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback: sc=0xffffff00015ae800 actlen=8
ums_intr_callback: data = 00 00 ec ff d5 ff 00 00
ums_intr_callback: x:-20 y:43 z:0 t:0 w:0 buttons:0x00000000
But nothing at all when it hasn't initialised properly.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
