Why do USB timeouts happen: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT ?
I have a USB Hantek PC-oscilloscope. Several seconds after the PulseView program begins to upload firmware into it, the device disconnects: ugen8.5: at usbus8 ugen8.5: at usbus8 (disconnected) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_TIMEOUT ugen8.5: at usbus8 (disconnected) I don't believe that the device is broken, it is brand new. Why would the device access, no mater what it is, cause the timeout and disconnect? Yuri ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/175731: detaching USB keyboard freezes other USB keyboards
On 01/31/2013 08:20, Norbert Koch wrote: It seems to be an X11 only problem. My xorg.conf is auto-generated. Hald is running. In xorg.conf I see Driver kbd. Does X11 bypass kbdmux? This is the same problem I was seeing. Xorg assumes there is only one keyboard. When hald notifies xorg that some keyboard is detached, xorg unloads the keyboard driver. Even though xorg didn't open that particular device (normally kbdmux is the keyboard driver) You can see it in xorg.log See this PR https://bugs.freedesktop.org/show_bug.cgi?id=60069 If you disable hald in xorg.conf, you may experience another issue with disconnectable devices: https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ 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
Re: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Yuri ___ 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
Re: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:10, Hans Petter Selasky wrote: On Wednesday 30 January 2013 09:56:21 Yuri wrote: On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Hi, I see what is going on now. Your keyboard is endpoint 0x81 and no events are reported here. Instead those key events are part of the mouse protocol, 0x82, and it is currently not supported that a mouse can generate key-events. However, it might be that those keys are mapped into some axis. Try to enable hw.usb.ums.debug=15 instead. Can you also try to dump the other HID descriptors: usbconfig -d X.Y do_request 0x81 0x06 0x2200 0 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 2 0x100 Here is what is printed from the keyboard click: ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 27 00 00 00 00 ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 00 00 00 00 00 Here are the other HID descriptors: # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = 0x05 0x01 0x09 0x06 0xa1 0x01 0x05 0x08 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x91 0x02 0x95 0x05 0x91 0x01 0x05 0x07 0x1a 0xe0 0x00 0x2a 0xe7 0x00 0x95 0x08 0x81 0x02 0x75 0x08 0x95 0x01 0x81 0x01 0x19 0x00 0x2a 0x91 0x00 0x26 0xff 0x00 0x95 0x06 0x81 0x00 0xc0)%u*u* # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1a 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x05 0x95 0x05 0x75 0x01 0x15 0x00 0x25 0x01 0x81 0x02 0x75 0x03 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x95 0x02 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xa1 0x02 0x85 0x12 0x09 0x48 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x85 0x1a 0x09 0x38 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xc0 0xa1 0x02 0x85 0x12 0x09 0x48 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x35 0x00 0x45 0x00 0x75 0x04 0xb1 0x01 0x85 0x1a 0x05 0x0c 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x0a 0x38 0x02 0x81 0x06 0xc0 0xc0 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1f 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0x85 0x17 0x06 0x00 0xff 0x0a 0x06 0xff 0x0a 0x0f 0xff 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0x95 0x02 0x75 0x02 0xb1 0x02 0x0a 0x04 0xff 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x01 0xb1 0x02 0x75 0x03 0xb1 0x01 0xc0 0x85 0x16 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x06 0x00 0xff 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 0x26 0xff 0x00)u%u01uHu%5E85EuHu%5E5Euu88u%5Eu5Euu*u* # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 2 0x100 REQUEST = 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x20 0x06 0x00 0xff 0x15 0x00 0x26 0xff 0x00 0x75 0x08 0x95 0x12 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x21 0x06 0x00 0xff 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x10 0x1a 0x10 0xfa 0x2a 0x1f 0xfa 0x81 0x02 0x85 0x28 0x06 0x00 0xff 0x1a 0x10 0xfa 0x2a 0x1f 0xfa 0xb1 0x02 0x85 0x22 0x06 0x00 0xff 0x15 0x00 0x26 0xff 0x00 0x75 0x08 0x95 0x1a 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x23 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x24 0x06 0x00 0xff 0x95 0x1f 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x25 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x26 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x27 0x06 0x00 0xff 0x0a 0x0a 0xfa 0x81 0x02 0x85 0x14 0x06 0x00 0xff 0x15 0x00 0x25 0x03 0x75 0x02 0x95 0x01 0x0a 0x01 0xfe 0x81 0x02 0x75 0x06 0x81 0x01 0x85 0x04 0x06 0x00 0xff 0x15 0x00 0x25 0x03 0x75 0x02 0x95 0x01 0x0a 0x01 0xfe 0x81 0x02 0x75 0x06 0x81 0x01 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x07 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x05 0x07 0x19 0x00 0x29 0xff 0x75 0x08 0x26 0xff 0x00 0x81 0x00 0x81 0x01 0x06 0x00 0xff 0x0a 0x03 0xfe 0x0a 0x04 0xfe 0x75 0x01 0x95 0x02 0x25 0x01 0x81 0x02 0x0a 0x05 0xff 0x95 0x01 0x75 0x05 0x25 0x1f 0x81 0x02 0x75 0x01 0x81 0x01 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 u!%u*(*u#$%'%uu%uu*u)uu%u%u* ___ 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
Re: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:25, Hans Petter Selasky wrote: usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x300 # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 1 0x300 REQUEST = 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1a 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x05 0x95 0x05 0x75 0x01 0x15 0x00 0x25 0x01 0x81 0x02 0x75 0x03 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x95 0x02 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xa1 0x02 0x85 0x12 0x09 0x48 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x85 0x1a 0x09 0x38 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xc0 0xa1 0x02 0x85 0x12 0x09 0x48 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x35 0x00 0x45 0x00 0x75 0x04 0xb1 0x01 0x85 0x1a 0x05 0x0c 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x0a 0x38 0x02 0x81 0x06 0xc0 0xc0 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1f 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0x85 0x17 0x06 0x00 0xff 0x0a 0x06 0xff 0x0a 0x0f 0xff 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0x95 0x02 0x75 0x02 0xb1 0x02 0x0a 0x04 0xff 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x01 0xb1 0x02 0x75 0x03 0xb1 0x01 0xc0 0x85 0x16 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x06 0x00 0xff 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 0x26 0xff 0x00 0x75 0x08 0x81 0x00 0x81 0x01 0x85 0x1c 0x06 0x00 0xff 0x0a 0x25 0xff 0x15 0x00 0x25 0x04 0x75 0x08 0x95 0x01 0x81 0x02 0x0a 0x26 0xff 0x75 0x10 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x81 0x02 0xc0)u%u01uHu%5E85EuHu%5E5Euu88u%5Eu5Euu*u*u%%uu' ___ 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
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
I found the cause of this problem. Due to the bug in Xorg it unloads the keyboard driver when it gets signal from hald that keyboard is disconnected, even though there is still another keyboard that is hooked up to kbdmux. Looks like Xorg code assumes that there can only be one keyboard and isn't aware of kbdmux. This was when hald is enabled (by default), and ServerFlags section in xorg.conf looked like this: Section ServerFlags Option AllowEmptyInput yes EndSection When I changed this section to this: Section ServerFlags Option AutoAddDevices False EndSection keyboard doesn't get affected, but mouse disappears for good when unplugged and plugged back, since (I guess) Xorg ignores ums0 device errors. I filed the following PRs with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=60069 https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ 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
Re: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:40, Hans Petter Selasky wrote: Work for you: RID=22 (0x16) is the one you are receiving. This is a microsoft specific extension to the HID class. I don't have time to look at this right now, but if you can get documentation for this HID usage, then we could map it to a mouse button at least. Else press all the buttons on your mouse while recording USB trace information. Then reverse engineer the values, make a nice table and I can implement it for you in the ums driver. So the keyboard signal comes to the mouse endpoint. One possible solution is to have a quirk in ums driver that would post the event to the corresponding ukbd instance. Since these are really the keyboard signals. Microsoft makes some of the best mice today (IMO, based on the research of what's available from all vendors). That's why I want FreeBSD to support their mice better. I will do some research, also will try to partially reverse-engineer the protocol. It might be something in their protocol that makes keyboard signals be piped into the mouse pipe. Yuri ___ 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
Re: Why my USB keyboard doesn't generate scancodes?
On 01/27/2013 00:54, Hans Petter Selasky wrote: Maybe you can dump the HID descriptor of this device? Setting quirk UQ_KBD_BOOTPROTO didn't change the behavior. # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = 0x05 0x01 0x09 0x06 0xa1 0x01 0x05 0x08 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x91 0x02 0x95 0x05 0x91 0x01 0x05 0x07 0x1a 0xe0 0x00 0x2a 0xe7 0x00 0x95 0x08 0x81 0x02 0x75 0x08 0x95 0x01 0x81 0x01 0x19 0x00 0x2a 0x91 0x00 0x26 0xff 0x00 0x95 0x06 0x81 0x00 0xc0)%u*u* Yuri ___ 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
Why my USB keyboard doesn't generate scancodes?
I have this mouse that also defines the usb keyboad with 2 buttons.
Below is USB log I get when I press one of the buttons. Looks like
scancode is 0x27 (another one being 0x28).
However, ukbd device doesn't return anything. ukbd0 (and atkbd0) are
connected to kbdmux0. Signals from atkbd0 are visible through DTrace on
kbdmux0. But USB keyboard signals just disappear.
While troubleshooting, I set DTrace probes on all ukbd_... functions in
kernel. See below what is called when keyboard is datached (first), and
attached again (later). No functions are called in ukbd module when the
keyboard buttons are pressed.
What could be wrong?
9.1-STABLE amd64
Yuri
---usbdump log---
# usbdump -i usbus1 -s 160 -v
17:40:16.961544 usbus1.2
DONE-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=8,IVAL=1,ERR=0
frame[0] READ 5 bytes
16 00 00 27 00 -- -- -- -- -- -- -- -- -- -- -- |...'. |
17:40:16.961551 usbus1.2 SUBM-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=1
frame[0] READ 10 bytes
17:40:17.113540 usbus1.2
DONE-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=8,IVAL=1,ERR=0
frame[0] READ 5 bytes
16 00 00 00 00 -- -- -- -- -- -- -- -- -- -- -- |. |
17:40:17.113545 usbus1.2 SUBM-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=1
frame[0] READ 10 bytes
---DTrace log---
dtrace: script './dt-ukbd.d' matched 35 probes
CPU IDFUNCTION:NAME
...detaching...
6 14388 ukbd_intr_callback:entry
5 14372ukbd_detach:entry
5 14370 ukbd_disable:entry
5 14396 ukbd_clear_state:entry
7 14388 ukbd_intr_callback:entry
...attaching ...
0 14366 ukbd_probe:entry
0 14401ukbd_attach:entry
0 14396 ukbd_clear_state:entry
0 14364 ukbd_parse_hid:entry
0 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b42
0 14396 ukbd_clear_state:entry
0 14374ukbd_enable:entry
0 14396 ukbd_clear_state:entry
0 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b07
0 14396 ukbd_clear_state:entry
0 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b14
0 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b42
0 14374ukbd_enable:entry
0 14366 ukbd_probe:entry
0 14366 ukbd_probe:entry
2 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b42
2 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b42
2 14397 ukbd_ioctl:entry ukbd_ioctl: cmd=20044b42
5 14366 ukbd_probe:entry
5 14403 ukbd_set_leds_callback:entry
7 14403 ukbd_set_leds_callback:entry
7 14388 ukbd_intr_callback:entry
7 14403 ukbd_set_leds_callback:entry
7 14403 ukbd_set_leds_callback:entry
7 14403 ukbd_set_leds_callback:entry
7 14403 ukbd_set_leds_callback:entry
---DTrace script---
#!/usr/sbin/dtrace -s
::ukbd_any_key_pressed:entry {}
::ukbd_start_timer:entry {}
::ukbd_put_key:entry {}
::ukbd_do_poll:entry {}
::ukbd_get_key:entry {}
::ukbd_interrupt:entry {}
::ukbd_event_keyinput:entry {}
::ukbd_timeout:entry {}
/*::ukbd_apple_fn:entry {}
::ukbd_apple_swap:entry {}*/
::ukbd_intr_callback:entry {}
::ukbd_set_leds_callback:entry {}
::ukbd_probe:entry {}
::ukbd_parse_hid:entry {}
::ukbd_attach:entry {}
::ukbd_detach:entry {}
::ukbd_resume:entry {}
::ukbd_configure:entry {}
::ukbd__probe:entry {}
::ukbd_init:entry {}
::ukbd_test_if:entry {}
::ukbd_term:entry {}
::ukbd_intr:entry {}
::ukbd_lock:entry {}
::ukbd_enable:entry {}
::ukbd_disable:entry {}
::ukbd_check:entry {}
/*::ukbd_check_char_locked:entry {}*/
::ukbd_check_char:entry {}
::ukbd_read:entry {}
/*::ukbd_read_char_locked:entry {}*/
::ukbd_read_char:entry {}
/*::ukbd_ioctl_locked:entry {}*/
::ukbd_ioctl:entry {printf(ukbd_ioctl: cmd=%x,arg1);}
::ukbd_clear_state:entry {}
::ukbd_get_state:entry {}
::ukbd_set_state:entry {}
::ukbd_poll:entry {}
/*::ukbd_set_leds:entry {}*/
/*::ukbd_set_typematic:entry {}*/
::ukbd_key2scan:entry {}
::ukbd_driver_load:entry {}
___
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
Re: Why my USB keyboard doesn't generate scancodes?
Sorry, forgot an important bit: ugen1.2: Microsoft Nano Transceiver v1.0 Microsoft at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0054 bNumInterfaces = 0x0003 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x no string Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x39, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0008 bInterval = 0x0004 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x no string Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x27, 0x08 | 0x01 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x000a bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x no string Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x3f, 0x08 | 0x01 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0020 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x ___ 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
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
On 01/14/2013 23:12, Hans Petter Selasky wrote:
The problem is that the Nano transceiver also provides a keyboard, which is
set as default.
See /etc/devd.conf and:
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/ukbd0;
};
detach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/kbd0;
};
Which probably should be updated.
These directives look quite crude.
device-name ukbd0; should probably be device-name ukbd[0-9]+;
Also why kbd0 is taken as new default after ukbd disconnect?
Replacing kbd0 with kbd1 there didn't fix the problem though as I expected.
Following /etc/rc.d/sysconsit looks like in my case /etc/rc.d/syscons
setkeyboard /dev/ukbd0 doesn't do anything, since kbdcontrol -k ${kbd}
${kbddev} is only called when there is no kbdmux.
Here is another problem:
In the presence of mouse, this command doesn't show ukbd0 attached to
kbdmux:
# kbdcontrol -i /dev/ttyv0
kbd1:
kbdmux0, type:AT 101/102 (2)
Also it looks like the keyboard provided by mouse isn't working. Mouse
keyboard only has 2 buttons, by default Page-Up and Page-Down and these
events are never triggered.
Trying to attach it manually, following kbdcontrol(1), I get this error:
# kbdcontrol -a ukbd0 /dev/kbdmux0
su: /dev/kbdmux0: Device busy
Who is normally supposed to connect ukbd to kbdmux?
Yuri
___
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
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
On 01/14/2013 23:12, Hans Petter Selasky wrote:
The problem is that the Nano transceiver also provides a keyboard, which is
set as default.
See /etc/devd.conf and:
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/ukbd0;
};
detach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/kbd0;
};
Which probably should be updated.
Actually, disabling the above entries altogether also doesn't solve the
problem.
However, stopping devd daemon causes the problem to disappear. Even
though devd.conf even didn't have those ukbd directives.
I ran devd with -D flag, but log only shows the execution of 'syscons'
and 'moused' when the mouse is plugged/unplugged.
Removing moused entries also doesn't solve the problem.
So devd does something that triggers this problem, even though it
doesn't execute any commands. Looks like a mystery.
Yuri
___
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
Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
I have Microsoft USB Explorer Touch mouse. It works fine, but when I plug out its (wireless) USB dongle, keyboard also stops working. Plugging the dongle back in enables the keyboard again. Plugging in some other USB mouse instead doesn't make keyboard work again. There were two keyboard devices defined before this mouse was first plugged in: kbd0 at atkbd0 and kbd1 at kbdmux0, see messages below. This mouse defines the new keyboard device kbd2 at ukbd0. When the dongle is plugged out, these two items (kbd2 at ukbd0) disappear from /dev, leaving all the same devices that existed before. Except keyboard becomes disfunctional. What could be a problem with this USB mouse? Looks like it interacts with the previous setup and leaves something modified when plugged out. Yuri PS: This of course isn't the major usability issue since, when plugged in, everything works. Nevertheless, I can't plug it out without losing the keyboard. ---messages (kbd related during boot)-- kbd1 at kbdmux0 ...skipped... atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ---messages (plug out)--- Jan 14 14:30:59 eagle kernel: ugen1.2: Microsoft at usbus1 (disconnected) Jan 14 14:30:59 eagle kernel: ukbd0: at uhub1, port 1, addr 2 (disconnected) Jan 14 14:30:59 eagle kernel: ums0: at uhub1, port 1, addr 2 (disconnected) Jan 14 14:30:59 eagle kernel: uhid0: at uhub1, port 1, addr 2 (disconnected) ---messages (plug in)--- Jan 14 14:31:09 eagle kernel: ugen1.2: Microsoft at usbus1 Jan 14 14:31:09 eagle kernel: ukbd0: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1 Jan 14 14:31:09 eagle kernel: kbd2 at ukbd0 Jan 14 14:31:09 eagle kernel: ums0: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1 Jan 14 14:31:09 eagle kernel: ums0: 5 buttons and [XYZT] coordinates ID=26 Jan 14 14:31:09 eagle kernel: ums0: 0 buttons and [T] coordinates ID=0 Jan 14 14:31:09 eagle kernel: uhid0: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1 $ ls -l /dev/*kbd* crw--- 1 root wheel0, 57 Jan 4 11:50 /dev/atkbd0 lrwxr-xr-x 1 root wheel 6 Jan 4 11:50 /dev/kbd0 - atkbd0 lrwxr-xr-x 1 root wheel 7 Jan 4 11:50 /dev/kbd1 - kbdmux0 lrwxr-xr-x 1 root wheel 5 Jan 14 14:38 /dev/kbd2 - ukbd0 crw--- 1 root wheel0, 13 Jan 4 11:50 /dev/kbdmux0 crw--- 1 root wheel0, 182 Jan 14 14:38 /dev/ukbd0 ___ 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
Should all known devices be added to usbdevs?
I see that many storage and network devices aren't in usbdevs. graphics/libgphoto2 package actually has more complete list. But it looks like they only process PTP/MTP storage interfaces. Should we add to usbdevs missing devices from the list in graphics/libgphoto2? For ex. I am looking at smartphone, it has MTP USB storage interface recognized by gphoto2, but FreeBSD also recognizes the umodem device, and this smartphone isn't in the list. Yuri ___ 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
Is there a facility to send USB requests through the script?
I am looking at the USB webcam device that doesn't work on BSD (stalls). I have the log of linux USB communcation to the same device, where it works fine. Is there a way I can send the particular requests to USB device through script, as a debugging facility, so that I can easily change what is sent, compare what is received to what I have in log, and make changes? I know that kernel also sends some requests to the USB device, and I would like to disable this in such case. Yuri ___ 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
usbdump(8) question
I am trying to use usbdump(8) on one webcam, but the produced, log causes some questions. 1. Why -s 1024 option doesn't show actual data even though SLEN for packets is non-zero? 2. When I run webcamd, first 4 lines of log (with the error) quickly appear. Webcamd exits quickly, in 0.035s, but usbdump after 1-2 secs shows the rest of the log. Why is this significant delay? Why the first 4 lines aren't delayed? Yuri --- usbdump log --- # usbdump -i usbus3 -s 1024 12:32:19.151777 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:19.155753 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=28,IVAL=0,ERR=0 12:32:19.155772 usbus3.2 SUBM-CTRL-EP=,SPD=HIGH,NFR=2,SLEN=36,IVAL=0 12:32:19.159264 usbus3.2 DONE-CTRL-EP=,SPD=HIGH,NFR=2,SLEN=0,IVAL=0,ERR=STALLED ... at this point webcamd process is ended, but the following lines appear after 1-2 secs. Why? ... 12:32:20.998845 usbus3.2 SUBM-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=8,IVAL=0 12:32:20.999006 usbus3.2 DONE-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=0,IVAL=0,ERR=0 12:32:20.999019 usbus3.2 SUBM-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=0,IVAL=0 12:32:20.999129 usbus3.2 DONE-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=0,IVAL=0,ERR=0 12:32:21.011833 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.013626 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=20,IVAL=0,ERR=0 12:32:21.014846 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.016000 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 12:32:21.016014 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.017375 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 12:32:21.017391 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.019250 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 12:32:21.019264 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.021625 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=20,IVAL=0,ERR=0 12:32:21.021644 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.028876 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=12,IVAL=0,ERR=0 12:32:21.028891 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 12:32:21.108758 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=1024,IVAL=0,ERR=0 12:32:21.108773 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=0,IVAL=0 12:32:21.191506 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=1024,IVAL=0,ERR=0 12:32:21.191522 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=0,IVAL=0 12:32:21.273003 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=1024,IVAL=0,ERR=0 12:32:21.273018 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=0,IVAL=0 12:32:21.286251 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=196,IVAL=0,ERR=0 12:32:21.286269 usbus3.2 SUBM-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=8,IVAL=0 12:32:21.286374 usbus3.2 DONE-CTRL-EP=,SPD=HIGH,NFR=1,SLEN=0,IVAL=0,ERR=0 ___ 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
Re: usb/77184: [umass] [panic] kernel panic on USB device disconnect, even if not detected
Now after rereading the original post I realize that I am testing the different condition but for quite similar situation. F828 camera isn't available any more and is probably supported by now, so it's really difficult to retest the original condition now. But my previous post indicates there is the problem in USB stack in the similar scenario, thiugh without unsupported device. Before I saw panic in the case of disconnect of the mounted disk. Yuri ___ 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
Re: usb/77184: [umass] [panic] kernel panic on USB device disconnect, even if not detected
Crash is gone. But there is something wrong. I did the following steps: 1. plug the camera into USB and mount it 2. unplug the camera without unmounting it -- no crash, looks good. 3. mount still exists. that's ok. 4. umount /mnt/camera -- command says: Device Busy, this looks reasonable. 5. umount -f /mnt/camera -- mount is gone. 6. repeated steps 1...4 on step 4 umount command without -f flag doesn't complain about device busy any more. This is really strange and this means that device disconnect or unmount hasn't been done cleanly and something is different now. So this issue has to be cleared -- outcome of steps 1..5 should always be the same. Yuri ___ 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
Re: usb/77184: [umass] [panic] kernel panic on USB device disconnect, even if not detected
The following reply was made to PR usb/77184; it has been noted by GNATS. From: Yuri y...@rawbw.com To: Cc: bug-follo...@freebsd.org Subject: Re: usb/77184: [umass] [panic] kernel panic on USB device disconnect, even if not detected Date: Wed, 14 Jul 2010 13:15:22 -0700 Crash is gone. But there is something wrong. I did the following steps: 1. plug the camera into USB and mount it 2. unplug the camera without unmounting it -- no crash, looks good. 3. mount still exists. that's ok. 4. umount /mnt/camera -- command says: Device Busy, this looks reasonable. 5. umount -f /mnt/camera -- mount is gone. 6. repeated steps 1...4 on step 4 umount command without -f flag doesn't complain about device busy any more. This is really strange and this means that device disconnect or unmount hasn't been done cleanly and something is different now. So this issue has to be cleared -- outcome of steps 1..5 should always be the same. Now after rereading the original post I realize that I am testing the different condition but for quite similar situation. F828 camera isn't available any more and is probably supported by now, so it's really difficult to retest the original condition now. But my previous post indicates there is the problem in USB stack in the similar scenario, thiugh without unsupported device. Before I saw panic in the case of disconnect of the mounted disk. Yuri ___ 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
weird USB keyboard behavior with new USB stack
Hi, I'm testing new USB stack as part of -CURRENT. My USB keyboard occasionally locks up (and I need to re-plug it), sends wrong modifiers keys, etc. which didn't happen with old USB stack. Are there any settings/options which I can use to debug this problem further? Info from usbconfig: ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: IrDA/USB Bridge Sigmatel Inc at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.5: Wireless Battery Free Optical Mouse A4Tech at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.3: product 0x2050 Cypress Semiconductor at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: product 0x004c KYE Systems at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON from dmesg: ukbd0: KYE Systems product 0x004c, class 0/0, rev 1.10/1.01, addr 4 on usbus0 TIA, Yuri ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/118741: [umass] [patch] Support for Nikon D300 digital camera (as USB mass storage device)
The following reply was made to PR usb/118741; it has been noted by GNATS. From: Yuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/118741: [umass] [patch] Support for Nikon D300 digital camera (as USB mass storage device) Date: Wed, 30 Apr 2008 10:37:40 -0700 Would anybody please check this patch in? Thanks in advance, Yuri ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
usb/118741: [PATCH] Support for Nikon D300 digital camera (as USB mass storage device)
Number: 118741
Category: usb
Synopsis: [PATCH] Support for Nikon D300 digital camera (as USB mass
storage device)
Confidential: no
Severity: non-critical
Priority: medium
Responsible:freebsd-usb
State: open
Quarter:
Keywords:
Date-Required:
Class: change-request
Submitter-Id: current-users
Arrival-Date: Sun Dec 16 07:20:01 UTC 2007
Closed-Date:
Last-Modified:
Originator: Yuri
Release:7.0-BETA4
Organization:
n/a
Environment:
Description:
Support for new Nikon high end digital camera D300.
This patch makes the camera to be identified as umassN device and can be
mounted as /dev/da0s1.
In my opinion this patch should be applied to 7.0 and 6.X
There is a caveat though: D300 has USB mode selection in menu: either [MTP/PTP]
(default) or [Mass Storage]. In [MTP/PTP] mode camera is designed to work with
proprietary Nikon software for Windows only and is not a mass storage device.
So in order for it to work with FreeBSD [Mass Storage] mode should first be
selected in menu.
Thanks,
Yuri
How-To-Repeat:
Fix:
Patch attached with submission follows:
diff -u sys/dev/usb.orig/umass.c sys/dev/usb/umass.c
--- sys/dev/usb.orig/umass.c2007-07-04 22:26:08.0 -0700
+++ sys/dev/usb/umass.c 2007-12-15 23:07:48.0 -0800
@@ -568,6 +568,10 @@
UMASS_PROTO_ATAPI,
NO_INQUIRY
},
+ { USB_VENDOR_NIKON, USB_PRODUCT_NIKON_D300, RID_WILDCARD,
+ UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
+ NO_QUIRKS
+ },
{ USB_VENDOR_OLYMPUS, USB_PRODUCT_OLYMPUS_C1, RID_WILDCARD,
UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
WRONG_CSWSIG
diff -u sys/dev/usb.orig/usbdevs sys/dev/usb/usbdevs
--- sys/dev/usb.orig/usbdevs2007-12-05 19:10:36.0 -0800
+++ sys/dev/usb/usbdevs 2007-12-15 23:07:32.0 -0800
@@ -1754,6 +1754,7 @@
/* Nikon products */
product NIKON E990 0x0102 Digital Camera E990
product NIKON LS40 0x4000 CoolScan LS40 ED
+product NIKON D300 0x041a Digital Camera D300
/* NovaTech Products */
product NOVATECH NV902 0x9020 NovaTech NV-902W
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
