On 08/12/15 12:32, Hans Petter Selasky wrote:
On 08/12/15 11:31, Anders Bolt-Evensen wrote:


When you don't see any activity, can you issue a reset of the touchpad:

usbconfig -d X.Y reset

while "usbdump" is running on the same device?

--HPS

Sure. 
usbconfig -d 0.3 reset results in the following output from the usbdump
command:

Can you run:

sysctl hw.usb.ums.debug=15

Then re-run the "usbconfig -d X.Y reset" and send resulting dmesg?

--HPS

Hi,

The issue might be that the BIOS is re-programming the USB device somehow. I see the HID descriptor has support for different modes, and possible the device is not re-setting its internal state upon re-enumeration. You can try:

usbconfig -d X.Y power_off
usbconfig -d X.Y reset

Maybe if you disable USB legacy support in the BIOS it will work.

BTW: The log you sent appears to be from a USB keyboard only device and not a USB mouse!

Also try:

kldload ums

Can you send output from:

usbconfig show_ifdrv

usbconfig dump_device_desc dump_curr_config_desc

When it works and when it doesn't work?

Output from dmesg is also appreciated.

--HPS
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to